Installed my SmartFTP application onto a new Windows 2008 Standard server and scheduled jobs are receiving "Access is denied" error?

I have a new server, Windows 2008 R2 Standard, and installed our SmartFTP software onto it so that my nightly download of various files will be run.  I've scheduled the job appropriately, but receive an error "Access is denied (0x80070005).  My SmartFTP jobs run just fine on my other server, which is a Windows 2003 server.  I'm wondering if the "Task Scheduler" on this new Windows 2008 server has different levels of permissions?  I've already checked with the technical support of our SmartFTP application and all settings are good.

Any ideas?  Thanks!
sushi1961Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

bominthuCommented:
If you manually run the task scheduled in server 2008, does it run ? Open the task scheduler and right click on particular task and "Run". Does it run ?

If no, did you make sure you use Administrator account to run?
Please make sure it has right to run the batch job as stated in this article http://forcecarrier.wordpress.com/2011/01/24/scheduling-tasks-in-windows-2003-mysterious-0x80070005-access-is-denied-error/

Alternatively, you can use system account to run the batch job and try.(Got to properties of scheduled job. click change user or Group and type system and Ok.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
sushi1961Author Commented:
Ok...I changed to use the "System" account and actually got further with the job; result was "Call was canceled by the message filter. (0x80010002).
Seems like I'm moving forward though...
0
sushi1961Author Commented:
Thanks...this worked! Changing the account to SYSTEM account was the solution!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Software

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.