iT Synergy Blogs

Growing Innovation - Soluciones a problemas reales

Copyright © 2025 · iT Synergy·

BAM Errors Could not load file or assembly ‘Microsoft.BizTalk.Bam.Portal’
BAM Errors Could not load file or assembly ‘Microsoft.BizTalk.Bam.Portal’ avatar

By Leave a Comment

BAM Installation Notes.

I want to public some errors that I get when I made the configuration of the feature BAM with BizTalk 2010.

  • BAM ERROR – Could not load file or assembly ‘Microsoft.BizTalk.Bam.Portal’ or one of its dependencies. Strong name signature could not be verified.  The assembly may have been tampered with, or it was delay signed but not fully signed with the correct private key. (Exception from HRESULT: 0x80131045)

In the event viewer show this

Event code: 3008

Event message: A configuration error has occurred.

Event time: 12/07/2011 01:19:55 p.m.

Event time (UTC): 12/07/2011 06:19:55 p.m.

Event ID: 7e81636267fe4bb58d4dc308137f315e

Event sequence: 1

Event occurrence: 1

Event detail code: 0

Exception message: Could not load file or assembly ‘Microsoft.BizTalk.Bam.Portal, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35’ or one of its dependencies. Strong name signature could not be verified.  The assembly may have been tampered with, or it was delay signed but not fully signed with the correct private key. (Exception from HRESULT: 0x80131045)

 

Solution: After hours of try to solve this,we figured it out, the copy of our BizTalk 2010 was corrupted so we opted to copy this ‘Microsoft.BizTalk.Bam.Portal.dll from other installation with the BAM portal working with the same version, we copy and it work fine.  You can also get a fresh copy of BizTalk Server 2010 and reinstall or repair BizTalk BAM.

 

  • BAM ERROR USER RIGHTS Then the problem was the permissions for the user’s, apparently  BAM  didn’t assign the right permissions to the user BAM management, so I had to gave to the user the right permission, in a command console I ran this commands.

With bm.exe I granted the permissions, replace domain name of the view and server name.

  • bm.exe add-account -Accountname:domain\user – view:ExcALL -Server:Srvtest
  • bm.exe add-account -Accountname:domain\user – view:ExcByApplication -Server: Srvtest
  • bm.exe add-account -Accountname:domain\user – view:ItineraryView -Server: Srvtest

Cumulative Update 2 for BizTalk 2010 and BizTalk Adapter Pack (BAP), also CU3 for BizTalk 2009 and CU2 for BizTalk Adapter Pack 2.0
Cumulative Update 2 for BizTalk 2010 and BizTalk Adapter Pack (BAP), also CU3 for BizTalk 2009 and CU2 for BizTalk Adapter Pack 2.0 avatar

By Leave a Comment

The BizTalk CRT(Customer Response) Team has made a great effort by quickly addressing all the errors on BizTalk 2010 and its adapters, now they deliver, 3 months after the first CU1 for BizTalk 2010 and CU1 for BAP 2010, the CU2 de BizTalk 2010 and CU2 de BizTalk Adapter Pack.

The most outstanding cumulative updates are:

[Read more…]

Error Setup Host Instance in a Cluster with SSO
Error Setup Host Instance in a Cluster with SSO avatar

By Leave a Comment

The installation had 4 servers with BizTalk server 2010, 2 for cluster and 2 for NLB, after installing BizTalk on each server, and setup the SSO, we attempted to create the host instances for the BizTalk group and the started to test the BizTalk cluster resources. When we tried to switch the active node,  we get this error:

The Enterprise Single Sign-On Service service terminated unexpectedly.  It has done this 12 time(s).

The Enterprise Single Sign-on delay about 15 minutes changing the node in the cluster, also In the Event Viewer shows another error about the DTC:

Failed trying to get the state of the cluster node: NODE-1.The error code returned: 0x80070005

After searching and working with the team we found a solution:

The explain you can found it here   http://msdn.microsoft.com/en-us/library/dd897475(v=BTS.10).aspx

I made a mistake creating a host instance non cluster, for both members of the cluster failover. We tested the failover with the host instances stopped, and the failover worked fine.

In this type of installation, we are using cluster a BizTalk host and the SSO master secret server on the same Windows Server cluster (Windows Server 2008 R2). We created a host with their hosts instances and then make cluster host, and worked fine.

Something that are obvious make you lose a lot of time, you don’t see it right away, so maybe this help.