I have MS VS 2005 running on two machines with W2003 servers as a host OS.
Both VS crashing host server at least once a day. All drivers are up to date
Servers: HP Proliant DL 380, 4G RAM, 2xCPU and IBM eServer xSeries 300
(8672-5xx, 6xx, 8xx) with 1.5G RAM, 1xCPU
Does anyone experiencing same or similar problem?
Thanks,
Can you report in detail what the "crash" says? How do you know VS2005 is
causing the "crash" and not some HP/IBM HW driver?

Signature
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
I have MS VS 2005 running on two machines with W2003 servers as a host OS.
Both VS crashing host server at least once a day. All drivers are up to date
Servers: HP Proliant DL 380, 4G RAM, 2xCPU and IBM eServer xSeries 300
(8672-5xx, 6xx, 8xx) with 1.5G RAM, 1xCPU
Does anyone experiencing same or similar problem?
Thanks,
John Strow - 29 Dec 2004 19:21 GMT
I don't see any other message except "The previous system shutdown at
9:08:35 AM on xx/xx/2004 was unexpected"
HP is a new system and i don't expect it to be crashing. It has been running
for some time before VS installation and has never crashed
Thanks
John
> Can you report in detail what the "crash" says? How do you know VS2005 is
> causing the "crash" and not some HP/IBM HW driver?
[quoted text clipped - 8 lines]
>
> Thanks,
Ben Armstrong [MSFT] - 29 Dec 2004 19:47 GMT
You need to change the System recovery settings to not automatically
restart on a system failure - then you will be able to see the contents
of the blue screen.

Signature
Cheers,
Benjamin Armstrong
===============================
Virtual machine Program Manager
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
> I don't see any other message except "The previous system shutdown at
> 9:08:35 AM on xx/xx/2004 was unexpected"
[quoted text clipped - 21 lines]
>>
>>Thanks,
John Strow - 29 Dec 2004 22:35 GMT
I'll give it try
thanks
> You need to change the System recovery settings to not automatically
> restart on a system failure - then you will be able to see the contents
[quoted text clipped - 24 lines]
> >>
> >>Thanks,