(imported topic written by SystemAdmin)
So we just set up DSS SAM and manually ran the 1st few imports. Then we set up a schedule of every 6 hours starting at 9 am. The problem is the scheduled import never runs. We’ve run manual imports again and reset the schedule, but the schedule never runs. And ideas?
(imported comment written by SystemAdmin)
Hi J,
The DSS SAM installer creates a Windows Scheduled Task called BigFix DSS Cron that is responsible for kicking off the import process according to the schedule you set using the DSS SAM UI. The cron simply checks every 5 minutes to see if it’s time to run the import. Can you check and confirm the following:
That BigFix DSS Cron exists in your Scheduled Tasks folder (Windows Control Panel > Scheduled Tasks)
When you look at the list of scheduled tasks, you can see the following columns populated with values for BigFix DSS Cron:
Schedule = Every 5 minute(s)
Next Run Time = any valid time
Last Run Time = any valid time
Status = Running or blank
Last Result = 0x0
Creator = any valid user
In the properties for BigFix DSS Cron, the “Run As:” field is filled in and the password is correct for that user.
In the properties for BigFix DSS Cron, the “Run:” and “Start in:” fields have valid values – that the paths specified there actually exist.
My guess is the “Run As:” user does not have the correct local security policy permissions (Run As Batch Job). Do you have a GPO that prevents this privilege?
If the above items all seem in tact, we might need to look at a registry setting that the import process uses find the paths to key files. Let me know.
– Jeff
(imported comment written by SystemAdmin)
Jeff,
Thank you for looking into this. The problem is sporadic. It works for a few days and then stops. What we found, based on the details you provided below, is that the scheduled task is there and is running as the service account that the DSS SAM services are running under. We also found that the scheduled task is what gets stuck in a running state.
All we had to do to fix it this morning was stop the task and restart - the imports then ran as expected and on schedule. We watched the process using pslist and can clearly see when it starts and stops, so the next time it happens, we will check to see which subtask is still running.
There does not appear to be any log file associated with the cron / scheduled task job. Is there a way to log the actions of the cron job?
BTW, we upgraded from DSS 1.1 to 1.1.1 and the issue still persists.
Thanks Again,
John
(imported comment written by SystemAdmin)
Logs can be found in :
<DSS_ROOT>\rails\log\etl\2009\09
Where <DSS_ROOT> is the folder DSS SAM is installed.
Example:
C:\Program Files\BigFix Enterprise\DSS\rails\log\etl\2009\09
Other logs might help us diagnose this issue are development.log and mongrel.log, they both are in <DSS_ROOT>\rails\log folder