Error: TSM Error - rc = 610, Unable to open message text file (4218542)

Error after upgradng TSM client (in this case from 5.3 to 6.3)

Complete error message displayed in the Advance Engine Log file:
Executing the query "execute master..xp_slssqlmaint N'-D "DBAtest"  -Bk..." failed with the following error: "
Msg 50610, Level 16, State 1, Line 1572864: TSM Error - rc = 610,  Unable to open message text file

The issue is the access to windows\system32 where a dsierror.log will be created by the TSM\Litespeed backup process.

This error is generated when the dsierror log is accessed. (Please note the creation of this file is done by the TSM API and not Litespeed this is not a Litespeed issue but will pervent Litespeed from starting a TSM backup)

This file is located in two places..the TSM client install and windows\system32 directories

You have two workarounds

1.       Grant the correct access rights for the accounts in question to the windows\system32 directory

2.       Or add the following to the dsm.opt file “errorlogname”

Example:  errorlogname c:\temp\dsierror.log

Give SQL server  and SQL agent startup accounts plus all user accounts that use the LS console  read\write permissions to the windows\system 32  directory 

or 

Use the parameter ERRORLOGNAME in the dsm.opt file.

Format of the parameter:  errorlogname  C:\tsm\dsierror1.log (file name is unimportant only the PATH matters)

If you receive the  error " Unable to open message text file" I would recommend you perform the following steps.  (please note you will need to reboot the server when done). These are most likely the system variables you are referring to.

Add "DSMI_CONFIG=path to dsm file\dsm.opt" to the Environment variables for the server.
1.       Open the Systems applet in Control Panel.
2.       Click on the Advance tab.
3.       Click the Environment variables button at the bottom.
4.       In the System variables area click New.
5.       For Variable name add "DSMI_CONFIG"
6.       For Variable value add the path to the customer's DSM file.

Add "DSMI_DIR = <patch to where the dscenu.txt file is located>" to the Environment variables for the server following the steps outlined above.
(this is the one which should have  fixed your issue)

Add " DSMI_LOG = <Any location> " to the Environment variables for the server following the steps outlined above.