Execute Package Utility has stopped working
Hi all i created a package and executed it successfully. Then i connected to the integration services and imported the package under the stored packages,MSDB and when i right click and execute it gives me the message "Execute Package Utility has stopped working". Any suggestions please? ThanksSV
May 15th, 2012 9:11am

Does SQL Agent service have enough permissions on package accessing folders?http://uk.linkedin.com/in/ramjaddu
Free Windows Admin Tool Kit Click here and download it now
May 15th, 2012 9:27am

Ram Can you please tell me as how to check the permissions on package accessing folders? ThanksSV
May 15th, 2012 10:19am

Is it package importing or exporting data in and out of files - does SQL Agent service have permissions on the folders where files are sitting. here are different ways to execute packages http://www.mssqltips.com/sqlservertip/1775/different-ways-to-execute-a-sql-server-ssis-package/http://uk.linkedin.com/in/ramjaddu
Free Windows Admin Tool Kit Click here and download it now
May 15th, 2012 10:53am

Hi all i created a package and executed it successfully. Then i connected to the integration services and imported the package under the stored packages,MSDB and when i right click and execute it gives me the message "Execute Package Utility has stopped working". Any suggestions please? Thanks SV Create a proxy account to run it (follow http://www.databasejournal.com/features/mssql/article.php/3789881/Proxy-Accounts-in-SQL-Server.htm is needed).Arthur My Blog
May 15th, 2012 11:08am

Ram, I opened BIDS and created a package on my desktop, the data source is the database on the prod server and then the target table is the warehouse table in the production, every time i need to execute the package i open the BIDS and open the dtsx file and execute the package, so i imported it under the integration services stored packages and cannot execute :-( ThanksSV
Free Windows Admin Tool Kit Click here and download it now
May 15th, 2012 11:10am

Hi SV, When you execute the package in SQL Server. Have you specify an instance of SQL Server? And what authentication you are using? When you run the package in SQL Server, you need specify an instance of SQL Server and provide a user name and password for SQL Server Authentication. Each user name and password adds the /USER username and /PASSWORD password options to the command prompt. For more information about Execute Package Utility, please see: http://msdn.microsoft.com/en-us/library/ms177184(v=sql.105).aspx Thanks, Eileen
May 18th, 2012 4:40am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics