User profile for JP7

Hi Peter I'm not using SSMS Express. Herewith the info taken from SSMS Microsoft SQL Server Management Studio 9.00.4035.00 Microsoft Analysis Services Client Tools 2005.090.4035.00 Microsoft Data Access Components (MDAC) 2000.085.1132.00 (xpsp.080413-0852) Microsoft MSXML 2.6 3.0 4.0 5.0 6.0 Microsoft Internet Explorer 8.0.6001.18702 Microsoft .NET Framework 2.0.50727.3082 Operating System 5.1.2600 / comments

Hi Peter I'm not using SSMS Express. Herewith the info taken from SSMS Microsoft SQL Server Management Studio 9.00.4035.00 Microsoft Analysis Services Client Tools 2005.090.4035.00 Microso...

0 votes

Hi Pete The SQL Prompt directory is present when the add-in fails to load. I ran SSMS as a different user, and it loads fine. SQL Prompt integration fails only when I launch SSMS from a keyboard shortcut. The keyboard shortcut does not launch as a different user. The release build of SQL Pompt does not output anything to the error logs when integration fails. Sorry I can't be of more assistance this time. JP / comments

Hi Pete The SQL Prompt directory is present when the add-in fails to load. I ran SSMS as a different user, and it loads fine. SQL Prompt integration fails only when I launch SSMS from a keyboard sh...

0 votes

I think I may have stumbled onto something. I usually open my Management Studio from a keyboard shortcut (CTRL + SHIFT + S) I assigned to the start menu entry. Whenever I start Management Studio from this keyboard shortcut it seems like SQL Prompt bombs out. However, when I start it by simply clicking on the shortcut all seems to work fine. I'm not 100% sure about this observation yet. Perhaps the SQL Prompt developers may be able to verify it? / comments

I think I may have stumbled onto something. I usually open my Management Studio from a keyboard shortcut (CTRL + SHIFT + S) I assigned to the start menu entry. Whenever I start Management Studio fr...

0 votes

Hi Chris FYI, I disabled SQL Prompt 4's integration with Visual Studio 2005, and it seems to work fine in SQL Enterprise Manager now. Not sure if that's of any help to you... / comments

Hi Chris FYI, I disabled SQL Prompt 4's integration with Visual Studio 2005, and it seems to work fine in SQL Enterprise Manager now. Not sure if that's of any help to you...

0 votes

Hi Chris You're more than welcome to contact me at any time. Regards JP / comments

Hi Chris You're more than welcome to contact me at any time. Regards JP

0 votes

Hi Chris I had a clean installation of Windows XP, which means I did not have SQL Prompt 3 installed. V4 was the first. After having rebooted my notebook, I did the following: Closed all unnecessary programs in the system tray. Disabled Eset Smart Security 4. At this stage I have the bare minimum running. Open a new instance of SQL Management studio. Type in a query and run. Everything is working fine at this stage. Close SQL Management Studio. Open SQL Management Studio again. Type in a new query. Now SQL Prompt does not pop up at all. Also, the SQL Prompt 4 main menu item becomes grayed out when I try to select "Refresh Suggestions" for instance. I can mail you a screenshot if you wish. Usually I would have to reboot my notebook to get SQL Prompt 4 working again. However, I just tried it again a couple of times and now it's working without fail. Very odd. Is there any sort of debugging/tracing information or logs I can look at to try and help pinpoint the problem? Please note that I have VS2008 installed in addition to VS2005. Please let me know if I can be of any assistance in helping trace the problem. Just by the way, I also experienced the same problem with V3.9 before reload WinXP. Thanks. JP PS: I found the following error repeated in nearly all logs 05 Jun 2009 09:02:24,843 [1] INFO RedGate.SqlPrompt.Engine.LogService - Starting new SQL Prompt editor session 05 Jun 2009 09:03:03,140 [5] ERROR RedGate.SqlPrompt.Engine.LogService - LogService caught unhandled exception in AppDomain: 'Thread was being aborted.' System.Threading.ThreadAbortException: Thread was being aborted. at RedGate.SQLPrompt.CommonUI.TaskExecuter.Executer.a() at System.Threading.ThreadHelper.ThreadStart_Context(Object state) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.ThreadHelper.ThreadStart() / comments

Hi Chris I had a clean installation of Windows XP, which means I did not have SQL Prompt 3 installed. V4 was the first. After having rebooted my notebook, I did the following: Closed all unnecessar...

0 votes

Hi Cris, At the moment I have some pending C# development keeping me from using SQL Prompt. I'll investigate the issue more thoroughly when time permits and revert with my findings. Thank you JP / comments

Hi Cris, At the moment I have some pending C# development keeping me from using SQL Prompt. I'll investigate the issue more thoroughly when time permits and revert with my findings. Thank you JP

0 votes

Hopefully just in time for my birthday [image] Thank you Tanya / comments

Hopefully just in time for my birthday Thank you Tanya

0 votes

Any update on the status of V4? / comments

Any update on the status of V4?

0 votes

Hi Paul Your suggestion dramatically improved the load times. Looking forward to V5.1. Cheers, Jean-Paul / comments

Hi Paul Your suggestion dramatically improved the load times. Looking forward to V5.1. Cheers, Jean-Paul

0 votes

How can we help you today?

JP7

Comments