Error during the installation: Configuration task is failed in step 12 (sometimes 13)
search cancel

Error during the installation: Configuration task is failed in step 12 (sometimes 13)

book

Article ID: 5805

calendar_today

Updated On:

Products

CA Service Desk Manager CA Service Management - Service Desk Manager

Issue/Introduction

During the installation, a problem in Configuration Task phase, with error message related to extension table validating, could happen.

Configuration task is failed in step 12

Sometimes the failure could be in step 13.

Messages in configure.log:

-----

INFO  ConfigThread.java      549 Executing task# 12, task name : Validate Extension Tables

INFO  Task.java              214 Running: Validate Extension Tables

INFO  CheckExtensionTables.java   184 Starting CheckExtensionTables

ERROR CheckExtensionTables.java   278 '1234' is not recognized as an internal or external command,

ERROR CheckExtensionTables.java   278 operable program or batch file.

ERROR CheckExtensionTables.java   220 An unexpected error occurred check state of Extension Tables.

See configure.log for additional details.

INFO  CheckExtensionTables.java   230 CheckExtensionTables complete

INFO  Task.java              276 retCode 99999: An unexpected error occurred check state of Extension Tables.

See configure.log for additional details.

WARN  ConfigThread.java      582 Configuration task (Validate Extension Tables) is failed in step : 12

-----

In a German localized release the message is:

Configuration task (Erweiterungstabellen validieren) is failed in step 12

Sometimes the failure could be in step 13.

Other messages in configure.log:

-----

ERROR CheckExtensionTables.java 278 Der Befehl "1234" ist entweder falsch geschrieben oder

ERROR CheckExtensionTables.java 278 konnte nicht gefunden werden.

..

ERROR CheckExtensionTables.java 220 Beim Überprüfen des Status der Erweiterungstabellen ist ein unerwarteter Fehler aufgetreten.

 

-----

 

Environment

CA Service Desk Manager 17.x

Cause

The problem could be due to a pipe symbol "|" in the mdbadmin password.

The pipe causes a command separation and the part after the pipe symbol is wrongly interpreted as a command.

Resolution

Remove the pipe symbol "|" from the mdbadmin password.