Target= ' CFH. Configurationfactoryhost '
Machine= ' ibm3850x5 '
Thread= ' 24072 '
Elapsed= ' 0.31200 ' >server Object instance is successfully created on machine ibm3850x5.</msg>
<msg
Time= ' 2011-11-15t13:25:49 '
Type= ' INFO3 '
Code= ' 4006 '
Target= ' CFH. Configurationfactoryhost '
Machine= ' ibm3850x5 '
Thread= ' 24072 '
Elapsed= ' 0.32800 ' >server Context created.</msg>
<msg
Time= ' 2011-11-15t13:25:50 '
Type= ' INFO3 '
Code= ' 4007 '
Target= ' CFH. Configurationfactoryhost '
Machine= ' ibm3850x5 '
Thread= ' 24708 '
Elapsed= ' 0.99800 ' >server Context released.</msg>
<msg
Time= ' 2011-11-15t13:25:50 '
Type= ' INFO3 '
Code= ' 4000 '
Target= ' Nmdis/topic_binhaishidi. MapServer '
Thread= ' 22952 ' >container
6732
Is
Successfully
Created on machine ibm3850x5.</msg>
<msg
Time= ' 2011-11-15t13:25:50 '
Type= ' INFO3 '
Code= ' 4001 '
Target= ' Nmdis/topic_binhaishidi. MapServer ' thread= ' 22952 ' >thread 17336 is successfully created
On container 6732 of machine ibm3850x5.</msg>
<msg
Time= ' 2011-11-15t13:25:52 '
Type= ' INFO3 '
Code= ' 10092 '
Target= ' Nmdis/topic_binhaishidi. MapServer '
Methodname= ' Mapserver.mapreader
. Open '
Machine= ' ibm3850x5 ' process= ' 6732 ' thread= ' 17336 ' >mapreader.open has started.</msg>
<msg
Time= ' 2011-11-15t13:25:53 '
Type= ' INFO3 '
Code= ' 10093 '
Target= ' Nmdis/topic_binhaishidi. MapServer '
Methodname= ' Mapserver.mapreader
. Open '
Machine= ' ibm3850x5 '
process= ' 6732 '
Thread= ' 17336 '
Elapsed= ' 0.73728 ' >mapreader.open
Has
Completed.</msg>
<msg
Time= ' 2011-11-15t13:25:53 '
Type= ' ERROR '
Code= ' 1016 '
Target= ' Nmdis/topic_binhaishidi. MapServer '
Machine= ' ibm3850x5 '
Thread= ' 22952 '
Elapsed= ' 3.05800 ' >server Object instance creation failed on machine ibm3850x5. </Msg>
<msg
Time= ' 2011-11-15t13:25:53 '
Type= ' INFO3 '
Code= ' 4002 '
Target= ' Nmdis/topic_binhaishidi. MapServer '
Thread= ' 22952 ' >container
6732
Of
Machine
IBM3850X5 is removed.</msg>
<msg
Time= ' 2011-11-15t13:25:53 '
Type= ' INFO3 '
Code= ' 4003 '
Target= ' Nmdis/topic_binhaishidi. MapServer '
Thread= ' 22952 ' >thread
17336
Removed
From
Process 6732 of Machine ibm3850x5.</msg>
<msg
Time= ' 2011-11-15t13:25:53 '
Type= ' ERROR '
Code= ' 1008 '
Target= ' Nmdis/topic_binhaishidi. MapServer '
Thread= ' 25292 ' >configuration
Nmdis/topic_binhaishidi. MapServer can started.</msg>
<msg
Time= ' 2011-11-15t13:25:53 '
Type= ' INFO3 '
Code= ' 4006 '
Target= ' CFH. Configurationfactoryhost '
Machine= ' ibm3850x5 '
Thread= ' 22812 '
Elapsed= ' 0.00000 ' >server Context created.</msg>
<msg
Time= ' 2011-11-15t13:25:53 '
Type= ' INFO3 '
Code= ' 4007 '
Target= ' CFH. Configurationfactoryhost '
Machine= ' ibm3850x5 '
Thread= ' 24536 '
Elapsed= ' 0.01600 ' >server Context released.</msg>
<msg
Time= ' 2011-11-15t13:26:23 '
Type= ' INFO1 '
Code= ' 2033 '
Target= ' CFH. Configurationfactoryhost '
Thread= ' 25236 ' >the
Server
Object
Instance
Is
Shutting
Down because the Idle Timeout Interval have elapsed</msg>
<msg
Time= ' 2011-11-15t13:26:23 '
Type= ' INFO3 '
Code= ' 4002 '
Target= ' CFH. Configurationfactoryhost ' thread= ' 25236 ' >container 5296 of Machine ibm3850x5 is
Removed.</msg>
<msg
Time= ' 2011-11-15t13:26:23 '
Type= ' INFO3 '
Code= ' 4003 '
Target= ' CFH. Configurationfactoryhost '
Thread= ' 25236 ' >thread
18088
Removed
From
Process
5296 of Machine ibm3850x5.</msg>
2
Problem analysis
2.1
Software Environment
The environment is as follows:
Windows Server R2
Operating system (comes with
IIS 7.5
)
,
ArcGIS Server 10.0. NET
Version.
2.2
Reason guessing
Based on past experience, there are several possible reasons for guessing.
2.2.1
License Expiration
This is the first reason to be excluded because the customer has already purchased a permanent formal license. Moreover, image services and
Gp
Services are
can be published.
2.2.2
Not enough memory
On the test machine there are
8GB
Memory, when service publishing fails, memory consumption is only
50%
, so the basic exclusion of memory is not
The possibility of a foot.
2.2.3
Security restrictions
This is more likely, such as firewalls, data access rights, and so on.
So first check the firewall, has closed all, to exclude the possibility.
The data permissions are then checked:
Ensure that the current
ArcGIS
Server
Account (already integrated into
Administrator
) for the test
Shapefiles
Folders and
Shapefiles
The file has read and write permission, the same problem has been tested;
Will
Shapefiles
Data import
File
Geodatabase
, make sure that the user
File
Geodatabase
Access rights, the tested
The same problem still exists in the trial;
Will
Shapefiles
Data import
ArcSDE
, the same problems are still being tested;
After the above test, it also basically excludes the possibility of insufficient permissions.
2.2.4
Data error
This possibility is also relatively large, so the data are tested.
From the previous successful release,
And now a few layers are being tested in the service data source that is running normally,
Find that there is still the same
Problems of the kind;
Completely create a new
Shapefiles
, the editor adds the simplest graphics and still has the same problem;
Optimized analysis of map documents that failed to publish,
Without any errors or warnings,
Save As
Msd
The document is then published,
The same problem still exists;
After the above test, also basically ruled out the possibility of data errors.
3
Problem solving
3.1
Problem Locator
The above analysis confirms that the license is correct, that the memory is sufficient, the permissions are correct, the data is correct, and the image service,
Gp
Clothing
Can be published, so the biggest possibility is that the map service-related configuration information is out of the question.
And when I was publishing a map service,
In addition to specifying the service name,
The other properties completely use the default configuration information.
Because
This inference should be the default configuration information in addition to the problem.
However, previously released services are default configurations that are used
Why is there no problem? The newly published service properties are then
The running service properties were one by one compared to the problem, and the output directory of the original service was
None
, the picture returns
Type is
MIME only
Such as:
While the newly released service, the output directory has been specified, the virtual directory is empty, but the picture return type is
Mime+url
The way! As shown in the following:
Here, finally found the problem, and then began to verify:
Change the output directory to
None
, the shape return type automatically becomes
Mime
Only
, and then start the service, success! Re-release the new
The map service, Success!
This is a stopgap measure, or it is better to use the correct virtual directory, so the correct virtual directory is reset below.
3.2
Change Directory
In
ArcCatalog
Or
ArcMap
Of
Catalog
Panel,
Found it
Gis
Server connection,
Then right-click on the server-
-Server properties, open the "Contents" tab, as shown in:
Sure enough, the virtual directory is empty. Click the Edit button to specify a virtual directory for the directory, as shown in:
The virtual path that you enter should be
Web
Real-World on the server, as in
Iis
In
The cache directory, in turn,
Enter a directory,
Output directory,
The working directory and the index directory specify the virtual path,
Then close the service
The Properties dialog box for the device.
Modify the Map service properties to specify the output directory as native
Arcgisserver
Under the
Arcgisoutput
, this time the virtual
The pseudo-path is automatically populated with the path you just specified, and the image return mode is automatically adjusted to
Mime+url
Mode, restart
Service, Success!
4
Summary
In fact, the problem is not very complicated,
But there are many reasons for this problem,
We need to calmly analyze the exclusion,
Until
Find the last true murderer.
The idea of solving the problem,
Should be first based on one's own or others ' experiences,
Make a list of possible causes,
And then divide it individually.
Analysis and testing,
With a variety of tools,
such as logs,
Network analysis tools, and so on.
When you exclude a possible cause,
The truth will soon surface.
To here,
The problem has finally been solved,
I also looked up some information from the Internet,
A lot of people, too.
The answer is all
multifarious,
But not the same as the situation I encountered,
So deliberately documenting this situation,
Hope someone in the future
If you encounter the same problem, you can have a reference
Troubleshooting Issues with ARCGIS Server Publishing services