SDM: After applying a cumulative patch or update, pdm_configure fails during the task named "Create localized resources".

book

Article ID: 49197

calendar_today

Updated On:

Products

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

Issue/Introduction

pdm_configure fails during the first step, Create localized resources.

During the failure, the following messages are written to $NX_ROOT\log\configure.log:

WARN TaskMediator.java 220 Create localized resources : Task failed (Create localized resources ). Continue?

The generation of localized resources had errors.

Please check the resource.log for detailed information.

 

Environment

Release:
Component: CA Service Desk Manager

Resolution

Verify that you have correctly applied the language patch of a cumulative patch set.

For example, for 12.6 CA SDM, cumulative patch #3 consists of three patches: a binary patch, a forms patch, and a language patch. The language patch must be unzipped using cazipxp. When it is unzipped, several .caz files are extracted. These are language-specific patches. One of these language-specific patches must be applied to Service Desk Manager using applyptf.

Specifically, for 12.6 CA SDM Cum#3, the language patch is patch RO53134. The language-specific patch for the English language that is contained in RO53134 isRO53126.

If you do not apply a language-specific patch, then when you run pdm_configure, the first task that is executed (after you finish entering the required information in the input forms) fails. The first task is called "Create localized resources". You should exit from the Configuration tool, apply the appropriate language-specific patch, and then re-run the tool.


One can also examine the resource.log file in the SDM Install's log directory for further information.  In one example, the following log entries were observed:

Creating localized resources in C:\PROGRA~2\CA\SERVIC~1\data\merged\ENU
Processing sa.dat with sa.xml
Processing sa.dat to reset the timestamp with that of XML file sa.xml
Processing sa_locale.dat with sa_locale.xml
Processing sa_locale.dat to reset the timestamp with that of XML file sa_locale.xml
Processing sa_messages.dat with sa_messages.xml
MergeXML: PDM_I18N tag "sa_branding:footer:1000:_nbsp;Copyright _copy; COPYRIGHT_YEAR_REPLACE Broadcom. All" is used in C:\PROGRA~2\CA\SERVIC~1\data\tagged\sa_messages.dat , but not defined in C:\PROGRA~2\CA\SERVIC~1\data\resources\ENU\sa_messages.xml

Processing sa_messages.dat to reset the timestamp with that of XML file sa_messages.xml

Of particular interest are the entries highlighted in bold.  Similar messages may also appear in the same log, ie:

German (language code DEU highlighted in bold)
MergeXML: PDM_I18N tag "sa_branding:footer:1000:_nbsp;Copyright _copy; COPYRIGHT_YEAR_REPLACE Broadcom. All" is used in C:\PROGRA~2\CA\SERVIC~1\data\tagged\sa_messages.dat , but not defined in C:\PROGRA~2\CA\SERVIC~1\data\resources\DEU\sa_messages.xml

French (language code FRA highlighted in bold)
MergeXML: PDM_I18N tag "sa_branding:footer:1000:_nbsp;Copyright _copy; COPYRIGHT_YEAR_REPLACE Broadcom. All" is used in C:\PROGRA~2\CA\SERVIC~1\data\tagged\sa_messages.dat , but not defined in C:\PROGRA~2\CA\SERVIC~1\data\resources\FRA\sa_messages.xml

One may need to examine the affected files, in this case, sa_messages.xml.  The above is a variation on the finding that the localized patch content may not have applied successfully.