Showing posts with label upgraded. Show all posts
Showing posts with label upgraded. Show all posts

Wednesday, March 21, 2012

Error in SSIS package after upgrade to SP2 release

I upgraded to SQL Server 2005 SP2 release today. I had been working with 9.00.1399. I had developed few packages in the older version which were getting invoked through the asp web application locally and it was working fine.

Today I upgraded to SQL server 2005 3042 version.
Now the same packages are not working when invoked through the web application. But it works fine stand alone. All errors refer to connection problem.

I need to resolve this urgently. Can anyone help me please?

Errors -

"SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005.\r\nAn OLE DB record is available. Source: \"Microsoft JET Database Engine\" Hresult: 0x80004005 Description: \"The Microsoft Jet database engine cannot open the file ''. It is already opened exclusively by another user, or you need permission to view its data.\".\r\n"

SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "Excel Connection Manager" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed.


I have seen that error from time to time. it indicates that the excel file where the connection manager is pointing to is open by other application/process. I read a Phil's suggestions to use a third party to monitor and detect who is actually holding the file, but I don't remember the name.

In the mean time, try closing all applications that may be 'holding the file' and run the package again.

|||Hi,

The error appears due to the upgrade to the SP2 version.

I restarted my system. No other process accessing the excel.
But still the same error.
This functionality used to work fine with the older version of SQL.

Friday, February 24, 2012

Error in Bulk Insert after Windows 2003 Upgrade

My production support group upgraded the version of Windows Server from 2000 to 2003 on a stand-alone SQL 8.0 development server. I am using a bulk insert command in a stored procedure that is now failing as a result of the upgrade.

The error message is: Server: Msg 7302, Level 16, State 1, Line 1
Could not create an instance of OLE DB provider 'BULKIMPORTSTREAM'.
OLE DB error trace [Non-interface error: CoCreate of DSO for BULKIMPORTSTREAM returned 0x8007045a].

We have checked the following based on other posts we have seen.

1) Re-registered impprov.dll
2) We are at SP 3
3) We are at MDAC 2.8

We also verified by copying the DB to a dev server that has not been upgraded it still works. Does anyone have any other suggestions or experience that may help?

Thank you,
KellyJust being curious, did they do an upgrade without scratch and rebuild the server? If that's the case, your server would have registry problems. If your dev box is a dedicated db box, you can simply run the rebuild registry with sql 2000 installation CD and patch up with sp3 after that. If you still have problem, since it's a dev box, I would recommand that you take backups, sratch the box, install Windows 2003, install sql 2000, patch up to sp3, and then reload the database on to the server.|||Well, I made the suggestion that the server be rebooted after the unregister and re-resgister process and that seems to have done the trick. The DBA thinks that restarting SQL Server may have been enough. Thanks for the idea Joe.

Kelly