0 Treat the interchange as its own distributed application to decompose and find performance problems.
0 Use a profiling tool such as Visual Studio Analyzer to track the interactions among the many COMs that will be introduced in a BizTalk solution.
0 Use XLANG Monitor to get detailed information on XLANG schedule state and events.
Troubleshooting Means Service Packs
0 Installing BizTalk Server 2000 Service Pack 1 might solve many of your problems.
0 All BizTalk servers in a group must be working with the same version. Therefore, upgrade them all at the same time.
0 Installing Windows 2000 Service Pack 2 might also serve to take care of many of the more common problems you will encounter.
0 Create a service account with the necessary permissions to execute all of the BizTalk services.
0 In a server environment, ensure that BizTalk Messaging Service, the XLANG Schedule Restart Service, and the XLANG Scheduler COM+ application are configured to use a service account.
0 Ensure that the SQL Server services MSSQLServer and SQLServerAgent are configured to use a service account.
0 The primary location for errors is the Event Viewer. In a default installation, the Application log will display the BizTalk and XLANG error messages.
0 The second important location is the Suspended Queue. The error message might not add anything to the Event Viewer information, but it will contain a copy of the interchange document before it failed.
0 For document validation errors, you can copy the document in the suspended queue to a file, and validate it using BizTalk Editor to get a specific location in the file where the validation fails.
Troubleshooting Message Queuing
0 Ensure that Message Queuing is installed; it is separate from BizTalk.
0 When creating message queues, ensure that they are transactional.
0 When referring to queues, keep in mind that different configuration objects use different syntax. "DIRECT=OS:" might need to prefix the private queue ".\private$\new_queue".
Interchange Size Limits
0 BizTalk Messaging supports interchanges of up to 20MB. Performance will slow significantly around that limit.
0 Messaging Queues support messages of only up to 4MB (2MB Unicode).
0 Flat files will be converted internally to XML, resulting in an increase in size; roughly, a 3 to 1 growth.
0 If you need to use XLANG with >4MB interchanges, you will need to implement via COM. BizTalk activation requires message queues behind the scenes.
Refreshing the Elements
0 When changing document specifications, always save to WebDAV.
0 Open and save any document definitions based on the changed specifications.
0 Reload specifications into dependent maps.
0 Open and save any channels dependent on changed maps.
Managing Receive Functions
0 Beware of competing Receive functions.
0 Try to use unique locations and unique document types for each Receive function.
0 Receive functions can disable themselves. If the Receive function finds a problem, it will disable itself until you re-enable it.
0 Report errors, variable values, and so forth in XLANG schedules by implementing custom COMs.
0 Make the COMs simple and generic to easily use in all schedules.
0 Use the Constants fields of the XLANG schedule to report static items such as the schedule filename or application name.
Working with WebDAV
0 Ensure that BTS SP 1 is installed.
0 Ensure the BizTalk repository virtual directory has read, write, and directory browsing permission.
0 Disable FrontPage extensions.
0 Disable IIS authoring.
0 Ensure that World Wide Publishing is running.
0 The Message Type in the XLANG schedule must be the same name as the root node of the document and label used in the message queue.
0 Distributed Transaction Coordinator must be running.
0 Using Receive functions is more optimized than calling the Submit method on the COM object.
0 When using flat files, you always need an envelope.
0 Remember to enter an SMTP host for your BizTalk Server Group when implementing SMTP transports.
0 Beware of using antivirus software on a BizTalk Server.
Was this article helpful?