|
|
|
Grasshopper
      
Group: General Forum Members
Last Login: Tuesday, May 14, 2013 6:30 PM
Points: 15,
Visits: 95
|
|
I have SSIS task calling custom powershell task and the package works when manually ran in BIDS. But when I call the package with SQL Agent as a scheduled job it complete in like 30 secs and it completes with successful reporting. It should take much longer; in BIDS like 15 mins. The powershell is not doing it's task with the SQL Agent. It's like it doesn't have enough time.
I have set the SQL Agent Service to run as myself to clear any security issues. I have also setup a proxy account to run as myself but get the same results.
When I run it from server's MSDB it works correctly. It just seems to be the SQL Agent process.
This my SSIS package and powershell script. http://www.red-gate.com/messageboard/viewtopic.php?t=16405
SSIS Powershell task: http://powershellscripttask.codeplex.com/ and http://ssisctc.codeplex.com/
|
|
|
|
|
SSCertifiable
       
Group: General Forum Members
Last Login: Today @ 7:33 AM
Points: 6,696,
Visits: 11,713
|
|
It could be a permissions issue. Anything in the Agent Job logs?
__________________________________________________________________________________________________ There are no special teachers of virtue, because virtue is taught by the whole community. --Plato
Believe you can and you're halfway there. --Theodore Roosevelt
Everything Should Be Made as Simple as Possible, But Not Simpler --Albert Einstein
The significant problems we face cannot be solved at the same level of thinking we were at when we created them. --Albert Einstein
1 apple is not exactly 1/8 of 8 apples. Because there are no absolutely identical apples. --Giordy
|
|
|
|
|
Grasshopper
      
Group: General Forum Members
Last Login: Tuesday, May 14, 2013 6:30 PM
Points: 15,
Visits: 95
|
|
I found this in the log.
Date 3/8/2013 8:16:52 AM Log Windows NT (Red Gate Software)
Source SQL Doc 2 Category (0) Event 32 Computer MYPC
Message CommandLine Main:Unhandled Exception System.ArgumentNullException: Value cannot be null. Parameter name: value at System.IO.Directory.SetCurrentDirectory(String path) at System.Environment.set_CurrentDirectory(String value) at RedGate.SQLDoc.Engine.Project.Project.(String ) at RedGate.SQLDoc.Engine.Project.Project.set_FilePathOfHtml(String value) at RedGate.SQLDoc.Engine.Project.Project..ctor() at RedGate.SQLDoc.Engine.Project.Project.LoadFromDisk(String pathAndFileName) at RedGate.SQLDoc.UI.CommandProcessor.RunProject() at RedGate.SQLDoc.UI.CommandProcessor.Run() at RedGate.SQLDoc.UI.Program.Main(String[] args)
|
|
|
|
|
SSCertifiable
       
Group: General Forum Members
Last Login: Today @ 7:33 AM
Points: 6,696,
Visits: 11,713
|
|
That's an error from SQL Doc and would not be related to this.
Try looking in the Agent Job History log. Right-click the job and select View History.
__________________________________________________________________________________________________ There are no special teachers of virtue, because virtue is taught by the whole community. --Plato
Believe you can and you're halfway there. --Theodore Roosevelt
Everything Should Be Made as Simple as Possible, But Not Simpler --Albert Einstein
The significant problems we face cannot be solved at the same level of thinking we were at when we created them. --Albert Einstein
1 apple is not exactly 1/8 of 8 apples. Because there are no absolutely identical apples. --Giordy
|
|
|
|