last week, we have a kind of distributed installation of a ArcGIS Server 9.3, one SOM and a SOC on another machine, no load balance or anything else, the installation was very smooth,
the SOC machine was intstalled and added to as a host to the SOM and it was publishing like a charm, then we thought of adding the a local SOC to the server, and then the fun started !!
after adding the Local SOC we are getting this message "SERVICE_NAME.MapServer.cfg could not be started" message made us feel really happy, solving this prblems took nearly 1.5 days experimneting and re-installation but WE "FORGOT" to take a look at the log.
the next day early in the morning, i took a look at the log and it was something silly,
when you install a SOC only on a standalone machine, it doesn't create "arcgisserver" that has the "arcgiscache" , "arcgisoutput" , and "arcgisjobs" and i really dunno why, it should create all this by it self and set the permissions
we created these things manually and everyhing worked after that, well i hope that this might be usefull to everyone else, something to note that if you ever get this message then the folder might be there but with a permission set to ArcGISSOC local account.
i hope it helps others
4 comments:
Thanks, it worked out for me!
in this case if you created server directories on the second soc machine and added the local soc account to it ,where are your vritual directories pointing to, this folder which you created now or the one which were created first.
in the scenario explained by you , where do the virtual directories are pointing two.machine 2 where soc was installed or machine one where the directories already existed.
in the scenario explained by you, where are the virtual directories pointing towards...
Post a Comment