Common Rollup Errors and Solutions

Version 1

    Verified Product Versions

    LANDESK Management Suite 9.6LANDESK Management Suite 2016.x

    Error 1:

    If you are seeing the following error, make sure that your SQL Server's SERVERNAME is correct. Within SQL Server Management Studio, execute SELECT @@SERVERNAME. If the server name is incorrect, use sp_dropserver and sp_addserver to correctly set the local name of the server.

     

    When executing sp_adddistributor for a remote Distributor, you must use a password. The password specified for the @password parameter must be the same when the procedure is executed at the Publisher and at the Distributor.

    1.png

     

    Resolution:

    In the Replication Definition configuration page, please make sure the "DBMS Server" is filled with the proper instance name. If your SQL server is using named instance, please write down the full name "hostname\instance name". Only when it's default instance, it need to be written as "hostname".

     

    Error 2:

    Column 'Name' in table 'ENVIRONSETTINGS' is of a type that is invalid for use as a key column in an index.

    2.png

     

    Resolution:

    The cause of the issue is when we trying to fix some inventory issue, we may change the column length following Database Exception: Error Committing on Table: . The change on the table Environsettings column Name is leading to this issue. The max length should be under 900, here I change that to 600. When SQL replication is used, the coredbutil method to change column length will not work, so here we use the SQL alter command.

    1. Open Management Studio, connecting to source DB, right click on it and select "New Query", then run the command below:

    alter table environsettings alter column name nvarchar(600); 
    

    2. connecting to the rollupDB, right click on it and select "New Query", run the command below:

    alter table environsettings alter column name nvarchar(600); 
    

    3. Run the rollup again and this error should be gone.