After applying cumulative 6.2.0.3057, management server fails to start.

Document ID : KB000004704
Last Modified Date : 14/02/2018
Show Technical Document Details
Issue:

After applying Cumulative fix 3057 for Release Automation, the management server will fail to start.

Environment:
OS: Microsoft Windows Server 2008 R2, 2012, 2012R2Database: MSSQL(confirmed, possibly others)Version: 6.2.0.3057
Cause:

Due to limitations on the length of path names to 255 characters, sometimes the above issue will occur due to a ddl file not being copied from the source path(too long) to the destination.

Resolution:

The workaround until this is addressed in the next cumulative, is to take the following steps:

First, to verify this is the issue:

1. Check for the existence of the following file below in your '%nac_install%\webapps\datamanagement\resources\db\migration\mssql':

V6.3.0.0.201609071104001__create_nac_broker_id_in_exec_servers_idempotent_-_MSSQL.sql


If this does not exist within this folder, then you should be able to do the following to fix this issue:


2. Extract the filename above from the original 6.2.0.3057 cumulative release zip archive to a temporary directory(eg; c:\tmp)
3. Copy this file to the directory where it was not present previously from the temporary directory to: (%nac_install%\webapps\datamanagement\resources\db\migration\mssql)
4. Now, restart NAC service via services.msc (Release Automation Server), and upon startup the missing column will be created and the issue should be resolved.

Additional Information:

This was addressed on 11/21/2016 in limited fashion with updates to the README released with cumulative 3057 explaining this issue and the subsequent workaround described herein.

 

If there are any questions at all around this process, please open a ticket with support 24/7 and we will gladly walk you through the process.