Hi,

We have Opalis 6.3 running on Windows 2008 R2. Our max policy limit per action server is 200. we have 4 action servers.

Today primary action server stopped running new jobs. When i queried database, it only showed about 10jobs assigned to this action server but there were about 60 PolicyModule.exe in task manager. Since there were no corresponding PolicyInstances, I assume these processes were left behind from previous executions and didn't close.

I didn't find anything useful in Events table, action server logs, event viewer and performance counters (mem/cpu/disk).

Wondering if anyone else had simialr issue where policymodule.exe processes are left behind by Opalis and if there is any resolution to this problem?

Regards,

Saad

Hi Saad,

never seen that.

Does this query detect the "missing" instances?

SELECT     POLICIES.Name, POLICYINSTANCES.ProcessID
FROM         POLICIES INNER JOIN
                      POLICYINSTANCES ON POLICIES.UniqueID = POLICYINSTANCES.PolicyID INNER JOIN
                      ACTIONSERVERS ON POLICYINSTANCES.ActionServer = ACTIONSERVERS.UniqueID
WHERE     (POLICYINSTANCES.TimeEnded IS NULL) AND (ACTIONSERVERS.Computer = 'NAMEOFTHEACTIONSERVER') AND (POLICIES.Published = 1)

Regards,

Stefan

No. There are no active policies in policyinstances table i.e. i stopped all jobs on this particular action server and above query resulted in zero rows. Still there were several policymodule.exe were running.

Not sure what can possibly cause this executable to not exit. If i check policyinstances history for those ProcessIDs, they appear to have completed successfully as per published data.