BAM Hotfix Event ID 14014 for X64 bit Servers

Home Page › Forums › BizTalk 2004 – BizTalk 2010 › BAM Hotfix Event ID 14014 for X64 bit Servers

Viewing 2 reply threads
  • Author
    Posts
    • February 22, 2010 at 3:53 PM #24270
      community-content

        Hello, we are experiencing event log erros 14014.  This link is for X86 machines only I cannot seem to find a hotfix for X64.  Does anyone know how to resolve this on a x64 bit machine?  The erros are constant and some BAM events are not firing.

        Here is the error as stated on http://support.microsoft.com/kb/969217

        Event Type: Error
        Event Source: Bam
        Event Provider
        Event Category: None
        Event ID: 14014
        Description:
        Retrieving updated events from bam db. Encountered error: System.Data.SqlClient.SqlException: Transaction (Process ID <number>) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) …

         

        Thanks!

      • February 23, 2010 at 12:13 PM #24279
        community-content

          I’m starting to think MS missed this fix for the x64?

        • February 23, 2010 at 12:33 PM #24280
          community-content

            Hi,

             

              Here’s an explanation from Microsoft about 64-bit support:

             

            http://msdn.microsoft.com/en-us/library/aa560166(BTS.10).aspx

             

               Daniel.

             

            • February 23, 2010 at 1:25 PM #24281
              community-content

                Thanks for that interesting link Daniel.  I marked it in my favorites although I’m not sure it solves my problem.

                I’m getting 100’s of Errors in my event viewer.  Right now, I’m combing through all Hot Fixes for R2 to see if it’s included in a cumalative Hot Fix.

                Thanks!

                • February 25, 2010 at 2:41 PM #24292
                  community-content

                    Just put in a call to Microsoft and this hotfix is for both 32 and 64 bit machines since it’s managed code.  I’m getting “installer terminated prematurely” and still cannot get this to install. 

                    Error log around the error looks like this…

                    02/25/10 15:11:03 DDSet_Exit: CMsHelpObject destructor
                    MSI (s) (18:44) [15:11:03:819]: Executing op: ProgressTotal(Total=2,Type=1,ByteEquivalent=1300000)
                    MSI (s) (18:44) [15:11:03:819]: Executing op: ServiceControl(,Name=WinMgmt,Action=2,Wait=1,)
                    MSI (s) (18:44) [15:11:04:756]: Internal Exception during install operation: 0xc00000fd at 0x0000000077EF3CB2.
                    MSI (s) (18:44) [15:11:04:756]: WER report disabled for non-console install.
                    MSI (s) (18:44) [15:11:04:756]: Internal MSI error. Installer terminated prematurely.

                    MSI (s) (18:44) [15:11:07:256]: MainEngineThread is returning 1603
                    MSI (s) (18:44) [15:11:07:256]: Destroying RemoteAPI object.
                    MSI (s) (18:B0) [15:11:07:256]: Custom Action Manager thread ending.
                    Installer terminated prematurely.
                    MSI (c) (A4:68) [15:11:04:756]: Font created.  Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg

                    MSI (c) (A4:FC) [15:11:07:272]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
                    MSI (c) (A4:FC) [15:11:07:272]: MainEngineThread is returning 1603
                    === Verbose logging stopped: 2/25/2010  15:11:07 ===

                    [02/25/10 15:11:07] Operation succeeded.
                    [02/25/10 15:11:07] Process exit code is 1603.
                    [02/25/10 15:11:07] Operation failed. Error code is 1603.

                    Has anyone seen this before?

                    Thanks!

                    • February 26, 2010 at 5:29 PM #24296
                      community-content

                        Just to close this out – I found out the issue was disabling the Antivirus, Rebooting, and then run the Hotfix.

                         

                        Hope this helps someone ; )

              • Author
                Posts
              Viewing 2 reply threads
              • The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.