Wednesday, March 21, 2012

MSXML6.dll fails to register when calling SSIS from win service

Has anyone encountered this error? I get it when I run the installer (c#). I have seen a few posts on google and msdn, but still can't get past the error. I have tried uninstall/resinstalling the parser, registering from the command line, setting the property of the interop to "donotregister" and others with no luck.

Any ideas?

Thanks,
LeeOK got past the installation - but the package shows to fire but doesn't. Might be permissions; I am going to try and point the SSIS package to a local set of folders.

I think the problem was the "donotregister" property of the .dll. The SSIS tools, as you know, must be installed on your local workstation as well.

Lee|||Where are all of the 'experts' out here? I've posted five times out here and haven't received a response that remotely touches anything that I've ever come up with. Indifferent

Oh well.

Still at the same place. I created another ssis package and pointed it to the local folders and ran via a console app and it works fine. Most likely permissions. Someone suggested turning logging on the package. Not sure which logging they were referring to.

Thanks,
Lee|||

Lee Everest wrote:

Where are all of the 'experts' out here? I've posted five times out here and haven't received a response that remotely touches anything that I've ever come up with.

Oh well.

Still at the same place. I created another ssis package and pointed it to the local folders and ran via a console app and it works fine. Most likely permissions. Someone suggested turning logging on the package. Not sure which logging they were referring to.

Thanks,
Lee

Package configurations. Right click on the control flow, select logging.

No comments:

Post a Comment