Thursday, May 8, 2014

SQL Integration Services error

Client T has an SSIS job running in SQL 2008 R2 that failed last night for the first time in a long time.

"What changed?"

Apparently they moved the source Access (accdb) database to a sub-folder on the network a level below where it was.  Thanks for the notice!

Not so fast though.  The first problem I have is I can no longer open the SSIS project that contains this database.  Business Intelligence Development Studio (BIDS - the version of Visual Studio used by SQL Server) turns grey and goes unresponsive to where I have to log off the server to kill it.  I can connect to other accdb files without issue in SSIS.

The next problem is when I try to create a new SSIS project in BIDS and connect to the source accdb I receive the following:

"Microsoft Visual Studio: Attempted to read or write protected memory.  This is often an indication that other memory is corrupt." "other memory"?  What other memory?

Searching for that error message leads to many hits; many meager attempts to resolve the error - but no solution.

I can open the accdb in both Excel and Access (2010.)  Interestingly when I try to create a backup of it in Access I get:

"You attempted to open a database that is already opened by user 'Admin' on machine 'x'.  Try again when the database is available."

I queried local IT to see if user 'Admin' can exit the database.  No response as yet but I suspect this might be the issue.  I will have to update this case later with the results as other items press.

No comments:

Post a Comment