“Message Catalog” daemon crashing and not running

Products

• CA Service Management - Service Desk Manager
• CA Service Desk Manager

Issue/Introduction

When performing a 'pdm_status' on a CA Service Desk Manager server, the “Message Catalog” daemon status is “Not Running”.

As per CA SDM design, the msgcat_build process should exist on the BG and all APP servers in an AA architecture.

This process is used to load the localization resource related information, like pdm.xml, into the CA SDM shared memory when the CA SDM service starts. 

If this process is not running, it might have impact on how the localization strings are rendered in the CA SDM UI.

Environment

CA Service Desk Manager 17.x

All Supported Windows Operating Systems

Resolution

As per the OS event logs, the process is crashing with the below exceptions:

Faulting application name: msgcat_build.exe, version: 17.4.0.78, time stamp: 0x64942200
Faulting module name: msgcat_build.exe, version: 17.4.0.78, time stamp: 0x64942200
Exception code: 0xc0000005
Fault offset: 0x000000000007aa69
Faulting process id: 0x26c8
Faulting application start time: 0x01db2276f7caa14a
Faulting application path: E:\PROGRA~1\CA\SERVIC~1\bin\msgcat_build.exe
Faulting module path: E:\PROGRA~1\CA\SERVIC~1\bin\msgcat_build.exe
Report Id: 80feb345-c579-4e6d-974b-38f75d262cd8
Faulting package full name: 
Faulting package-relative application ID: 

CA SDM logs do not provide any additional information.  

According to Microsoft forums, this can happen when the computer is not able to correctly process the files and settings required to run a particular program. 

Microsoft suggests that you check for corrupted Windows system files. The System File Checker (SFC) is a Windows utility that scans for corrupted Windows system files. If it finds a problem, it will try to replace the problematic system files from a cached version that’s on the computer.

To run System File Checker (SFC), follow these steps:

1.  Launch a Command Prompt with 'Run as Administrator'

2.  At the command prompt, type sfc /scannow (note the space between sfc and the /). Scanning will take a few minutes.

If SFC finds corrupted files and replaces them, restart the computer and check if the issue persists.