https://www.quest.com/community/litespeed/en-USTelligent Community 13https://www.quest.com/community/litespeed/f/forum/37267/error-during-litespeed-v9-installation---certificate-chainThu, 02 Apr 2026 22:42:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:bb2ab0b1-d998-45d3-b678-6e4995e80bd2matt oconnellAt the Activity logging portion of the Litespeed install, the Litespeed install fails with: "SSL Provider: The certificate chain was issued by an authority that is not trusted" The Windows Event Log shows: The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. The SSPI client process is SLSInstaller (PID: 9096). I've installed many times on other servers with no issues. Any ideas?authorityLiteSpeed for SQL Servertlscertificatehttps://www.quest.com/community/litespeed/f/forum/37055/litespeed-for-sql-server-hotfix-9-0-0-33625-checksum-hash-not-matching/86052Fri, 12 Dec 2025 17:15:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:ac62ee05-ccf5-4e19-a418-9ea74a6a32d4JulioHello leo zipper Thank you for bringing this to our attention. We have already reached out to our technical team and the checksum has been updated accordingly. The issue was related to the file's hash being assigned to the installer and not the downloadable zip file.https://www.quest.com/community/litespeed/f/forum/37055/litespeed-for-sql-server-hotfix-9-0-0-33625-checksum-hash-not-matchingWed, 10 Dec 2025 18:56:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:df302408-a4f0-4b9f-a278-b47f3cb1f12dleo zipperHello, I downoloaded the hotfix 9.0.0.33625. The checksup on the download page shows to be SHA256: a3d0fa756079ff054d23afd98a7a202d7b2893c03f3f61fe29a850d03a79da4f. The hash i get from powershell get-filehash LiteSpeed90033625.zip is 03396B986A84372CF4C2FAF0E57874D3F03EE64394497EB5FD4036130E530BAF.https://www.quest.com/community/litespeed/f/forum/36413/how-to-find-the-recovery-point/84880Fri, 20 Jun 2025 21:28:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:32e068e9-e09b-4684-9af5-c68a761877b0nodier garciaYou can query the msdb to verify the last backup performed for an specific database using the following query SELECT /* Columns for retrieving information */ -- CONVERT(CHAR(100), SERVERPROPERTY('Servername')) AS SRVNAME, msdb.dbo.backupset.database_name, msdb.dbo.backupset.backup_start_date, msdb.dbo.backupset.backup_finish_date, -- msdb.dbo.backupset.expiration_date, CASE msdb.dbo.backupset.type WHEN 'D' THEN 'Full' WHEN 'I' THEN 'Diff' WHEN 'L' THEN 'Log' END AS backup_type, -- msdb.dbo.backupset.backup_size / 1024 / 1024 as [backup_size MB], msdb.dbo.backupmediafamily.logical_device_name, msdb.dbo.backupmediafamily.physical_device_name, -- msdb.dbo.backupset.name AS backupset_name, -- msdb.dbo.backupset.description, msdb.dbo.backupset.is_copy_only, msdb.dbo.backupset.is_snapshot, msdb.dbo.backupset.checkpoint_lsn, msdb.dbo.backupset.database_backup_lsn, msdb.dbo.backupset.differential_base_lsn, msdb.dbo.backupset.first_lsn, msdb.dbo.backupset.fork_point_lsn, msdb.dbo.backupset.last_lsn FROM msdb.dbo.backupmediafamily INNER JOIN msdb.dbo.backupset ON msdb.dbo.backupmediafamily.media_set_id = msdb.dbo.backupset.media_set_id /* ---------------------------------------------------------------------------- Generic WHERE statement to simplify selection of more WHEREs -------------------------------------------------------------------------------*/ WHERE msdb.dbo.backupset.database_name = 'YOURDATABASE' Order by msdb.dbo.backupset.backup_finish_datehttps://www.quest.com/community/litespeed/f/forum/36413/how-to-find-the-recovery-point/84879Fri, 20 Jun 2025 19:48:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:21e3e269-6613-4c48-8b2f-031f08c75459Ken.HemmerlingI'm looking at things from the perspective of the SQL Server databases. Is there a query I can run to show the "restore to" time?https://www.quest.com/community/litespeed/f/forum/36413/how-to-find-the-recovery-point/84878Fri, 20 Jun 2025 18:32:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:f5d6260c-e5ca-4380-abf5-899304d30a8enodier garciaHello Ken, the answer will depend on the point of view. If you are looking into it in the SQL Server instance point of view, the recovery point will always be the last transaction log created. If you are looking from the sever standpoint, the recovery point will be the last H backup done by Commvault. Hope this helped.https://www.quest.com/community/litespeed/f/forum/36413/how-to-find-the-recovery-pointThu, 05 Jun 2025 20:45:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:60cbf550-80ec-494c-a8c9-a973927c9689Ken.HemmerlingI'm testing my disaster recovery process and have a question about the Recovery Point of SQL Server databases. My database instances use the Ola Hallengren scripts to run backups calling Quest LiteSpeed. In production we have full backups every night with transaction log backups every 15 minutes during the day. These backups are stored in H:\MSSQLBACKUPS. The H: drive is then backed up by the Commvault backup system every hour throughout the day. In addition, once a day we back up the VMware virtual server. In a disaster, we do the following: 1) Use Commvault to restore the VMware SQL virtual host 2) Use Commvault to restore the most recent .BAK and .TRN backup files on H: 3) Use Quest Litespeed to restore databases. Because of the delays involved between Quest LiteSpeed and Commvault, the question came up: Exactly what is our recovery point? I can see the date stamp on the most recent .TRN (database transaction log backup) file. Is that what I should report as the Recovery Point? Is there a more accurate number to report? Any help is appreciated. KenRecovery PointDisaster RecoveryLiteSpeed for SQL Serverhttps://www.quest.com/community/litespeed/f/forum/36292/restricting-user-access/84466Tue, 13 May 2025 18:24:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:4b2d5aa2-3e95-4ff1-9294-1ae4d59b6bfccesar adamesHello michael deputy_62433 The way to limit LiteSpeed functions is exactly the same as limiting native SQL access. For example: Have your DBA create the required jobs (these are SQL Agent jobs) and limit the NOC to access to these jobs.https://www.quest.com/community/litespeed/f/forum/36292/restricting-user-accessFri, 02 May 2025 15:31:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:ee002858-df53-465b-a559-d44dd7f2abb2michael deputy_62433I am looking around LIteSpeed and I am not seeing any way to limit user's access to functions, can anyone point me to it? What I am interested in is letting my NOC get alerted on backup failures and rerunning the job, but not be able to manage templates or do deployments. I am also thinking of not allowing them to do restores. Thank you, Deppermissionsusershttps://www.quest.com/community/litespeed/f/forum/35730/litespeed-log-reader---identify-the-user-account-login-who-ran-a-ddl-dml-statement/82263Tue, 21 Jan 2025 20:35:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:2595a7b7-a8e7-4f77-a392-a68e6ba2c27bcarlos ortizIn the case of the Log Reader, the user name is part of the information displayed after the Log reading process. Usually is the last column in the section of DML/DDL.https://www.quest.com/community/litespeed/f/forum/35730/litespeed-log-reader---identify-the-user-account-login-who-ran-a-ddl-dml-statementThu, 16 Jan 2025 15:17:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:a10439cc-79f3-4818-8255-f15ed9ae27dajeffery burtonThe log reader is very useful to see the ddl/dml statements and the before/after versions of the tables/rows affected. Is there a way to show the user/account/login who ran those ddl/dml statements?https://www.quest.com/community/litespeed/f/forum/34530/change-the-language/80245Tue, 28 May 2024 19:03:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:77145f79-6e2d-4d8c-8278-75dca716a3fcariel cobaHello @jarevalo, Unfortunately, LiteSpeed does not have an Spanish Version. Apologies for not bringing some good news.https://www.quest.com/community/litespeed/f/forum/34530/change-the-languageThu, 23 May 2024 21:24:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:51b26f97-194a-4a56-ac75-c40fd2808426jarevaloHow can I change the language from English to Spanish LiteSpeed?https://www.quest.com/community/litespeed/f/forum/34335/tde-compression/79810Tue, 27 Feb 2024 19:40:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:006ab748-b5da-4293-a7d4-badbf69f86c4nodier garciaHello Brian, It is not recommended to use compression while having TDE enabled for database backups as the limitations of the technology from SQL Server does not allow much to be compressed. This is why we suggest using either compression 1 or 2. But if you use other values greater than 2, the result will not be different from the ones while using level 1 or 2. This is expected from LiteSpeed. Hope this helps.https://www.quest.com/community/litespeed/f/forum/34335/tde-compressionMon, 26 Feb 2024 21:58:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:fbd6a81a-4dbd-48f0-8c50-9254f9baacc6bpeaseyLitespeed Enterprise 8.9.8.48 SQL Server 2017 CU31 (14.0.3460.9) Hi, We've been implementing TDE in non-production servers and so far have no been able to get the same high compression levels with with non TDE databases. . The documentation for Litespeed 8.9.8, says the recommended compression level is 1 when backup databases that are using TDE. support.quest.com/.../compression-levels Following documentations recommended compression level of 1, We are seeing less than 1 % compression instead of more than 70% compression without TDE. Is this expected with Litespeed, or are there other ways of using Litespeed settings to get compression levels of greater than 70% with TDE? Thanks, BrianTDEhttps://www.quest.com/community/litespeed/f/forum/34285/changing-next-js-port-configuration/79747Tue, 20 Feb 2024 17:35:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:48fe12cd-a983-4ecb-994c-c06ed8c8ff7bariel cobaHello, It looks like you're using a different product, the product we support from Quest Software is LiteSpeed for SQL Server per below information: https://www.quest.com/products/litespeed-for-sql-server/ It looks like you're referring to LiteSpeed Web Server. www.litespeedtech.com/.../litespeed-web-server Thanks in advance,https://www.quest.com/community/litespeed/f/forum/34285/changing-next-js-port-configurationFri, 16 Feb 2024 06:35:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:9842bf07-73b8-473f-bc82-0ac2f2fde60000 garrets slightI've configured a Next.js application on my VPS, and currently, when I launch it with yarn start, it initiates on port 3040. I'm interested in learning how to adjust the configuration to commence on ports 80 and 443 instead. Your guidance on this matter would be greatly appreciated. Note: I'm utilizing koo ws the LiteSpeed web server.https://www.quest.com/community/litespeed/f/forum/34017/enhancing-dreamhost-server-speed/79292Sat, 11 Nov 2023 15:22:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:28b8c36a-b812-432c-a0b1-54511f8d0080nodier garciaHello Grant, I believe that you are referring to a different product called LiteSpeed? LiteSpeed for SQL Server is a backup/restore tool that works with Microsoft SQL Server databases. Please let us know if we can help you somehow.https://www.quest.com/community/litespeed/f/forum/34022/sql-stability-challenges-and-solutions/79290Fri, 10 Nov 2023 17:32:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:c1dfcbb7-2b28-444a-9c58-3a6c39157f0ecesar adamesHello tie cinder0y Thank you for using our forums, your feedback is well received. Generally speaking, issues matching the aforementioned description were introduced after a Microsoft update and thus resolved by Microsoft on a future CU. Moreover, please note these issues were observed on older SQL versions such as 2016 and most of our users mitigated them with a SQL Server version upgrade. Further, kindly recall that LiteSpeed, as a third-party tool, depends on the technology SQL Server offers and thus in some respects depends on Microsoft for specific solutions such as in the case in question. It is unfortunate that you feel the support experience was not optimal for your scenario. If you would allow us the chance to improve your views of our support system, as a LiteSpeed product specialist I will make the exception to take care of you directly and assure to follow-up your cases until resolution, including possible collaboration calls with you and Microsoft. Looking forward to hearing from you soon.https://www.quest.com/community/litespeed/f/forum/34022/sql-stability-challenges-and-solutionsTue, 07 Nov 2023 04:31:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:2459cf40-91c5-4648-8067-e821ce8e6c95tie cinder0yWith my limited SQL background, I'm seeking insights into an intricate issue that unfolded with our meticulously built SQL 2016 server. Our setup, constructed with utmost care, adhered strictly to Microsoft's best practices and recommendations from renowned entities like PURE (iSCSI), Litespeed, and Brent Ozar. Notably, even a third-party SQL specialist's review affirmed the soundness of our approach. However, our experience was marred by a series of vexing challenges related to Litespeed. These included failed log shipping, recurring troubles with locked or corrupted backup files, and SQL crashes attributed to a Litespeed dll triggering memory violations, purportedly addressed in SQL CU7 and subsequent updates. Strangely, these issues were absent in earlier iterations of Litespeed on older SQL versions. Despite our efforts to seek resolutions from Litespeed, the problems persisted, compelling us to eliminate all remnants of the software. Since transitioning to native backup solutions, our system has maintained stability, albeit at the cost of prolonged backup and restore durations. Even with attempts to mitigate this via multiple file usage, the problem persists. As we evaluate backup tools on a test server, the critical question looms: how can I reassure both myself and my superiors about the server's stability? I'm particularly concerned about litespeed.exe's tendency to lock backup files indefinitely, hindering completion. Consequently, the dilemma remains between embracing a third-party tool, with lingering apprehensions from past experiences, or persisting with native procedures despite their sluggishness. It's worth mentioning our disappointment with Litespeed's support, as their inability to resolve any of our issues persisted, often shifting the blame to Microsoft, who in turn redirected it to Litespeed. Since eliminating Litespeed, our predicaments have dissipated, leaving us in a state of uncertainty koow spin moving echat random forward.