Can't run SSIS package in query or in SQL Agent job

Posted on 2008-11-20
Last Modified: 2013-11-10
I know this question has been asked and answered many times but I can't seem to resolve this issue.  We just setup a new windows 2003 64 bit server with Sql server 2005 64 bit developer edition.  Installed SP2 and CU 7.  SQL Agent and SSIS are both running under the same service account which has been added to the local sql windows groups:  SQLSErver2005DTSUser & SQLServer2005SqlAgentUser.  By default, the SQLServer2005SQLAgentUser is given sysadmin privileges to the local SQL server so the service account has sysadmin privileges.  I think that is all the background on current configuration.

I brought over SSIS packages from our old server.  I modified them to reference the new server and saved them back to the MSDB database.  The protection level on the package is set to use a password.  If I connect to SSIS directly, the package runs successfully.  If I try to execute using XP_Cmdshell and dtexec.

I am getting the following error:

Microsoft (R) SQL Server Execute Package Utility
Version 9.00.3042.00 for 32-bit
Copyright (C) Microsoft Corp 1984-2005. All rights reserved.
Started:  6:53:58 AM
Could not load package "LoadGraphicsProjectData" because of error 0xC0014062.
Description: The LoadFromSQLServer method has encountered OLE DB error code 0x80004005 (Login failed for user ''. The user is not associated with a trusted SQL Server connection.).  The SQL statement that was issued has failed.
Started:  6:53:58 AM
Finished: 6:53:59 AM
Elapsed:  0.891 seconds

I have gone through the different KB articles but haven't found it yet.  I must be missing a setting somewhere but can't remember or figure out where.

Any ideas?
master.dbo.xp_cmdshell '"C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\dtexec.exe" /Sq LoadGraphicsProjectData /ser dbatest2 /de crypt'

Open in new window

Question by:Soccerman55
    1 Comment
    LVL 1

    Accepted Solution

    I am embarrassed to post this back but I figured out my issue.  Our systech guys had renamed my server.  I could still connect to SQL Server using the name expected but ssis was running with the newly configured server name.  So that was the missing piece....


    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    What Is Threat Intelligence?

    Threat intelligence is often discussed, but rarely understood. Starting with a precise definition, along with clear business goals, is essential.

    Suggested Solutions

    Introduced in Microsoft SQL Server 2005, the Copy Database Wizard ( is useful in copying databases and associated objects between SQL instances; therefore, it is a good migration and upgrade tool…
    International Data Corporation (IDC) prognosticates that before the current the year gets over disbursing on IT framework products to be sent in cloud environs will be $37.1B.
    Familiarize people with the process of utilizing SQL Server functions from within Microsoft Access. Microsoft Access is a very powerful client/server development tool. One of the SQL Server objects that you can interact with from within Microsoft Ac…
    Via a live example, show how to extract information from SQL Server on Database, Connection and Server properties

    779 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    14 Experts available now in Live!

    Get 1:1 Help Now