BizTalk is a daunting development environment. If everything works as expected, we're fine! If it doesn't, then you don't even know where to start looking!
Here are some tips on BizTalk bug hunting to help you get started:
1st - check service instance database
Go to BizTalk Administrator, BizTalk Group, Show suspended service instances (if you don't find it here, try the dehydrated section).
If your instance is listed here, you can look at the exception report. Read the message and try to interpret it from the server's perspective.
2nd - use Health and Activity Tracking (HAT) to look at messages and debug orchestration
BizTalk logs its steps for each process in a database, and HAT allows you to access the database. Use this if the exception message itself is not enough to find out what's happening. Beware, too much detail can confuse as well as help.
3rd - check Windows Event Viewer
If the problem is in the server the best place to find out something is the Windows Log. Use the Event Viewer (Control Panel, Administrative Tools, Event Viewer).
Happy hunting!
Feel free to post here about other tips on BizTalk bug hunting. Your input is welcome!
No comments:
Post a Comment