L
Loane Sharp
Hi there
I've got a hang of a problem ...
I'm running the .NET framework (2.0.40903), SQL Server 2000 and SQL Express
2005 on Windows XP Pro on a pretty good and new IBM Thinkpad X41.
Some time ago, following the advice in
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnvs05/html/codecompilation.asp, I
used aspnet_compiler.exe to compile my application. Soon thereafter, every
time I made a change to the underlying .aspx script, my application started
to hang, requiring a cold boot of the system. At first, I thought that this
might be due to the very large number of files in my virtual directory
(about 80,000 files); i.e. I thought that, perhaps, each time I changed an
underlying .aspx script file, aspnet_compiler.exe was recompiling my entire
application, which is pretty large mostly on account of there being so many
charts in JPG files. So, suspecting this, I produced the charts on-the-fly
using Office Web Components (rather than physically stored as pre-made
charts), which I needed to do anyway, but still the problem remained.
Trying something different, I noticed that, when I make a change to the
underlying .aspx script and then attempt to load this page in Internet
Explorer, SQL Server hangs too. (Nothing appears to happen to SQL Express
2005, except when Windows as a whole collapses a few minutes later.) If I
have an active ADO connection between Excel and SQL Server, before Windows
crashes, I get a message that SQL Server timed out. I tried to spot
something unusual about SQL Server's behaviour using sysinternals.com's File
Monitor, but I'm not entirely sure I knew what I was looking for. Anyway my
latest thinking on this is that there might be some conflict between SQL
Server (I'm using named pipes to connect to the server) and my ASP.NET
application. Is this possible?
I was frustrated at first, but have become alarmed since my first ever "STOP
0x0000008E (0x00000005, 0x804F28BA, 0xF0CE2878, 0x00000000)" notification,
after which I've done a memory dump and sent this into the ether using
Microsoft's error reporting service. I've had 3 of these in the last few
days, so I back up twice a day and have a new machine on order. (The advice
given by Microsoft's error reporting service is that I may need to change
the video adapter, disable a driver, or upgrade my BIOS, which doesn't rule
out a hardware problem).
Is there a solution, or at least an interpretation of the problem, that I'm
missing?
Best regards
Loane
I've got a hang of a problem ...
I'm running the .NET framework (2.0.40903), SQL Server 2000 and SQL Express
2005 on Windows XP Pro on a pretty good and new IBM Thinkpad X41.
Some time ago, following the advice in
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnvs05/html/codecompilation.asp, I
used aspnet_compiler.exe to compile my application. Soon thereafter, every
time I made a change to the underlying .aspx script, my application started
to hang, requiring a cold boot of the system. At first, I thought that this
might be due to the very large number of files in my virtual directory
(about 80,000 files); i.e. I thought that, perhaps, each time I changed an
underlying .aspx script file, aspnet_compiler.exe was recompiling my entire
application, which is pretty large mostly on account of there being so many
charts in JPG files. So, suspecting this, I produced the charts on-the-fly
using Office Web Components (rather than physically stored as pre-made
charts), which I needed to do anyway, but still the problem remained.
Trying something different, I noticed that, when I make a change to the
underlying .aspx script and then attempt to load this page in Internet
Explorer, SQL Server hangs too. (Nothing appears to happen to SQL Express
2005, except when Windows as a whole collapses a few minutes later.) If I
have an active ADO connection between Excel and SQL Server, before Windows
crashes, I get a message that SQL Server timed out. I tried to spot
something unusual about SQL Server's behaviour using sysinternals.com's File
Monitor, but I'm not entirely sure I knew what I was looking for. Anyway my
latest thinking on this is that there might be some conflict between SQL
Server (I'm using named pipes to connect to the server) and my ASP.NET
application. Is this possible?
I was frustrated at first, but have become alarmed since my first ever "STOP
0x0000008E (0x00000005, 0x804F28BA, 0xF0CE2878, 0x00000000)" notification,
after which I've done a memory dump and sent this into the ether using
Microsoft's error reporting service. I've had 3 of these in the last few
days, so I back up twice a day and have a new machine on order. (The advice
given by Microsoft's error reporting service is that I may need to change
the video adapter, disable a driver, or upgrade my BIOS, which doesn't rule
out a hardware problem).
Is there a solution, or at least an interpretation of the problem, that I'm
missing?
Best regards
Loane