Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Process Task Not Executing when Scheduled Expand / Collapse
Author
Message
Posted Wednesday, January 21, 2009 6:39 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Friday, November 7, 2014 9:50 AM
Points: 40, Visits: 282
I have a "process task" in a package running a secure ftp to an offsite client. It will run fine in the development environment (on my machine and on the server). Once I deploy the package to the server and schedule it...this task always fails.

I am using psftp.exe from puTTY as the executable. Could any please help with this...I am tired of manually running this every morning when I get in to work.

Thanks in advance.



Post #640652
Posted Wednesday, January 21, 2009 11:23 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Monday, October 27, 2014 12:20 PM
Points: 226, Visits: 728
When you run manually its using your credentials and when run as a job it runs under the SQL Server Agent credentials. Make sure the user under which the agent is running has appropirate permissions.
You can create proxy account for this, follow:

http://support.microsoft.com/kb/912911

HTH
Post #641002
Posted Wednesday, January 21, 2009 11:32 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Friday, November 7, 2014 9:50 AM
Points: 40, Visits: 282
Thanks for the reply Mukti -

Is it a must that you create a proxy account? The link below has two methods and states to use one of the following...

I did Method 1 and the job hangs until timeout.



Post #641007
Posted Wednesday, January 21, 2009 11:57 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Monday, October 27, 2014 12:20 PM
Points: 226, Visits: 728
Can you do a simple test? Logon to the machince using the SQL Server Agent account and from the command line try to test run the psftp.exe see if it throws error.

Just want to check if the sql server agent has permissions to run the exe...

Post #641028
Posted Wednesday, January 21, 2009 12:25 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Friday, November 7, 2014 9:50 AM
Points: 40, Visits: 282
THANK YOU...THANK YOU...THANK YOU...and THANKS AGAIN!!

When I ran it from the command line as the agent account...it prompted for a trusted key. As soon as I said yes...the process completed from the command line.

I went back the scheduled job and fired it off and it worked like a charm!

I appreciate you input!!!



Post #641051
Posted Wednesday, January 21, 2009 3:41 PM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: 2 days ago @ 2:09 PM
Points: 69, Visits: 256
Guys,

I thought the report was running, while it was actually just hung. I'm still having the same problem, I can run it from BIDS but not when scheduled under sql server agent. I even moved the report locally, gave that share full access to everyone - doesn't make a difference.

So how do you do that, log in or run as SQL server agent? Is this account supposed to show up under users? I have the service set up to login as a domain user account, which for sure has the credentials to run that report.

I appreciate your help!!
Post #641222
Posted Thursday, January 22, 2009 6:06 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Friday, November 7, 2014 9:50 AM
Points: 40, Visits: 282
I verified the user that is used to start the SQL Server Agent under the SQL Server Configuration Manager. I then used that user to login to the server and ran the process task of the scheduled job from the command prompt.


Post #641599
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse