two things come to mind...if you can log on locally then the credential in VisualCron should be like this:
That would be your user account literally logging in and acting as that user with all of its profile elements loading. That should really be the end of it.
If that does not work I would test using PsExec from sysinternals. The issue may not be the user it might be VC itself.
From your remote computer (not using visualcron) open a command prompt and use this command
psexec \\server -u username -p password net start ServiceName
psexec is an executable found here:
https://download.sysinte...es/SysinternalsSuite.zip Documentation found here:
https://docs.microsoft.c...loads/sysinternals-suite \\server would = the server you are trying to control
-u = username (you may need domain\username)
-p = the password for the remote user
net start is the command to start a service
or
net stop if you need to stop
for testing I would do a 'net stop' to test. Net start would start it back up. There is no 'net restart' that I know of
ServiceName is the name of the service - make sure you are using the right service name. There are usually two names associated with services.
For VisualCron the two names are identical
for other services the names may differ
In this case the service name you would use in the command line is lmhosts
IF the psexec command run works then the issue is NOT on the server where the service is located and the user rights are good. If the command does not work then I would look more towards something like this:
http://woshub.com/set-pe...ions-on-windows-service/