Category
제품 버전
항목
하위 항목
How to generate a LiteSpeed Enterprise Console log (4323804)
To generate a LiteSpeed Enterprise Console log for purposes of troubleshooting from the LiteSpeed Enterprise Console in Version 5.x + ... Console logging is enabled in the console by: 1. ... Click the tools menu and choose options.
Error: "The process cannot access the file because it is being used by another process" while att (4224862)
Error received when attempting to run a back up: ... "The process cannot access the file because it is being used by another process". ... This issue may occur if antivirus software is running in the same location of the backup file or mutliple jobs may be simultaneously scheduled to backup the same database.
Error: "server msg 60900- level 19, state 1, line 1, error saving data to file ..." (4317706)
Error when attempting to execute a backup and the backup terminates: ... The error can be seen when starting a backup whether manually or in the log from being scheduled. ... The 60900 is often the result of insufficient disk space for the backup to complete.
Object Level Recovery only restoring part of a table that ought to contains years of data. Only one specific date's data restored. (4240087)
When we attempt to restore a table that contains data for a period of several year from a Full/Diff/Tran Log backup via Object Level Recovery (OLR), we only receive data from one specific date, and not the full historical table.
Error: "The operating system returned the error '32(error not found)' " on running backup with "F (4351839)
- The operating system returned the error '32(The process cannot access the file because it is being used by another process.)' while attempting 'CreateFile' on ... 'D:\Microsoft SQL Server\MSSQL.1\MSSQL\FTData\TestDB_Search\SQL.HDR' at 'fulltext.cpp'(529).
restore of appended t-log backups not working. Only first t-log backup is actually restored (4252035)
From the 'Restore Wizard' console UI, we are selecting to restore the most recent full backup, the most recent diff backup, and all the t-log backups listed under that diff backup. ... The t-logs are configured to all append into one physical file that keeps growing with each t-log backup.
Operating system error 0x80070008 (Not enough storage is available to process this command.) (4224988)
Operating system error 0x80070008(Not enough storage is available to process this command.) when backing up or restoring LiteSpeed files. ... This error message may accompany the error message Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
maintenance plan see new databases which are created after that maintenance plan? (4240081)
Does a maintenance plan see new, recently created databases. ... Database which are created after the time that that maintenance plan had been created? <p>New databases that are created after the maintenance plan (MP) has already been created with its specified databases will also be included in the backup task if for the 'Include Databases' option, you have selected "All databases", "User databases".
XP_RESTORE_VERIFYONLY for files on non-local (4323369)
The LiteSpeed xp_restore_verifyonly stored procedure is used to verify backups. ... Is there a way to use this to verify backup files located across on a different servers? ... The xp_restore_verifyonly store procedure can be used on backup files that are local and across servers.
What is the script to restore master database using TSM? (4231691)
When there is the need to restore master database using Tivoli Storage Manager (TSM), the script is not the same as restoring database from SQL Server native mode or LiteSpeed format, although the database must be set to single-mode.
What is the LiteSpeed feature 'IntelliRestore'? (4224871)
LiteSpeed has a feature 'IntelliRestore' to help restore complete backups. ... This feature is enabled by default and is visible in the Restore Wizard on the Backup Files and Backup Content screens.
Error: "Cannot create file "C:\Program Files\Microsoft SQL Server\MSSQL\Binn\xpLogShipping.dll". (4326834)
The process cannot access the file because it is being used by another process" ... The message may be displayed for the following .dll files: XpSLS.dll xpLogShipping.dll xpSLSImportStats.dll ... The .dll file has been loaded to cache.
Error: "Could not find stored procedure 'master.dbo.xp_slssqlmaint'. [SQLSTATE 42000] (Error 2812 (4327722)
[SQLSTATE 42000] (Error 2812)" The extended stored procedure xp_slssqlmaint was not written in the master database, has been deleted or has become corrupt. ... Using the SQL Server Enterprise Manager or SQL Server 2005 Management Studio, verify the existence of the extended stored procedure xp_slssqlmaint in the Master database.
Is it possible to have LiteSpeed conduct the backup of a single database in SQL Server? (4333190)
Is it possible to have LiteSpeed conduct the backup of a single database in SQL Server, and the rest backup using SQL Server? <p>Yes, that is possible.<br>With LiteSpeed you can Back up individual databases.
Error: %\LiteSpeed\Engine\SQLLiteSpeed.exe process (4218522)
Incorrect permissions on %:\Program Files\Imceda\LiteSpeed\SQL Server\Engine folder. ... Grant permission to %:\Program Files\Imceda\LiteSpeed\SQL Server\Engine folder, which will allow the sqllitespeed.exe to run.
Object Level Recovery using a native SQL Server backup file. (4218273)
User would like to use the LiteSpeed Object Recovery on a backup file the was generated by MS SQL Server, not by LiteSpeed. ... To access the GUI Wizard, in Enterprise Console select Backup | Object Recovery Tables.
Error: "Cannot load the DLL xpSLS.dll, or one of the DLLs it references. Reason: 126 (The specifi (4352687)
Reason: 126 (The specified module could not be found.)." ... The xpSLS.dll file is missing or the extended store procedure is pointed to an incorrect path. ... Check the Microsoft SQL Server Binn directory: "C:\Program Files\Microsoft SQL Server\MSSQL\Binn".
How can I verify that a restore is completing? (4218394)
How can I verify that a restore is completing? ... The process of restoring a backup file using LiteSpeed may be affected by the network environment, the server configuration, size of database, parameters of the actual restore.
Error during install: "SQL Server option 'Lightweight pooling' is enabled!" (4218265)
This option cannot be set when using SQL Litespeed. ... The lightweight pooling option on SQL Server is set to 1. ... The lightweight pooling option on SQL Server provides a mean of reducing the system overhead.
Error 4305 during a restore operation (4218593)
Error 4305 received during a restore operation. ... The LiteSpeed log will contain information similar to the following: ... "RESTORE LOG is terminating abnormally." ... "The log in this backup set begins at LSN
How to Enable Non LiteSpeed Job Statistics (4351928)
Scheduled Non-Litespeed jobs/activities don't show up or show up incorrectly in the JOB Statistics. ... Central repository is not enabled or "Job and DTS Statistics" is set to manually update. ... You need to "Configure local and central repositories" in order to see statistics in the Enterprise Console.
Error - "The backup set holds a backup of a database other than the existing database" during the (4220636)
This error message is not a LiteSpeed 2005 message.
Cannot run SQLDIAG on Itanium based processor systems or SQL Server 2005. (4223066)
- If the SQLdiag utility is running as a console application, you do not receive any output in the console window. ... - The Sqldiag.exe process stops responding. ... "Failed Assertion" and "Access Violation" error messages may be displayed when running SQLDIAG on Itanium server.
Can SLS be used with IBM's TSM LAN-Free (Storage Agent) option? (4218619)
Can LiteSpeed for SQL Server (SLS) be used with IBM's TSM LAN-Free (Storage Agent) option? ... Yes, LiteSpeed for SQL Server can be used with IBM's TSM LAN-Free (Storage Agent) option.
Engine and Product do not display same version on a cluster installation. (4223094)
When upgrading LiteSpeed, the xpSLS.dll from the earlier version has been written to the cache and is not overwritten during the installation of the newer version. ... The output from Query Analyzer EXEC xp_sqllitespeed_version displays Engine Version displays the newer version and the Product version displays the older version of LiteSpeed.
신제품 조합