|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: Tuesday, March 26, 2013 12:29 PM
Points: 154,
Visits: 333
|
|
Hi, I am trying to schedule a SSIS package in SQL agent 2005. I can run the package manually using Business Intelligents Studio but when I try to schedule it the following error orrurs. I set it up using windows authentication. I have administrator rights. SQL Server Scheduled Job 'TestImport' (0x5EB86F3C24723D41B5C5779C026CCFCC) - Status: Failed - Invoked on: 2007-03-06 09:55:13 - Message: The job failed. The Job was invoked by User QDSSVR1\bibeaultd. The last step to run was step 1 (testimport1). Is this another security issue? Should I set up using system administrator? Help! Newbie
|
|
|
|
|
SSC Veteran
      
Group: General Forum Members
Last Login: Friday, May 03, 2013 9:09 AM
Points: 267,
Visits: 622
|
|
| The account the sql server agent is running under should have all permissions necessary to run the IS package. Check all your connections and check whether the agent-account has permission.
|
|
|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: Tuesday, March 26, 2013 12:29 PM
Points: 154,
Visits: 333
|
|
Thanks, How do you check to see if SQL agent can run a SSIS package? One more question, does the standard install install SSIS on the server? How can I tell if all the peices are in place? thanks,
|
|
|
|
|
Grasshopper
      
Group: General Forum Members
Last Login: Friday, February 17, 2012 5:12 PM
Points: 24,
Visits: 208
|
|
I am having a similar problem - SSIS package executes fine in BIDS but fails when scheduled as SQL Server Agent job. Different error... Windows Server 2003/SQL Server 2005 64-bit. Package Protection - DontSaveSensitive (prior to this error I was getting a password encryption error so changed to this protection level with new error result) Error Message Text: Executed as user: SVHPSQL\SYSTEM. Microsoft (R) SQL Server Execute Package Utility Version 9.00.3042.00 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 10:14:31 AM Error: 2007-03-06 10:14:32.33 Code: 0x00000000 Source: D_Member Month Description: This task does not support native Win64 environment. Please run the package in 32-bit WOW environment instead. End Error Error: 2007-03-06 10:14:32.35 Code: 0xC0024107 Source: D_Member Month Description: There were errors during task validation. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 10:14:31 AM Finished: 10:14:32 AM Elapsed: 0.359 seconds. The package execution failed. The step failed.
|
|
|
|
|
SSC Rookie
      
Group: General Forum Members
Last Login: Friday, May 03, 2013 7:25 AM
Points: 32,
Visits: 79
|
|
Hi All
To check that SSIS is running you can have a look under your services and look for SSIS and if it is running I would asume that all was installed.
The account that starts the SQL server agent does not neccesarily need to be an admin on the machine but it would help to avoid unnessasary complications. You could also add the user SQL agent starts up with to the "SQLServer2005DTSUser" user group and check if the security issue is resolved.
Kindest regards Jacques
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Wednesday, August 15, 2012 4:38 AM
Points: 1,
Visits: 101
|
|
|
|
|
|
SSCommitted
      
Group: General Forum Members
Last Login: Thursday, May 16, 2013 7:33 AM
Points: 1,547,
Visits: 272
|
|
wyliec2, You need to call out the 32 bit dtexec as opposed to the 64 bit. It is located here if you installed to the default location: "C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\dtexec.exe" Are you doing anything with ODBC in your SSIS package? If so, odbc is not supported on the 64 bit platform. That is the biggest issue we ran into with 64 bit. Hopefully this helps, John
|
|
|
|
|
Grasshopper
      
Group: General Forum Members
Last Login: Tuesday, August 21, 2007 6:59 PM
Points: 15,
Visits: 1
|
|
Hi,
I also faced similar problem before. I added a credential for running Sql Agent in Database server. since that time, my Sql agent has been working well. I hope it will help you
regards, Budiman
|
|
|
|
|
Grasshopper
      
Group: General Forum Members
Last Login: Monday, May 12, 2008 9:47 AM
Points: 17,
Visits: 5
|
|
| I'm new to this and I'm having the same problem. Only some jobs are failing but act like success. How do I add a credential? We too are running on 64 bit. Thanks!
|
|
|
|
|
SSC Eights!
      
Group: General Forum Members
Last Login: Thursday, May 09, 2013 2:25 PM
Points: 956,
Visits: 873
|
|
All,
The standard security on an SSIS package is "EncryptSensistiveWithUserKey" which only allows the user that created it to be able to run in as long as there is sensitive information (passwords) stored within the package.
A workaround that I am using is that I changed the package security to "EncryptAllWithPassword" which protects the entire package with a password. When you set the package as a job step, go into the properties of that job step, click on the "Command Line" tab and you should be prompted for the password. After you enter the password, the /DECRYPT switch should show up in the command line and the job should then be able to run under a different user.
Users won't be able to see the password because they will need to enter it before viewing the command line for the job step.
Let me know if that helps.
Steve
|
|
|
|