Deployment Manager: Last Event more than 3 weeks old

Hi David,

That's right. Run the following query against the InTrust_Cfg_DB via SQL Studio:

Delete From [dbo].[ITRTAgentDataSource]

Thank you,
Chris

Hi Chris,

The computer Status for my domain controllers in my collection is showing 'Configuring' and from time to time when I refresh, some of the servers are Green and collecting and the Last event date is current.

I can refresh after 10 minutes and the Collecting servers turn back to configuring.

I did not install the update and hotfix AFTER removing the stale records, I did it before. could this have an impact on what I am seeing?

David

Hi David,

Please try stopping the InTrust services once again and run the following 2 queries against the InTrust_cfg_db:

Truncate Table [dbo].[ITRTAgentDataSource]
Truncate Table [dbo].[ITRTAgent]

Once complete re-start the services and allow some time for the collections to update.

Based on the results, it sounds like there was some duplicates created previously in ITRTAgent table as well. Clearing both should help resolve the issue. Now that you have the patch applied will prevent the problem from returning.

Let us know the results.

Thank you,
Chris

Hi Chris,

That did the trick! Al servers are 'Collecting' and the Last event date is current.

Thank you for your support!

david

Hi Chris,

As mentioned, all servers are 'Collecting' and the Last event date is current. This is working fine in my DEV environment.

In my PRODUCTION environment, all servers are 'Collecting', however, the Last event date for some servers is old, other servers it is up-to-date. This can also change. On an up-to-date server, if I reopen the Deployment Manager, it will no longer show an up-to-date value for the Last event date, instead it switches back to the older date. This is random for the servers that are collecting.

I have performed the SQL Server actions on the InTrust_Cfg_DB database and have installed the hotfixes.

Any other thoughts or options?

david

Hi David,

Are we certain it is the correct InTrust_Cfg_DB we targeted?

Can check on the InTrust server via the following registry key if the database is the right one:

HKLM\Software\Wow6432Node\Aelita\ADC\CfgConnection\

Datasource= SQLServer
Initial Catalog = InTrust_Cfg_DB_Name

Another possible reason might be if not clicking 'Execute' when running the SQL query but instead clicking 'Parse' (the check-mark) in SQL Studio. It clicking 'Parse' this would just check the query for validity and not delete anything.

Try executing the query like this:

Truncate Table [dbo].[ITRTAgentDataSource]
Select Count(*) From [dbo].[ITRTAgentDataSource]
Truncate Table [dbo].[ITRTAgent]
Select Count(*) From [dbo].[ITRTAgent]

You should see that there are 0 entries returned for both tables. They will start re-populating with new entries short time after InTrust services are re-started.

Hi David,

We have a KB article created for this issue:
support.quest.com/.../agents-within-a-collection-switch-from-configuring-to-collecting-or-have-out-of-date-last-event-timestamps
Please update if you still having the issue and if the link helps.
Thanks.