topic Re: GP Service Publishing Issue in ArcGIS Enterprise Questions

GP Service Publishing Issue

BrianLeroux — Wed, 31 Dec 2014 14:32:38 GMT

Hi,

When publishing a gp service to AGS server 10.22 my service is failing. It works fine in desktop though. It seems to be a problem with the sde connection file during the service creation. Taking a look at the script uploaded to the v101 folder, the esri added variable looks like g_ESRI_variable_1 = u'..\\..\\..\\..\\..\\GP_Tools\\Database Connections\\GISDB_ArcSDE(PROD Server).sde'. This path is modified from my original path to the sde connection file on my computer Shakemap_Table_Target = os.path.join("D:\\agsResources\\GP_Tools\\GISDB_ArcSDE(PROD Server).sde", "ArcSDE.dbo.EQ_SHAKEMAPS").

When debugging, AGS Server can't seem to locate that location. Is this a known bug or something I may be doing incorrectly? I am able to fix the problems by modifying the script to point that variable at a server location where i store the sde files but I am wondering if there is a better solution. I have to jump through hoops to get access to the uploaded scripts on my production server and would rather this just work when publishing.

i appreciate any and all feedback.

Re: GP Service Publishing Issue

Anonymous User — Wed, 31 Dec 2014 15:41:22 GMT

Can you publish map services successfully, or do they fail also?

Re: GP Service Publishing Issue

BrianLeroux — Wed, 31 Dec 2014 16:12:45 GMT

I have no issues publishing map services that reference my sde DB. The sde DB is registered properly.

Re: GP Service Publishing Issue

Anonymous User — Wed, 31 Dec 2014 16:42:09 GMT

So the issue is exclusively with gp services. What does the AGS Server log say?

Re: GP Service Publishing Issue

BrianLeroux — Wed, 31 Dec 2014 16:56:07 GMT

Yes just gp services. Pretty basic error messages.

"FieldMappings: Error in adding table to field mappings Failed to execute (ImportWildfirePerim). Failed to execute (ImportWildfirePerim)"

As I mentioned before, it is all about the sde location variable created when publishing the service. If i hard code a correct location the service will run without issue.

Re: GP Service Publishing Issue

DavidColey — Wed, 31 Dec 2014 17:03:44 GMT

Brian,

I'm sure you are already doing something similar, I always use sde connection files that are located in my data-store directory and never have issues publishing any type of services. In our distributed 3-machine 2-cluster architecture, our server directories are located on a file share server, where our domain arcgisserver account has read write access to all directories and all directories are shared.

Under the data-store folder, we use a DataConnections folder to house sde connection files and file geodatabases, and a GpServices folder to store toolboxes and python scripts. This way I am always sure everything is in a shared location. I also use UNC paths and although server complains about that at analzye, I never then have any issues with a resource not being read or otherwise not being available to Server.....hope this helps

David

Re: GP Service Publishing Issue

BrianLeroux — Fri, 02 Jan 2015 14:00:56 GMT

David,

We only have 1 live gis server and the directories are all local on that server. I am not allowed to access anything on that server but the server domain account has R/W access to eveything. So that means I have to publish using a local sde connection file. With map services this is fine as the DB is registered with the server.

I will have to talk to the server team to see if we can look at a similar apprach to yours where we would move the directories to a shared location.

One question I have for you is, when you publish a GP service with your UNC path to an sde file, does esri add variables that point to the location of these files? I am curious is they are recognizingnetwork paths and not changing those but if it sees a local path it makes modifications. Looking at the variables created it seems like the sde file should be copied with the service but that is not happening.

Thanks!

Re: GP Service Publishing Issue

DavidColey — Mon, 05 Jan 2015 16:19:44 GMT

Does esri add variables? I'm not sure what you mean

Re: GP Service Publishing Issue

BrianLeroux — Mon, 05 Jan 2015 16:32:35 GMT

They do. If i look at the python scripts after publishing I notice new variables g_ESRI_variable_1, g_ESRI_variable_2, etc... You would notice them at the top of the python script.

Here is what I wrote in my initial post describing my issue.

"Taking a look at the script uploaded to the v101 folder, the esri added variable looks like g_ESRI_variable_1 = u'..\\..\\..\\..\\..\\GP_Tools\\Database Connections\\GISDB_ArcSDE(PROD Server).sde'. This path is modified from my original path to the sde connection file on my computer Shakemap_Table_Target = os.path.join("D:\\agsResources\\GP_Tools\\GISDB_ArcSDE(PROD Server).sde", "ArcSDE.dbo.EQ_SHAKEMAPS")."

Re: GP Service Publishing Issue

DavidColey — Mon, 05 Jan 2015 17:35:53 GMT

Now I understand. I'll check and reply back

Re: GP Service Publishing Issue

DavidColey — Mon, 05 Jan 2015 18:42:23 GMT

Yes, arcgis is adding variables to the python scripts created in the v101 folder of the arcgisinput system directory, as well as copying over sde connection file(s) as is the case with the data extract tool.

So to me it makes sense that arcgis would have to add a string variable to handle the change in location of the source connection. To me, if you are still having issues, then look to a share or security issue with your domain account and associated directories.

Re: GP Service Publishing Issue

BrianLeroux — Mon, 05 Jan 2015 20:20:35 GMT

David - Thank you for the information. Knowing that the connection files are being copied over for you gives me some direction for troubleshooting.

Re: GP Service Publishing Issue

SørenNielsen — Mon, 16 Jan 2017 12:06:49 GMT

Hello Brian.

Now I am sitting in the same situation as you did two years ago. I would like to know if you found a better solution than changing the path in the published script.

Søren