ArcSDE Connection Errors
The link here will provide you detailed information about all the errors in ArcSDE and the important one's are given below :
"SDE not running on server"
If a service is your preferred connection method, you may be familiar with this error.
This simply means that the ArcSDE service has not been started (or has stopped). Check the Connection Properties dialog and make sure the correct service name or port number is specified properly. If you’re confident this right, you can check the status of the service one of two ways. For Windows users, open the service panel by right clicking on My Computer and clicking Manage (or click Run>services.msc). If the service is not started, click start and check.
Linux users will prefer to use the SDE command sdeservice -o list. The -i parameter can be used to specify a particular service. If the status returns NOT_STARTED, use the sdemon -o start command to fire it up.
SDE Command Reference
http://help.arcgis.com/en/geodatabase/10.0/admin_cmds/Support_files/whnjs.htm
“Server library could not be loaded”
The Desktop 10 help states that “This message is usually returned when SDEHOME is set incorrectly in your system path variable or as its own environment variable”. This reason is certainly valid and common, but it’s usually the direct connect syntax. Ensure the server name is spelled right and the direct connect string follows the specified standards for you DBMS.
About the path….
A good tip is to check the path variable (in a command prompt type path). Ensure the SDEHOME path is correct and is also the first entry in the series of paths. Also, look at the actual %SDEHOME% variable. Look for extra slashes or backwards slashes. Forward slashes that should be back slashes or vice versa. There is also the ever elusive semicolon.
“Bad user login”
This isn’t always as simple as it seems. However, it usually means the user name or password was entered incorrectly. If you’re sure everything is typed right……..
Check what ArcSDE instance was specified for the connection. If the wrong ArcSDE service, direct connection syntax, or database name was supplied, authentication is occurring against another database or server, which may not have this user in it.
If you are using operating system authentication, be sure the login is recognized by the DBMS.
If you are connecting to a geodatabase in SQL Server, check to see if the complex password policy is set in the SQL Server database. If so, be sure the user’s password meets the requirements of the password policy. If it does not, the user cannot connect to the database.
If a service or direct connection on either OS fails to start manually, it may be a good time to call Esri support. Be sure to note any error messages and navigate to the SDEHOME\etc folder and copy out the log files. If you’re feeling adventurous, look at the log files, note down the errors and look up the return codes. It sometimes takes a little deciphering but the info needed to solve the problem is out there.
Thanks,
NJ
The link here will provide you detailed information about all the errors in ArcSDE and the important one's are given below :
"SDE not running on server"
If a service is your preferred connection method, you may be familiar with this error.
This simply means that the ArcSDE service has not been started (or has stopped). Check the Connection Properties dialog and make sure the correct service name or port number is specified properly. If you’re confident this right, you can check the status of the service one of two ways. For Windows users, open the service panel by right clicking on My Computer and clicking Manage (or click Run>services.msc). If the service is not started, click start and check.
Linux users will prefer to use the SDE command sdeservice -o list. The -i parameter can be used to specify a particular service. If the status returns NOT_STARTED, use the sdemon -o start command to fire it up.
SDE Command Reference
http://help.arcgis.com/en/geodatabase/10.0/admin_cmds/Support_files/whnjs.htm
“Server library could not be loaded”
The Desktop 10 help states that “This message is usually returned when SDEHOME is set incorrectly in your system path variable or as its own environment variable”. This reason is certainly valid and common, but it’s usually the direct connect syntax. Ensure the server name is spelled right and the direct connect string follows the specified standards for you DBMS.
About the path….
A good tip is to check the path variable (in a command prompt type path). Ensure the SDEHOME path is correct and is also the first entry in the series of paths. Also, look at the actual %SDEHOME% variable. Look for extra slashes or backwards slashes. Forward slashes that should be back slashes or vice versa. There is also the ever elusive semicolon.
“Bad user login”
This isn’t always as simple as it seems. However, it usually means the user name or password was entered incorrectly. If you’re sure everything is typed right……..
Check what ArcSDE instance was specified for the connection. If the wrong ArcSDE service, direct connection syntax, or database name was supplied, authentication is occurring against another database or server, which may not have this user in it.
If you are using operating system authentication, be sure the login is recognized by the DBMS.
If you are connecting to a geodatabase in SQL Server, check to see if the complex password policy is set in the SQL Server database. If so, be sure the user’s password meets the requirements of the password policy. If it does not, the user cannot connect to the database.
If a service or direct connection on either OS fails to start manually, it may be a good time to call Esri support. Be sure to note any error messages and navigate to the SDEHOME\etc folder and copy out the log files. If you’re feeling adventurous, look at the log files, note down the errors and look up the return codes. It sometimes takes a little deciphering but the info needed to solve the problem is out there.
Thanks,
NJ
No comments:
Post a Comment