Comments
Sort by recent activity
Thank you @Jon_Kirkwood. I look forward to the proper fix with the release of (v10.12.7+) as I don't want to lose my new tab history saved in %localappdata%\Red Gate\SQL Prompt 10\SqlHistory.db. Now if there was a tool that could merge the changes together between the SavedTabs.db and SqlHistory.db then I would not have any objections with rolling back to 10.12.4. But since that doesn't seem to be the case I am stuck limping along with 10.12.6 until it's addressed. / comments
Thank you @Jon_Kirkwood. I look forward to the proper fix with the release of (v10.12.7+) as I don't want to lose my new tab history saved in %localappdata%\Red Gate\SQL Prompt 10\SqlHistory.db. ...
Thanks for the information Jon. When I look in my %localappdata%\Red Gate\SQL Prompt 10\ folder I see two files. SavedTabs.db with a last modified date of 9/29/2022 and SqlHistory.db with a last modified date that's current. So it's reasonable for me to assume that if I were to try your recommended workaround, that I would lose all the queries recorded for the month of October. To that extent, I ask what problem should this workaround solve? Does it solve the problem where tab history sort of works but it's very slow and performing a tab history search often leads to the "The semaphore timeout period has expired." crash. Or does it solve the other error "Access to path is denied." I suppose that it could potentially solve the first one if the problem is that the migration from SavedTabs.db to SqlHistory.db performed by the previous version (10.12.5) somehow corrupted the SqlHistory.db file and making this conversion again with 10.12.6 will result in a non corrupted SqlHistory,db file. If that's the issue, I would like confirmation of that before committing to losing all my last month's history. / comments
Thanks for the information Jon. When I look in my %localappdata%\Red Gate\SQL Prompt 10\ folder I see two files. SavedTabs.db with a last modified date of 9/29/2022 and SqlHistory.db with a last...
Alright I was able to address the path not found error on my end by performing the following: 1. Signed out of my workstation 2. Logged back into my workstation as the user I was using for the runas another user option. 3. Ran SSMS normally 4. This time previously remembered query windows opened up and SQL Prompt did not crash. 5. Logged out of my workstation 6. Logged back in as my normal user. 7. Launched SSMS under the runas another user option using the same user I had logged in as in step 2. 8. Confirmed it didn't crash. Evidently SQL Prompt needs to do something initially that doesn't work under the runas another user feature. But once fully logged into the workstation as that user, it can handle it. This only addresses the Runas another user issue as a viable workaround Slow Tab history is still a problem SQL Prompt crashing with the error "The semaphore timeout period has expired." message while performing searches in the Tab history is still a problem. [image] / comments
Alright I was able to address the path not found error on my end by performing the following:1. Signed out of my workstation2. Logged back into my workstation as the user I was using for the runas ...
I tried using a shortcut that launches SSMS via the runas.exe syntax. While the runas.exe prompted me for credentials via a command window as apposed to Windows GUI, it still worked as expected. Nevertheless, it didn't change the outcome for SQL Prompt for me. I was still presented with a crash screen when SQL Prompt loaded. [image] [image] [image] / comments
I tried using a shortcut that launches SSMS via the runas.exe syntax. While the runas.exe prompted me for credentials via a command window as apposed to Windows GUI, it still worked as expected. ...
I too had this issue as outlined in this post: https://forum.red-gate.com/discussion/88649/updating-issue-from-12-2-to-12-10 While I don't know what changed to cause this issue in the first place, changing authentication from active directory back to basic and then back to active directory seems to be a viable work around. / comments
I too had this issue as outlined in this post: https://forum.red-gate.com/discussion/88649/updating-issue-from-12-2-to-12-10While I don't know what changed to cause this issue in the first place, c...
I can confirm that it's now fixed. / comments
I can confirm that it's now fixed.
Thanks. Just to let you know, I just upgraded to 12.0.11 and the problem persists. I also observed active alerts for long running queries that are not running. So it may extend beyond active blocking alerts to other types of active alerts not auto clearing. / comments
Thanks. Just to let you know, I just upgraded to 12.0.11 and the problem persists. I also observed active alerts for long running queries that are not running. So it may extend beyond active blo...
Just to confirm and for the benefit of others. pbleggi solution worked for me as well. I basically ran the procedure documented here: https://documentation.red-gate.com/sm12/troubleshooting/can-t-log-in-to-sql-monitor-with-active-directory/incorrect-service-account-credentials just against my primary web host that connects to multiple base monitores. And it ended up fixing it on all of my web and base monitors. / comments
Just to confirm and for the benefit of others. pbleggi solution worked for me as well. I basically ran the procedure documented here: https://documentation.red-gate.com/sm12/troubleshooting/can-t...
Lovely. Thanks for the potential work around. I will give it a try. / comments
Lovely. Thanks for the potential work around. I will give it a try.
No, I just upgraded to 12.10 and now I can't login on systems where the base monitor and web monitor are separate. / comments
No, I just upgraded to 12.10 and now I can't login on systems where the base monitor and web monitor are separate.