|
Home > Archive > BizTalk Server General > June 2004 > Biztalk Messaging Service Stops Abruptly
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Biztalk Messaging Service Stops Abruptly
|
|
| Arindam 2004-06-29, 5:52 pm |
| Hi,
We are using Biztalk server 2002[SP1] on Win2K machines[SP3]. Recently
we upgraded the .Net Framework version from 1.0 to 1.1 After that
things were working fine but suddenly I am having a problem with
Biztalk. The Biztalk service is stopping abruptly after running for
time. Following are the error messages from event log
In System Event I see the following message:
The BizTalk Messaging Service service terminated unexpectedly. It has
done this 4 time(s). The following corrective action will be taken in
0 milliseconds: No action.
In Application event log I find the following message logged:
Event Sourece = .Net Runtime
The description for Event ID ( 0 ) in Source ( .NET Runtime ) cannot
be found. The local computer may not have the necessary registry
information or message DLL files to display messages from a remote
computer. The following information is part of the event: .NET Runtime
version 1.1.4322.573- Setup Error: Failed to load resources from
resource file
Please check your Setup.
Any idea what is going on? If there is some problem with .Net 1.1.4322
installation shouldn't it always throw this error?
Any help regarding this will be highly appreciated.
Regards,
Arindam
| |
| Lee Graber [MSFT] 2004-06-30, 3:30 am |
| I am guessing you have an AIC system BTS 2002 obviously did not use any
managed code. Have you stress tested your AIC? I don't really see why a
resource load failure would cause a service crash, but something is
bringing our service down hard. If you have this happening often, there
are couple of things you could try to debug it. 1) You could simply attach
the debugger to the process and let it run if you can do this in a test
environment. This would be ideal. 2) You could make your component a
serviced component and register it in COM+ as a server package so that it
runs out of process. Then see if we (mscis.exe) crash or if dllhost.exe
crashes which would definitively indicate that it is in your AIC somehow.
Unfortunately, then you would be back to the debugging step. Let me know if
these options are possible.
Thanks
Lee
This posting is provided "AS IS" with no warranties, and confers no rights.
EBusiness Server Team
--------------------[vbcol=seagreen]
19:48:19 GMT)[vbcol=seagreen]
cpmsftngxa06.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.s
ul.t-online.de!t-online.de!newsfeed.icl.net!proxad.net!postnews2.google.com!
not-for-mail[vbcol=seagreen]
|
|
|
|
|