johnnyt Posted June 5, 2019 Posted June 5, 2019 Nodelink needs to run as administrator, which I can do easily using a desktop shortcut but I'm not having success starting it from Windows Task Scheduler or my preferred option StartUp Delayer. In Task Scheduler it simply doesn't start and in StartUp Delayer it reports an error launching in elevated stated (see attached screenshot), even if I tell it to use a shortcut that has "Run As Adminstrator" property set. In both cases I set it in the scheduler to "run with highest privileges." Though it runs the other way, it doesn't run properly. How would I have to do it for it to work?
johnnyt Posted June 5, 2019 Author Posted June 5, 2019 10 hours ago, io_guy said: Why does it need to run as Administrator? If I don't it can't open the port, I can't access it via web and commands don't work... Seems to be related to my running it on a Windows Server 2012 Server Essentials machine.
johnnyt Posted June 5, 2019 Author Posted June 5, 2019 I tried it from "run" command and from command windows that was "Run as Administrator" and neither worked The run command did not show anything but as I couldn't "run as administrator" probably didn't take. For the command prompt I tried with and without quotes but neither worked. See screenshot below. Below that is message showing port still can't open when Nodelink started normally
io_guy Posted June 5, 2019 Posted June 5, 2019 Come on, you gotta modify the command for your system. NodeLink's window tells you the exact command you need.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.