Export (0) Print
Expand All

Troubleshooting BizTalk Server Administration

This section provides a centralized location for information about common problems encountered while using Microsoft® BizTalk® Server Administration.

Supplemental information about issues discovered after this Microsoft BizTalk Server 2004 documentation release are included in the Readme file located in the \Program Files\Microsoft BizTalk Server 2004\Documentation folder.

Note  You can also check the error messages in the suspended queue for more troubleshooting information.

Note  You can also check the Event Log for detailed information, such as event and warning messages. For more information about the Event Log, see Event log in Windows Server Help.</NOTE>

Reusing Windows group names that were previously deleted

If, when reinstalling BizTalk Server 2004, you use a Windows® group name that had been previously deleted, the Windows group will not have access to the BizTalk Server databases. Deleting a Windows group and then creating a Windows group with the same name produces a new Security Identifier (SID) for the Windows group. However the old SID is still cached in SQL Server™, so the new Windows group will not be able to login to SQL Server.

When you delete the Windows group, you must also remove the SQL Server login for the Windows group.

BizTalk Administrator cannot start the BizTalk Administration console

A BizTalk Administrator (member of the BizTalk Administrators Windows group) may not be able to open the BizTalk Administration console if that user is not a member of the Windows Administrators group on the local computer.

This issue is the result of changing S-IDs in SQL Server when you reinstall or reconfigure BizTalk Server. SQL Server uses cached S-ID instead of fresh ones.

Cannot delete host

You must be a member of the Administrators Windows group on the local runtime computer to delete both in-process and isolated hosts that contain one or more host instances. If you are not an administrator, you will not be able to delete the host.

The following table shows the error messages that appear if you are not a member of the local Windows Administrators group and you attempt to delete an in-process or isolated host that contains one or more running host instances.

Host typeStatusError message
In-processRunningFailed to uninstall at least one instance of BizTalk host <host name>.

You cannot request an install or delete operation on the BizTalk host instance because it is currently running. You must stop the BizTalk host instance before trying it again.

In-processStoppedFailed to uninstall at least one instance of BizTalk host <host name>.

Failed while deleting the Windows NT service BTSSvc{<GUID number>}.

IsolatedStatus UnavailableFailed to uninstall at least one instance of BizTalk host <host name>.

Access is denied.

If you are not a member of the local Windows Administrators group and you attempt to delete an in-process host that contains one or more running or stopped host instances, you will experience the following results:

  • The host is not removed.
  • The status of any host instances changes to "Status unavailable".
  • The installation status of any host instances changes to "Uninstallation Failed".

If you are not a member of the local Windows Administrators group and you attempt to delete an isolated host that contains one or more running or stopped host instances, you will experience the following results:

  • The host is not removed.
  • The status of any host instances does not change. Status remains "Status unavailable".
  • The installation status of any host instances does not change. Status remains "Installed".

Cannot start a Host instance on a remote computer

When you create a BizTalk Host instance on a remote computer, you may see the following error when you start the BizTalk Host instance: "Failed to start due to logon failure." The reason for this error is either you entered invalid credentials for the service account under which the BizTalk Host instance is running, or the service account does not have logon as service rights.

You must assign logon as a service right to the service account in the remote computer before you start the BizTalk Host instance. This is done automatically on a local computer, but you must do it manually on a remote computer.

Trusted host instances and non-trusted host instances cannot use the same service accounts

Host instances of trusted hosts and host instances of non-trusted hosts cannot use the same service accounts. If you want to change the trust setting of a host instance and the host instance uses a service account that other host instances use, you can do one of the following:

  • You can change the service account of the host instance for which you want to change the trust settings to a new service account.
  • You can change the service account of the host instance to an existing service account that other host instances with the same trust setting use.
  • You can delete the host instance, and re-create it with a different trust setting and service account.

Host instance deletion does not clear registry information

If you are not an administrator on the local computer, when you delete an in-process or isolated host, an access denied error message appears.

You can forcibly delete the host. However, deleting the host in this manner does not clear all of the related registry information.

To forcibly delete a host

  1. In the access denied error message, click OK to forcibly delete the host.

    The following error message appears: "You can forcefully delete this host instanc. This may leave orphan orchestrations and prevent cleanup of COM+ spplicaitons and NT services on machine '<computer name>. Do you want to prceed with forceful host instance deletion?"

  2. Click OK to delete the host.

Error appears when you attempt to remove host

If you forcibly delete a running host instance, and then attempt to delete the related host, the following error message appears:

"Failed to delete database objects associated with BizTalk Host "<host name>" from MessageBox database server "<server name>"/ database name "BizTalkMsgBoxDb". Cannot delete a BizTalk host until all its instances are deleted."

Orphaned services may still be running after you deleted the host instance. You must first stop any orphan services before you can delete the host. You must locate and stop any services with the host name on every BizTalk Server computer on which you installed the host instance. After all of the services are stopped, you should be able to delete the host.

Cannot delete a MessageBox database

You may not be able to delete a MessageBox database. If the deletion fails, one of the following issues may be responsible:

  • The cache refresh interval has not expired.
  • The MessageBox database contains incomplete instances.
  • The MessageBox database contains left behind host tracking data.

If the cache refresh interval has not yet expired, the following error message appears when the deletion fails: "MessageBox cannot be deleted since there could be remaining work in the MessageBox. Please ensure that there are no more incomplete instances in the MessageBox, and try again."

The cache refresh interval must expire between the time you disable new message publication in the MessageBox database and the time you delete the database. By default, the cache refresh interval is 60 seconds.

To delete a MessageBox database, you must first disable new message publication for that MessageBox database, and then wait until the cache refresh interval expires, before you delete the MessageBox database.

If the MessageBox database contains incomplete service instances, the following error message appears: “The MessageBox cannot be delted because it may still contain incomplete instances. Ensure that there are no incomplete instances in the MessageBox, and try again.”

You use the Health and Activity Tracking (HAT) tool to view incomplete service instances in the MessageBox database, For information about viewing the status of service instances in HAT, see Service Instances and Message Views in HAT.

If the MessageBox database contains unprocessed tracked data, Microsoft© Windows© Management Instrumentation (WMI) will not allow you to delete it. You use the WMI MSBTS_MsgBoxSetting class method "ForceDelete" to remove the MessageBox database. Because this method is not exposed in the BizTalk Administration console, you must use a script such as the following to delete the message:

Cscript ForceDeleteMsgBox.vbs <name of the MessageBox database to delete>

To download updated BizTalk Server 2004 Help from www.microsoft.com, go to http://go.microsoft.com/fwlink/?linkid=20616.

Copyright © 2004 Microsoft Corporation.
All rights reserved.
Show:
© 2014 Microsoft