Tuesday, November 04, 2008

BizTalk Document Tracking no longer works after the installation of the Microsoft Security Advisory 956391

If you follow the following links:

You might think that the Microsoft Support Team have done a great job: you have a BizTalk update (even for 2000) so the BizTalk Document Tracking works again after the installation of the Microsoft Security Advisory 956391!

But (there is always a "but"), what about the BizTalk Document Tracking running on your personal computer. It does not work, and you cannot install the BizTalk update since BizTalk is not installed on your personal computer (only on the server), sh@~+*&^%!

Here is what I have discovered, by comparing the registries of the server and my personal computer ;-)

  1. You should update your MSOWC.DLL to the latest version that has been installed on the server. This DLL should be located in "C:\Program Files\Microsoft Office\Office", and the version installed by the BizTalk Update should be "9.0.0.8966".
  2. Then, you should re-register the DLL, with the command << regsvr32 "C:\Program Files\Microsoft Office\Office\MSOWC.DLL" >>. You need to re-register because this new DLL clones the component {0002E530-0000-0000-C000-000000000046} (Microsoft Office Data Source Control 9.0) with a new CLSID {0002E533-0000-0000-C000-000000000046}.
  3. Then, with the registry editor (regedit.exe), you should go to the key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{0002E530-0000-0000-C000-000000000046}", and add the string value "AlternateCLSID" with the value "{0002E533-0000-0000-C000-000000000046}".

The BizTalk Document Tracking should now work again on your personal computer, you’re welcome ;-)

Wednesday, September 17, 2008

Which account is used by the BizTalk Scriptor?

The BizTalk Scriptor AIC is using the account of the "BizTalk Server Interchange Application" COM+ application. (By the way, I have discovered it while making a "SubmitSync").