AnsweredAssumed Answered

Error Publishing GPService with name exceeding 19 characters

Question asked by ryarbrough on Nov 15, 2017
Latest reply on Nov 15, 2017 by ryarbrough

Like • Show 0 Likes0
Comment • 6

I'm having a problem publishing a geoprocessing service in which the name exceeds 19 characters on ArcGIS Server 10.5.1. The service will stage and I can build a service definition just fine, but when I go to publish it, if the name of the service exceeds 19 characters, the publish will fail. I've gone as far as to strip everything out of the python script the service calls, it still fails if the name is too long.

I have instances that I've upgraded from 10.3.1 to 10.5.1 and the service in question exists on an upgraded 10.5.1 server, but I cannot create the service on a fresh install.

Any ideas on how to make this work would be greatly appreciated!

Thanks!

JQuinn-esristaff

Nov 15, 2017 2:41 PM

Correct Answer

Are the config-store and directories paths in a similar path, (for example C:\arcgisserver\... on each site)? What are the errors in the logs? Is this on Windows or Linux? Since this points to some type of pathing issue, you can try to run ProcMon and filter for any file activity from the Server processes to determine if there's a write or read failure due to the path being too long, as the limit is 260 characters.

See the reply in context

No one else had this question

Outcomes

rastrauch

Nov 15, 2017 2:33 PM

I'm not sure if this will help as a work around, but there is a tool that will let you copy a service from one AGS install to another. It doesn't work for all types, but I have got it to work for many of our services (although just trial runs/tests, not production yet). I also modified our copy of the tool for our purposes.

Check out this thread if interested.

Move/Copy Services to another Service Directory

Actions

ryarbrough Nov 15, 2017 2:38 PM

I should note that I have a workaround of sorts, I can publish the service with a shorter name then rename it. The process seems to fail, but it looks like the service gets renamed. I'd rather not have to do this, but I don't see any setting anywhere that would limit the name size of a service.

Actions

JQuinn-esristaff

Nov 15, 2017 2:41 PM

3 people found this helpful

Actions

ryarbrough @ JQuinn-esristaff on Nov 15, 2017 2:52 PM

Hmm... the config stores are in similar paths, but the new one is a bit longer. I'll try this with a shorter path name on the config store directory.

Thanks for the suggestion!

Actions

ryarbrough @ JQuinn-esristaff on Nov 15, 2017 3:07 PM

I rebuilt the site using a shorter path name, and publishing the service worked just fine with the longer name.

Thanks again!

1 person found this helpful

Actions

ryarbrough Nov 15, 2017 2:50 PM

It seems I spoke too soon... I can rename the service, but after it is renamed, it won't start. I get the following error message when trying to start the service.

Service failed to start
TestLongServiceNameFail.GPServer: java.rmi.UnmarshalException: Error unmarshaling return header; nested exception is: java.net.SocketException: Connection reset

Actions

6 Replies

rastrauch Nov 15, 2017 2:33 PM
Mark Correct
Correct Answer
I'm not sure if this will help as a work around, but there is a tool that will let you copy a service from one AGS install to another. It doesn't work for all types, but I have got it to work for many of our services (although just trial runs/tests, not production yet). I also modified our copy of the tool for our purposes.

Check out this thread if interested.
Move/Copy Services to another Service Directory
Like • Show 0 Likes0
Actions
ryarbrough Nov 15, 2017 2:38 PM
Mark Correct
Correct Answer
I should note that I have a workaround of sorts, I can publish the service with a shorter name then rename it. The process seems to fail, but it looks like the service gets renamed. I'd rather not have to do this, but I don't see any setting anywhere that would limit the name size of a service.
Like • Show 0 Likes0
Actions
JQuinn-esristaff Nov 15, 2017 2:41 PM
Unmark Correct
Correct Answer
Are the config-store and directories paths in a similar path, (for example C:\arcgisserver\... on each site)? What are the errors in the logs? Is this on Windows or Linux? Since this points to some type of pathing issue, you can try to run ProcMon and filter for any file activity from the Server processes to determine if there's a write or read failure due to the path being too long, as the limit is 260 characters.
3 people found this helpful
Like • Show 0 Likes0
Actions
- ryarbrough @ JQuinn-esristaff on Nov 15, 2017 2:52 PM
  Mark Correct
  Correct Answer
  Hmm... the config stores are in similar paths, but the new one is a bit longer. I'll try this with a shorter path name on the config store directory.
  
  Thanks for the suggestion!
  Like • Show 0 Likes0
  Actions
- ryarbrough @ JQuinn-esristaff on Nov 15, 2017 3:07 PM
  Mark Correct
  Correct Answer
  I rebuilt the site using a shorter path name, and publishing the service worked just fine with the longer name.
  
  Thanks again!
  1 person found this helpful
  Like • Show 1 Like1
  Actions
ryarbrough Nov 15, 2017 2:50 PM
Mark Correct
Correct Answer
It seems I spoke too soon... I can rename the service, but after it is renamed, it won't start. I get the following error message when trying to start the service.

Service failed to start
TestLongServiceNameFail.GPServer: java.rmi.UnmarshalException: Error unmarshaling return header; nested exception is: java.net.SocketException: Connection reset
Like • Show 0 Likes0
Actions

GeoNet

The Esri Community

Error Publishing GPService with name exceeding 19 characters

Outcomes

Related Content

Recommended Content