Omicron Llama

Coding all day, every day.

29 09 2010

Could not load package "\MSDB\MySSISPackage" because of error 0x80131500.

Jimmywim | DTExec, Error, SQL Server, SQL Server Integration Services, SSIS | 0

Came across an interesting error whilst thrashing out some deployment automation scripts today.

As part of the deployment it was executing a SSIS package using DTExec running on the machine local to SQL Server, thus as part of the command line it omitted the /SERVER switch, insinuating that the package I’m executing exists in the default instance. However, DTExec was throwing me this error message:

Microsoft (R) SQL Server Execute Package Utility 
Version 10.50.1600.1 for 64-bit 
Copyright (C) Microsoft Corporation 2010. All rights reserved. 


Started: 10:41:21 
Could not load package “\MSDB\MyPackage” because of error 0x80131500. 
Description: The SQL Server instance specified in SSIS service configuration is not present or is not available. This might occur when there is no default instance of SQL Server on the computer. For more information, see the topic “Configuring the Integration Services Service” in SQL Server 2008 R2 Books Online. 


Login failed for user ‘VM\_svc_ssis_packages’. 
Source: MsDtsSrvr 
Started: 10:41:21 
Finished: 10:41:22 
Elapsed: 0.344 seconds 

Most of my Googling efforts pointed me to the SQL Server Books Online on configuring Integration Services by modifying the config xml file when your SSIS packages existed on a specific named instance – this wasn’t my case, my packages were on the default instance of the machine on which DTExec was being run.
In my situation, I had created a service account, in this example called “VM\_svc_ssis_packages” to clamp down what the SSIS package could and couldn’t do during execution, but I had forgot to add that particular service account to the Logins folder of the Database instance from within SQL Server Management Studio (SSMS). I also had to add this service account the usual Roles it needed to the usual databases it was going to query, but also I had to add it to the “msdb” database and apply the roles for ssis datareader to allow it to actually execute the SSIS package. 
Once I added the Login and applied the roles all was hunky-dory. 

Leave a Reply

Your email address will not be published. Required fields are marked *