we are running LDMS 8.7 SP2.
Since our last Activation of the core server on friday, we have a strange issue.
Normally we had one scheduled tasks for some basic configuration for all of our clients.
This task is filled by a regular query, we resolved this query on a hour base, to have new clients very fast in the result list for basic configuration.
Due to the fact that the normal scheduled "Schedqry.exe /allqueries" is only scheduled in a 3 hour interval (because it runs very long), we decided to run schedqry for the basic configuration task on a hour base by calling the schedry.exe with parameter /policy=545051 (545051 is the LD_TASK_IDN).
Since our last activation on friday this schedqry.exe /policy=545051 will not resolve the query anymore. There is no exception in schedqry.exe log, only
27.01.2009 11:00:10 : Evaluating queries for task 545051
27.01.2009 11:00:12 : Scheduled query resolution has been completed.
27.01.2009 12:00:10 : Evaluating queries for task 545051
27.01.2009 12:00:11 : Scheduled query resolution has been completed.
27.01.2009 13:00:11 : Evaluating queries for task 545051
27.01.2009 13:00:13 : Scheduled query resolution has been completed.
As you can see the tool woll run for 2 seconds and then stop. But normally the query which is connected to task 545051 will run 10 minutes to resolve.
Due to this fact we have no targets in the task and our basic configuration will not run.
The strange issue is that schedqry.exe /allqueries will resolve the query and add the targets again into the task.
But that is not a way because we can not schedule /allqueries to run on a hour base, because this will takes to long till it ends with resolving all queries.
Anybody any Idea, why this happends after our laster Coreserver activation (licensing is okay).
We have this issue on all of our 4 core servers and we can exactly correlate the misbehaviour with the time point of reactivating the servers.
Is there a XTRACE value for schedqry.exe? I could not find a value.
Thx for any help!