After move of scalability server, collect task fails with "Software Signatures validation failed for sector..."


Article ID: 36232


Updated On:


CA Automation Suite for Data Centers - Configuration Automation CA Client Automation - Asset Management CA Client Automation - IT Client Manager CA Client Automation CA Client Automation - Remote Control CA Client Automation - Asset Intelligence CA Client Automation - Desktop Migration Manager CA Client Automation - Patch Manager



After moving a Scalability Server to a new Domain Manager the first collect in the engine shows the following error:

"Software Signatures validation failed for sector <new scalability server name>"

The next collects run without an error.

The TRC_SYSTEMENGINE_*.log file shows entries similar to:


041115-07:34:51.8369812L|005636|00001bb4|SystemEngi|debug.cpp | |000000|ERROR | ********************StartFileTransferA:src C:\Temp\\sXa07092 dest C:\Program Files (x86)\CA\DSM\ServerDB\SECTOR\SSFW\W0000061.ZML with uuid not successful 022778A3-7809-4D97-8D39-8D6F6724833E 

041115-07:34:51.8370288L|005636|00001bb4|SystemEngi|debug.cpp | |000000|ERROR | **************RSAPI_WriteSoftwareSignatures CCACopyFile:1 

041115-07:34:51.8370692L|005636|00001bb4|SystemEngi|cmEngine |cAmoSectorITRM::Save|000000|DETAIL | After Write SSF retcode=0 

041115-07:34:51.8370985L|005636|00001bb4|SystemEngi|cmEngine |cAmoSectorITRM::Vali|000000|DETAIL | SaveSoftwareSignatureFile(...) for Windows failed 

041115-07:34:51.8371598L|005636|00001bb4|SystemEngi|cmEngine |cAmoSectorITRM::Vali|000000|INFO | ValidateSoftwareSignatureFiles() Failed. 



Client Automation 12.9 in Windows environment



The transfer of the signatures fails because amrss deletes the SSFW/SSFU dirs in the sector during the move.

After the first collect they are not present in \Program Files (x86)\CA\DSM\ServerDB\SECTOR.

This is reflected by entries in TRC_AMRSS_*.log:

041115-07:34:21.3068312L|005012|00000c1c|RSS |RSS |Debug.cpp |000150|NOTIFY | DM_SectorThread::deleteSignatures: deleting signatures in C:\Program Files (x86)\CA\DSM\ServerDB\SECTOR\SSFW 
041115-07:34:21.3381989L|005012|00000c1c|RSS |cfUtilities |cfUtilities |000000|DETAIL | CFUtilities_rmdir: deleted C:\Program Files (x86)\CA\DSM\ServerDB\SECTOR\SSFW: OK 
041115-07:34:21.3382629L|005012|00000c1c|RSS |RSS |Debug.cpp |000150|INFO | DM_SectorThread::deleteSignatures: sectorPath: C:\Program Files (x86)\CA\DSM\ServerDB\SECTOR\ 
041115-07:34:21.3383950L|005012|00000c1c|RSS |RSS |Debug.cpp |000150|INFO | DM_SectorThread::deleteSignatures: sigdir : SSFU 
041115-07:34:21.3384512L|005012|00000c1c|RSS |RSS |Debug.cpp |000150|NOTIFY | DM_SectorThread::deleteSignatures: deleting signatures in C:\Program Files (x86)\CA\DSM\ServerDB\SECTOR\SSFU 
041115-07:34:21.3618198L|005012|00000c1c|RSS |cfUtilities |cfUtilities |000000|DETAIL | CFUtilities_rmdir: deleted C:\Program Files (x86)\CA\DSM\ServerDB\SECTOR\SSFU: OK 

The problems is with the order of the creation and deletion of the folders.

From the code side we are first trying to create the folders in the path (which would be available then so cannot create new ones) and then delete the folders required.



Apply testfix T5IZ306 which can be provided by the CA Client Automation support department.


Additional Information:

The testfix is only required if it is imperative that the first collect job runs fine from the start.

Because the SSFW/SSFU directories are not present after the first collect, they will be created correctly at the second collect job and the signatures will be written to it.






Release: UASIT.99000-12.9-Asset Intelligence