Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

FIX: "Unable to Verify Message Signature" Error Message When BizTalk Server Tries to Process a Signed RosettaNet Message


View products that this article applies to.

Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 (http://support.microsoft.com/kb/256986/ ) Description of the Microsoft Windows Registry

↑ Back to the top


Symptoms

After you install Microsoft BizTalk Server 2002 Service Pack 1 (SP1), you may receive one of the following error messages from BizTalk Server when it tries to process a signed RosettaNet message:

Message 1
An error occurred in BizTalk Server.

Details:
------------------------------
[0x00000000] Security: Error occurred Unable to verify message signature.
[0x80004005] Unspecified error
[0x1730] Suspended Queue ID: "{7A8AC6BB-EEA6-45D2-A500-F036A7E11FA8}"
[0x80004005] Unspecified error
Message 2
An error occurred in BizTalk Server.

Details:
------------------------------
[0x00000000] Security: Error occurred Bad message signature.
[0x80004005] Unspecified error
[0x1730] Suspended Queue ID: "{7A8AC6BB-EEA6-45D2-A500-F036A7E11FA8}"
[0x80004005] Unspecified error

↑ Back to the top


Resolution

Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
   Date         Time   Version     Size     File name
   ------------------------------------------------------
   06-Nov-2003  04:55  3.0.2510.0  553,232  Ciscore.dll
   06-Nov-2003  04:55  3.0.2510.0  430,352  Cisengine.dll
Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.Important After you install this hotfix, you must create a DWORD value ScanForMIMEHeader in the registry under the following registry key:
HKLM\SYSTEM\CurrentControlSet\Services\BTSsvc
Set this DWORD value to 0.

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.

↑ Back to the top


More information

For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
824684� Description of the Standard Terminology That Is Used to Describe Microsoft Software Updates

↑ Back to the top


Keywords: kbautohotfix, kbhotfixserver, kbhotfixserver, kbqfe, kberrmsg, kbqfe, kbfix, kbbug, kbqfe, KB831147

↑ Back to the top

Article Info
Article ID : 831147
Revision : 7
Created on : 11/15/2007
Published on : 11/15/2007
Exists online : False
Views : 412