Unable to Start a Published GeoData Service (AGS 10.5)

442
2
Jump to solution
12-13-2018 07:10 AM
WilCowart1
New Contributor III

 I've created a GDB in our Enterprise SDE, populated the GDB with some data, and shared the GDB as a Geodata Service to AGS 10.5,

that part works fine but when I try to start the Geodata service in ArcGIS Server Manager (v10.5), I get this error:

Service failed to start

####.####_Hydrants.GeoDataServer:
####-MAPSERVER.####.LOCAL
Unable to init from SERVER=####-sqlserver;INSTANCE="DSID=d50ff2c1-b4c4-4af8-8a03-bdf40378ed11";DBCLIENT=sqlserver;DB_CONNECTION_PROPERTIES=####-sqlserver;DATABASE=####;VERSION=dbo.DEFAULT;AUTHENTICATION_MODE=OSA.

in the Log, I get these error code(s):

Failed to construct instance of service '####/####.GeoDataServer'. Unable to init from SERVER=####-########;INSTANCE="DSID=d50ff2c1-b4c4-4af8-8a03-bdf40378ed11";DBCLIENT=sqlserver;DB_CONNECTION_PROPERTIES=####-#########;DATABASE=Milledgeville;VERSION=dbo.DEFAULT;AUTHENTICATION_MODE=OSA.

Failed to initialize server object '#############': 0x800501b2: Unable to init from SERVER=####-######;INSTANCE="DSID=d50ff2c1-b4c4-4af8-8a03-bdf40378ed11";DBCLIENT=sqlserver;DB_CONNECTION_PROPERTIES=####-#####;DATABASE=######;VERSION=dbo.DEFAULT;AUTHENTICATION_MODE=OSA.

Unable to init from %s

Anyone else seen anything like this?

0 Kudos
1 Solution

Accepted Solutions
WilCowart1
New Contributor III

From our troubleshooting, we discovered that the service editor either did not recognize the input being used for the server parameter or it was being read as null. As a workaround, we established a new server connection in the service editor. As we discussed, this issue seems to occur sporadically and the quickest way to fix it is to establish new server connections when it occurs. 

I have some additional notes from a call with Esri support, but so far I've been able to publish services that work as intended using this workaround

View solution in original post

0 Kudos
2 Replies
BrendanBladdick3
Esri Contributor

My customer is having this issue right now and I have found the following information:

https://community.esri.com/thread/15421

https://community.esri.com/thread/4071

https://community.esri.com/thread/51989
-"This problem came for both Mapserver and Geodataserver. I made a mistake of not giving the GDB/MXD file the required 
permissions (ie ArcGISSOC & ArcGISSOM)."

https://community.esri.com/thread/9870

I have yet to figure this out though my customer has a local account running ArcGIS Server and catalog is on a different machine

In my experience when the ArcGIS Server account is a local account you need to create identical accounts on other machines that the server needs access to those files on those machines

My customer has a UNC file share to the sde connection with the ArcGIS Server local account granted full access HOWEVER we are accessing this connection through a UNC on the client machine (different machine than ArcGIS Server) where there is no identical ArcGIS Server account for the client machine

I am thinking that we need to create an identical account on the client machine and grant security (and sharing?) to that file with this newly created identical account

I think it should work then however I have not tested this

I will reply when we do solve this

Any help would be appreciated

0 Kudos
WilCowart1
New Contributor III

From our troubleshooting, we discovered that the service editor either did not recognize the input being used for the server parameter or it was being read as null. As a workaround, we established a new server connection in the service editor. As we discussed, this issue seems to occur sporadically and the quickest way to fix it is to establish new server connections when it occurs. 

I have some additional notes from a call with Esri support, but so far I've been able to publish services that work as intended using this workaround

0 Kudos