Navigation¶

• Main Page
  

• Random Page
• Create a new Page
• All Pages
• Categories
  

• Administration
• File Management
  

• Login/Logout
• Language Selection
• Your Profile
• Create Account
  

Quick Search
»
Advanced Search »

Generic OD Web Services - Troubleshooting

This page lists common problems and solutions related to installation of the ODM WaterOneFlow web service.

Table of Contents [Hide/Show] Problems when setting folder permissions for the web service folder    Security tab missing from folder Properties dialog Problems when opening the localhost/YOUR SERVICE NAME page in a web browser    Directory Listing Denied    Server Error in '/MyDataService' Application. Failed to access IIS metabase.    The XML page cannot be displayed    Unrecognized attribute 'xmlns'    Configuration Error Problems when testing the database connection after configuring the service in a web browser    Login failed for user 'YOUR COMPUTER NAME\YOUR USERNAME'    Error connecting to server...Could not open a connection to SQL Server    Error connecting to server...No connection could be made because the target machine actively refused it    Error connecting to server...No process is on the other end of the pipe Problems when calling methods on the web service    Invalid Operation Exception: Unable to generate a temporary class

Problems when setting folder permissions for the web service folder¶

Security tab missing from folder Properties dialog¶

Problem

You've installed the WaterOneFlow web service files into a folder. You view properties for the folder to set permissions, but the Security tab is missing from the folder Properties dialog.

Solution

A couple of culprits may be at work. If your computer doesn't use the NTFS file system, then the Security tab may not be available at all. To check for this, in Windows Explorer, you can try right-clicking the C:\ (or whatever drive you've installed the service on) to view the drive's properties. If the drive uses NTFS, you should see something like "File system: NTFS" in the Properties dialog.

Another culprit could be that you are set up to use simple file sharing. To check this and turn it off:

1. Open Windows Explorer.
2. Click Tools | Folder Options.
3. Click the View tab.
4. Scroll to the very bottom, and make sure "Use simple file sharing" is unchecked.
5. Click OK.
   

Problems when opening the localhost/{YOUR SERVICE NAME} page in a web browser¶

Directory Listing Denied¶

Problem

When you try to view your service page in a web browser, you see a message that says "Directory Listing Denied. This Virtual Directory does not allow contents to be listed."

Solution

It's likely that "Default.aspx" has not been set as a document type in Internet Information Services (IIS). Think if Default.aspx as the web service. If IIS doesn't know to look for that document, it doesn't think the directory is a web service, and so it tries to just give a plain view of the contents of that directory. But most likely permissions aren't set to allow the contents to be viewed publicly, so that's why you get that error.

The solution is to add Default.aspx as a default document type in IIS.

1. Start IIS by clicking Start | Control Panel | Administrative Tools | Internet Information Services.
2. Click the plus sign to expand the computer name | Web Sites | Default Web Site, or whichever web site you installed the web services under.
3. Right click Default Web Site and click Properties.
4. Click the Documents tab.
5. Click Add.
6. Type Default.aspx and click OK.
7. Click the up arrow to promote Default.aspx to the top of the list of documents.
8. Click OK.
9. Click OK if prompted about "Inheritance Overrides".
10. Close IIS.
11. Try viewing the localhost/{YOUR SERVICE NAME} page in a web browser again.
    

Server Error in '/MyDataService' Application. Failed to access IIS metabase. ¶

Problem

When you try to view your service page in a web browser, you see a "Server Error in '/MyDataService' Application. Failed to access IIS metabase." error.

Solution

Configure ASPNET 2.0 for IIS:

1. Click Start | All Programs | Microsoft .NET Framework SDK v2.0 | SDK Command Prompt.
2. Type "aspnet_regiis.exe -i" and press ENTER.
3. You should now be able to view the Default.aspx page for the service in a browser. You can also now give the ASPNET account permissions on the web service folder.
   

For more information about setting up an HIS machine, see Setting Up A New HIS Server.

The XML page cannot be displayed¶

Problem

When you try to view your service page in a web browser, you see a "The XML page cannot be displayed" error similar to the one below.

Figure: The XML page cannot be displayed

Solution

Configure ASPNET 2.0 for IIS:

1. Click Start | All Programs | Microsoft .NET Framework SDK v2.0 | SDK Command Prompt.
2. Type "aspnet_regiis.exe -i" and press ENTER.
3. You should now be able to view the Default.aspx page for the service in a browser. You can also now give the ASPNET account permissions on the web service folder.
   

For more information about setting up an HIS machine, see Setting Up A New HIS Server.

Unrecognized attribute 'xmlns'¶

Problem

When you try to view your service page in a web browser, you see an "Unrecognized attribute 'xmlns'" error similar to the one below.

Figure: Installer Error cause by not using Net 2.0

Solution

Change ASP.NET to use 2.0 for application

Configuration Error¶

Problem

You navigate to http://localhost/{YOUR SERVICE NAME}, and get an error message that says: Server Error in '/{YOUR SERVICE NAME}' Application. Configuration Error. Description: An error occurred during the processing of a configuration file....

Figure: Configuration Error - Missing File

Most likely cause

The installation zip file for the web service includes a certain folder structure. If you unpack all files without preserving the folder structure, you will get the error above.

Solution

When unzipping the contents of the web service installation file, make sure you preserve the folder structure of the files within the zip file.

Problems when testing the database connection after configuring the service in a web browser¶

Login failed for user '{YOUR COMPUTER NAME\YOUR USERNAME}'¶

Problem

You set properties on the configuration page, click OK, and then click the "Test Database Connection" link. You get an error that says: Server Error in '/{YOUR SERVICE NAME}' Application. Cannot open database "{YOUR DATABASE NAME}" requested by the login. The login failed. Login failed for user '{YOUR COMPUTER NAME\YOUR USERNAME}'.

Figure: Login Failed

Most likely cause

Check your connection string. You may have a keyword and value of "Integrated Security = true". If this value is set to "true", then the web service will try to use your Windows login to access the database, instead of a SQL login such as "webclient".

Solution

We recommend using a SQL login in your connection string, rather than integrated security. On the configuration page, remove "Integrated Security = true" from the connection string, add "user={User};password={password}" (substitute a valid username and password for the items in brackets and remove the brackets), click OK, and then test the database connection again.

Error connecting to server...Could not open a connection to SQL Server¶

Problem

SQL Server Express is your database engine. Your operating system is Windows XP. You set properties on the configuration page, click OK, and then click the "Test Database Connection" link. You get an error that says: Server Error in '/{YOUR SERVICE NAME}' Application...Could not open a connection to SQL Server.

Figure: Error connecting to server

Most likely cause

In the configuration string, the “data source” keyword has a value of "localhost".

Solution

On the configuration page, change the “data source” keyword value to ".\sqlexpress". Click OK, and then test the database connection again.

Error connecting to server...No connection could be made because the target machine actively refused it¶

Problem

SQL Server Express is your database engine. Your operating system is Windows XP. You set properties on the configuration page, click OK, and then click the "Test Database Connection" link. You get an error that says: Server Error in '/{YOUR SERVICE NAME}' Application...No connection could be made because the target machine actively refused it.

Most likely cause

The SQL Server service hasn't been started on your computer.

Solution

1. Open the Services window by clicking Control Panel | Administrative Tools | Services.
2. Scroll down to SQL Server (SQLEXPRESS). If the Status column doesn't say "Started", then you need to start the service.
3. Right click on that service and click Start.
4. Once the service has started, test the database connection again.
   

On the configuration page, change the “data source” keyword value to ".\sqlexpress". Click OK, and then test the database connection again.

Error connecting to server...No process is on the other end of the pipe¶

Problem

SQL Server Express is your database engine. Your operating system is Windows XP. You set properties on the configuration page, click OK, and then click the "Test Database Connection" link. You get an error that says: Server Error in '/{YOUR SERVICE NAME}' Application...No process is on the other end of the pipe.

Most likely cause

The SQL Server service hasn't been started on your computer.

Solution

1. Open the Services window by clicking Control Panel | Administrative Tools | Services.
2. Scroll down to SQL Server (SQLEXPRESS). If the Status column doesn't say "Started", then you need to start the service.
3. Right click on that service and click Start.
4. Once the service has started, test the database connection again.
   

On the configuration page, change the “data source” keyword value to ".\sqlexpress". Click OK, and then test the database connection again.

Problems when calling methods on the web service¶

Invalid Operation Exception: Unable to generate a temporary class¶

Problem

When you call a method on the web service, you get an error similar to the one below.

Figure: Unable to generate a temporary class error

Solution

Give ASP.NET Write permission on the c:\windows\temp\ folder.

1. In Windows Explorer, navigate to c:\windows\temp\.
2. Right click the folder and click Properties.
3. Click the Security tab.
4. Click Add.
5. Add the ASP.NET user.
6. Give ASP.NET Write permission by checking the "Write" box. Leave other permissions as they are.
7. Click OK, and try calling the web service method again.