CMT Universal (CMTU) installs and uses an XML web service for storing user and settings data. You may encounter issues with the installation of the XML server. This guide presents detailed information on troubleshooting the XML server.
The most frequent issues occur when some other program locks port 80 on the machine. Programs like “Skype” (with its installation defaults) and several printer monitor utilities use port 80 and prevent IIS from working correctly. You may discover what program is using the port by typing “localhost:80” in a browser window and see who answers.
The easiest way to test whether the XML server is working is to use a web browser (Internet Explorer) and navigating to the web site.
Type (or click on this link):
You should see the CMTXMLService description page in the browser window.
This verifies that Microsoft “Internet Information Server” (IIS) and the XML server are running. You can further verify the ASP.NET 2.0 engine by scrolling to and clicking on the “Hello World” function.
And click the “Invoke” button. The following screen should be displayed:
If the following page is displayed IIS is not running.
This error page indicates a problem with the .NET 20 framework installation (Note the version information at the bottom of the screen).
This error (404) indicates a problem with the installation of the CMT_XMLServer.
Verifying the CMTU XML server installation files:
Verify that the XML server files are present.
Verify the access permission of the CMT_XMLServer directory. Make sure that “Everyone” or “ASPNET” have modify permission on the directory.
If the security tab is not available in the properties window you must turn off the “simple file sharing” option.
In the folder view select Tools/Folder Options
And un-check the “Use simple file sharing” option.
Verify Internet Information Server configuration:
Open the “Internet Information Services” management console.
Expand the (local computer)/Web Sites/Default Web Site. Verify that “CMT_XMLServer” is a valid virtual directory.
Verify the local path is correct and read and write access is checked.
Verify directory security allows “Anonymous access” to the local IIS user account..
Confirm that version 2.0.50727 is selected in the ASP.NET tab.
If the “ASP.NET” tab is not displayed in the IIS properties window you can use the command line program “aspnet_regiis.exe”. Open a command prompt and type:
If the registered version is incorrect you can use the same command line program to modify it.
Change to the “C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727” directory and use the aspnet_regiis program with the “-s” option using the path to the xml server displayed from the “-lk” option.
aspnet_regiis -s W3SVC/1/ROOT/CMT_XMLServer
If the computer is running IIS version 6 (Windows 2003 server), verify that the ASP.NET v2.0.50727 “Web Service Extension” is allowed.