Is there anyone out there that can help me - please! I'm about to put my head through a wall.
I used to be able to create SSIS packages in VS 05. It's been a while since I've done it, but when I went in the other day, it would let me - all I can do is get errors. It tells me an "error prevented the view from loading" when it opens in control flow (blank packages and ones I created before all this started) and I get this error :
"Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)) (System.Windows.Forms)"
If I go over to the Data Flow tab and there are no errors until I click "Click here to add a new Data Flow task", then I get this :
"Object reference not set to an instance of an object. (Microsoft.DataTransformationServices.Design)"
So... here's what I've tried.
Uninstalled and reinstalled VS 05 and SP1 (this was before I realized the problem was with SQL).
Uninstalled and reinstalled Office 2003 Web Tools.
Made sure all the MSXMLs were registered.
Uninstalled and reinstalled all SQL Servers and Tools/Components.
Made sure all SQL Services were running under Local Account
Made sure Integrated Services service was running.
Applied all SQL patches.
I cannot get this to work and I need to be able to create packages. The only other step I can think of is wiping my computer and I don't want to have to do that.
Please please can anyone help me? I've been scouring the internet and working on this for 1 day and 1/2.
Miraculously - it's started working again. All I've done since then is go to the MS Update website and tried to add SQL 2005 SP2 again. It failed again, but this time when I opened my SSIS project, it opened ok.
I also just realized that I disabled the antivirus on my computer in an attempt to upgrade to SP2 again (although I haven't tried to upgrade the second time), but the antivirus is still off - When I reboot, I'll try to open it again - of it fails it must be the antivirus.
|||Well, it wasn't the antivirus, because I've rebooted and it's still working - with the antivirus running. So if anyone else is running into this issue and is reading this thread for help - sorry - don't know what to tell you or how it fixed itself.
All I know is - you live by Microsoft, you die by Microsoft.
No comments:
Post a Comment