I m geeting this Error:

"An unhandled exception ('System.NullReferenceException') occurred in ClearCanvas.ImageServer.ShredHostService.exe [5448]. Just-In-Time debugging this exception failed with the following error: Debugger could not be started because no user is logged on."

Is there a solution / workaround to this problem?
Please advise.

Regards,

AR

This sounds like a crash of the service. Can you check the Windows Event Viewer and see if there's a record of the crash, and a stack trace of where the crash occurred? This may help diagnosis where the problem is occurring, at least.

Steve

Windows Event Viewer shows the following message.

  Provider Name="VsJITDebugger"
  EventID Qualifiers="49152" 4096
  Channel = Application
  Data = An unhandled exception ('System.NullReferenceException') occurred in ClearCanvas.ImageServer.ShredHostService.exe [1840]. Just-In-Time debugging this exception failed with the following error: Debugger could not be started because no user is logged on. Check the documentation index for 'Just-in-time debugging, errors' for more information.

Please advise & I really appreciate for the reply.

Thank You

Regards,
AR

AR,

Unfortunately, that's not enough information to help with the problem. A couple of things might help:

First, the error message seems to imply that more information is not available because a user is not logged in. Do you have a user logged into the console of the server when the error occurs? This might help.

Second, although it won't directly point to the problem, it would help to match the time when the error happens, and see if there's any logs right before the crash occurs. That might help to understand what the server was doing when the crash occurs.

Steve

Following Error Message log at the time of Crash.

ERROR - Exception thrown
Unexpected User exception, description: Unexpected exception on OnDimseTimeout
System.NullReferenceException: Object reference not set to an instance of an object.
at ClearCanvas.Dicom.Network.DicomServer.OnDimseTimeout()

Thank You,

Regards,
AR

 AR,

One possible solution would be to increase the ReadTImeout and WriteTImeout in the ShredHostService's configuration file.  It appears that the problem is happening due to a timeout and a likely uncaught exception.  Increasing the timeout so it doesn't occur may help fix the problem...

Steve