"The handle is invalid" error installing HL7

When installing the HL7 Accelerator on BizTalk Server 2009, BizTalk Server 2010, or BizTalk Server 2013, the following error occurs:

The specified account “Domain\AccountName” is invalid. Error code: The handle is invalid.


Resolution – Updated October 1, 2015

BizTalk 2013

Install HL7 using the updated Microsoft BizTalk 2013 Accelerator for HL7.msi file (attached). No updates need to be uninstalled.


BizTalk 2010 / BizTalk 2009

1. Uninstall the 2871997 security update and any post-2871997 updates. The comments in this blog post include a wusa.exe /uninstall script that will save you time.

2. Restart the server.

3. Install HL7

4. Reinstall the updates.

This is now documented in KB article 2988484


January 13, 2015 Update

Question: Why is there no fix for BizTalk 2010?

Answer: The accelerator fixes are not cumulative. When the attached 2013 fix was tested with the existing (and only) 2013 HL7 hotfix, there were no issues and the hotfix still fixed <whatever bug it resolved>. This 2013 fix is the baseline for newly-created/yet-to-be-created HL7 hot fixes. When the 2010 fix was tested, it broke most of the 2010 HL7 hot fixes (about 15). Meaning, whatever bugs were resolved would be broken again after installing this 2010 fix. As a result, the current resolution on 2010 and 2009 is the only resolution.


Comments (25)

  1. Raj says:

    Thank you for your help. I was struggling with this error for 3 days. It really helps.

  2. Prasad B says:

    This is applicable to Biztalk 2009 also  the steps solve the problem on BT 2009 also,

  3. Thank you. I updated the post to include BizTalk 2009.

  4. Gnani says:

    I had the same issue today and after uninstalling the following windows security updates, i am able to install the Biztalk Server 2010 HL7 accelerator successfully. You can re-install these updates after the HL7 accelerator installation is complete.






  5. Thank you for the updates. Attached to this blog post is an updated HL7 MSI file. Installing HL7 using this updated file should resolve the problem on BizTalk 2013.

  6. Prasad B says:

    It would help  if you can create modiied MSI for BT2009 also, I tried using your modified MSI on BT 2009 installtion it dose not go through , or publish the steps to create such an MSI

  7. Sri Kondeti says:

    Thanks for the fix, it gets past the issue, but now it throws error 1309. Error reading from file… on several files including schemas.

  8. Sri Kondeti says:

    The Msi is looking for HL7 schemas 2.5 and 2.5.1 these folders do not exist in the downloaded iso image from Microsoft website. I am missing something here? By the way we have downloaded the image from Volume Licensing Service Center. Please help.

  9. Paul C says:

    We had the same issue and looked at the KB2871997 article, and saw that this patch includes KB2982378. We uninstalled KB2982378, rebooted, and we were then able to install the HL7 Accelerator.

  10. Glenn C says:

    I'm very surprised MS never put out a patch to get past this error on 2010. So now, on 2010, we have to uninstall 5  windows updates just to get the install to work. Getting this done when you work for a large Healthcare company is very problematic and a big hold-up when you are trying to get this install done in a timely manner.

  11. Asle J says:

    We have 2 different biztalk 2010 installations (windows 2008 R2) – test and prod. In the test we had to uninstall nearly all windows security patches (>50) to get the hl7-installation to work. Now we are going to install HL7 in produktion. Is there a way to install HL7 to avoid uninstalling windows patches?

  12. rpara says:

    We are building out a new QA environment (BizTalk 2010 , Windows 2008 R2 Enterprise) and are experiencing the same issue when attempting to install BizTalk 2010 Accelerator for HL7.  We uninstalled the security updates as recommended by Gnani and checked the account privileges as recommended in other posts to no avail. The software was installed successfully 3 years ago on our other servers. We have 91 Windows Security Updates on the server and are not able to determine which one(s) are causing the issue. Is there any other solution?

  13. gcooper says:


    we just got the BizTalk 2010 HL7 accelerator installed yesterday on two servers. We had to uninstall several Windows updates. We tried to pinpoint which updates are causing the problem, but were unable to narrow the list much. Along with the original 4 mentioned earlier in the post here is a list of the other unpdates we uninstalled. It's a bit long, but it worked. Uninstalling these also worked for a friend of mine at another company this week.




































  14. rpara says:

    Thank you, gcooper. After uninstalling the updates as you recommended, I was able to successfully install the HL7 accelerator.

  15. Vikas Bhardwaj says:

    Microsoft should release a hotfix for this since BizTalk 2010 is still used widely. Installing HL7 accelerator is becoming an issue every day

  16. Thank you for the input. I've updated the post to reflect the Security Update list. As an FYI, I removed some comments due to the updated post. If the KB list changes, please add it to the comments.

  17. Julie Chan says:

    Using attached msi>was successful in passing the account setup, successfully passed the Database connection to establish BTAHL7 test. but was stuck on that screen, the next button does not work… (system BizTalk 2013, WinServer 2013 R2).. Please advise. Thanks

  18. Julie Chan says:

    Clarification on earlier post> system setup>BizTalk Server 2013 R2, Window Server 2012 R2. Sorry for mis-stated. Thank you for your guidance.

  19. Julie Chan says:

    Update on earlier post> issue resolved> was able to locate the accelerator setup files within BizTalk program folder. Installation completed with no errors. Thank you.

  20. Desmond says:

    Thanks for posting this.  I was running into this issue for 4 days.  Figured I had nothing to loose and tried this and worked like a charm.  Great job and thank you.

  21. criccrazy says:

    Hi there,

    I am trying to install HL7 accelarator and its giving me following error:

    Product: Microsoft BizTalk 2013 Accelerator for HL7 — Error 1308.Source file not found: C:Program Files (x86)Microsoft BizTalk Server 2013Pipeline ComponentsMicrosoft.Solutions.BTAHL7.HL72fDasm.dll.  Verify that the file exists and that you can access it.

    I am getting this error just after you get "copying files…" message on the installer window. Looks like its not able to write the dll to pipeline folder. But I have tried giving full permissions to the account with biztalk administrator privileges. Its the same accont which succesfully used for logging services earlier in the installation process

    Firstly I got "handle is invalid " message when installing from the biztalk installation disc. So used the msi from in here, which did away with "handle is invlaid" error. But now get the above error.

    Any idea what this could be?

    I got windows 8.1 pro N with biztalk 2013 and therefore sql 2012

    Thanks in advance


  22. Punani says:

    For 2010, I uninstalled the updates and rebooted as listed; however, I still get an Handle is Invalid error. I tried the attached 2013 msi, and the msi gets past the Handle is Invalid; however, it never goes past the database test dialog.

    I'm curious to know how the others in here installed HL7 for 2010. I'm running 2008 R2 SP1 Standard 64bit

  23. MarcusP says:


    I still got the Handle is invalid error after uninstallation of the listed updates. However, after uninstallation of additional updates I was able to continue with the HL7 Accelerator installation. I've not pinpointed out exactly the update(s) that caused the problem. I did a bat script to automate the uninstallation, it can be helpful for you too. Note that  I had to split it into two posts.

    rem Part 1/2:

    echo Uninstalling, this will take some time…

    wusa /uninstall /kb:2973351 /norestart /quiet

    wusa /uninstall /kb:2973201 /norestart /quiet

    wusa /uninstall /kb:2962872 /norestart /quiet

    wusa /uninstall /kb:2961072 /norestart /quiet

    wusa /uninstall /kb:2871997 /norestart /quiet

    wusa /uninstall /kb:2982378 /norestart /quiet

    wusa /uninstall /kb:3000869 /norestart /quiet

    wusa /uninstall /kb:2991963 /norestart /quiet

    wusa /uninstall /kb:3005607 /norestart /quiet

    wusa /uninstall /kb:3006226 /norestart /quiet

    wusa /uninstall /kb:3010788 /norestart /quiet

    wusa /uninstall /kb:3011780 /norestart /quiet

    wusa /uninstall /kb:2979570 /norestart /quiet

    wusa /uninstall /kb:2840631 /norestart /quiet

    wusa /uninstall /kb:2978120 /norestart /quiet

    wusa /uninstall /kb:2972100 /norestart /quiet

    wusa /uninstall /kb:2861191 /norestart /quiet

    wusa /uninstall /kb:2832414 /norestart /quiet

    wusa /uninstall /kb:2861698 /norestart /quiet

    wusa /uninstall /kb:2973112 /norestart /quiet

    wusa /uninstall /kb:3000061 /norestart /quiet

    wusa /uninstall /kb:2987107 /norestart /quiet

    wusa /uninstall /kb:2984976 /norestart /quiet

    wusa /uninstall /kb:2977292 /norestart /quiet

    wusa /uninstall /kb:2968294 /norestart /quiet

    wusa /uninstall /kb:2937610 /norestart /quiet

    wusa /uninstall /kb:2943357 /norestart /quiet

    wusa /uninstall /kb:2993958 /norestart /quiet

    wusa /uninstall /kb:3002885 /norestart /quiet

  24. MarcusP says:

    rem Part2/2:

    wusa /uninstall /kb:953196 /norestart /quiet

    wusa /uninstall /kb:3046482 /norestart /quiet

    wusa /uninstall /kb:3046306 /norestart /quiet

    wusa /uninstall /kb:3046269 /norestart /quiet

    wusa /uninstall /kb:3045999 /norestart /quiet

    wusa /uninstall /kb:3045685 /norestart /quiet

    wusa /uninstall /kb:3042553 /norestart /quiet

    wusa /uninstall /kb:3038314 /norestart /quiet

    wusa /uninstall /kb:3037574 /norestart /quiet

    wusa /uninstall /kb:3002657 /norestart /quiet

    wusa /uninstall /kb:3046049 /norestart /quiet

    wusa /uninstall /kb:3039066 /norestart /quiet

    wusa /uninstall /kb:3035132 /norestart /quiet

    wusa /uninstall /kb:3035131 /norestart /quiet

    wusa /uninstall /kb:3035126 /norestart /quiet

    wusa /uninstall /kb:3034344 /norestart /quiet

    wusa /uninstall /kb:3033929 /norestart /quiet

    wusa /uninstall /kb:3033889 /norestart /quiet

    wusa /uninstall /kb:3032359 /norestart /quiet

    wusa /uninstall /kb:3032323 /norestart /quiet

    wusa /uninstall /kb:3030377 /norestart /quiet

    wusa /uninstall /kb:3031432 /norestart /quiet

    wusa /uninstall /kb:2852386 /norestart /quiet

    wusa /uninstall /kb:3029944 /norestart /quiet

    wusa /uninstall /kb:3023562 /norestart /quiet

    wusa /uninstall /kb:3021952 /norestart /quiet

    wusa /uninstall /kb:3013455 /norestart /quiet

    wusa /uninstall /kb:3004375 /norestart /quiet

    wusa /uninstall /kb:3004361 /norestart /quiet

    wusa /uninstall /kb:3000483 /norestart /quiet

    wusa /uninstall /kb:3023266 /norestart /quiet

    wusa /uninstall /kb:3022777 /norestart /quiet

    wusa /uninstall /kb:3021674 /norestart /quiet

    wusa /uninstall /kb:3014029 /norestart /quiet

    wusa /uninstall /kb:3019978 /norestart /quiet

    wusa /uninstall /kb:3013126 /norestart /quiet

    wusa /uninstall /kb:3012176 /norestart /quiet

    wusa /uninstall /kb:3008923 /norestart /quiet

    rem These didn't seem to be uninstalled when the quiet switch was used

    wusa /uninstall /kb:3003743 /norestart

    wusa /uninstall /kb:2992611 /norestart

    wusa /uninstall /kb:2984972 /norestart

    wusa /uninstall /kb:3003057 /norestart

    echo Done!

    echo Please check manually if KB289484v2 is installed

    echo Don't forget to restart to finish the uninstallation


  25. sandbrock says:

    Thank you for the script!  It solved the issue for me with BizTalk Server 2010 on Windows Server 2008 R2.