- This topic has 6 replies, 1 voice, and was last updated 9 years, 2 months ago by
.
-
Posts
-
-
Hi,
I have this problem with Biztalk 2006 Enterprise edition.
The server is running 24/7 and usually it works fine, but every now and then, twice a day the last week, it suddenly hang. It stops to process the messages in the queue, and the receive locations stop working as well as the send ports. In general nothing happens. I am able to access the biztalk databases and the databases used for the applications. I'm also able to suspend and terminate messages.
In the Application log, there are no errors except for this: "The following information is part of the event: Unable to open shim database version registry key – v2.0.50727.00000. ". The sollution is to restart the service, wait for about 10 min, and then everything starts up like nothing happened, and biztalk is as fast as always. This is not a good sollution, since we can't manually monitor biztalk every 10th minute.
Have anyone had similar problems and found a sollution?
Thanks in advance for any help.
Best Regards
Per Jørgensen
-
per – hope this is helpful
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=131584&SiteID=1
-wa
-
Sorry for bringing up this old topic, but while searching the web this page was the only one that describes almost the exact problem I’m having. I’m hoping Per found a solution and still reads this forum, or maybe someone else can help me.
A small difference between Per’s environment and ours is that we have BizTalk 2006 R2 Enterprise Edition (v3.6.1404.0). Our system is a physical Dell system, running Windows Server 2003 Standard Edition SP 1 (v5.2) with an Intel Xeon 2.8 GHz cpu and 2 GB RAM.
Just like described above, our system is running fine most of the time. A dozen of different document types are being processed very fast and if anything wrong happens, we get a nice alert (if we programmed it to do so).
We have experienced that BizTalk may stop working properly without warning. We process a lot of files every day and most of them require quick processing. Some people try again if they don’t receive an answer within a minute, so another file is submitted to BizTalk. Meanwhile BizTalk isn’t doing anything with those files, so they just keep adding up to its queue until it decides to continue working. Often some files are processed incorrectly because other services can’t handle all the requests they receive from BizTalk. If someone notices something’s wrong, we can manually correct everything, but the later that happens, the more there is to fix.
The above happened yesterday for – I think – the third time this year. And the fourth time this morning. And the fifth time this afternoon. We decided to do a full reboot and everything seems okay for now. You can understand that I’m a bit concerned however, maybe even scared.
Unlike Per however, we don’t get any errors in our event log that I can relate to these problems. Also, I don’t believe the mentioned error has anything to do with what we describe.
The worst thing about this is that I don’t know what’s causing this. Like I said the problem on this page is the only one I found on the web that is [pretty much] the same as ours.
Hopefully anyone can help me out here. Thanks in advance.
-
This exact same situation has also started happening on our production BizTalk 2006 server Standard edition (Windows Server 2003 R2 – 64bit – sp2). This system has been running fine for years, and then a month ago BizTalk went into this zombie state for the first time. Then it happened again last week, and again today. There was nothing in any event log in each case, and restarting the BizTalk service got all the files flowing again.
Any help would be greatly appreciated!
-
-
-
-
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.