Production Terminal seems to lock up and become inoperable after 5 to 7 minutes. Upon further review you may find the following error in the Windows Event Viewer on the server where Production Terminal is installed.

Error:

It is not possible to run two different versions of ASP.NET in the same IIS process. Please use the IIS Administration Tool to reconfigure your server to run the application in a separate process.

The problem is caused having two different websites configured with the same Application Pool. This sometimes occurs if you have Webview v1 and Production Terminal v2 installed on the same server both configured to utilize the same application pool. At current date, Webview v1 utilizes .NET 2.0 while Production Terminal v2 utilizes .NET 4.0. Both of these sites can not be configured to utilize the same application pool since they use different versions of Microsoft .NET.

Creating A New Application Pool

  1. Open the IIS Configuration Tool under Control Panel | Administrative Tools | IIS Configuration
  2. Navigate to the Application Pools section.
  3. Right-click on the Application Pool and choose New Application Pool.
  4. Specify an Application Pool name of ProductionTerminal and copy the configuration from the existing DefaultAppPool.
  5. Click OK to create your new Application Pool.

Configuring Production Terminal To Use The New Application Pool

  1. Open the IIS Configuration Tool under Control Panel | Administrative Tools | IIS Configuration
  2. Navigate to the Web Sites section and locate ProductionTerminal in the list.
  3. Right-click on ProductionTerminal and choose Properties.
  4. Navigate to the Home Directory tab and change the Application Pool from the current setting to ProductionTerminal. ProductionTerminal is the new Application Pool you created in the previous step.
  5. Click OK to apply your changes.

Verifying Your Changes

  1. Right-click on the computer icon within the IIS Configuration Tool that is directly below Internet Information Services and choose All Tasks | Restart IIS. The restart process will take between 20 seconds to 1 minute to complete. Once completed please close the IIS Configuration Tool.
  2. Shutdown the Cyrious SSLIP and re-open it.
  3. Log into Production Terminal, Log into Control, Log into Webview if you have it installed. Repeat the log in and log out process a few times.
  4. Check the Windows Event Viewer to see if any new occurrences of errors have been logged. It is a good idea to check over the next 10-15 minutes, then again an hour later.
  • Entered : 8/03/2010
You could leave a comment if you were logged in.