LiteSpeed for SQL Server 8.9.8 - User Guide

Troubleshoot LiteSpeed

Refer to the Release Notes for the current list of issues known to exist in this version of LiteSpeed.

Troubleshoot LiteSpeed Activity

Local repository is not populated

If the computer name is changed, the local repository settings are not found, because LiteSpeed refers to the old computer name. As a result, the Local Repository database is not being populated and you cannot view LiteSpeed activity.

You need to update @@SERVERNAME for all instances on that computer and re-run the Instance Configuration wizard.

To update @@SERVERNAME value

Run the following:

exec sp_dropserver 'old_name'
exec sp_addserver 'new_name', 'local'

To run Instance Configuration

1. Select Start | All Programs | Quest Software | LiteSpeed for SQL Server | Instance Configuration.
2. Review the names of the instances on the SQL Instances step.
3. Complete the wizard.

4.x jobs not displayed

The timeline does not automatically show 4.x backup/restore jobs. However, you can manually rename the jobs and they will appear in the timeline.

To view 4.x jobs

• Rename backup jobs to:

  LiteSpeed Backup SERVER_NAME.database_name

• Rename restore jobs to:

  LiteSpeed Restore SERVER_NAME.database_name

Be sure to use upper case for SERVER_NAME. Additionally, you need to add a comment to maintenance plans to provide information about the databases involved in the plan:

• Comment should begin with /** and end with **/
• Specify the databases inside {}. Use a semicolon as a separator. For example: {northwind;pubs;litespeedlocal}
• {*system} means all system databases.
• {*user} means all user databases.
• {*} means all databases
• It is possible to use combinations. For example: {northwind;pubs;litespeedlocal}{*system} means all system databases plus specified. {master}{*user} means all user databases plus master.

Dell storage appliance not working with LiteSpeed

LiteSpeed has been tested and is certified to work with Dell DR4000, DR4100, and DR6000 storage appliances. In rare cases the DR storage appliance may not work with LiteSpeed.

To check the DR storage appliance

1. Confirm the access rights of the SQLserver\agent startup account to the DR resource.
2. Confirm network connectivity between the SQL server and the DR storage appliance.

Troubleshoot Maintenance Plans

Leverage SSIS and LiteSpeed advanced options

Some tasks and advanced options can be unavailable if you do not select Use LiteSpeed when configuring tasks. See About Automating Maintenance Tasks for more information.

Install Backward Compatibility components

If you receive one of the following error messages, you probably need the Backward Compatibility components installed:

• "Executed as user: ... sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed."- double-click a plan in the History page to view the event message.
• "The SQLDMO 'Application' object failed to initialize." - run the maintenance plan task script in SSMS 2008.

For more information, see http://support.microsoft.com/kb/955626.

Resolve upgrade issues

LiteSpeed plans may fail after the in-place upgrade of SQL Server. Upgrade LiteSpeed Maintenance Plans

Analyze log information

Enable advanced logging and review log files for errors or work with Quest Software support to identify and resolve plan problems. Reporting and Logging in Maintenance Plans

NOTE: For all scenarios, the best is to upgrade all of your servers to the latest LiteSpeed version.

Upgrade LiteSpeed Maintenance Plans

LiteSpeed for SQL Server Upgrade

If upgrading LiteSpeed 5.x or later, the Maintenance Plans should remain intact and no additional steps are required. See the LiteSpeed Installation Guide for more information about the upgrade scenario.

If upgrading LiteSpeed 4.x, the SSMS plug-in maintenance plans need to be manually upgraded. LiteSpeed allows you to read SSMS plug-in maintenance plans and upgrade them to SSIS LiteSpeed maintenance plans.

To upgrade a maintenance plan

1. Select Maintenance Plans in the Navigation pane (CTRL+4).
2. Right-click a maintenance plan and select Convert to LiteSpeed.

NOTE: The Remove files older than option in the Backup Database task does not remove LiteSpeed 4.x SSIS maintenance plans backups. To remove old backup files for these plans, you can use a separate Clean up maintenance plans task.

SQL Server In-Place Upgrade

SSIS LiteSpeed plans must be manually upgraded to use the appropriate library, otherwise they will fail after SQL Server upgrade. If you have at least one LiteSpeed task in a SSIS plan, then you need to upgrade the plan after upgrading SQL Server to a higher version.

To upgrade plans in LiteSpeed 6.1 or later

Right-click an instance in the Maintenance Plan pane and select Upgrade LiteSpeed Maintenance plans.