AHD50050 and AHD50060 errors appears when trying to start SDM services after moving database

book

Article ID: 205894

calendar_today

Updated On:

Products

CA Service Management - Service Desk Manager CA Service Desk Manager

Issue/Introduction

sqlagt:Default       3856 SIGNIFICANT  sql_agent.c            245 STARTUP of sql_agent:mdb:key_prov_nxd:Default
confirm_db           4996 SIGNIFICANT  ntservice.c            311 Command return non-zero exit code. Command: redirect -m "C:\Windows\TEMP\tmp24" "C:\Windows\TEMP\tmp25" "C:/PROGRA~2/CA/SERVIC~1/bin/sql_check_db"   -c -s itasm >"C:\Windows\TEMP\tmp24" 2> "C:\Windows\TEMP\tmp25" . Exit Code: 10
pdm_proctor_nxd      4920 SIGNIFICANT  STDIO                    0 AHD50050:A confirmação do BD falhou. Razão: AHD50060:FALHA na verificação do banco de dados.
pdm_proctor_nxd      4920 SIGNIFICANT  STDIO                    0 AHD50051:Encerramento do servidor solicitado.
confirm_db           4996 SIGNIFICANT  api_misc.c             585 Requesting shutdown of system. Reason (AHD50060:FALHA na verificação do banco de dados. )
slump_nxd            4464 EXIT         server.c              2857 Slump_nxd was requested to shutdown. Check Prior log information.

Cause

Script from source database has not been run so there are empty tables in mdb

Environment

Release : 17.1

Component : SERVICE DESK MANAGER

Resolution

Implement step 5 to load data into mdb database:
https://techdocs.broadcom.com/us/en/ca-enterprise-software/business-management/ca-service-management/17-2/administering/moving-the-ca-mdb-data-from-the-source-to-the-target-systems/moving-the-ca-mdb-database-on-microsoft-sql-server.html