Steps to reproduce:
Have SSMS open with an active query and ensure the editor window has focus.
Right Click the SQL Assist Tray App -> Select Options
(Configure any options or not, it doesn't matter)
Click OK to dismiss the options dialog

The following exception is generated from Management Studio

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
at Microsoft.SqlServer.Management.UI.VSIntegration.NativeMethods.SetFocus(IntPtr hWnd)
at Microsoft.SqlServer.Management.UI.VSIntegration.ShellTextEditorControl.OnGotFocus(EventArgs e)
at System.Windows.Forms.Control.WmSetFocus(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at Microsoft.SqlServer.Management.UI.VSIntegration.ShellTextEditorControl.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system>
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

Fri Jul 13, 2007 2:33 am

SysOpSite Admin

Joined: 26 Nov 2006Posts: 6776

Thanks for the detail bug reports. This seems be one of the Vista issues which we are trying to address. I new build will be posted today that partially takes care of this and related Vista problems.

Fri Jul 13, 2007 9:35 am

ChrisRickard

Joined: 12 Jul 2007Posts: 16

Same behavior with 2.5.12

Fri Jul 13, 2007 11:49 am

SysOpSite Admin

Joined: 26 Nov 2006Posts: 6776

Thanks for the update. We are committed to resolve this problem. I will keep you posted on the progress.

Fri Jul 13, 2007 3:04 pm

pkmccarthy

Joined: 18 Jul 2007Posts: 6

So are you saying this version is not Vista compatible - on my vista machine it appears to lockup the entire machine wether or not i have SSMS running or not (I had to boot into safe mode and disable the startup app from running)

What is the ETA for the patch to this and where does one get it?

I am currently evaluating this tool - i own prompt sql but it has issues with very large peoplesoft databases (40,000 tables and 30,000 views) - i am hoping this tool is more like aquadata's intelisense (another user of the tool says it is)

thanks,
Patrick

Wed Jul 18, 2007 1:28 pm

SysOpSite Admin

Joined: 26 Nov 2006Posts: 6776

Well.. let's put it this way. It is compatible with Vista. In fact I am running it now on Vista as we speak.

However, you are third person I know who reported Vista desktop freezing problem after installation and use of SQL Assistant. So far, we were unable to reproduce this problem in our development environment and still looking for a way to reproduce it. We are planning to make a new build by the end of next week. If we can reproduce this problem during this week, beginning of next week, we can surely engineer a fix for it. Any details you can provide about your setup, or steps to reproduce, would be greatly appreciated.

Did it started to happen as soon as you got SQL Assistant installed?
If not, can you reproduce this problem at will?
Did you check Event Logs for any related messages? If yes, what did you find there?
Which Vista Edition are you running?

Wed Jul 18, 2007 2:14 pm

pkmccarthy

Joined: 18 Jul 2007Posts: 6

nothing in the log file that i can see yet - however, the trial version expired before i could get back to using it again (i used msconfig to disable it during startup since it locked the OS - I was hoping for a patch sooner) -- can i get a trial extension?

Tue Jul 31, 2007 9:17 pm

SysOpSite Admin

Joined: 26 Nov 2006Posts: 6776

Please email to sales and request a trial extension.

By the way, can you describe the process that leads to Vista hanging? Do you have any debuggers installed on the system like Visual Studio NET or something like that? Which Vista edition are you running?

Tue Jul 31, 2007 11:43 pm

pkmccarthy

Joined: 18 Jul 2007Posts: 6

the last time i re-enabled it all i did was just open Visual Studio 2005 and it locked the machine - its interesting - the machine is still running just fine (i had a vmware image build process going and it completed overnight) its just that the screen is locked up -- keyboard does not work(mostly - you can get ctrl-alt-del one time to lock the machine but after that, nothing) - mouse pointer is there and you can move it -- very strange...

i am running Vista Enterprise....

before i request a trial extension i will wait for another build from your dev team -- the current version is pretty much useless to me (bummer because prompt sql isnt very good)
-- i would be happy to test a beta release of any newer versions

Tue Aug 07, 2007 11:47 pm

SysOpSite Admin

Joined: 26 Nov 2006Posts: 6776

Thanks for getting back. Our current hypothesis, this is issue is caused by some software conflict. So far we have identified that virtually all people who experienced and reported this issue got both SSMS and VS 2003 or VS .NET installed on the same Vista system and the VS is having Just-in-time debugger feature activated.

By the way, built 2.5.14 was posted today. It includes a number of changes including replacing of SQL Assistant's INI based config file with a binary file in order to avoid issues with Vista trying to virtualize access to INI files via the registry keys which in certain cases creates undesired side effects affecting SQL Assistant behavior.

Regarding the keyboard locking, that's what I suspected from very beginning, that the issue is not the system locking, but the Desktop input locking. I wonder since you can easily reproduce this issue, can you try pressing Ctrl+Esc when it locks again and let us know if this global Windows hot key unlocks it, also try same for Ctrl+Break

Wed Aug 08, 2007 12:43 am

SysOpSite Admin

Joined: 26 Nov 2006Posts: 6776

Hi everybody,

We've developed special version of SQL Assistant to help with troubleshooting Vista lockups issues. Please help us identify the problem on your systems so we can fix it for you. Here is what we are asking to do.

1. Shutdown SQL Assistant if it is running on your Vista machine.
2. Backup C:\Program Files\SQL Assistant folder to some other folder on your disk.
3. Download http://www.softtreetech.com/sqlassist/builds/2.5.16_preview.zip and unzip it into the folder mentioned above
4. Open command line and navigate to C:\Program Files\SQL Assistant folder. Start SQL Assistant using the following command
sqlassist.exe "/SA:TraceLogLevel:9"
5. Do what is necessary to reproduce the locking keyboard/mouse issue
6. Restart the system and after restart either post the contents of email C:\Program Files\SQL Assistant\data\sqlassist.log file or email it to support.