Kategorie
Product Version
Topic
Subtopic
Configure LiteSpeed backup with SQL proxy account (4374392)
When security policies restrict access to the backup destination and requirements are not met for SQL Services backup/restore operations fail with error: "Backup of database "Database" failed.
Is there a way to ensure Transaction Log backups are not overwritten, and contain timestamps within the filename? (4374354)
Is there a way to ensure Transaction Log backups are not overwritten, and contain timestamps within the filename? ... In the Maintenance Plan, select the option 'Create unique media' at the time of taking the .TRN backups.
Unable to find credentials/You must specify AccessKey and SecretKey to connect to Amazon S3 (4373890)
When working with an IAM Role authenticated EC2 Instance and <strong>IMDSv2</strong> set<strong> </strong>to <strong>Required</strong>:<br> ... <p style="text-align: center;"><strong><img src="https://prod-support-images-cfm.s3.amazonaws.com/KB_kA06R000000HLYbSAO_003.png"></img></strong></p>
Restoring a database backup is stuck at 0% (4373825)
When restoring a backup made in Litespeed, from a mapped network drive (e.g. ... Y:\), it hangs at 0% and never completes.<br>There is no job failure in the Litespeed Activity window though, and no errors in the Event Viewer.
Hanging SPIDS from LiteSpeed processes in a killed/rollback state (4323452)
When you kill the SQL Server spid for a LiteSpeed backup/restore process, the spid may go into a killed\rollback state which may process slowly or hang. ... Then kill the spid in SQL Server. ... If that does not resolve, restart the sql server service.
How to create a LiteSpeed support bundle? (4252047)
How to create a LiteSpeed support bundle? ... RDP to the machine that you would like to create the support bundle, then launch LiteSpeed console. ... Under the Backup Manager tab, highlight the local instance.
'Failed to execute operation LiteSpeed restore for database DatabaseName. Message Unexpected termination on thread: 0, Return code: x80770004 when running a restore (4371708)
The following error appears when trying to restore from a cloud location:<br><br>'Failed to execute operation LiteSpeed restore for database DatabaseName.<br>Message Unexpected termination on thread: 0, Return code: x80770004<br><br>The media family on device LiteSpeed® for SQL Server® backup file is incorrectly formed. SQL Server cannot process this media family.'<br><br>It fails with random transaction logs, This issue may occur with SQL Server 2019 with CU13 installed Please upgrade SQL Server to CU16 or above (the latest for SQL Server 2019 CU is CU19) and after upgrading perform again the steps to check if the issue is fixed
Maintenance Plan failure with OPTOLR option checked (4255582)
In order to use @OLRMAP=1, the sql server user will need to have read/write access to the cluster service users temp directory. ... <p>On a cluster, the temp directory returned from theOperating Systemis the temp directory of the user that is running the cluster service, which will be %USERPROFILE%\Local Settings\Temp.<br><br>Resolution:<br>1.
How to query multiple servers for LiteSpeed information? (4354277)
<div>How to query multiple servers for LiteSpeed information? ... Is there a built in feature to gather information regarding the LiteSpeed application?</div> <div>LiteSpeed does not have a built-in function to query multiple servers for LiteSpeed application information at the same time.
Version mismatch when setting up Log Shipping (4220516)
Please check the version of LiteSpeed Logshipping in the LSOption table of the LiteSpeedLocal table on both the Publisher and Subscriber(s). ... In query analyzer: use LiteSpeedLocal go select LSVersion from LSOptions
Does the LiteSpeed Activation key need to be changed after an upgrade of SQL Server? (4256189)
Does the LiteSpeed Activation key change after an upgrade of SQL Server and re-install LiteSpeed.? ... New license key is not required. ... It is advised that the LiteSpeed be uninstalled prior to the SQL Server update and reinstalled when the new version of SQL Server is running.
"Error: Timeout expired" when setting up Logshipping (4353569)
Make sure the SQL Server Service Account and the SQL Server Agent Service Account are run under the same domain account and have permission on the both the Publisher and Subscriber servers. ... The accounts must be able (have the right) to access the other master and msdb database, to call system procedures, to create jobs and have full permission to access LiteSpeedLocal Database.
Error: On-disk structure backup version 611. Server supports version 539 (4256371)
Full error message: The backup database has on-disk structure backup version 611. ... The server supports version 539 and cannot restore or upgrade this database. ... This error occurs when restoring SQL Server 2005 backup to SQL Server 2000.
Is there any direct translation between xp_slssqlmaint and xp_backup_database? (4351811)
Datetime punch and delete old backups capabilities is not avaliable in xp_backup_database.</p>
Can't delete old central repository connection from Enterprise Console (4250818)
Central repository was moved to another server or instance. ... However, prior moving the repository, it was not deleted from Enterprise Console. ... When attempting to delete and add new central repository in Enterprise Console, the old central repository will not delete.
Is it possible to do partial backups in SQL Server 2005? (4313646)
Partial backups are new in SQL Server 2005. ... Description from Microsoft Books Online: A partial backup is similar to a full backup, but a partial backup does not contain all of the file groups.
RESTORE ERROR: "The log in this backup set cannot be applied because it is on a recovery path inc (4353602)
When doing a restore, the following error is displayed: The log in this backup set cannot be applied because it is on a recovery path inconsistent with the database ... This is not a LiteSpeed Error.
SQL Server 2005/2008 Upgrade Advisor has picked up LiteSpeed objects as incompatible with SQL Ser (4241137)
Upgrade Advisor analyzes instances of SQL Server 7.0, SQL Server 2000 and SQL Server 2005 to help prepare for upgrades to SQL Server 2005/2008. ... Running this may detect certain LiteSpeed objects as not compatible with SQL Server 2005/2008.
automated restore not recognizing backup files. Manual restore does see and restore those same files (4256936)
We can use LiteSpeed console Restore Wizard to manually restore a database full backup file and tlog files. ... However, when we use the Restore Wizard to do an 'Automated restore' on those same files in that same directory, LiteSpeed does not recognize the backup files.
Restore backup to a non-default port instance. (4273844)
When trying to restore backup to and instance with non-default port the following error appear: VDI open failed due to request abort error:61700. ... Update to the latest version of LiteSpeed.
Maintenance Plan creating full backups every time for some databases (but not others) even though MP is configured to create a tlog backups (4251912)
On one of our servers we are backing up multiple databases and some but not all are getting a full backup created every time no matter whether it is a full, differential or transaction log backup specified in the Maintenance Plan 'Back up Database' task.<br><br>It seems to be because we have selected the option to “Force a full backup if one has not been created" in our Maintenance Plans (MPs).
patching SQL Server to next Service Pack. This server houses our LiteSpeed Central Repository. Anything we need to do? (4240092)
We are looking to patch our Litespeed Central Repository SQL Server to the next Service Pack level and wanted to know if there are any precautions or steps that are needed to do this? <p>There's no concerns/precautions/steps needed with this regarding LiteSpeed.
Automated restore process requires a FULL backup to be restored first every time? Can the Automated Restore be used ONLY with tlogs? (4246201)
We see that the automated restore process requires a FULL and will not work with a directory that just contains the subsequent tlogs. ... If so, what would I give our clients/customers to use to restore subsequent log files automatically on a specified schedule?
Automated restore fails with error "not a valid pathname in directory" when database/index with a filestream filegroup in it (4256748)
Automated restore fails with error "not a valid pathname in directory" when database/index with a filestream filegroup in it. ... <div>When automated restore is used to restore a database/indes with a filestream filegroup in it.
Logshipping related questions (4323601)
This will show any failed jobs and suggested next steps. ... EXAMPLE: ... You can also review the jobs that make up the plan on the job manager page. ... EXAMPLE: (right click the log shipping plan and select “display jobs”)
Neue Produktverknüpfung
- Self-Service-Tools
- Knowledge Base
- Benachrichtigungen und Warnmeldungen
- Produkt-Support
- Software-Downloads
- Technische Dokumentationen
- Benutzerforen
- Videoanleitungen
- RSS Feed
- Kontakt
- Technische Support
- Alle anzeigen