File Error: Exclusively Used/Opened by Another User

Error encountered: "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.

Why? Because the Excel file I was processing in SSIS was open.

This is a common file error not only in SSIS but in the general development arena. This is encountered when the file is open or another process is using it (either the process hung or a running service is consuming the file). Therefore you need to close the file, stop the calling service or end the hanging application in the Task Manager.

VSA Error in SSIS Design Script

Error message: Cannot show Visual Studio for Applications Editor.

I added a Script Component in my package to generate the error description for my fallout table when I clicked the "Design Script" button from the Script tab and got this error.

Through searching the net, I found answers that stated to remove the C# project and restart the Visual Studio application but I did not have any other project than SSIS on my solution.

James McAuliffe also commented a workaround on some forums/blogs like in Jamie Thomson's blog. He recommended registering all the assemblies once more in case of conflicts on Visual Studio or SQL versions but it didn't work out for me either.

I was just too stubborn to download SQL 2005 SP2 which solved the problem afterwards.

Error Descriptions for SSIS Error Outputs

I don't know why SSIS didn't put error descriptions automatically in the source error outputs. We just have the error code and error column. Thus we still need to place a Script Component to get the error description.

On the Script Transformation Editor, add an output column "Error Description" in the Inputs and Outputs tab. Then click the Design Script button from the Script tab and add the ff. code which gets the error description based on the error code:

Row.ErrorDescription = ComponentMetaData.GetErrorDescription(Row.ErrorCode)

Take note to change the data type of the newly-created output column since the default data type is integer.

I almost always overlook this and jump to the script code soon and get a mismatched data type exception afterwards. :)

Thanks to Jamie Thompson's article for this very useful info on getting the error descriptions in SSIS.

SSIS Logging Configuration Error

Error encountered: “The connection is not found. The error is thrown by Connections collection when the specific connection element is not found.”

This happened when I copied a package that had logging enabled and then deleted the log file from the Connection Managers. I forgot to switch off the SSIS logging and thus encountered this error upon running the new package. If you search through the net, this error is also encountered as long as the SSIS logging is not configured properly.