Continue reading »]]> 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: 0×80131045)

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: 0×80131045)

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

Continue reading »]]> 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: 0×80070005

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.

Continue reading »]]> la idea del laboratorio es simular el funcionamiento del cluster Failover en Windows, para esto vamos a utilizar

· Windows Server 2008

· VMWARE Workstation

· Windows Storage Server 2008

Caracteristicas Maquina Host

· 8 GB de RAM

· 300 GB DD

· I7  720 QM 1.6Ghz 4 nucleos

· Windows 7

· VMWAre Workstation

la idea es tener un entorno Windows configurado para esto debemos tener un controlador de dominio un Storage y Servidores

El Domain Controller debe tener Active Directory y el DNS configurados el Server con Windows Storage Server debe pertenecer al dominio que se configuro previamente en el controlador de dominio.

Los aspectos más importantes para los nodos del failover

· las maquinas deben ser iguales tanto en hardware como software

· dos conexion de RED una LAN y la Heartbeat

· acceso a un Storage(esto se puede emular mediante Windows Storage server o Freenas)

· pertenecer al mismo dominio.

Pasos de instalación

Para conectar los nodos a la Red hay que recordar que hay dos conexiones

Conexión LAN esta configuración la da el controlador de dominio un IP valida en el segmento de red definido.

Conexión Heartbeat, seleccionar una ip que no este en la misma subred o network que la conexión LAN o Pública ej:

Nodo 1  ip 10.10.10.10 mask 255.0.0.0

Nodo 2 ip 10.10.10.11 mask 255.0.0.0

El Storage configurado con Windows Storage Server 2008

1. Crear los Targets en el Server manager de Windows Storage Server 2008

2. Crear el Disco Virtual seleccionando los target previamente creados

3. Darle un Path valido, tamaño y descripcion

4. adicionar los ISCSI target a los cuales se les va a exponer los Discos

Para exponer estos discos a los nodos

1. Abrir Disk Management

2. Botón derecho sobre los discos y ponerlos online

3. Inicializar los Discos

4. Crear los volúmenes sobre los discos con sus respectivos nombres dependiendo en que se vayan a utilizar.

Ya cuando tenemos todos los recursos instalados y configurados podemos instalar el feature Failover Cluster

1. Abrir Server Manager. Click Start, click Administrative Tools, luego click Server Manager.

2. Click Adicionar Features.

3. Click en Failover Clustering checkbox.

5. Click Next.

6. Click Install.

7. Repetir estos pasos en el otro nodo del Cluster

Al momento de adicionar el Feature Cluster Failover ya podemos Validar la configuración del Cluster, es importante que en este paso todos los test nos salgan estado “Successful”, para minimizar errores futuros en configuración de servicios pasos

1. Click En Validate

2. Seleccionar Nodos

3. Run All Test

4. Revisar Reporte

5. En caso de error corregir y volver a correr el wizard validate y correr el test que fallo no todos los test.

Cuando ya tenemos bandera verde “all test have been  successful” podemos crear nuestro cluster

1. Click Create Cluster Wizard

2. Seleccionar Nodos

3. Ingresar nombre e IP Validos

4. Finalizar

En el cluster Fail over podemos configurar servicios o aplicaciones como: SQL, Exchange, Hyper V, File System Etc, dependiendo la necesidad, queria mostrarles lo basico y darles una idea de que es lo que deben tener.

por ultimo recomendaciones los errores mas comunes son

Heartbeat, la configuracion de la Red Privada

Active Directory la cuenta no posee los permisos para crear objetos en el dominio

SAN los discos no los reconocen los nodos una forma facil de hacerlo es mediante Windows Storage Server, si no pueden cofigurar un Freenas para simular una SAN.

al clonar Maquinas hay que cambiarles el SID se puede por me dio del sysprep.

mas informacion para crear FAilover Cluster con Windows 2008 server es un muy buen documento

http://www.microsoft.com/downloads/en/details.aspx?displaylang=en&FamilyID=176a89cd-1250-4670-8ff0-87b1c4c711af