SQL Profiler doesn't luanch correctly

9 Nov 2005 10:09 PM

Chris Newby

In the past I've been able to use SQL Profiler without any problems on this
machine within this network. Recently, however, whenever I try to start
Profiler, a task item shows up in the task bar, but GUI never actually
opens. Using ProcessExplorer from sysinternal.com, a stack trace of
profiler.exe only thread shows:

ntdll.dll!KiFastSystemCallRet
SEMSFC.dll!SFCApp::PumpMessage+0x33
SEMSFC.dll!SFCApp::Run+0x95
profiler.exe!CTraceScriptGenerator80::operator=+0x35b
profiler.exe!CTraceScriptGenerator80::operator=+0x1b5
profiler.exe!CRowsetTracePropertiesGeneralTab::Proc+0xae8
kernel32.dll!RegisterWaitForInputIdle+0x49

I can see that something is happening because its still context switching
.... however like I said, no GUI. It's almost as if the appliction is
permanently minimized.

Anyway, this is really bugging me as profiler is often such a useful tool
and I'm unfortunately not that good at lower level debugging yet.

So any help would be apreciated, thanks,
Chris Newby

10 Nov 2005 12:06 AM

David Gugick

Chris Newby wrote:
Show quote

> In the past I've been able to use SQL Profiler without any problems
> on this machine within this network. Recently, however, whenever I
> try to start Profiler, a task item shows up in the task bar, but GUI
> never actually opens. Using ProcessExplorer from sysinternal.com, a
> stack trace of profiler.exe only thread shows:
>
> ntdll.dll!KiFastSystemCallRet
> SEMSFC.dll!SFCApp::PumpMessage+0x33
> SEMSFC.dll!SFCApp::Run+0x95
> profiler.exe!CTraceScriptGenerator80::operator=+0x35b
> profiler.exe!CTraceScriptGenerator80::operator=+0x1b5
> profiler.exe!CRowsetTracePropertiesGeneralTab::Proc+0xae8
> kernel32.dll!RegisterWaitForInputIdle+0x49
>
> I can see that something is happening because its still context
> switching ... however like I said, no GUI. It's almost as if the
> appliction is permanently minimized.
>
> Anyway, this is really bugging me as profiler is often such a useful
> tool and I'm unfortunately not that good at lower level debugging yet.
>
> So any help would be apreciated, thanks,
> Chris Newby

You could try reapplying the SQL Server service pack to the client. That
will update the client tools and may solve the problem.

--
David Gugick
Quest Software
www.imceda.com
www.quest.com

10 Nov 2005 11:03 AM

Tibor Karaszi

Which version of SQL Server and the OS? I recall issues with Profiler 2005 on Windows 2003, where
you needed (as I recall) sp1 for the OS or you'd get this very behavior.

--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/

Show quote

"Chris Newby" <Chris.Ne***@Rockcreekglobal.com> wrote in message
news:%23dAvtpX5FHA.1248@TK2MSFTNGP14.phx.gbl...
> In the past I've been able to use SQL Profiler without any problems on this machine within this
> network. Recently, however, whenever I try to start Profiler, a task item shows up in the task
> bar, but GUI never actually opens. Using ProcessExplorer from sysinternal.com, a stack trace of
> profiler.exe only thread shows:
>
> ntdll.dll!KiFastSystemCallRet
> SEMSFC.dll!SFCApp::PumpMessage+0x33
> SEMSFC.dll!SFCApp::Run+0x95
> profiler.exe!CTraceScriptGenerator80::operator=+0x35b
> profiler.exe!CTraceScriptGenerator80::operator=+0x1b5
> profiler.exe!CRowsetTracePropertiesGeneralTab::Proc+0xae8
> kernel32.dll!RegisterWaitForInputIdle+0x49
>
> I can see that something is happening because its still context switching ... however like I said,
> no GUI. It's almost as if the appliction is permanently minimized.
>
> Anyway, this is really bugging me as profiler is often such a useful tool and I'm unfortunately
> not that good at lower level debugging yet.
>
> So any help would be apreciated, thanks,
> Chris Newby
>
>