Sage 100

Client is trying to create a scheduled task (in Sage task scheduler) but any task they try to make is getting a message ""Error creating task: Access is Denied"" Screen shot attached. this is on Sage100 advanced version 5.40 user has admin rights in Sage and windows user has admin rights on the server even happens when running Sage directly on the server. we can create a task using windows task scheduler when logged into the server I can't find any reference to this on Sage KB. So any thoughts/ideas would be appreciated.

What about the service account? Is that a local admin on the server? Does MAS90 mode work?

I haven't tried it in mas90 mode - that is a good idea, but I'll need to wait until tomorrow morning to get back with them to test that. I'm not familiar with what a service account is (but the client might be, I'm working with some one in IT.

David - Kevin is referring to the Sage 100 service for the app server (assume you're not running it App Server as a desktop application). On the server, who you are logged into Windows as could be different than the user you're running Sage 100 as. What you want to tell the IT person is knowing the the Sage Task Scheduler creates job in the Windows Task Scheduler, the error message indicates the Sage service account (not who you are logged into Windows as) is not allowed to create jobs in the Windows Task Scheduler. It also sounds like if you try running Mas90 style, because you are now running as the same user who is logged into Windows as, the Sage Task Scheduler would work. Hope that helps.

Thanks for the clarification! The That makes sense and I thought that would certainly be the cause. but I just called the client; they are running Sage100 Advanced as an application and we tried running in MAS90 mode (logged in as the user that has rights to create windows task scheduler). We get the same message Any other thoughts out there?

I think there is a windows policy for log on as a batch which we've run into sometimes. Our usual is to run the service with a local admin account to bypass this sort of thing.

what if they are running as an application and not a service? wouldn't running in MAS90 mode take that out of the equation?

It should... just throwing out ideas.

Local account vs domain account (when creating the scheduled task)? Did you try to specify domainname\domainusername or ..\localusername?

Great Idea! I'll have them give that a try!

I have tried the domain\username username@URL.com xxx.net, local accounts, etc. Nothing works it always still gives the access denied

I vaguely remember having a similar issue where I think I had to disable the 'prompt for company code' setting in user maint

ok we tried turning off the Prompt for Company Code and the client does not want to continue troubleshooting the issue. they are going to manually create the scheduled task in windows.