Error: “Packaging succeeded, but publishing failed”,

16617
59
Jump to solution
10-05-2014 01:21 PM
JamalNUMAN
Legendary Contributor

Error: “Packaging succeeded, but publishing failed”,

I couldn’t figure out why I’m getting the error below

“Packaging succeeded, but publishing failed”

Clip_685.jpg

What might be the issue here?

Thank you

Best

Jamal

----------------------------------------
Jamal Numan
Geomolg Geoportal for Spatial Information
Ramallah, West Bank, Palestine
59 Replies
GeoffreyWest
Occasional Contributor III

Have you attempted to overwrite previously published map services or just create a service definition and publish from server manager?    

JamalNUMAN
Legendary Contributor

Many thanks Geoffrey for the prompt help,

Good hint. I have overwrite a previously map service and it works fine.

What might this indicate for?

Clip_799.jpg

----------------------------------------
Jamal Numan
Geomolg Geoportal for Spatial Information
Ramallah, West Bank, Palestine
0 Kudos
GeoffreyWest
Occasional Contributor III

Not sure what this indicates unfortunately, with overwriting you maintain previous service definitions. Id stop all services temporarily and see if you can publish a new map service. If so id say you have too many processes consuming resources.

JamalNUMAN
Legendary Contributor

Thank you very much Geoffrey and Sapna for the massive help,

I have reduced the number of published services (they are less than 30 services at the moment) with 1 and 2 as min\max number of instances per machine (pooling). The problem disappears.

By the way, is there a way to count the number of ArcSoc.exe? I assume that there counts shouldn’t exceed 80 as the number of cores of our server is 16 (16*5 = 80).

I’ll be reporting if the error appears in the future

Clip_103.jpg

Clip_104.jpg

----------------------------------------
Jamal Numan
Geomolg Geoportal for Spatial Information
Ramallah, West Bank, Palestine
0 Kudos
StevenGraf1
Occasional Contributor III

If you need all those services running, I would add another machine to your server and create a cluster out of it and publish to that new cluster.

JamalNUMAN
Legendary Contributor

Thanks Steven,

I can live at the moment with having many layers in one service to avoid exceeding the hardware limit of the 16 cores (16*4 =64 ArcSoc.exe)

----------------------------------------
Jamal Numan
Geomolg Geoportal for Spatial Information
Ramallah, West Bank, Palestine
0 Kudos
847396730
Occasional Contributor III

I have a similar problem.  I try to publish a service, I get the same error shown above.  Then I stop a service already running on that server, and I can successfully publish the service, then restart the one I sacrificed. 

My question is: how much memory do the publishing tools require?  Is there a mechanism which AGServer uses to detect available memory and then "decide" whether or not to publish, and if so, what is the threshold?

JamalNUMAN
Legendary Contributor

Very interesting question Marianne. Hope experts can provide an answer.

----------------------------------------
Jamal Numan
Geomolg Geoportal for Spatial Information
Ramallah, West Bank, Palestine
0 Kudos
sapnas
by
Occasional Contributor III

you can check the hardware resources usage from windows task manager of the server. You can also install splunk on the server which monitors and keeps the history of memory/CPU usage

JamalNUMAN
Legendary Contributor

Many thanks Sapna,

Our query here is related to the quota of the ArcSoc.exe on the server as this is controlled by the number of cores available on it.

Notes:

1 core on the server can take up to 5 ArcSoc.exe.

1 core needs 3 GB

Now:

Each map service will consume a number of ArcSoc.exe. The total consumed ArcSoc.exe shouldn’t exceed #of cores*5

There should be an indicator to show the remaining number of ArcSoc.exe before proceeding in publishing.

What do you think?

----------------------------------------
Jamal Numan
Geomolg Geoportal for Spatial Information
Ramallah, West Bank, Palestine
0 Kudos