| Author |
Message |
Winuser
Guest
|
 Posted: Fri Dec 15, 2017 7:19 am Post subject: "the requested operation requires elevation' on Windows |
 |
|
| On Windows 10 the error I am getting is "the requested operation requires elevation". It only happens when trying to run the job from the scheduler. Same job works fine when running it directly from ViceVersa. |
|
| Back to top |
|
 |
TGRMN Software
Site Admin
Joined: 10 Jan 2005
Posts: 8763
|
|
| Back to top |
|
|
rjowenusa
Joined: 04 Nov 2015
Posts: 2
|
| Posted: Wed Jan 03, 2018 3:12 pm Post subject: "the requested operation requires elevation" |
|
|
| I received the same issue after upgrading from Server 2008 R2 to Server 2016. My server is up to date with patches/updates. The solution I found was to manually edit the VV tasks in Administrative Tools, Task Scheduler and change the General tab option 'Configure for:' to Windows Server 2016. Now my tasks run although they no longer appear in VVScheduler. |
|
| Back to top |
|
|
TGRMN Software
Site Admin
Joined: 10 Jan 2005
Posts: 8763
|
| Posted: Wed Jan 03, 2018 11:37 pm Post subject: |
|
|
Hi, if the Windows Server 2016 is fully up-to-date (after using check for updates) that should not be necessary. Even new servers when that are installed are not always fully up-to-date yet. thanks
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com |
|
| Back to top |
|
|
rjowenusa
Joined: 04 Nov 2015
Posts: 2
|
| Posted: Wed Jan 03, 2018 11:55 pm Post subject: |
|
|
| To the best of my knowledge my server is up to date. It has the December 2017 cumulative update and everything prior to that. Windows Update reports no available updates. VV scheduler would fail with 'the requested operation requires elevation'. After I manually edited the tasks they than ran. VV scheduler had set the tasks to be configured for Windows XP/2000.[/img] |
|
| Back to top |
|
|
TGRMN Software
Site Admin
Joined: 10 Jan 2005
Posts: 8763
|
| Posted: Thu Jan 04, 2018 11:23 pm Post subject: |
|
|
Which type of account are you using to schedule the tasks? It is correct for VVScheduler tasks to be configured for previous Windows versions. thanks
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com |
|
| Back to top |
|
|
Dukethornon
Joined: 16 Jan 2018
Posts: 1
|
| Posted: Wed Jan 17, 2018 5:20 am Post subject: |
|
|
| Same issue with a fully patched Windows 2016 server. The problem is with TGRMN not the OS. It is how the program creates the task not the guess that somehow a magic patch will fix your problem. |
|
| Back to top |
|
|
TGRMN Software
Site Admin
Joined: 10 Jan 2005
Posts: 8763
|
| Posted: Thu Jan 18, 2018 11:49 am Post subject: |
|
|
Can't reproduce on our servers...  Which scheduling settings are you using? Are you scheduling using a full admin account / backup account ? thanks
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com |
|
| Back to top |
|
|
WBeatty
Joined: 30 Nov 2007
Posts: 13
|
| Posted: Mon Feb 19, 2018 7:52 pm Post subject: Re: "the requested operation requires elevation" |
|
|
| rjowenusa wrote: | | I received the same issue after upgrading from Server 2008 R2 to Server 2016. My server is up to date with patches/updates. The solution I found was to manually edit the VV tasks in Administrative Tools, Task Scheduler and change the General tab option 'Configure for:' to Windows Server 2016. Now my tasks run although they no longer appear in VVScheduler. |
I am having this same issue when scheduling VVPro on Server 2016. I scheduled a task in VVScheduler and it appears in Windows Task Scheduler but then disappears from the VVScheduler. This is not satisfactory. Even though it works from the Windows Scheduler, I prefer to view the results in the VVScheduler window.
Thanks
_________________
Thanks,
Bill |
|
| Back to top |
|
|
TGRMN Software
Site Admin
Joined: 10 Jan 2005
Posts: 8763
|
| Posted: Tue Feb 20, 2018 1:41 am Post subject: |
|
|
Hi, make sure the accnt you use to schedule the task in VVScheduler has the "Log on as batch job" right... which account type are you using to schedule the task. We have feedback from some users that some accounts do not work, but using a different account then works. thanks
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com |
|
| Back to top |
|
|
WBeatty
Joined: 30 Nov 2007
Posts: 13
|
| Posted: Wed Feb 21, 2018 7:22 pm Post subject: |
|
|
| TGRMN Software wrote: | | Hi, make sure the accnt you use to schedule the task in VVScheduler has the "Log on as batch job" right... which account type are you using to schedule the task. We have feedback from some users that some accounts do not work, but using a different account then works. thanks |
I am using an admin account. I also tried giving that account explicit "Log on as a batch job" permission which is obviously redundant. It is still very odd that on Server 2016 it doesn't seem to be executing under VVScheduler. Last Run Time doesn't change unless I run the job manually - and the job synch doesn't seem to work manually as well. AND that the task disappears from VVScheduler once the task in Windows Task Scheduler is changed to "Configure for Windows Server 2016".
I didn't have these problems on Server 2012 R2.
_________________
Thanks,
Bill |
|
| Back to top |
|
|
WBeatty
Joined: 30 Nov 2007
Posts: 13
|
| Posted: Wed Feb 21, 2018 8:40 pm Post subject: |
|
|
I upgraded to the latest 2.5 build to make sure it's compatible with Windows 2016 and still no luck. I also tested on another 2016 server and the same thing happened there as well.
"the requested operation requires elevation"
_________________
Thanks,
Bill |
|
| Back to top |
|
|
WBeatty
Joined: 30 Nov 2007
Posts: 13
|
| Posted: Wed Feb 21, 2018 8:53 pm Post subject: |
|
|
I think we found an issue relating to the accounts. If I schedule a job with the same account I am logged onto Windows with, it returns the error "the requested operation requires elevation". If I schedule the job with another admin account, it works!!! So the workaround is to make sure you don't have the task run under the account you are logged on with, EVEN IF IT IS AN ADMIN ACCOUNT!
We tried this with several accounts and this fixes the error. That is just crazy.
_________________
Thanks,
Bill |
|
| Back to top |
|
|
TGRMN Software
Site Admin
Joined: 10 Jan 2005
Posts: 8763
|
| Posted: Thu Feb 22, 2018 12:05 am Post subject: |
|
|
It must be a new security restriction added to Win Server 2016.... like you can't run Internet Browser under the default admin account.
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com |
|
| Back to top |
|
|
WBeatty
Joined: 30 Nov 2007
Posts: 13
|
| Posted: Thu Feb 22, 2018 2:36 pm Post subject: |
|
|
But support has been telling everyone to make sure their server is patched when this actually seemed to be causing the issue for me. I wonder if this was the reason others were having the same error?
_________________
Thanks,
Bill |
|
| Back to top |
|
|
|
ViceVersa HOME 
Forum FAQ
Search Forum
Register
Profile
Log in
