After reboot all vvengine tasks are marked as disabled

deriderj · Joined: 16 Sep 2007 Posts: 24

Hi,

After I reboot my workstation, all scheduled tasks in vvengine are marked as disabled. I can manually enable them and they will then run as scheduled if I reschedule them.

How can I mark the tasks as enabled schedule them and have them stay that way even if a reboot occurs?

Thanks!

TGRMN Software · Site Admin Joined: 10 Jan 2005 Posts: 8759

Hello

please check / post here the file VVEngine.log ... it should contain useful info on the shutdown process.

thanks!
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com

Guest · Posted: Sat Nov 03, 2007 5:00 am Post subject:

I did a visual and computer search but could find no vvengine.log. I am not running vvengine as a service. I did fined a vvengineservice.log and this is the contents. If there is something else that would help figure out why I am losing my schedule information and all tasks show up as disabled after a reboot, please just let me know!

10/23/2007 01:59:25 [6521.705-PID:1424-00824] VVEngine path: C:\Program Files\VVEngine\vvengine.exe
10/23/2007 01:59:25 [6521.721-PID:1424-00824] Command Line Flag: vvengineservice
10/23/2007 01:59:25 [6521.736-PID:1424-00824] Command Line Flag: -i
10/23/2007 01:59:25 [6521.736-PID:1424-00824] Shutting down existing VVEngine task... try 1
10/23/2007 01:59:28 [6524.361-PID:1424-00824] VVEngine shut down.
10/23/2007 01:59:28 [6524.502-PID:1424-00824] Service VVEngine installed
10/23/2007 01:59:32 [6528.689-PID:1424-00824] Done.
10/23/2007 02:01:23 [3428.566-PID:1496-00228] VVEngine path: C:\Program Files\VVEngine\vvengine.exe
10/23/2007 02:01:23 [3428.566-PID:1496-00228] Command Line Flag: C:\Program Files\VVEngine\serv\vvengineservice.exe
10/23/2007 02:01:23 [3428.582-PID:1496-01364] ServiceMain called
10/23/2007 02:01:24 [3429.582-PID:1496-01200] Checking Process...
10/23/2007 02:30:00 [5145.253-PID:1496-00228] Service Stopping from console. (XYNTServiceHandler)
10/23/2007 02:30:00 [5145.269-PID:1496-00228] Ending VVEngine Process.
10/23/2007 02:30:00 [5145.441-PID:1496-00228] VVEngine Shutdown OK
10/23/2007 02:30:00 [5145.441-PID:1496-01200] Service stopping from console. (CheckProcess)
10/23/2007 02:30:00 [5145.457-PID:1496-00228] Service Stopped from console. (XYNTServiceHandler)
10/23/2007 02:30:00 [5145.457-PID:1496-01200] Exit Checking Process ...
10/23/2007 02:30:00 [5145.457-PID:1496-00228] Done.
10/23/2007 02:30:29 [5174.332-PID:112-01244] VVEngine path: C:\Program Files\VVEngine\vvengine.exe
10/23/2007 02:30:29 [5174.332-PID:112-01244] Command Line Flag: C:\Program Files\VVEngine\serv\vvengineservice.exe
10/23/2007 02:30:29 [5174.347-PID:112-00332] ServiceMain called
10/23/2007 02:30:30 [5175.363-PID:112-00792] Checking Process...
10/23/2007 02:32:00 [5265.128-PID:112-01244] Service Stopping from console. (XYNTServiceHandler)
10/23/2007 02:32:00 [5265.128-PID:112-01244] Ending VVEngine Process.
10/23/2007 02:32:00 [5265.160-PID:112-00792] Service stopping from console. (CheckProcess)
10/23/2007 02:32:00 [5265.175-PID:112-01244] VVEngine Shutdown OK
10/23/2007 02:32:00 [5265.175-PID:112-00792] Exit Checking Process ...
10/23/2007 02:32:00 [5265.175-PID:112-01244] Service Stopped from console. (XYNTServiceHandler)
10/23/2007 02:32:00 [5265.191-PID:112-01244] Done.
10/23/2007 02:32:46 [5311.925-PID:1400-00844] VVEngine path: C:\Program Files\VVEngine\vvengine.exe
10/23/2007 02:32:46 [5311.941-PID:1400-00844] Command Line Flag: C:\Program Files\VVEngine\serv\vvengineservice.exe
10/23/2007 02:32:46 [5311.941-PID:1400-01356] ServiceMain called
10/23/2007 02:32:47 [5312.957-PID:1400-00352] Checking Process...
10/23/2007 02:33:08 [5333.066-PID:360-01588] VVEngine path: C:\Program Files\VVEngine\vvengine.exe
10/23/2007 02:33:08 [5333.066-PID:360-01588] Command Line Flag: C:\Program Files\VVEngine\serv\vvengineservice.exe
10/23/2007 02:33:08 [5333.082-PID:360-01536] ServiceMain called
10/23/2007 02:33:08 [5333.082-PID:360-01536] Shutting down existing VVEngine task... try 1
10/23/2007 02:33:10 [5335.613-PID:360-01536] VVEngine shut down.
10/23/2007 02:33:11 [5336.613-PID:360-00920] Checking Process...
10/23/2007 02:35:35 [5480.894-PID:360-01588] Service Stopping from console. (XYNTServiceHandler)
10/23/2007 02:35:35 [5480.972-PID:360-01588] Ending VVEngine Process.
10/23/2007 02:35:36 [5481.175-PID:360-01588] VVEngine Shutdown OK
10/23/2007 02:35:36 [5481.191-PID:360-00920] Service stopping from console. (CheckProcess)
10/23/2007 02:35:36 [5481.207-PID:360-01588] Service Stopped from console. (XYNTServiceHandler)
10/23/2007 02:35:36 [5481.207-PID:360-00920] Exit Checking Process ...
10/23/2007 02:35:36 [5481.207-PID:360-01588] Done.
10/23/2007 03:00:29 [4291717.440-PID:2024-02028] VVEngine path: C:\Program Files\VVEngine\vvengine.exe
10/23/2007 03:00:29 [4291717.471-PID:2024-02028] Command Line Flag: C:\Program Files\VVEngine\serv\vvengineservice.exe
10/23/2007 03:00:29 [4291717.503-PID:2024-02036] ServiceMain called
10/23/2007 03:00:30 [4291718.518-PID:2024-00992] Checking Process...
10/23/2007 03:03:32 [4291900.893-PID:3416-03420] VVEngine path: C:\Program Files\VVEngine\vvengine.exe
10/23/2007 03:03:32 [4291900.893-PID:3416-03420] Command Line Flag: vvengineservice
10/23/2007 03:03:32 [4291900.893-PID:3416-03420] Command Line Flag: -u
10/23/2007 03:03:32 [4291900.924-PID:2024-02028] Service Stopping from console. (XYNTServiceHandler)
10/23/2007 03:03:32 [4291900.940-PID:2024-02028] Ending VVEngine Process.
10/23/2007 03:03:32 [4291901.128-PID:2024-00992] Service stopping from console. (CheckProcess)
10/23/2007 03:03:32 [4291901.128-PID:2024-02028] VVEngine Shutdown OK
10/23/2007 03:03:32 [4291901.143-PID:2024-00992] Exit Checking Process ...
10/23/2007 03:03:32 [4291901.143-PID:2024-02028] Service Stopped from console. (XYNTServiceHandler)
10/23/2007 03:03:32 [4291901.143-PID:2024-02028] Done.
10/23/2007 03:03:32 [4291901.143-PID:3416-03420] Killed service VVEngine.
10/23/2007 03:03:32 [4291901.159-PID:3416-03420] Service VVEngine removed
10/23/2007 03:03:34 [4291903.049-PID:3416-03420] Done.

deriderj · Joined: 16 Sep 2007 Posts: 24

Hi, I figured out the problem on my own. Some of the files in the directory that held the profiles had the read-only attribute turned on. I don't know how or why the read-only attribute was on but changing to off seemed to correct the problem. After I rebooted the profiles were still marked as active.