smart upgrade troubleshoot

8/3/2019 Smart Upgrade Troubleshoot

1/4

Tips and tricks for troubleshootingSmart Upgrade issues

Technote (troubleshooting)

Problem

This document contains tips and tricks for troubleshooting Lotus Notes SmartUpgrade (SU) issues including errors or unexpected behavior.

Symptom

Some of the symptoms of problems include:

-- No prompts for users-- Files missing-- No kit found and other errors-- Upgrade incomplete

Resolving the problemThis content, "Tips and tricks for troubleshooting Smart Upgrade issues", nowresides in the Lotus Notes wiki. The purpose of a Lotus product wiki is to sharedeployment experiences and best practices and help IBM to create scenariosfor successful deployments. Please check the Lotus Notes and Domino wiki forthis type of content in the future.

Checking on the server side:

* If you are using separate Configuration documents for every server, theSmart Upgrade Kit database must be on every home mail server, and every

server must have a correct link in the appropriate Configuration Document.

* The link to the SU database in the server's Configuration Document shouldbe taken from the server. You can check the Link hint to make sure it's thecorrect one

* The SU cache is updated hourly but you can do a "sucache refresh" on theserver console if you suspect that it hasn't been updated (due to server load) orif you just want to refresh it. You can run "repl SUServername" (whereSUServername is the name of the server hosting the kit documents andpackages) to force the mail server to connect to SU server

Documentinformation

Lotus Notes

Software version:

6.0, 6.5, 7.0, 8.0

Operating system(s):

Linux, Windows

Reference #:

1306212

Modified date:

2010-06-03

Page 1 of 4IBM Tips and tricks for troubleshooting Smart Upgrade issues - United States

09/Sep/11https://www-304.ibm.com/support/docview.wss?uid=swg21306212


2/4

* When using policies to push SU, make sure that the Desktop SettingsDocument has the "Deploy version" option set to "Release x.x.x" (withoutquotes), for example, "Release 7.0.3". Other settings do not usually create aproblem. This also has to match the "Target version" field in the SmartUpgrade Kit Document. Policies are not a mandatory part of SU since it willprompt users to upgrade if a matching kit document is found on the server(provided Dynamic Client Configuration [DCC] works) and it will find SU

entries in the notes.ini file.

* All users to be upgraded must have appropriate rights to the server on whichthe kit is located.

* SU tracking reports are a good feature to have. For more information onconfiguration and troubleshooting using these reports, refer to the followingIBM Redbooks publication, "Understanding Lotus Notes Smart Upgrade".

Checking the Smart Upgrade database:

* The SU database Kit Document must contain the same "Target version" asthe "Deploy version" in the Desktop Settings Document.

* If you enter anything in the SU Kit Document --> Advanced --> "AllowedUsers & Servers" field, you must also add LocalDomainServers to it since it isa Readers field. If this field is blank, it applies to all.

* The "Optional arguments" field is only visible in the Kits view of the SUdatabase if the Location field contains "On a Shared network drive" or "Sharednetwork drive & attached kit".

* When using the "qb" or "qn" switches for optional arguments, you can use"gb+! " to hide the Cancel button, such as in

-s -a /s /v"TRANSFORMS=\\server\notes\upgrade.mst" /qb+"

* If you have SU tracking enabled in Notes 6.5.3, theLotus\Notes\data\IBM_TECHNICAL_SUPPORT\SmartUpgrade directorycontains a new log for every SU attempt. These are attached to reports foradministrators to view. For information on how to read these logs, refer to theRedbooks publication, "Understanding Lotus Notes Smart Upgrade", page 47.* Starting with Notes 6.5.5, SU has the ability to determine the type of clientinstalled (single or all). The SU process can only upgrade to and from the sameinstallation type. If you want to change the installation type, you mustmanually upgrade to the desired installation type.

* If you want to use the "On a shared network drive" location in the KitDocument, the client package must be unpacked on the network location to beused. Remember that you can only use a UNC path in the Kit Document, suchas \\networkfileservername\shareddirectoryname\setup.exe.

* Staring with Notes 7.0, the SU Kit Document contains a Localization fieldwhich must correspond to the installed client (on user machines). Make surethis matches the language version of the kit because it is only compared withthe language of the installed client.

It is also very useful to configure a Smart Upgrade Tracking database:




3/4

Doc #: 1312864 "How to configure and use Smart Upgrade Trackingdatabase"URL: http://www.ibm.com/support/docview.wss?rs=899&uid=swg21312864

Checking on the client side:

* All users must have sufficient rights and privileges on the operating system

(as an administrator). If that is not the case, you can use the SURunAs facilityto upgrade the clients. Refer to Document #1247849, "Using the 'SmartUpgrade Run As' feature to upgrade Notes clients".

* All users must be able to connect to the server and open the database.Accurate server information must be present in the user Location documentswith the server name in hierarchical format.

* To check if DCC is enabled in the notes.ini file, the following parametersshould be included: DisableDynConfigClient=0 and DocumentAcceptUpdates=1 (in the Location Document).

* Starting with Notes 6.5.3, after the kit is downloaded, the client willautomatically shut down without a notification. In 7.0 releases, users areprompted whether to start the process or not. If they don't start it, they canresume by going to the File menu --> Tools --> Notes Smart Upgrade, or it willstart again after the interval set in the notes.ini file parameters,SU_NEXT_UPDATE and SUT_NEXT_UPDATE. These settings in thenotes.ini file can be removed for troubleshooting.

* For the Notes client only, check the install client type in the notes.ini file(InstallType=2 [All clients], InstallType=6). If these are not correct in Notes orif they were modified, they must be corrected for the SU to occur.

* The Smartupgrade*.log is found in the

Lotus\Notes\data\IBM_TECHNICAL_SUPPORT\SmartUpgrade directory. Anew log is created for each SU attempt (the naming convention [email protected]). If SU trackingis enabled, it is attached to the report sent after each attempt to the SU UpgradeTracking report mail-in database. If policies are not used, the log is stillcreated. This is very useful since it can tell you why the SU is failing.

* The Lotusinstall.log is created during the Notes client installation andoverwritten at each upgrade. SU also writes to this file (located inc:\Documents and Settings\WinLoginName\My Documents) which is also e-mailed to the tracking reports database.

* When debugging, you can also use the parameter, Debug_Smart_Upgrade=1,

on either the client or server.

Related information

Using the 'Smart Upgrade Run As' feature to upgrade NotUnderstanding Lotus Notes Smart Upgrade

Cross Reference information




4/4

Rate this page:

Rated by 0 users

Copyright and trademark information

IBM, the IBM logo and ibm.com are trademarks of International BusinessMachines Corp., registered in many jurisdictions worldwide. Other product andservice names might be trademarks of IBM or other companies. A current listof IBM trademarks is available on the Web at "Copyright and trademarkinformation" at www.ibm.com/legal/copytrade.shtml.

Segment Product Component Platform Version Edition

MessagingApplications

LotusDomino

Lotus DominoServer

AIX, Linux,Solaris,Windows

8.0, 7.0,6.5, 6.0


09/Sep/11https://www 304 ibm com/support/docview wss?uid=swg21306212