LiteSpeed for SQL Server Version 6.0 - Defect or Enhancement Requests that have been addressed in (4277241)

Installer

ST#61376

The installer does not warn when there is not enough disk space for installation.

Backup and Restore

ST#72662

Smart Diff may crash with the error "ResultSet" property not set correctly".

ST#67834

The "Cannot use KILL to kill your own process" error may occur when trying to restore msdb.

ST#69888

Using the parameter @verify or @verifyonly may cause backups to fail with VDI errors.

Double-Click Restore Backups

ST#66256

The "Restore/backup from/to file with .exe extension is reserved for executables with embedded backups" error may occur when creating a mirrored double-click restore.

ST#69194

Double-Click Restore may fail to restore a database if UAC is turned on.

TSM Backups

ST#68978

LiteSpeed should populate all TSM properties fields correctly.

ST#71479

When restoring to a point in time LiteSpeed may select the wrong backup to restore.

ST#72557

LiteSpeedx64 engine may crash if the dsm.opt file is missing.

Tape Backups

ST#71196

The "Cannot read dataset 1 from tape" error may occur when attempting a restore from tape.

Maintenance Plans

ST#66035

Maintenance plan may fail with the error - "Possible failure reasons: Problems with the query, "ResultSet" property not set correctly".

ST#71567

Creating a maintenance plan may fail on a SQL 2000 box.

ST#71200

A plan should be able to be exported to other SQL instances.

ST#61846

Maintenance plan reporting needs to be improved to include more options and details as it had in LiteSpeed 4.8.4.

ST#70517

Maintenance plan stops executing if an error is encountered and does not continue backing up other databases.

ST#69018

When editing a maintenance plan, request an option to save it to file.

ST#73146

Cannot select the second email operator from the drop-down list.

ST#73815

The Fast Compression Backup task may fail, if a database is in read-only mode.

ST#71993

Double-click restore backup fails if a maintenance plan is configured to backup all databases.

ST#73208

Maintenance plan report lists deleted databases.

ST#65602

Databases involved in log shipping are not excluded from a backup task by default.

ST#69897

When a plan is set up to check database integrity, the html report file is empty, but there is data in the generated text report file.

ST#68832

LiteSpeed fails to load 4.8.x legacy plans in LiteSpeed Console, if they have several schedules within one task.

ST#69490

The "Include first-level subfolders" option in the Clean Up task deletes files in folders below first level.

ST#70663

LiteSpeed is allowed to close without asking user if they would like to save changes made in the maintenance plan.

ST#69870

Changes made to a maintenance plan in SSMS are reverted back to the default, if the plan is edited and saved in the LiteSpeed Console.

ST#71360

Add -DelTxtRpt and -DelHtmlRpt to non-legacy maintenance plans.

Log Shipping

ST#66901

Restoring a backup may fail with "ERROR 10200: The Backup name exceeds the maximum length (128 characters) imposed by SqlServer".

ST#70752

Cannot set acceptable latency greater than 999.

Object Level Recovery

ST#73,682

OLR does not recover a column as empty when variable length data not available for that column but no null bit on.

ST#72637

OLR may fail if there are gaps in the sequence of log operation between a full and a differential backup.

ST#70812

The "Invalid use of null pointer bcp_bind" error may occur when trying to restore a very large table on SQL Server 2000.

ST#64861

OLR tail log processing cannot handle LOP_FORMAT_PAGE log operations that fully logged the page.

Performance

ST#69513

Optimize query performance when retrieving statistics in the Backup History tab.

ST#71076

The ActivityManager.exe process may consume nearly 100% of the CPU on a 64-bit system.

ST#74331

LiteSpeed may hang when CPU throttle parameter is used.

ST#67802

Writing backups to SAN may cause heavy write latency.

ST#73140

When running a TSM backup it takes much longer than the same backup saved to a local disk.

ST#70684

Executing TSM filespace queries may take a long time.

ST#72728

Executing xp_restore_verifyonly may have a 5 second delay.

UI

ST#69886

The Instance Configuration Wizard does not come up to the foreground on a Server 2008 machine.

ST#68051

Backup file name cannot be edited in the Backup wizard without re-entering (or browsing to) the backup directory path.

ST#65596

The Activity page should show failed log shipping plan names rather than or in addition to planID.

ST#70111

LiteSpeed does not display all drives in Backup Manager.

ST#73714

The LiteSpeed Jobs tab does not show maintenance plan jobs on SQL Server 2008.

ST#70748

The LiteSpeed Console may crash on exit, if the first character in computer name is number.

ST#68801

The "Could not load file or assembly 'ActiproSoftware.WinUICore.Net20, Version=1.0.93.0" error may occur when launching the LiteSpeed Console.

ST#69029

The "Cannot find table 0" error may occur when using the Show database status option and when trying to connect to SQL Server.

ST#70930

The Overview tab shows the "Operation completed with errors: System.xml.xsl.runtime.stringconcat.concatnodelimiter(system.sring)" message.

ST#72349

Description for a subplan or a maintenance plan is not shown in Job Manager.

ST#61254

Provide an option to disable error messages warning that a local repository is not found by the UI.

ST#53599

The Backup wizard should remember the specified path to the dsm.opt file so that it is available next time the backup or restore wizard is used.

ST#67002

Error messages should contain more details when login fails.

ST#70314

Error should be reported when LiteSpeed fails to write backup file header.

T-SQL

ST#62710

The LiteSpeed license key information should be available using a T-SQL command.

ST#70162

Unless the user also specifies @FileNumber with @attachedfiles, details are returned as if @HeaderDetails='all'.

Logging

ST#66929

Logging should be added to instance configuration.

ST#68409

Encryption passwords should not be visible in the advanced trace log.

Date and Time

ST#72558

Value specified for EXPIREDATE parameter is invalid on server with British English.

ST#70415

'Custom' is not a valid value for 'timeZoneId' error occurs when current TimeZone is set to (GMT) Coordinated Universal Time.

SmartCleanup

ST#73345

SmartCleanup sometimes does not delete all expired backup sets (files).

Permissions

ST#60550

Local repository may be unavailable, if SQL service startup account has only read access to the registry.

ST#55681

The log shipping tables are not created or updated on cluster.

Documentation

ST#73720

Document how to recover objects from a TSM backup.

ST#69191

Explain the difference between the native SQL Server and the LiteSpeed maintenance plans.

ST#70676

Explain the difference between the Remove files older than option and the Clean Up Maintenance Plans task.

ST#67698

Document @tsmarchive and @tsmbrieflist parameters for xp_view_tsmcontents.

ST#70931

Document @BackEnd.

ST#73553

Should explicitly state that the TSM parameters, @tsminsdatelower, @tsminsdateupper,' @tsmexpdatelower, @tsmexpdateupper can only be used with TSM archive.

ST#68071

Add examples with @With = checksummm and checksum.

ST#67547

Add a sample with and parameters, a sample with a striped backup file.

ST#67755

Document how to correct for warning that repositories are not compatible