Export (0) Print
Expand All
This topic has not yet been rated - Rate this topic

Troubleshooting: Issues and Resolutions

This topic addresses issues related to running Microsoft® BizTalk 2009 Accelerator for RosettaNet (BTARN). The individual issues detail a specific symptom, a possible cause, and a solution.

Symptom

You receive the following or similar error in the event log:

The Messaging Engine encountered an error publishing a batch of "n" messages to the Message Box database for the transport adapter "BizTalk HTTP Receiver". Please refer to Health and Activity Tracking tool for more detailed information on this failure and check the endpoint bindings are correctly configured.

Possible Cause

This error could be caused by one of the following reasons:

  • Missing decryption certificate

  • Incorrectly encrypted message

  • Unauthorized message (source not recognized as a valid partner)

  • Message failing validation of any header part: preamble, delivery header, or service header.

This message may be preceded by another error message that details the cause.

Solution

Review the details provided with the error message for additional help. Restarting Microsoft SQL Server™ may resolve this issue.

Symptom

Running the BTARNClean utility does not unenlist all artifacts.

Possible Cause

If you run the BTARNClean utility before deleting agreements and partners from the Microsoft® Management Console (MMC), the BtarnClean utility will not be able to unenlist all artifacts because they are still used.

Solution

  1. At the command prompt, type:

    lookback.exe /disable <home org or partner>
    
  2. Run the BtarnClean.exe file.

  3. In BizTalk Explorer, delete the parties.

Symptom

Running the ConfigFramework.exe file yields no results on a computer that does not have Microsoft BizTalk Server 2009 or Microsoft Visual Studio installed. You can only use this BTARN configuration as an HTTP client.

Possible Cause

Two DLL files are missing from the installation.

Solution

Install SQLXML on the computer, and then manually copy the Msxml4.dll and Atl71.dll files to the System folder.

Symptom

You receive the following error message when you import a configuration file using the BTARN Management Console:

Could not store transport type data for Primary Transport of Send Port 'RNSTT.Async' to config store. Access is denied.

You can also receive this error when you try to change the configuration, such as by creating a new partner.

Possible Cause

The current user is not a member of the BizTalk Administrators group.

Solution

Make sure that the current user is a member of the BizTalk Administrators group.

Symptom

You receive the following error messages in the Event Viewer:

Error happened in tracking Message activity. Error message is Stored Procedure Does Not Exist.

-or-

Error in terminating BAM message activity with id <ID number>.

Possible Cause

The Business Activity Monitoring (BAM) tracking tool is not installed.

Solution

Install the BAM tracking tool using the Custom Installation option. If you do not need BAM functionality, you can ignore these messages or disable tracking using the BTARN Management Console. After you disable tracking, you must restart BizTalk Server and Internet and Information Services (IIS).

Symptom

You cannot view the content of a schema properly in BizTalk Editor.

Possible Cause

The schema is missing the displayroot_reference attribute for the schemaInfo element.

Solution

Open the schema in Notepad or another text editor and add the displayroot_reference attribute to the schemaInfo element. The value of the displayroot_reference attribute should be the same as the root_reference attribute.

For example:

<schemaInfo document_type="4A1" version="V02_00" xmlns="http://schemas.microsoft.com/BizTalk/2003" displayroot_reference="Pip4A1StrategicForecastNotification" root_reference="Pip4A1StrategicForecastNotification" />

Symptom

You receive the following or similar errors when sending a HTTP request:

The remote server returned an error: (404) Not Found.

Message cannot be sent to ../BTSHttpReceive.dll.

Possible Cause

The BizTalk Server Internet Server API (ISAPI) extension DLL (BTSHttpReceive.dll) has not been configured in Internet Information Services (IIS). This occurs if the HwsMessages HttpReceive web service extension is not configured and if this web service extension is configured, but not allowed.

Solution

To determine whether the HwsMessages HttpReceive web service extension is configured, and if it is not configured, to allow it, perform the following procedure.

  1. Click Start, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.

  2. Expand <computer name> (local computer), and then click Web Service Extensions.

  3. In the Web Service Extension pane, verify that the status for HwsMessages HttpReceive is Allowed. If not, right-click HwsMessages HttpReceive, and then click Allow.

If the HwsMessages HttpReceive web service extension is not configured (it is not included in the Web Service Extensions list in IIS Manager), perform the following procedure.

  1. Click Start, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.

  2. Expand <computer name> (local computer), right-click Web Service Extensions, and then click Add a new Web service extension.

  3. In the New Web Service Extension dialog box, in the Extension Name box, type BizTalk ISAPI Extension, and then click Add.

  4. In the Add File dialog box, in the Path to file box, type <drive>:\Program Files\Microsoft BizTalk Server 2009\HttpReceive\BTSHttpReceive.dll, and then click OK.

  5. In the New Web Service Extension dialog box, select Set extension status to Allowed, and then click OK.

Symptom

You receive the following or similar error in the event log:

A BizTalk isolated host instance configured with the user account '\HostSvc' was either not running or does not exist on this computer. Use the BizTalk Administration Console to create a new isolated host or reconfigure an existing to run as '\hostsvc'.

Possible Cause

To run the Configuration Wizard, the user should be configured as '<machine name>\hostsvc', not '\hostsvc'.

Solution

Open the BizTalk Administration Console, and change hosts that are running under the account '\hostsvc', so that they run under the account '<machine name>\hostsvc'.

Symptom

You receive the following or similar error in the event log:

error CS0234: The type or namespace name 'SerializableAttribute' does not exist in the class or namespace 'RosettaNet.Schemas.System' (are you missing an assembly reference?).

Possible Cause

One of your schemas, for example, StandardDocumentHeader.xsd, has a .NET namespace of RosettaNet.Schemas.System.

Solution

Remove the "System" from the .NET namespace for the schema, so that the namespace is RosettaNet.Schemas.

Symptom

When you manually try to deploy the BAM package for BTARN, you receive an error indicating that you cannot deploy the package.

Possible Cause

The DTS packages BAM_DM_Process and BAM_DM_Message are installed on your system, preventing deployment of the BAM package.

Solution

  1. Click Start, point to All Programs, point to Microsoft SQL Server, and then click Enterprise Manager.

  2. In Enterprise Manager, expand Microsoft SQL Servers, SQL Server Group, (local) (Windows NT), and Data Transformation Services.

  3. Click Local Packages, right-click BAM_DM_Message, and then click Delete.

  4. Right-click BAM_DM_Process, and then click Delete.

  5. Click Start, click Run, type cmd, and then click OK.

  6. At the command prompt, type the following code to deploy the tracking file, and then click OK.

    cd %ProgramFiles%\Microsoft BizTalk Server 2009\Trackingbm deploy all  "%ProgramFiles%\Microsoft BizTalk 2009 Accelerator for RosettaNet\BAMTracking\tracking.xml"
    

Symptom

You receive the following or similar error in the event log:

UNP.SCON.VALERR: A failure occurred while validating the service content.

Details: Finding document specification by message type failed. Verify that the schema is deployed properly.

Possible Cause

Either the document namespace or the root node property the deployed schema for the instance Pip4A5NotifyofForecastReply is incorrect.

Solution

Verify that the document namespace and the root node property for the deployed schema for instance Pip4A5NotifyofForecastReply is correct.

Symptom

During the configuration process, you receive an error in the error dialog box indicating that the computer is not properly connected to the network, when in fact it is.

Possible Cause

This error may be caused by the BTARN configuration program misinterpreting IP addresses. The hosts file in C:\Windows\system32\drivers\etc contains an entry mapping the localhost host name to the IP address 127.0.0.1. The configuration program may confuse this value with the loopback address, and assume that the computer is not connected properly to the network.

Solution

  1. In Windows Explorer, move to C:\Windows\system32\drivers\etc, and open the hosts file using Notepad.

  2. Comment out the line "127.0.0.1        localhost" by placing "# " at the start of the line. Save the changed hosts file.

  3. Click Retry in the error dialog box.

  4. After configuration has completed successfully, re-open the hosts file in Notepad, remove the comment mark at the start of the line mapping localhost, and then save the hosts file.

Symptom

You receive the following or similar error in the event log:

There was a failure executing the receive pipeline: "Microsoft.Solutions.BTARN.Pipelines.Receive" Source: "MIME/SMIME decoder" Receive Location: "/BTARNHttpReceive/BTSHTTPReceive.dll?xRNResponseType=async" Reason: Incorrect signature length, value = 1935897193.

Possible Cause

This error message indicates that the signature length is incorrect. In addition to the above cause, this error could also due to the incorrect or incomplete header content length which leads to the wrong bytes read on the signature length.

Solution

Verify that both of the signature length and header content length is correct.

Symptom

After BTARN 2009 configuration is completed, when you try to access http://localhost or http://localhost/BtarnApp/RnifSend.aspx, you may receive the following or similar error:

503: Service Unavailable

Possible Cause

This error may be caused by the ISAPI filter found under C:\windows\system32\rpcproxy\rpcproxy.dll being set on IIS Web Sites.

Solution

  1. Click Start, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.

  2. Expand <computer name> (local computer), right-click Web Sites, and then click Properties.

  3. Select ISAPI Filters tab.

  4. Select RpcProxy filter, and click Remove.

  5. Click OK.

  6. Click Start, click Run, type cmd, and then click OK.

  7. At the command prompt, type the following code to reset IIS.

    iisreset
    
Bb950214.note(en-US,BTS.10).gifNote
If you try to access http://localhost or http://localhost/BtarnApp/RnifSend.aspx again after performing the above steps, you will receive HTTP 400 message back from the Internet Explorer which means that IIS is now functioning properly.

Symptom

When you run setup.bat in <drive>:\Program Files\Microsoft BizTalk 2009 Accelerator for RosettaNet\SDK\HubScenario to set up the HubScenario sample, the operation fails.

Possible Cause

The HubScenario and HubHelper assemblies were not deployed correctly because the assembly key files were not set in the projects.

Solution

Set the assembly key files for the HubScenario and HubHelper projects. For more information, see HubScenario Sample.

Symptom

When you run setup.bat to build and initialize the Double Action PIPAutomation Orchestration sample, the PipAutomationGetAction stored procedure in the BTARNData database is not created.

Possible Cause

You ran setup.bat on a 64-bit computer or on a BizTalk Server 2009 installation that is running on SQL Server 2008. Both of these instances require you to run setupx64.bat.

Solution

Run setupx64.bat to create the stored procedure. For more information, see Double Action PIPAutomation Orchestration.

To run the BTARN End to End scenario on Windows Server 2003/2008,64-bit Windows Operating System (OS), Internet Information Services Manager 6.0/7.0.

1. Enable the BTARN Application Pools for 32 bit.

2. Add a HTTP Handler for *.dll refering the IsapiModule Filters.

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft. All rights reserved.