We have a virtual machine with Postgres & ArcSDE 10 SP1 installed. Another virtual machine with ArcGIS Server 10 with SP1 installed on Linux.When I restart the server, sometimes not all services start back up. I can manually start these services by clicking on them in arcgismanager. It is not the same services each time that don't start up. When services don't start, I get the following log file errors for each service:

1. How many services are you running?2. Can you describe the specs of the machine you're running AGS on?3. Are you using optimized or classic map services?4. How complex are these services?5. How many SOC instances do you have dedicated to these services?6. Are these services operating in high isolation or low isolation?7. Pooled or non-pooled?

When started, ArcGIS Server will attempt to start each service individually until no further memory can be allocated to an ArcSOC.exe process. At that point, you'll start to see errors like those you're reporting. I'd be curious to know how many arcsoc.exe processes are running, and to know the amount of RAM they are consuming. I've never seen a single SOC host, no matter the amount of memory there is on the machine, instantiate more than ~120 SOC instances.

3. Are you using optimized or classic map services?About half are .msd and half are .mxd

4. How complex are these services?Most are simple. One is a feature access. One or two MXD�??s reference a lot of data and have unique symbolization.

5. How many SOC instances do you have dedicated to these services?The SOM and SOC are both installed on the above virtual machine.

6. Are these services operating in high isolation or low isolation?All are high isolation

7. Pooled or non-pooled?All are pooled.

You mentioned �?? �??I'd be curious to know how many arcsoc.exe processes are running, and to know the amount of RAM they are consuming.�?� I�??m not sure how to check this. I would be happy to if you could explain how. Thanks for your help. I�??d love to hear any recommendations of better settings/configurations.

You might want to look at increasing the startup timeout in the service .cfg files. The problem could be that starting the 25 services takes too much time so some of the services actually timeout before they get a chance to instantiate.

I'm getting a similar error when trying to start my 15th Geoprocessing Service:

Configuration OEMS/<GPServiceName>.GPServer can not be started.Configuration OEMS/<GPServiceName>.GPServerJobScheduler can not be started.Server Object instance creation failed on machine <MachineName>. Error: 0x80080005 (Server execution failed)

If I Stop one of the first 14 services then I can Start the one that I previously could not start.

This is in a Test/Dev environment using ArcGIS 10.0 SP2 on Windows XP SP3 so I think will "evaporate" as an issue when we move to a Production server. However, I'm keen to hear whether the limit I'm hitting sounds like it is to be expected by answering Randall's questions from above.

1. How many services are you running? 14 - 15th won't start2. Can you describe the specs of the machine you're running AGS on? i7 CPU 870 @ 2.93 GHz, 3.42 GB RAM3. Are you using optimized or classic map services? Geoprocessing Services published using A Map4. How complex are these services? Based on Python scripts that open several MXDs, apply some logic using ArcPy and then save a couple of maps and sometimes a report into a single PDF5. How many SOC instances do you have dedicated to these services? Have not specified this but with 14 GP Services there are 43 x ArcSOC.exe running6. Are these services operating in high isolation or low isolation? High Isolation - was only option I had to choose from7. Pooled or non-pooled? Pooled