APPENDIX B

Troubleshooting




This section discusses some of the possible errors that you may encounter while installing or using SMCS on either the server or client side. TABLE B-1 and TABLE B-2 list the errors and possible solutions for the server and client.



SMCS Server- Side Troubleshooting

Following is a listing of possible server errors and their resolutions.

TABLE  B-1   Sun Messaging Connectivity Services Server Admin Errors
User Errors
Resolution

The user could not be authenticated with SMCS

User or password is incorrect

SMCS has not yet been initialized

/opt/SUNWmail/sbin/smcs initialize

The directory is not configured properly to work with SMCS

SMCS initial directory items missing

The directory server does not appear to be running

/etc/initd/slapd start

There are not enough available licenses for the channel

restricted number of channels

There are no licenses for the channel

/var/opt/SUNWmail/gtw/lic/license.dat

A method invocation error occurred

Some java component is missing

Could not read or write the PMDF configuration file

/etc/opt/SUNWmail/imta/imta.cnf

The SMCS shell process encountered an error starting up

can not run /opt/SUNWmail/sbin/smcs

The SMCS shell process was interrupted

/opt/SUNWmail/sbin/smcs was killed

The SMCS shell process encounterd an error

problem with /opt/SUNWmail/sbin/smcs

The SMCS internal router channel is not configured

Dir problem/Previous setup had failed

The SMCS internal router channel server is <channel_name>

Dir problem/Previous setup had failed

The <channel_name> channel server is {1}

running normally

starting up

stopped due to an error

stopping

not responding

not running

invalid for unknown reasons

The <channel_name> channel shared directory {1}

does not exist

has insufficient permissions

The <channel_name> channel transport server is {1}

running normally

starting up

stopped due to an error

stopping

not responding

not running

invalid for unknown reasons

The <channel_name> channel lan gateway client is {1}

running normally

starting up

stopped due to an error

stopping

not responding

not running

invalid for unknown reasons

The <channel_name> channel NJE transport server is {1}

running normally

starting up

stopped due to an error

stopping

not responding

not running

invalid for unknown reasons

The <channel_name> channel is not configured

Directory problem/Previous config failed

The <channel_name> channel has not been started

The <channel_name> channel NJE transport has not been started

The SMCS administraive logging mechanism failed

Login to MMAD failed as admin

Following is a listing of possible server errors and their resolutions.


cc:Mail Client Troubleshooting

TABLE  B-2   Sun Messaging Connectivity Services cc:Mail Client Errors
User Errors
Resolution

Error spawning EXPORT.EXE config

Invalid program directory in config

You are asked to enter: Post office direct

Invalid data directory in config

You are asked to enter: Post office or user name:

Invalid post office name in config. This could be in dirsync or client run

connect failed: Connection timed out

Invalid SPX address

server is not running

server socket or server name doe not match

what is on the server

fopen(P:\CCMAIL\OUT\heartb.eat): No such file or directory

Path to file share is incorrect

Access rights are incorrect

bad parameter: exportschedule = "Hourly at 30"

Invalid export schedule time

bad parameter: importschedule = "Hourly at 30"

Invalid import schedule time

Import/Export error 5: Post office path is not correct

Invalid remote address in dirsync config




Copyright © 1999 Sun Microsystems, Inc. All Rights Reserved.