https://www.quest.com/community/apexsql/en-USTelligent Community 13https://www.quest.com/community/apexsql/f/forum/37176/failed-commit-erases-commit-message/86341Wed, 18 Mar 2026 09:49:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:1fb9e0dd-aeb3-49c1-b099-2478e3cfe047alexdanapurI’ve run into this same frustration before—there’s nothing worse than spending time writing out a detailed commit message only for it to vanish because of a connection glitch or a failed validation. If you're still dealing with this, one thing that helped me was to get into the habit of 'pre-processing' my messages in a simple notepad or a scratchpad first. That way, if the commit fails or the tool refreshes, you aren't stuck trying to remember exactly what you wrote. It’s a bit of a manual workaround, but it definitely saves a lot of re-typing until a proper fix or an 'auto-save' feature is added to the UI!https://www.quest.com/community/apexsql/f/forum/37176/failed-commit-erases-commit-message/86252Mon, 02 Feb 2026 17:06:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:ac9cc7bf-14de-49b5-98e8-b910371dba48nodier garciaIf you are still having issues, please go to support.quest.com and open a case with Support for better assistance.https://www.quest.com/community/apexsql/f/forum/37176/failed-commit-erases-commit-message/86233Sat, 24 Jan 2026 04:06:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:8e77482b-2ee9-4a8e-a016-57a812de026anodier garciaHi! Could you please let us know if this is in ApexSQL Source Control? If so, what version of the tool are you currently using? Please let us know so we can better help you.https://www.quest.com/community/apexsql/f/forum/37176/failed-commit-erases-commit-messageThu, 22 Jan 2026 21:11:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:2804e41d-5c6e-43c6-9553-e5e467d50bc5ClemsonTiger04When a commit fails, why is the commit message removed? It's a real pain to have to keep putting it back when commit fails because credentials were accidently typed wrong or similar. What's the harm in leaving the entered commit message so one does not have to re-enter it? i.e. wrong credentials are saved, type commit message, select what to commit. Get "Commit failed and changes are not applied. Contact ApexSQL-SA@!quest.com for help" Additionally, why does it seem like when credentials are saved, and then they change and then I go to commit and it fails due to invalid credentials that ApexSQL seems to keep trying the same wrong credentials so many times so quickly that it locks one's AD account? If it fails once, make it not try again until the user initiates it.https://www.quest.com/community/apexsql/f/forum/37140/chm-search-works-in-trial-output-but-not-licensed-output-full-text-search-enabled-but-returns-no-results/86210Fri, 16 Jan 2026 15:19:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:57757217-0d3d-4be4-b89d-d2606abd25f1anna clareHi, Thanks for your suggestion. I created a new project and regenerated the chm to a different file location but the search is still not working. I understand the 2022 is not supported however, the trial version of the software I used was able to generate searchable chms against the same SSISDB without any issues. I'll create a service request.https://www.quest.com/community/apexsql/f/forum/37140/chm-search-works-in-trial-output-but-not-licensed-output-full-text-search-enabled-but-returns-no-results/86194Wed, 14 Jan 2026 16:49:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:c4763048-fe2b-4b35-94ef-216044e4225aariel cobaHello Anna, I hope you're doing good today, Can you try generating the packages again with other names and in other location? Not sure if this is related but just in case, t here is a known issue in regards of Inability to generate SSIS package connection managers with "Project Deployment Model" (Bug 229774) Additionally, SQL Server 2022 is not supported by ApexSQL Doc yet. If you require more assistance, you can open a support case so they can assist you investigating this issue. https://support.quest.com/create-service-request Thanks in advance,https://www.quest.com/community/apexsql/f/forum/37140/chm-search-works-in-trial-output-but-not-licensed-output-full-text-search-enabled-but-returns-no-resultsFri, 09 Jan 2026 19:47:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:576c805d-582e-4dbd-b3e7-e6cc3e38d91banna clareWe are using ApexSQL Doc to generate CHM documentation for SSIS packages. A CHM generated with the trial version has fully working Search A CHM generated with the licensed version shows the Search tab but returns "No topics found" for all searches Same machine, same packages, same environment The generated .hhp file explicitly contains: Full-text search=Yes Binary TOC=Yes Auto Index=Yes The Search tab appears in the CHM UI, the CHM is opened locally (not from a network share) and is not blocked I have tried setting options to Detailed and Custom with all options checked It feels like CHM Search is technically enabled but practically unusable. Any suggestion? TIAApexSQL DOChttps://www.quest.com/community/apexsql/f/forum/34702/unable-to-download-free-trail-apexsql-devops-plus-toolkit-for-apexsql-doc/85734Mon, 03 Nov 2025 00:10:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:98b1954d-b5cf-44bc-af57-ba5b3929040djikifo5398I had the same issue earlier you’ll need to install the ApexSQL DevOps Plus Toolkit separately from the main DevOps installer. Try downloading it directly from ApexSQL’s tools page, that’s where I finally found the Doc add-on.https://www.quest.com/community/apexsql/f/forum/34702/unable-to-download-free-trail-apexsql-devops-plus-toolkit-for-apexsql-doc/84877Fri, 20 Jun 2025 18:27:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:44e13272-40d3-4731-af3e-36ce35fc61c6nodier garciaHello Shane, ApexSQL Doc is not offered as a standalone product since 2021. If you need further assistance, please email us at support@quest.comhttps://www.quest.com/community/apexsql/f/forum/34702/unable-to-download-free-trail-apexsql-devops-plus-toolkit-for-apexsql-doc/84860Thu, 19 Jun 2025 10:17:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:0dcea6c9-fc95-4157-ac8f-096fea9dd893Shane WarneApexSQL Doc is usually available as a standalone tool. If it's not showing up in the toolkit installation, it's possible it wasn't bundled in that installer.https://www.quest.com/community/apexsql/f/forum/35948/microsoft-sql-server-2022-support-for-apexsql-log/82666Tue, 04 Mar 2025 16:43:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:a0ca6140-cce1-4707-b7f3-5713836701b3nodier garciaThe roadmap of the product is currently on planning stages to do a new release this year that would support SQL Server 2022.https://www.quest.com/community/apexsql/f/forum/35948/microsoft-sql-server-2022-support-for-apexsql-logTue, 25 Feb 2025 19:22:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:4555732e-5112-49f6-859b-e6ac5f9214c4crandellmpI am trying to figure out if this tool can help us locate some table changes that were made using the database TRN files, but after getting the free trial of the ApexSQL Log tool, I found that it doesnt support SQL Server 2022. Is this product still being updated? The last release note is from 2020...https://www.quest.com/community/apexsql/f/forum/33612/install-apexsql-developer-error/81756Tue, 26 Nov 2024 10:59:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:aa652921-1563-4dfe-a1d7-47c3d7d402d1bgibbons_36795I have, thank you, someone is looking into it, maybe we have to download and try the individual product installers, will see. Thank you.https://www.quest.com/community/apexsql/f/forum/33612/install-apexsql-developer-error/81744Mon, 25 Nov 2024 20:44:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:52660a5e-5390-48c0-82be-8495aa2b9450nodier garciaFor this issue, please open a Support Case from our portal: support.quest.comhttps://www.quest.com/community/apexsql/f/forum/33612/install-apexsql-developer-error/81741Mon, 25 Nov 2024 13:04:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:aaa23a02-014e-408a-a1c8-2a4ba7dff9e7bgibbons_36795We are just about to renew our licenses, we have had a desktop refresh to Windows 11 24H2 clean installs, so we decided to re-apply our installs and get the latest versions of the ApexSQL Developer Bundle - only to find we encounter the error immediately on install. Runtime error (at 236:455) Access Violation at address 0CC88FF9, Read address of 00000000https://www.quest.com/community/apexsql/f/forum/34944/source-control-action-center-how-can-one-ignore-user-changes-and-not-default-select/81093Tue, 24 Sep 2024 16:52:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:21d015a0-335c-4e6a-a517-0d31f40caf6bcesar adamesClemsonTiger04 thank you for using our forums. In this case I recommend you open a support case to further investigate this issue. support.quest.com/create-service-requesthttps://www.quest.com/community/apexsql/f/forum/34944/source-control-action-center-how-can-one-ignore-user-changes-and-not-default-select/81061Thu, 19 Sep 2024 13:16:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:5822306d-fdb8-4b65-8810-d70844c152edClemsonTiger04I removed it from local. I don't want to remove it globally as other developers may want to see the User pending changes.https://www.quest.com/community/apexsql/f/forum/34944/source-control-action-center-how-can-one-ignore-user-changes-and-not-default-select/81060Thu, 19 Sep 2024 13:03:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:1dd90055-b444-4542-b7cd-bd96de0302a6nodier garciaCould you please confirm that you have removed the User option from the Type section of the Local and Global object filter as shown in this screenshot. https://prnt.sc/ohZHIuULBS9qhttps://www.quest.com/community/apexsql/f/forum/34944/source-control-action-center-how-can-one-ignore-user-changes-and-not-default-select/81049Wed, 18 Sep 2024 17:09:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:3d31d2fe-e1eb-4c8d-9638-c32c4eac2c00ClemsonTiger04No, User is unchecked in local Settings for object filter, but action center continues to list User changes.https://www.quest.com/community/apexsql/f/forum/34944/source-control-action-center-how-can-one-ignore-user-changes-and-not-default-select/81034Tue, 17 Sep 2024 13:32:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:07322eab-1dad-41bd-81e0-124f044a1d74nodier garciaThe application shows a message in a new address when the application has logged in correctly. We will review this with devs. Now that you have successfully logged in. Were you able to ignore the users from the Action Center?