Ben ([info]dojothemouse) wrote,
@ 2006-06-27 14:43:00
Previous Entry  Add to memories!  Tell a Friend!  Next Entry
Entry tags:embarrassing, fyi, unglued

thank google
So, I was trying to deploy an SSIS Package via the Package Installation Wizard:

Could not save the package C:\Documents and Settings\bdonley\My Documents\Playground_01\Playground_01\bin\Deployment\cmdata.dtsx to SQL Server BKAPLAN5 Additional Information: No description found

Could not save the package "C:\Documents and Settings\bdonley\My Documents\Playground_01\Playground_01\Playaround_01\bin\Deployment\cmdata.dtsx" to SQL Server "BKAPLAN5".
Additional Information:
-> No description found

Exception details: System.BadImageFormatException: No description found
at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServer(Package package, IDTSEvents events, String serverName, String serverUserName, String serverPassword)
at Microsoft.SqlServer.Dts.Deployment.DtsInstaller.SavePackageToSqlServer(WizardInputs wizardInputs, String packagePassword, Boolean bUseSeverEncryption, String serverName, String userName, String password, String packageFilePath, List`1 configFileNames)
at Microsoft.SqlServer.Dts.Deployment.DtsInstaller.InstallPackagesToSqlServer(WizardInputs wizardInputs)
No dice.

I tried importing the package via "Import Package" in Microsoft SQL Server Management Studio:


Invalid access to memory location. (Exception from HRESULT: 0x800703E6) (Microsoft.SqlServer.ManagedDTS)
Invalid access to memory location. (Exception from HRESULT: 0x800703E6)
(Microsoft.SqlServer.ManagedDTS)

Program Location:

at Microsoft.SqlServer.Dts.Runtime.Application.SaveToDtsServer(Package pPackage, IDTSEvents pEvents, String sPackagePath, String sServerName)
at Microsoft.SqlServer.Dts.ObjectExplorerUI.ImportPackageAsAction.ImportPackage(ImportPackageAsForm dlg)


No dice.

Oren Ellenbogen had the answer I was looking for, in one little comment I almost didn't notice:
this problem occurs when MSXML registration became corrupted

The following commands should fix this problem:

regsvr32.exe msxml3.dll
regsvr32.exe msxml6.dll


hope that it will help.
good luck.
Obviously. And it does work, even though I was rubbing up on this bug through a completely different venue than Oren Ellenbogen. I wasn't sure if the exception was being thrown by my dev tools or by the server, so I ran those two commands on both machines. Just to be sure. FYI. I just thought this bullshit deserved to be on the internet. You know, for posterity.

P.S. Due to spam, I'm screening comments here & not getting email updates about them. If you'd really like to discuss this particular problem in a comment here, make the comment & then email me separately.

(Post a new comment)


[info]p0llux
2006-06-27 11:35 pm UTC (link)
i like pancakes

(Reply to this)

Graarr
(Anonymous)
2006-09-26 02:42 pm UTC (link)
Amen to that, bro. Dontcherjustlurve those super-obscure problems and their oh-so-obvious fixes? Cheers for the post...

(Reply to this)


(Anonymous)
2006-10-11 03:22 pm UTC (link)

I ALSO tried importing a package via "Import Package" in Microsoft SQL Server Management Studio:

I received the same error as above:

Invalid access to memory location. (Exception from HRESULT: 0x800703E6) (Microsoft.SqlServer.ManagedDTS)

------------------------------
Program Location:

at Microsoft.SqlServer.Dts.Runtime.Application.SaveToDtsServer(Package pPackage, IDTSEvents pEvents, String sPackagePath, String sServerName)
at Microsoft.SqlServer.Dts.ObjectExplorerUI.ImportPackageAsAction.ImportPackage(ImportPackageAsForm dlg)

I tried the suggested Fix:

regsvr32.exe msxml3.dll
regsvr32.exe msxml6.dll

I ran these commands both on my client workstation
and on the SQL Server machine.

When I tried to import the package I still got the same error.

Is there something I am missing?



(Reply to this) (Thread)

[info]dojothemouse
2006-10-11 04:32 pm UTC (link)
No, I don't think there is anything you're missing. That's really too bad.

I typically don't import packages. Make sure that the Package Installation Wizard is also giving you that error. I never checked whether package importing worked after I did the fix.

If that's no good, I'd MD5 those DLLs on both your client & your server, and I'd explicitly unregister both of them before reregistering. "regsvr32.exe /u" or whatever.

Also, you might want to email Shimon Krokhmal, since he was the first person to suggest the fix:

http://www.lnbogen.com/CommentView,guid,6b18f655-e823-43d6-9e04-f51adf93e9dc.aspx#commentstart

(Reply to this) (Parent)
fixes other problems too
(Anonymous)
2007-05-11 12:21 pm UTC (link)
Re-registering these dlls fixes a host of other problems too, namely

(1) Attempting to copy and paste an SSIS in SSIS designer fails and displays a message along the lines of "unable to serialize object"

(2) Inability to call a child package from a parent package that is called from a .net app using the Dts runtime objects.

Note that you'll need to restart SQLServer Management Studio for the changes to take effect.

Thank you for posting this. I was dumbfounded by the copy/paste problem for weeks.

(Reply to this) (Thread)
Re: fixes other problems too
[info]dojothemouse
2007-05-11 06:00 pm UTC (link)
Cool. Thanks. If anyone can get me the exact text of that error message, this page might be more useful for future googlers.

(Reply to this) (Parent)(Thread)
Re: fixes other problems too
(Anonymous)
2007-08-10 01:50 am UTC (link)
Well, I found this page by googling on the error message (I was having trouble copy-pasting tasks in the BI designer.)

The error message I was searching for was:
"SSIS Designer could not serialize the SSIS runtime objects"

which was the exact text of the error.

Since I found this page by googling for that text, I'm not sure this will help that much, but I just wanted to send you the exact error, and also note that the regsvr commands you suggested certainly fixed the problem for me.

(Reply to this) (Parent)
Thank you so much!!!
(Anonymous)
2008-11-10 02:21 pm UTC (link)
My problem was almost same, just to help someone having same problem I am pasting here the exact error statement I am getting. I was trying to create package in SSIS Import Export Wizard and in the step saving, I got the following error. And by just applying these two commands at both server and client it worked :)


===================================

No such interface supported


------------------------------
Program Location:

at Microsoft.SqlServer.Dts.Runtime.Wrapper.ApplicationClass.SaveToSQLServer(IDTSPackage90 Package, IDTSEvents90 pEvents, String ServerName, String ServerUserName, String ServerPassword)
at Microsoft.SqlServer.Dts.DtsWizard.Execute.DoFileSaveStep(Exception& ex)


Regards,
Divya
divya@hea.biz

(Reply to this) (Thread)
Re: Thank you so much!!!
[info]dojothemouse
2008-11-12 05:37 am UTC (link)
You are quite welcome :)

I'm very glad this helped.

(Reply to this) (Parent)

Create an Account
Forgot your login or password?
Login w/ OpenID
English • Español • Deutsch • Русский…