Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

Server Configuration Manager Collector service starts but immediately stops without errors (1023922)

Symptoms

  • Server Configuration Manager (SCM / VMware vRealize Configuration Manager, formerly known as VMware vCenter Configuration Manager) Collector service starts but immediately stops without errors.
  • SCM / vRealize Configuration Manager Collector service will not remain started.
  • SCM / vRealize Configuration Manager debug log contains errors similar to: 

    error converting IDENTITY to data type int.

Resolution

This issue can be resolved immediately by truncating the debug event log tables using this SQL script:

USE SCM
GO
TRUNCATE TABLE ecm_dat_log_debug_event
GO
USE SCM_Coll
GO
TRUNCATE TABLE ecm_dat_log_debug_event
GO

If you cannot truncate the logs because of active troubleshooting actions, you can reduce the table size by:

  • Reducing the Debug Log retention time
  • Manually purging the debug logs

The proceeding sections describe how to do each of these tasks. If the issue persists, file a support request with VMware Support and note this KB article ID in the problem description. For more information, see How to submit a support request .

Reducing the Debug Log retention time

To reduce the Debug Log retention time:
  1. Navigate to Administration > Settings > Windows > Data Retention.
  2. Change the Debug Log setting to the default.

    Note: The default debug log retention setting is 5 days. If the Debug Log retention setting has not been changed or is set to the default of 5 days, continue to the next section to purge the debug logs.

Manually purging the SCM / vRealize Configuration Manager debug logs

To manually purge the SCM/vRealize Configuration Manager (formerly known as VMware vCenter Configuration Manager) debug logs, run this SQL script to run the debug log purge operation:
USE SCM
GO
EXEC ecm_sp_command_purge_logs
GO
After the debug log purge script completes without errors, try to start the SCM/vRealize Configuration Manager Collector service again.
 
If the issue persists, file a support request with VMware Support and note this KB article ID in the problem description. For more information, see How to submit a support request .

Additional Information

This issue may occur because the IDENTITY property of the debug event log table has increased to the limit of the INT data type (2,147,483,647). This issue can occur for these reasons:

  • The debug event options are set to Exception, Error, Warning, and Info for the Collector and Database for a long period of time.
  • The retention settings for Debug Log are set for a large number of days.

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 0 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 0 Ratings
Actions
KB: