This table shows some log
codes written by the Server Object Manager (SOM), their associated messages, and additional comments that may
be helpful for troubleshooting:
|
Code
|
Meaning
|
Comments
|
| 1000 |
Machine can not be added |
This error may occur if you attempt to add a new server
container machine that does not exist or cannot be found by the
SOM. |
| 1001 |
Machine can not be deleted |
Error logged if removing a machine fails. |
| 1002 |
Configuration name contains illegal characters |
|
| 1003 |
Configuration failed to load |
This error may be logged if the service configuration file is
corrupt or contains invalid values. |
| 1004 |
Configuration can not be added |
Error logged when adding a new service fails, for example, if
you attempt to add a service with the same name and type as an
existing service. |
| 1005 |
Configuration can not be deleted |
Error logged when deleting a service fails, for example, if you
attempt to delete a service that does not exist. |
| 1006 |
Configuration can not be stopped |
Error logged when stopping a service fails, for example, if you
attempt to stop a service that is already stopped. |
| 1007 |
Configuration can not be paused |
Error logged when pausing a service fails, for example, if you
attempt to pause a stopped or already-paused service. |
| 1008 |
Configuration can not be started |
Error logged when starting a service fails, for example, if you
attempt to start an already-started configuration or none of the
minimum instances could be started. |
| 1009 |
Configuration initialization failed |
|
| 1010 |
Type not found |
Error logged when a server object configuration is trying to
use a server object type that is not registered with the server.
The registered types are MapServer, GeocodeServer, GeodataServer,
GlobeServer, and GPServer. |
| 1011 |
Server failed to start |
|
| 1012 |
Server.dat failed to load |
Error logged when the server configuration file, Server.dat,
cannot be read on SOM startup, for example, if the SOM startup
encounters a corrupted Server.dat or if Server.dat contains invalid
values. |
| 1013 |
Server context creation failed |
This error is logged if a client application cannot start using
a service. The error occurs if the server fails to create a server
context for a client, for example, if the client asks the server to
create a context for a server object configuration that does not
exist. |
| 1014 |
Container failed to create. The server process could not be
started because the Server or Container accounts are not configured
properly or they do not match the server machine you are trying to
add to. |
Error logged if the server failed to create a new container
process on one of the server object container machines. This can
happen if the SOM and SOC accounts do not have the same names and
passwords on all machines in your ArcGIS Server configuration. |
| 1015 |
Container failed to create thread. |
Error logged if the server failed to create a new thread in a
container process on one of the server object container
machines. |
| 1016 |
Server Object instance creation failed |
This message may contain more specific error information. |
| 1017 |
Container process has crashed |
Error logged if a container process containing server objects
for the target server object configuration crashes. If this is a
pooled service, the server will create a new process and services
to repopulate the pool. |
| 1018 |
Server Directory path is invalid |
|
| 1019 |
Server Directory can not be added |
You may get this error if you attempt to add a server directory
if one of the same name and type already exists. |
| 1020 |
Server Directory can not be deleted |
You may get this error if you attempt to delete a server
directory that does not exist. |
| 1021 |
Server Directory can not be updated |
You may get this error if you attempt to update a server
directory that does not exist. |
| 1022 |
File not found |
Error logged if the server object types file cannot be found
when the SOM starts. The server object types file is
<install_location>\Server\system\ServerTypes.dat. |
| 1023 |
File ServerTypes.dat is empty. No Types registered. |
Error logged if the server object types file is empty. The
server object types file is
<install_location>\Server\system\ServerTypes.dat. |
| 1024 |
Server does not have write access to a directory |
|
| 1025 |
Configuration name is too long |
|
| 1026 |
Type name is too long |
|
| 1027 |
Failed to create cache for server statistics |
|
| 1028 |
Required tag Name is not found in ServerTypes.dat. |
This message is applicable to developers who create custom
server object extensions. |
| 1029 |
Required tag CLSID (or PROGID) is not found in
ServerTypes.cfg. |
This message is applicable to developers who create custom
server object extensions. |
| 1030 |
File failed to load |
|
| 1031 |
Server is enabled. |
|
| 1032 |
Server is disabled |
|
| 1033 |
Warning: SOM configuration changes could not be saved to disk
and will not be available when SOM restarts. |
|
| 1034 |
Warning: Changes to server object configuration could not be
saved to disk and will not be available when SOM restarts. |
|
| 1035 |
Warning: Changes to server object extension type configuration
could not be saved to disk and will not be available when SOM
restarts. |
|
| 1036 |
The server has lost its connection to SOC machine. The machine
has been dropped from the list of SOC machines but can be manually
returned to the list using an administration client like
ArcCatalog. |
|
| 1037 |
Unexpected error. |
An unknown error occurred while trying to disable a SOC
machine. |
| 1038 |
Failed to load properties of a folder. File is missing,
unavailable, or invalid. |
|
| 1039 |
Failed to save properties of a folder. File is
unavailable. |
|
| 1040 |
Feature is not supported with ArcGIS Server edition. |
This message may appear when ArcGIS Server Enterprise is required. |
| 1041 |
ArcGIS Server edition is required for feature. |
This message may appear if you have ArcGIS Server Workgroup and you attempt an operation that is only supported with
Enterprise. |
| 1042 |
Server object instance creation failed on all SOC
machines. |
|
|
|
|
| 2000 |
Machine is not found |
Message logged if the SOM attempts to create a new container
process or thread on a machine that it can't find. This error will
typically occur if the machine becomes unavailable (due to a
network problem) while the SOM is running. |
| 2001 |
Machine already exists |
Message logged when you attempt to add a server object
container machine that has already been added to the GIS
server. |
| 2002 |
Configuration already exists |
Message logged when you attempt to add a new server object
configuration with the same name and type as an existing server
object configuration. |
| 2003 |
Configuration is not found |
Message logged when a client requests a server object
configuration that does not exist. |
| 2004 |
Configuration is not stopped |
|
| 2005 |
Configuration is not started |
|
| 2006 |
MinInstances value is greater than MaxInstances |
When adding or updating server object configuration, minimum or
maximum instances specified are invalid, for example, a minimum
that is larger than the maximum. |
| 2007 |
Context timed out |
A client held on to a server object for longer than its usage
time-out, and the server automatically released it. |
| 2008 |
Context creation has timed out |
An instance of a server object took longer to create than the
creation time-out, and the server cancelled the creation. |
| 2009 |
Server.dat is not found |
Message logged if the SOM, while it is running, cannot read the
server configuration file Server.dat. |
| 2010 |
Server configuration contains an invalid parameter |
Message logged if the SOM encounters invalid tags or values
when reading the Server.dat file. |
| 2011 |
Server Directory is not found |
Message logged if you attempt to find or delete a server
directory that does not exist. |
| 2012 |
Server Directory already exists |
Message logged if you attempt to add a new server directory
that already exists. |
| 2013 |
Server has no associated SOC machines or all SOC machines are
at capacity. |
|
| 2014 |
The server process could not be started because the Server or
Continer accounts are not configured propertly or they do not match
the server machine you are trying to add to. Check the username and
password for these accounts or re-run the Post Install. |
|
| 2014 |
Server is not licensed for this operation. You need an
Enterprise license to add remote Server Object Container
machines. |
|
| 2014 |
The license for the machine is not appropriate for this ArcGIS
Server. A different license is required. |
|
| 2015 |
Server Object Extension type is not registered with Server
Object type |
|
| 2016 |
Server Object Extension type is already registered with Server
Object type |
|
| 2017 |
Server Object Extension type was successfully registered with
Server Object type |
|
| 2018 |
Server Object Extension type could not be registered with
Server Object type |
|
| 2019 |
The server has lost its connection to SOC machine. The machine
was disabled by server. |
|
| 2020 |
The server repaired connection to SOC machine. The machine is
enabled by server. |
|
| 2021 |
Unexpected error |
An unknown error occurred while trying to enable a SOC
machine. |
|
|
|
| 3000 |
Machine successfully added |
Message logged when the user adds a new server object container
machine to the GIS server. |
| 3001 |
Machine successfully deleted |
Message logged when the user removes a server object container
machine from the GIS server. |
| 3002 |
Attempt to load configuration |
Message logged for each server object configuration when the
SOM starts. |
| 3003 |
Attempt to add configuration |
This event occurs when you either add a new server object configuration or update an
existing one. |
| 3004 |
Attempt to delete configuration |
This event occurs when you either delete or update a server
object configuration. |
| 3005 |
Attempt to stop configuration |
|
| 3006 |
Attempt to pause configuration |
|
| 3007 |
Attempt to start configuration |
This message is not logged when server object configurations
are started during SOM startup. |
| 3008 |
Configuration successfully loaded |
This message is logged for each server object configuration
that was successfully loaded on starting the SOM. This message is
logged after a message with code 3002. If the load failed, an error
with code 1003 is logged. |
| 3009 |
Configuration is successfully added |
Message logged when the SOM starts and successfully adds the ServerDirectoryManager (SDM) and internal ArcGIS Engine server object
configurations. |
| 3010 |
Configuration is successfully deleted |
|
| 3011 |
Configuration is stopped |
|
| 3012 |
Configuration is paused |
|
| 3013 |
Configuration is started |
Note that a successful start may occur after errors have been
logged. |
| 3014 |
Server is successfully started |
Note that a successful start may occur after errors have been
logged. |
| 3015 |
Server is stopped |
No additional messages will be added to a log file after this
message. |
| 3016 |
Server.dat successfully loaded |
Message logged when the SOM starts and the information in
Server.dat is successfully loaded. |
| 3017 |
Server directory is successfully added |
|
| 3018 |
Server directory is successfully updated |
|
| 3019 |
Server directory is successfully deleted |
|
| 3020 |
ArcGIS Server is authorized at the enterprise license
level |
|
| 3020 |
ArcGIS Server is authorized at the workgroup license level |
|
| 3020 |
ArcGIS Server license has been reinitialized |
|
|
|
|
| 4000 |
Container is successfully created |
This message is logged each time a container process for the
target server object configuration is started on a server object
container machine. |
| 4001 |
Thread is successfully created on container |
This message is logged each time a thread is created in a
container process for the target server object configuration. |
| 4002 |
Container removed |
This message is logged each time a container process for the
target server object configuration is removed from a server object
container machine. |
| 4003 |
Thread removed from process machine |
This message is logged each time a thread is removed from a
container process for the target server object configuration. |
| 4004 |
Server Object instance is successfully loaded |
This message is logged each time an instance of a server object
is created in a thread within a container process for the target
server object configuration. The elapsed time logged is the amount
of time taken to create the server object. |
| 4005 |
Configuration initialization succeeded |
|
| 4006 |
Server context created |
This message is logged anytime a client successfully begins
using a service. The client application calls CreateServerContext
for the target server object configuration. The elapsed time is the
wait time between the call to CreateServerContext and when the
client receives the server context. |
| 4007 |
Server context released |
This message is logged anytime a client successfully stops
using a service. The client calls ReleaseContext for a context
created for the target server object configuration. The elapsed
time is the usage time between when the client's call to
CreateServerContext is completed and when the client is
released. |
| 4008 |
Recycling started |
|
| 4009 |
Recycle next object |
Message logged when an instance of the target server object
configuration is recycled. |
| 4010 |
ConfigurationFactoryOP creation failed |
A common cause of this error is that the GIS Server Post Install has not been run correctly or needs to be re-run. This can happen when you apply a service pack and neglect to re-run the GIS Server Post Install. |
| 4100 |
Folder already exists |
|
| 4100 |
Folders root directory not found |
|
| 4100 |
Folder can not be created |
|
| 4100 |
Folder name is empty or contains illegal characters |
|
| 4101 |
Folder is successfully created |
|
| 4102 |
Folder is not empty |
|
| 4102 |
Folder can not be deleted |
|
| 4103 |
Folder is successfully deleted |
|
| 4104 |
Folder is not found |
|
| 4105 |
Attempt to rename folder |
|
| 4106 |
Folder is successfully renamed |
|
| 4107 |
Folder can not be renamed |
Folders can only be renamed before they contain any
services. |
| 4200 |
Attempt to validate configuration |
|
| 4201 |
Configuration is successfully validated |
|
| 4202 |
Configuration is invalid |
|
| 4203 |
Configuration validation failed |
|
