Troubleshoot database servers

ArcMap 10.3
|
Other versions

10.6

10.5

10.4

10.3

Below you will find suggestions for solutions to the problems you may encounter when using the servers of
databases or geodatabases stored on database servers.

Error!: Unable to connect to the data server...SQLServer does not exist

or access to it is denied.
Possible reasons why you received the error message:

The SQL Server Express instance has not been started, the remote client will not be able to locate it.
Your user account has never been set up on the database server or it has been deleted, you will not be able to
Do not interrogate him or connect with him.
Remote clients must have a way to communicate with the SQL Server Express instance. If the network protocol is not
defined, this communication method is not defined, and a connection cannot be established with the instance on a network.
The SQL Server Browser service provides information about the installed SQL Server instances on the computer when it receives a
Client request for SQLServer. If SQL Browser is disabled, the client will not receive the names and ports used for each.
SQL Server instance installed and, therefore, will not be able to locate the instance.

Solution!

First of all, check that the database server you are trying to connect to is started. If so,
confirm that you have the necessary permissions to remotely access this database server. If the database server
data has started and you have the right to connect to it and query it, the network protocols are probably not
activated on the database server. To reactivate the network protocols, proceed as follows:

1. Open the Microsoft SQL Server Configuration Manager. To access it, point to Start > All Programs >
Microsoft SQL Server > Configuration Tools.
2. Expand SQLServer Network Configuration in the tree and click on the protocols for your SQLServer instance.
3. Right-click on the protocol TCP/IP and select Enable.

The following warning message appears:

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 cannot connect to the server
database from the remote client, the SQL Server Browser service is probably stopped. To start the SQL Server service
Browser:

1. Open the Microsoft SQL Server Configuration Manager.

2.Click on the SQLServer icon to display the SQLServer Browser service.
3. If the state of SQL Server Browser is suspended, right-click on it and select Resume. If the state of SQL Server
Browser is stopped, right-click on it and select Start.

.kci lc-g
h
te
d
iw
o
h
u
e
n
rya
b
lse
d
ip
a
rn
d
e
sH
e
li to
p
e
rP
re
p
tcxo
n
sm
ie
n
u
lo
p
tA
l
On SQL Server Browser, the startup mode of this service is set to Disabled. To remedy this, proceed as follows:

1. Right-click on SQL Server Browser and select Properties.

2. Click on the Service tab.
3. Click on Boot Mode.
4. In the dropdown menu, choose Automatic or Manual. If you set the startup mode to Automatic, the service
SQL Server Browser starts automatically when you restart the computer.
5. Click OK.

Now, if you right-click on the SQL Server Browser service, the Start option should be available.
 Error!: Unable to generate the SSPI context
Possible reason why you received the error message:

You will mainly encounter this error if you are working on a laptop and logging in using your credentials.
domain, but you are not actually connecting to your domain. This can happen if you are connected to a client site (by
opposition to your own network) or if you use your mobile phone while you are not connected to any network, such as when you
work on the field. The report is linked to the TCP/IP network protocol and Windows authentication. You can also
visit the Microsoft website to consult an article from the knowledge base regarding the resolution of the error message
Unable to generate the contextSSPI.

Solution!

Establish your connection to the database server on your local computer (by adding a database server) by
using the TCP/IP loopback 127.0.0.1 instead of the domain name; for example: 127.0.0.1\sqlexpress.

This will work as long as the database server (the SQLServerExpress instance) is installed on your local computer.

Error: The connection to the database failed - Underlying DBMS error

(Microsoft OLEDB Provider for SQL Server. Failed to open the session for
The user '<username>' is not associated with a SQL connection.
Approved server.)
Possible reason why you received the error message:

When the environment variables SDEUSER or SDEPASSWORD are set in the system environment variables, they are
prioritize your Windows ID when connecting to a geodatabase. Do not set these variables if you need to
connect from this computer to a geodatabase located on a database server or if you need to connect to
an enterprise geodatabase via operating system authentication.

Solution!

Make sure you do not have the environment variables SDEUSER or SDEPASSWORD set on the client computer that is
connected.

Error: Adding the class of entities failed. <class name of the entities> is in
loading mode only and therefore cannot be added as a layer.
Possible reason why you received the error message:

m
tp
h
o
e
rite
,a
b
sh
e
g
o
d
a
to
tn
t i t im
tp
o
rie
m
ttp
w
o
h
u
e
n
a
ty0
,te
tsie
ta
sa
d
te
o
fzisn
d
e
xi a
l ip
a
h
te
stfI
fails and the dataset risks getting stuck in input/output (I/O) loading mode only. If you recalculate
the spatial index, or remove the spatial index and recreate it, the feature class must switch back to normal input/output (I/O) mode, and you
you should then be able to use it.

Solution!

Recalculate or recreate the spatial index on the entity class.

1. In the catalog tree, right-click on the entity class that is in read-only mode,
Select Properties, then click on the Index tab of the Entity Class Properties dialog.
2. If your entity class uses geometry SQL Server for storing geometries, you can recalculate the index. In the
In the Indexspatial section, click on Recalculate. If your entity class uses a binary data type or the geography type.
SQLServer for storing geometries, recreate the spatial index. Click on Delete then on Create in the Index section.
spatial to recreate the spatial index.
3. Click OK to close the Entity Class Properties dialog.

Bad login user

Possible reason why you received the error message:

You probably tried to connect to a geodatabase on a database server using a username.

and a password authenticated by the database.
Solution!

Connections to geodatabases on database servers use only Windows authenticated credentials.

Therefore, select the operating system authentication option in the dialog box Connect to a database.
spatial data and connect with a valid Windows ID.

Error! Connection failed. The connection comes from an untrusted domain and
cannot be used with Windows authentication.
Possible reasons why you received the error message:

You tried to connect to a geodatabase on a remote database server while you were connected.
to a local Windows account.
You tried to connect to a geodatabase on a database server with a domain account that does not
has not been added to the database server.

Solution!

Log in to the client computer with a domain account that a server administrator has added to the database server.
data.

Error: Connection was attempted with an older version of SQL Server client
communications software that is not compatible with the SQL Server database server
Attempt to connect with a version of the clientSQL communication software
PreviousserverthatisnotcompatiblewiththeSQLdatabaseserver
Server
Reason for receiving the error message:

No supported version of Microsoft SQL Native Client is installed on the client computer from which you are
connect to the geodatabase.

Solution!

Install a version of the SQL NativeClient application on the client computer that is compatible with the version of SQL Server Express you have.
use.