Select to view content in your preferred language

Unable to start sdeservice for Sql Server 2008 R2 Standard, Windows, 10.1

3453
8
03-20-2013 06:23 PM
KarenRobine
Frequent Contributor
Having problems getting an SDE Service started.
Environment:  Windows 7 64 bit, Sql Server 2008 R2 Standard, Desktop/Enterprise SDE on 10.1
Did the following steps:
1.  Ran Create Enterprise Geodatabase:
     Platform: SQL_SERVER
     Instance:  <Machine Name> (but the instance is MSSQLSERVER so could this be wrong)
     Database Administrator sa
     Database Administrator Password: <DB password>
     Checked SDE owned
     Geodatabase Administrator sde
    Geodatabase Admin Password: sde (but I later changed this to sde123
   Auth File: C:\Program Files\ESRI\License 10.1\sysgen\keycodes

2. Made sure I have esri_sde set in my services.sde and my system services location.

3. Created the service:
   sdeservice -o create -d sqlserver -p sde123
4. Registered the service:
   sdeservice -o register -d sqlserver -r admin_database -v G
5. Listed the service
6. Connected to the database using ArcCatalog with my user sde. No problem. Also connected using Sql Server Management studio. No problem.
7. Started the service.

Errror (always the same error):
IDBInitialize::Initialize Failed
init_DB DB_instance_open_as_dba: -93
DBMS error code: 18456
Microsoft SQL Server Native Client 10.0: Login failed for user 'sde'.

Checked out:  http://forums.arcgis.com/threads/73608-ArcGIS-10.1-Starting-�??ArcSDE-Service-(esri_sde)-quot-stops!...
And another document on that error.
0 Kudos
8 Replies
VinceAngelo
Esri Esteemed Contributor
First of all, it is unwise to use a trivial password for the ArcSDE administrator
account.  You should always use a "strong" password (8-12 characters, mix
of upper and lower case, with numerals and special characters).  The 'sde'
login password should be closely held, since anyone who knows it can corrupt
the entire instance (accidentally or otherwise). The fact that SQL-Server now
enforces password strength just reinforces the need for good database security
practice.

Manual service creation can be a challenge.  As in the thread you referenced,
including the output of 'sdeservice -o list' (as text) is critical for us to identify
possible problems.

- V
0 Kudos
KarenRobine
Frequent Contributor
Yes. Understood. This is just a Dev server.
Here's the SDE Commands to generate the Service, including the List command. See attached image.

But one curious thing too is that when I did the "Create Enterprise Geodatabase" command, I could not run it with the Instance set to <Instance_Name> or the instance set to <Machine_Name>\<Instance_Name>
It ONLY ran if the Instance was set to <Machine_Name>
0 Kudos
VinceAngelo
Esri Esteemed Contributor
As you remarked at the top of the thread, the Datasource is incorrect.
Here's what I have on mine:

C:\Temp>sdeservice -o list -i sql101

SDE service Information
--------------------------------------------------------------------
RDBMS:                  SQLServer
Name:                   ArcSde Service(sql101)
SDEHOME:                C:\Esri\arc101sql64-sp1\ArcSDE\sqlexe
Datasource:             laptopnaname
Admin_database:         sql101
Version:                10.1
Status:                 SERVICE_STOPPED


- V
0 Kudos
KarenRobine
Frequent Contributor
It didn't work by putting in the name of the computer for the -d option either. 2 pictures attached. The first one are the commands to create and register the service. The second one shows the service being listed as well as starting the service.
Other ideas?

From giomng_esri_sde.log:
Fri Mar 22 12:36:41 2013 - ****** Spatial Database I/O Manager ******
Fri Mar 22 12:36:41 2013 - SDE System Startup Initiated . . .
Fri Mar 22 12:36:41 2013 - Validated System Paths.
Fri Mar 22 12:36:41 2013 - SDE IOMGR going into background . . .

From sde_esri_sde.log:
-------------------------------------------------------
ArcSDE 10.1  for SQL Server Build 679 Thu Apr  5 11:43:21  2012
-------------------------------------------------------
IDBInitialize::Initialize Failed
init_DB DB_instance_open_as_dba: -93
DBMS error code: 18456
Microsoft SQL Server Native Client 10.0: Login failed for user 'sde'.

positive the login is correct.
0 Kudos
VinceAngelo
Esri Esteemed Contributor
The correct parameter for specifying the datasource is '-s'.

C:\Temp>sdeservice

ESRI ArcSDE System Service Utility  Fri Mar 22 14:55:40 2013
-------------------------------------------------------------------------
sdeservice -o create     -d <ORACLE,SID|SQLSERVER,SQLSERVERINSTANCE|
                             DB2,DB2INSTANCE|POSTGRESQL,PGINSTANCE|
                             INFORMIX|COVERAGES>
                         -p <SDE_DBA_Password> [-s <datasource>]
                        [-i <service>] [-u <service_user>] [-n]
                        [-H <sde_directory>] [-P <service_user_password>]


Please use text, not images, to document the commands you issue and the
command-line response.  400 characters are worth far more than 43kb.

Since the 18456 error is documented as being password-related, please
try changing the 'sde' login password to a strong password, then using
that to create and modify the service before attempting a NET START.

Is the database on the server where you're attemping to start the service,
or is it remote?

- V
0 Kudos
KarenRobine
Frequent Contributor
The database/SDE/ArcGIS Server environment is local.

Havent changed the password yet, but did just try it with the -s option. Same error.
0 Kudos
xiannianchen
Deactivated User
Hi,

Have you had the problem solved? I met the exact same issue.

Can you share your precious experience withe me?

Thanks,

Mike


The database/SDE/ArcGIS Server environment is local.

Havent changed the password yet, but did just try it with the -s option. Same error.
0 Kudos
KarenRobine
Frequent Contributor
Nope. Never did solve this.  But since I am able to use Direct Connect to connect, I'm not worrying about this right now.
0 Kudos