Troubleshooting connections to the database server

Troubleshooting connections to the database server
Release 9.3

• Error:

 Cannot connect to this Data Server...SQL Server does not exist or access denied.



Fix: First, be sure the database server to which you are trying to connect is started. If it is, confirm that you have permissions to access this database server remotely.
If the database server is started and you have rights to connect to and query it, the network protocols are probably not enabled on the database server.
To reenable network protocols
1. Open the Microsoft SQL Server Configuration Manager.
This can be accessed from Start > All Programs > Microsoft SQL Server 2005 > Configuration Tools.
2. Expand SQL Server <version> Network Configuration in the tree and click on the Protocols for <your SQL Server instance>.
3. Right-click the TCP/IP protocol and click Enable.
You will receive the following warning message:

Any changes made will be saved; however, they will not take effect until the service is stopped and restarted.



Stop and restart the service.
If the network protocols are enabled and you still can't connect to the database server from the remote client, the SQL Server Browser service is probably stopped.
To start the SQL Server Browser service
1. Open the Microsoft SQL Server Configuration Manager.
2. Click the SQL Server <version> icon to see the SQL Server Browser service.
3. If the state of the SQL Server Browser is paused, right-click it and click Resume. If the state of the SQL Server Browser is stopped, right-click it and click Start.
If all the context menu options except Properties and Help are grayed out when you right-click the SQL Server Browser, your SQL Server Browser start mode is set to Disabled. To change this
1. Right-click the SQL Server Browser and click Properties.
2. Click the Service tab.
3. Click Start Mode.
4. From the pull-down menu, choose either Automatic or Manual. Setting the start mode to Automatic means the SQL Server Browser service will automatically start when you reboot the machine.
5. Click OK.
Now when you right-click the SQL Server Browser service, Start should be an available option.
Possible reasons you received the error message:
• If the SQL Server Express instance has not been started, the remote client will not be able to locate it.
• If your user account was never set up on the database server or your user account was removed from the database server, you won't be able to query or connect to it.
• Remote clients have to have a way to communicate with the SQL Server Express instance. If the network protocol is not set, that method of communication is not set, and there is no way for a connection to be made to the instance over a network.
• The SQL Server Browser service provides information about the SQL Server instances installed on the computer when it receives a request from a SQL Server client. If the SQL Browser is disabled, the client will not receive the names and ports used for each installed SQL Server instance and, therefore, can't find the instance.
• Error:

Cannot Generate SSPI Context



This might be received when attempting to connect to a database server on a laptop that is not connected to the network.
Fix/Workaround: Make your connection to the database server on your local machine (Add Database Server) using the TCP/IP loopback of 127.0.0.1 rather than the domain name; for example:

127.0.0.1\sqlexpress



rather than

domainname\sqlexpress



This will work as long as the database server (the SQL Server Express instance) is installed on your local machine.
Possible reason you received the error message: This error is most commonly encountered if you are working on a laptop and are logging on with your domain credentials, but you are not actually connecting to your domain. This might happen if you are plugged in at a client site (as opposed to your own network) or using your laptop while not connected to a network at all such as working in the field.
It is related to TCP/IP network protocol and Windows authentication.
You could also consult the Microsoft Web site for a knowledge base article on how to troubleshoot the "Cannot generate SSPI context" error message.
• Error:

Failed to add feature class. 
<feature class name> is in load-only mode and cannot be added as a layer in this state.



Fix/Workaround: Recalculate the spatial index grid sizes on the feature class.
1. In the ArcCatalog tree, right-click the feature class that is in load-only mode, click Properties, then click the Indexes tab on the Feature Class Properties dialog box.
2. In the Spatial Index section, click Recalculate.
3. Click OK on the Indexes tab.
Recalculating the spatial index grid size should put the feature class back in normal input/output (I/O) mode, and you should then be able to work with it.
Possible reason you received the error message: If the spatial grid size of a dataset is set to 0, when you try to import it to the ArcSDE geodatabase, it fails during the import and can end up stuck in load-only I/O mode.
• Error:

Failed to connect to database
Underlying DBMS error (Microsoft OLE DB Provider for SQL Server. 
Login failed for user '<username>'. The user is not associated with a trusted SQL Server connection.)



Fix: Make sure you do not have an SDEUSER or SDEPASSWORD environment variable set on the connecting client machine.
Reason you received the error message: When these environment variables are set either in the System Environment Variables or in a dbinit.sde file, they will take precedence over your Windows login when connecting to an ArcSDE geodatabase. Don't set these variables if you are going to connect from that machine to an ArcSDE geodatabase on a database server, or if you are going to connect to an ArcSDE geodatabase licensed with ArcGIS Server Enterprise using OS authentication.
• Problem: Connecting user does not have access to database server administrative tasks, such as New geodatabase, Restore, or Permissions, even though the user has been added to the Windows Administrator group on the server machine.
Fix: Either disable User Access Control (UAC) on the server machine or log in as the administrator user that was added to the ArcSDE database server during postinstallation setup, add the desired user to the database server, and grant him or her Server administrator privileges.
Reason the Windows Administrator could not perform server administrator tasks: Windows Vista and 2008 Server computers have UAC enabled by default. This enforces a tighter security model, which means Windows administrators are not automatically sysadmin in the SQL Server database. Users accustomed to accessing ArcSDE database servers or other instances of SQL Server on a Windows XP or 2003 Server machine may be accustomed to the default behavior on these operating systems, and they may forget to take the steps necessary to add other Server administrator users to the database server.

• If you contact ESRI technical support, they may request you send them error logs to track down a problem. You can capture errors in logs by creating an etc folder in your ArcGIS installation location. For example, if you use the default installation location, c:\Program Files\ArcGIS, create a folder named etc in that location—c:\Program Files\ArcGIS\etc. After you have gotten the information you need from the files or sent copies to technical support, delete the etc folder. The error logs that get created in the etc folder are not truncated and can rapidly grow to many megabytes in size. If you only delete the log files, they will automatically get re-created in the etc folder, so you must delete the entire folder.