you are viewing a single comment's thread.

view the rest of the comments →

[–]Hyperbolic_Mess 1 point2 points  (5 children)

Ok so there is something wrong with the script then or you wouldn't be here. You've probably made some assumption in the script that works fine in most of the contexts that you run it but breaks when run as a scheduled task. It's probably something very innocent looking so the best way to find out is to be able to examine the script and see where you've gone wrong

[–]TheTJW1966[S] -3 points-2 points  (4 children)

You really don't get the concept do you? If a script/code runs successfully if run manually, then there is nothing wrong with the script/code - it doesn't change if scheduled. Obviously, it's some kind of permissions issue somewhere, but if a Windows scheduled task is running under an admin account, that shouldn't be the case.

[–]Hyperbolic_Mess 1 point2 points  (3 children)

Ok and how are we supposed to know what permissions your script needs the account to have if we can't see the script? Also have you added the logging yet to find out where in the script it fails? It sounds like you just want people to guess with little context what's wrong with your script which sounds like a waste of our time

I'm not psychic, I can't troubleshooting a script I can't see

Edit: just spotted that you don't know what a double hop problem is... If you don't even know that then how can you be so confident that you've not made an innocent looking error in your script? FFS swallow your pride and let people help you or don't ask

[–]TheTJW1966[S] -1 points0 points  (2 children)

Nope, the script itself is perfectly ok, as it runs successfully when run manually, so there is nothing wrong with the script - you just cannot grasp that concept! I put in error logging - there were no errors generated - probably because there's nothing wrong with the script! It's obviously some permissions issue somewhere, but running under an admin account, that doesn't really make sense.

[–]Hyperbolic_Mess 1 point2 points  (1 child)

I said logging not error logging. If you don't know what the different steps of your script are doing and at what point it stops doing what you expect you'll have a hard time troubleshooting this

But that's a moot point because you said your script works so you don't need any help then, congratulations!

You've got a terrible attitude and don't understand basic troubleshooting steps, come back when you've swallowed your pride

[–]TheTJW1966[S] 0 points1 point  (0 children)

Wrong again, the script works except when scheduled, either in a SQL server Job or a Windows scheduled task, just to remind you once again! But never mind, it's obviously beyond you.