BizTalk troubleshooting

• BAM Web Services and SQL Server mixed mode authentication : http://blogs.msdn.com/tihot/archive/2006/06/13/630313.aspx


• BAM troubeshooting
  
  Please logon local to your BAM Portal server and check the following:

1. Open IE and navigate to the BAM Portal for example like this: http://localhost/bam/BamManagementService/BamManagementService.asmx
   If it works, your web service is working.


2. Click: GetViewSummaryForCurrentUser


3. Press the Invoke button, displayed in the upper left corner
   
   
   
   1. If it works, your web service is able to talk to the database
      
   
   
   2. If it does not work, check the web.config file under for example
      C:\Program Files (x86)\Microsoft BizTalk Server 2006\BAMPortal\BAMManagementService
      

Now look for the following entry:

  <appSettings>
     <add key="BamServer" value="SKLAB5026" />
    <add key="BamDatabase" value="BAMPrimaryImport" />
  </appSettings>

Make sure the correct database server and name is entered. Also check the web.config file of the BAMQueryService as well.

• BizTalk Adapter Package version
  

  ProductVersion for that adapter (most probably under): "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\BizTalk Adapter.."
  



• How TPE log the data to PrimaryImport DB
  

  To be more precise, TPE utilize OrchestrationEventStream to log data to the messagebox.
  

  Later, the TDDS writes data to the PrimaryImport database…
  



• About DehydrationFailedException: The string '' is not a valid AllXsd value.
  

  This is a serialization issue. While dehydrating, engine tries to serialize objects – apparently in the orchestration code there are some objects being used which are not serializable. We advice to use Atomic Shape in such cases so that orchestration does not dehydrate.
  



• Set up a Windows Server Cluster on Hyper-V virtual machines using iSCSI for storage (see http://blogs.technet.com/pfe-ireland/archive/2008/05/16/how-to-create-a-windows-server-2008-cluster-within-hyper-v-using-simulated-iscsi-storage.aspx)
  


• You can see the whitepaper for the BizTalk Adapter pack to get an idea of what the supported scenarios are.
  


• Since everything is SSL-encrypted I used the .Net tracing from here: http://blogs.msdn.com/dgorti/archive/2005/09/18/471003.aspx


• How to monitor BizTalk performent: http://msdn.microsoft.com/en-us/library/aa578302.aspx


• Creating, Updating, and Deleting a Host Instance Using WMI: http://msdn.microsoft.com/en-in/library/aa560467(en-us).aspx


• BizTalk performent: http://www.unisys.com/eprise/main/admin/corporate/doc/BL100200.pdf


• Keperos in Sharepoint: http://www.windowsecurity.com/articles/Kerberos-Sharepoint-Environment.html


• BizTalk Server Database Optimization: http://msdn.microsoft.com/en-us/library/bb743398.aspx