"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
Anonymous
June 30, 2014
Thank you for your help. I was struggling with this error for 3 days. It really helps.Anonymous
July 01, 2014
This is applicable to Biztalk 2009 also the steps solve the problem on BT 2009 also,Anonymous
July 02, 2014
Thank you. I updated the post to include BizTalk 2009.Anonymous
July 31, 2014
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. KB2973351 KB2973201 KB2962872 KB2961072 KB2871997Anonymous
August 05, 2014
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.Anonymous
August 10, 2014
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 MSIAnonymous
August 21, 2014
Thanks for the fix, it gets past the issue, but now it throws error 1309. Error reading from file... on several files including schemas.Anonymous
August 21, 2014
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.Anonymous
October 16, 2014
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.Anonymous
November 07, 2014
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.Anonymous
December 03, 2014
The comment has been removedAnonymous
December 04, 2014
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?Anonymous
December 04, 2014
Guys, 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. KB2973351 KB2973201 KB2962872 KB2961072 KB2871997 KB2982378 KB3000869 KB2991963 KB3005607 KB3006226 KB3010788 KB3011780 KB2979570 KB2840631 KB2978120 KB3003743 KB2972100 KB2861191 KB2832414 KB2861698 KB2973112 KB2992611 KB3000061 KB2987107 KB2984976 KB2984972 KB2977292 KB2968294 KB2937610 KB289484v2 KB2943357 KB2993958 KB3002885 KB3003057 KB953196Anonymous
December 05, 2014
Thank you, gcooper. After uninstalling the updates as you recommended, I was able to successfully install the HL7 accelerator.Anonymous
December 12, 2014
Microsoft should release a hotfix for this since BizTalk 2010 is still used widely. Installing HL7 accelerator is becoming an issue every dayAnonymous
December 21, 2014
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.Anonymous
December 26, 2014
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. ThanksAnonymous
December 26, 2014
Clarification on earlier post> system setup>BizTalk Server 2013 R2, Window Server 2012 R2. Sorry for mis-stated. Thank you for your guidance.Anonymous
December 26, 2014
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.Anonymous
January 13, 2015
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.Anonymous
March 08, 2015
The comment has been removedAnonymous
March 24, 2015
The comment has been removedAnonymous
April 22, 2015
The comment has been removedAnonymous
April 22, 2015
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 pauseAnonymous
May 05, 2015
Thank you for the script! It solved the issue for me with BizTalk Server 2010 on Windows Server 2008 R2.