The "aspnet_wp.exe" process takes up to 90% of theCPU Resources all the time. I am seeing tremendous amounts of lines in the log looking like:

First-chance exception at 0x77e4bee7 in aspnet_wp.exe: 0xE0434F4D: 0xe0434f4d.

Additionally, many references to "No Symbols Loaded" as in the line below:

'aspnet_wp.exe': Loaded 'C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_wp.exe', No symbols loaded.

Lastly:

[2008/01/02 11:38:38 P1500 T00D i PEDI] Pedi.Application_EndRequest.

or:

[2008/01/02 11:38:38 P1500 T00D i PEDI] InitializeSession site_code=SITECODE
[2008/01/02 11:38:38 P1500 T012 i PEDI] InitializeSession site_code=SITECODE
[2008/01/02 11:38:38 P1500 T00D i PEDI] InitializeSession OK, UTCTime=01/02/2008 11:38:38
[2008/01/02 11:38:38 P1500 T012 i PEDI] InitializeSession OK, UTCTime=01/02/2008 11:38:38
[2008/01/02 11:38:38 P1500 T00D i PEDI] Pedi.Application_EndRequest.
First-chance exception at 0x77e4bee7 in aspnet_wp.exe: 0xE0434F4D: 0xe0434f4d.
[2008/01/02 11:38:38 P1500 T00E i PEDI] InitializeSession site_code=SITECODE
[2008/01/02 11:38:38 P1500 T012 i PEDI] Pedi.Application_EndRequest.
[2008/01/02 11:38:38 P1500 T00E i PEDI] InitializeSession OK, UTCTime=01/02/2008 11:38:38
First-chance exception at 0x77e4bee7 in aspnet_wp.exe: 0xE0434F4D: 0xe0434f4d.
First-chance exception at 0x77e4bee7 in aspnet_wp.exe: 0xE0434F4D: 0xe0434f4d.
[2008/01/02 11:38:38 P1500 T011 i PEDI] InitializeSession site_code=SITECODE
[2008/01/02 11:38:38 P1500 T011 i PEDI] InitializeSession OK, UTCTime=01/02/2008 11:38:38
[2008/01/02 11:38:38 P1500 T00E i PEDI] Pedi.Application_EndRequest.
[2008/01/02 11:38:38 P1500 T011 i PEDI] Pedi.Application_EndRequest.


Is found in the log file. Attatched a copy of a sample log file output.

Pharos recommend uninstalling and re-installing several components:

- .NET Services
- Pharos EDI

Clients that have Pharos Omega Terminals are recommended to update to the latest firmware revision, which is available on the Pharos website:

http://www.pharos.com/support/terminals/index.html

There are also several known viruses that attack this process. We recommend running an updated virus utility on the effected server.