Fault on MSCORWKS on virtual server

[Salvador]

Hi,

I have a service that runs perfectly well on a normal server but when I
install it on a virtual server the service suddenly stops (at random times),
all the exceptions on my service are caught, the only entries that I have
found are "The service terminated unexpectedly. It has done this 2 time(s)."
but sometimes appears an error saying:

"Faulting application Myservice.exe, version 3.0.0.0, faulting module
mscorwks.dll, version 1.1.4322.573, fault address 0x00031e79."

Any ideas of any problem with .NET 1.1 and virtual server 2005?

Cheers

Salvador Alvarez Patuel
Exony Ltd - London, UK

[Nicholas Paldino [.NET/C# MVP]]

Salvador,

Have you considered wrapping your service methods with exception
handlers and logging the exceptions? It is possible that something is
occuring and you are just not catching it (which occurs as the result of
running on a virtual machine).

Hope this helps.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"Salvador" <Sa******@discussions.microsoft.com> wrote in message
news:81**********************************@microsof t.com...

Hi,

I have a service that runs perfectly well on a normal server but when I
install it on a virtual server the service suddenly stops (at random
times),
all the exceptions on my service are caught, the only entries that I have
found are "The service terminated unexpectedly. It has done this 2
time(s)."
but sometimes appears an error saying:

"Faulting application Myservice.exe, version 3.0.0.0, faulting module
mscorwks.dll, version 1.1.4322.573, fault address 0x00031e79."

Any ideas of any problem with .NET 1.1 and virtual server 2005?

Cheers

Salvador Alvarez Patuel
Exony Ltd - London, UK

[Salvador]

Hi,

I have a file tracing on my exceptions, anything that happens is logged on a
file, but nothing appears there. This kind of behaviour is common when the
..NET fails (the base is down so it kills all the processes running on it).

The service runs perfectly well on a normal server (not virtual). I am
starting to believe that is some kind of problem with .NET 1.1 and virtual
server 2005 R2. I have other service running and no problems are detected but
they use different features on .NET, like remoting, message queuing and WMI.

Also for more information the architecture is quite complex, I have two very
powerful machines (4 processors + 16 Gb of memory), each cluster has
installed 4 virtual servers and they are load balanced. Sounds wired but is a
cheap way of having a reproduction of the live environemnt (on the cluster is
the database installed only - the services run on the virtual servers that
are not cluster aware).

Cheers.

--
Salvador Alvarez Patuel
Exony Ltd - London, UK
"Nicholas Paldino [.NET/C# MVP]" wrote:

Salvador,

Have you considered wrapping your service methods with exception
handlers and logging the exceptions? It is possible that something is
occuring and you are just not catching it (which occurs as the result of
running on a virtual machine).

Hope this helps.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"Salvador" <Sa******@discussions.microsoft.com> wrote in message
news:81**********************************@microsof t.com...

Hi,

I have a service that runs perfectly well on a normal server but when I
install it on a virtual server the service suddenly stops (at random
times),
all the exceptions on my service are caught, the only entries that I have
found are "The service terminated unexpectedly. It has done this 2
time(s)."
but sometimes appears an error saying:

"Faulting application Myservice.exe, version 3.0.0.0, faulting module
mscorwks.dll, version 1.1.4322.573, fault address 0x00031e79."

Any ideas of any problem with .NET 1.1 and virtual server 2005?

Cheers

Salvador Alvarez Patuel
Exony Ltd - London, UK