SSIS 2005 not running after upgrading (32 bit, Windows XP to 64 bit Windows 7)

Question

I really need some help. Recently I went from using Visual Studio and SQL 2005 on a laptop (32bit system - Windows XP) to a desktop unit 64bit processor with Windows 7). SSIS on the laptop worked just fine and I could execute and open packages in SSIS; however, my new desktop unit will not even allow me to open a new package or run an existing package. As soon as I attempt to create a new SSIS project, I receive the following error: "An error prevented the view from loading. The specified module could not be found. (Exception from HResult:0x8007007E)(System Windows Forms).

SSIS won't allow me to view the control flow or data flow screens and if I attempt to run an existing package created with the SSIS wizard I receive the following error: SSIS package "Package1.dtsx" starting.
Information: 0x4004300A at Data Flow Task, DTS.Pipeline: Validation phase is beginning.
Error: 0xC0202009 at Package1, Connection manager "SourceConnectionExcel": SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. Error code: 0x80040154.
An OLE DB record is available.  Source: "Microsoft OLE DB Service Components"  Hresult: 0x80040154  Description: "Class not registered".
Error: 0xC020801C at Data Flow Task, Source - Without_Sample$ [1]: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER.  The AcquireConnection method call to the connection manager "SourceConnectionExcel" failed with error code 0xC0202009.  There may be error messages posted before this with more information on why the AcquireConnection method call failed.
Error: 0xC0047017 at Data Flow Task, DTS.Pipeline: component "Source - Without_Sample$" (1) failed validation and returned error code 0xC020801C.
Error: 0xC004700C at Data Flow Task, DTS.Pipeline: One or more component failed validation.
Error: 0xC0024107 at Data Flow Task: There were errors during task validation.
SSIS package "Package1.dtsx" finished: Failure.

I have tried changing the properties in the package to run in 32-bit mode; however, this does not work. I can run queries and import data in SQL Server Management Studios just fine, as well as run queries and reports in Visual Studios; however, I can't execute or create any package in Visual Studio with the new machine. Am I missing a needed system file in the new sysWOW64 folder? The IT person who installed the software isn't familiar with the program and doesn't know how to fix it either. I'm relatively new with using SSIS and really need some help on how to get this fixed. Any help you can offer would be greatly appreciated.

Answer 1

Have you tried this Project level setting?

In the Solution Explorer window, right-click on the project name and select Properties.

---

- Aalamjeet Rangi | (Blog)

Answer 2

I did try that but it didn't work. SSIS gives me an error if I even try to open up or create a package - it says the module or object isn't found. I'm new at SSIS but it would seem like there has to be some sort of issue with the system files it may be referencing, as it doesn't want to open up at all when I attempt to open or create a new project.

---

MelissaS

Answer 3

If the Development Studio environment does not even open then it is probably an installation issue. Possibly a DLL did not register properly. Could you take a look at the following forums where a similar issue is being discussed? You can also look for more responses by searching for "0x8007007e visual studio on windows 7" in your search engine.

http://support.microsoft.com/kb/978714

http://social.msdn.microsoft.com/Forums/sqlserver/en-US/0bcf22d6-adab-4595-b0d8-3a37ce7fbff3/2008-ssis-designer-stops-working-after-installing-vs11-dev-preview?forum=sqlintegrationservices

http://stackoverflow.com/questions/10460118/the-specified-module-could-not-be-found-exception-from-hresult-0x8007007e

---

- Aalamjeet Rangi | (Blog)

Answer 4

You are correct - there are files needed that were not installed. The forum threads you posted were very helpful. I plan to have the IT person reinstall the program and we'll go from there. Thanks so much for getting back to me and for your help.

Have a great rest of the week,

Melissa

---

MelissaS