Jim Zimmerman

So today I ran into my first real gotcha since switching every machine I have at work and home to Vista.  

For about an hour today, a fellow developer and I could not figure out why an SSIS package with a script component was getting this error on the script control:

[Script Component [311]] Error: System.BadImageFormatException: An attempt was made to load a program with an incorrect format. (Exception from HRESULT: 0x8007000B) at Microsoft.VisualBasic.Vsa.VsaEngine.Compile() at Microsoft.SqlServer.VSAHosting.Runtime.LoadSource(String project) at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.CreateUserComponent()

I did a google search "0x8007000B ssis" and was lucky, only one page in result and it was the answer I had been looking for.  Not the one I wanted, but what I needed to know on the following post.

This is a known issue, which (together with other Vista compatibility issues) will be fixed by SQL 2005 SP2 early next year. For now, please don't use Vista machines for SSIS development.
P.S. There is a preview (November CTP) release of SP2, it fixes many Vista compatibility problems, but it does not fix this issue yet.

---

Michael Entin, IS team // This posting is provided "AS IS" with no warranties, and confers no rights

Ok, well at least we know now.  We still used SSIS Development the rest of the day, but had to be creative on how to change some of the data with clean up SQL after the integration.  I still love SSIS and can wait for a fix.  But I hope it is soon.  I am sure it is very tough work being a developer at Microsoft right about now.  They have to rush to make all these fixes and everybody is watching.  Good luck guys!