Labview 2010 crashes XP while looking for webserver

[Steve_G]

Hi,

I am using a Windows 7 laptop with LV 2010 to compile my 32-bit executable.  I've copied it to my target Windows XP, SP3 computer and after running it for a short while it rebooted the computer automatically (I believe the reboot was caused by a BSOD).

I've gone into the Windows Event Viewer and there is an event that says "Labview information:  Error: 404 "Not Found" for "national instruments/ni-rpc/interface/eadfc80d-1e6f-425b-8986-12ccef98f646/ncalrpc", file "c:/program files/national instruments/shared/ni webserver/www/national instruments/ni-rpc/interface/eadfc80d-1e6f-425b-8986-12ccef98f646/ncalrpc": Can't access URL     ."

I'm attaching a jpg of the Event in case I typed it incorrectly.  There is another post that mentions this error but there is no resolution and the discussion went in a different direction:  http://forums.ni.com/t5/LabVIEW/LabVIEW-2010-unstable-on-Windows-7/m-p/1247366/highlight/true

Neither my Win 7 development laptop or my target Win XP system have this www folder.

Has anyone seen this before or know the cause?  Thanks.

Steve

[altenbach]

That error should not cause a reboot.

Can you compare the time stamp of the log entry with the time of the actual crash just to make sure we a looking at the right thing?

Did it happen once or can you reproduce this?

[Steve_G]

Altenbach,

Thanks for the quick reply.

Yes, the time stamp of this error coincides with the crash.  I guess I assumed that it caused the crash because I see about 20-25 instances of it in the Event Viewer.  Immediately before these errors appear there are two instances of the NI Configuration Manager with the Description saying "Opening configuration database".

This only happened on time and I have not been able to reproduce it again.

I'll need to explain to my customer why this Error has appeared so many times in the Event Viewer, and also how I can get it to not happen again.  Do you have any suggestions?  Once I isolate this error and prevent it from happening again then I can monitor the computer for future crashes.

Thanks.

Steve