Troubleshooting of supermapis. Net failure

Common Phenomena

Generally, you cannot view a map on a map page. The following are common phenomena:

1 page reported: "unable to connect because the target computer is actively rejected. IP Address: 8800 ".

2 page: "ApplicationProgramServer error. You have not set the object reference to the instance of the object"

3. The Red Cross sign is displayed on the map form, and the progress bar continues.

4. The map form is displayed in gray, but it does not respond when it is zoomed in or out. A script error is reported in the lower left corner of the browser.

5. view the demo page. The demo framework is displayed, but the map display window is blank.

6. The map form is gray, but the map list and layer list are displayed.

7. access from the local machine is allowed, but access from the LAN is not shown.

8. Create a project, drag a map control, and click load map in the upper-right corner. An error is reported, indicating that the map server fails to be connected or that the map contains a cross sign.

For more information, see: 1. Are you sure you have referred to "Supermap is. Net do not show common problems" and still cannot solve your problem. 2 If the number of iis5.1 concurrent connections in the XP system is limited to 10, the figure is often not displayed, or the picture with a cross sign is displayed when the figure is highlighted, it is recommended to replace it with a Windows Server Series server. 3. If Supermap is. net 20008 Professional Edition, because the Professional Edition does not support Ajax development, so the configuration of the Professional Edition license ajaxdemo is not shown in the figure, the same Ajax development method of the project will not be returned. 4. This document applies to the Supermap is. net 2008 series, Supermap is. Net 6.0, Supermap is. Net SP1 SP1, and other versions.

Common Causes

The common causes for not going out of the graph are as follows:

1. The map server is not started or fails to be started.

2maphandler writing error

3. The server address and port cannot be accessed.

The 4output virtual directory cannot be accessed.

5. Incorrect image access or output address

Solution

The symptom is caused by a specific cause, and the cause of the failure is many. For common phenomena, we can analyze the cause:

Symptom 1: The map service cannot be connected or the map service fails. This type of problem is generally caused by the failure of the map server or startup. For specific solutions, refer to supermapis. net startup failure frequently asked questions;

Symptom 2: Generally, the map service is not restarted because the workspace is modified, or the map requested by the project does not exist in the workspace. In the first case, we recommend that you restart the map service, Web server, and browser after changing the workspace published by the map service. In the second case, we recommend that you viewCodeRequest that the map be changed to an existing map of the workspace;

Symptom 3: by default, a progress bar is displayed when mapcontrol is enabled for webcontrol to load images. a progress bar always indicates that images are being obtained, the output directory cannot be accessed, the image is accessed, or the output address is incorrect. If the output virtual directory can be accessed, you can directly use a browser to browse the content in the output virtual directory, such as http: // localhost/is/output/image name, you can directly see whether the output directory can be accessed, if the image access address is correct, you can use the status bar in the lower right corner of the browser to check whether the image access address is correct or directly view the map service management tool to check whether the image access address is correct;

Symptom 4: During the first development with the ajaxscripts method and deployment of your own maphandler, in addition to the details of the code writing process, this is mainly because of the understanding of maphandler and the failure to access the output directory or the incorrect image access or output address. We have described the following reasons in detail, for more information about maphandler, see the maphandler introduction and Creation Document. symptom 5 and 6: Generally, there are two situations where the output directory cannot be accessed, the image access or the output address is incorrect, if the output virtual directory can be accessed, you can directly use a browser to browse the content in the output virtual directory, for example, http: // localhost/is/output/image name. Then you can see whether the output directory can be accessed, if the image access address is correct, you can use the status bar in the lower right corner of the browser to check whether the image access address is correct or directly view the map service management tool to check whether the image access address is correct, if the output virtual directory cannot be accessed, you can view the IIS introduction and modify it to make it normally accessible. If the image access address is incorrect, change it to the normal access address, for example, the default image access address is {hostname}. If the LAN access address is used, the address is changed to the server IP address;

Symptom 7: Generally, the image access address is the host name by default. If the LAN access fails, the image access address is not accessible. Therefore, we recommend that you change the image access address to the Host IP address;

Symptom 8: Generally, this error is caused by a maphandler writing error. This is common in the ajaxcontrol development mode. The default ajaxcontrol development mode is used to drag a mapcontrol control to the page, click the load Map button on the mapcontrol task panel in the upper right corner to bring up the load map panel. In this case, you need to enter the IP address displayed in the ADDR input box, but the output must be filled with maphandler, for example, the local access can be "http: // localhost/is/ajaxdemo/".

The above is a simple analysis of common phenomena. If you want to quickly locate the problem in the subsequent development process and find the cause, we strongly recommend that you continue to read it. To solve this problem, we generally need to consider the following issues: first, make sure that the map server is near and started successfully. If you do not know how to determine whether the map server is successfully started, see determine Supermap is. if the startup fails, see Supermap is. net startup failure troubleshooting considerations and Supermap is.. Net startup failure FAQ and other documents.

Second, the output virtual directory is the image publishing address. In general, make sure that there is an output directory under IIS and the directory is configured for normal access. The default value is supermapis. after installation, an output virtual directory is created on IIS at http: // localhost/is/output/. If an output directory is created and cannot be accessed or created, you need to set anonymous access to this directory, integrate windows identity authentication, and set authorization rules to allow all users to access the directory.

The image access address is the address that the map server sends to the client map server to generate a map. Find the Supermap is. net installation directory/bin supermapis. config File, open it in notepad, and locate website = http: // localhost/is/output node to check whether the node setting is the output address above; the image output directory is the directory where the map server generates the map and finds the supermapis. options output = ".. \ output ", the default plotting directory is Supermap is. net installation directory/output. If you modify the directory, redirect it. Note that the website of the image access address must point to the virtual directory that the options node points.

If the project is developed using Ajax, check whether maphandle is correctly written. The correct format of maphandle is "http: // localhost/Project virtual directory/" or ". /", provided that the system reference library and web are configured for the project. the map server address and handler of the config file. The default example is "http: // localhost/is/ajaxdemo/". If it is not port 80, set maphandler to ". /". We recommend that you write maphandler as "./". In the web. in the config file, the <add key = "mapserver_address" value = "localhost"/> <add key = "mapserver_port" value = "8800"/> node is configured with the map server, if the WEB Project and map server are not on the same server, change mapserver_address to the IP address of the map server and ensure that the address and port can be accessed normally.

More information

1 If Supermap is. NET is installed for the first time, please refer to Supermap is. net installation and debugging considerations first

2. For more intuitive and quick problem locating, refer to using tools such as fiddle or httpwatch for quick analysis and problem locating.

3. If you do not understand cross-origin access, refer to Supermap is. net online help in Development Guide-topic introduction-Cross-origin access introduction, common examples such as Access Project address such as http: // ip address/virtual directory name /, however, both the image access address and maphandler are written as http: // localhost/virtual directory name/, which may cause cross-origin access problems. We recommend that you use both IP addresses and localhost.

4 If tcpmap is used for development, note that the correct address and port are written during connection establishment, and the map server can be started normally, and the port and address can be accessed normally. The common method is IMAP m_map = tcpmap. create (mapserveraddress, mapserverport, new hashtable ());.