Has anyone seen the issue with SQL Profiler 2000 where you cannot pause or stop a trace? The only way I can stop it, is by doing a control - alt - delete and then end the application process. This just randomly started happening. Also the pause and stop buttons grey out.
Any help on this issue is greatly appreciated.
How patient are you being? Is this a few seconds, few minutes, half an hour? What amount of data are you talking about and over what sort of connection.
I have had to wait for the profiler to "catch up" before when viewing a database with very high usage.
I have also had to wait for it to respond if I've been profiling over a slower vpn connection.
A combination of the two can have you waiting for some time.
I've seen this happen consistently on some (virtual) machines - clicking the stop button causes it to grey-out (but not enable start etc), but seem to wait forever in the "stopping" state without actually stopping. Unfortunately, I don't have a fix.
However, the systems where this happen were all fairly low-resource VPCs. The fact that this always happened for the VPCs, but never for my desktop system made me suspicious that it may be related to low memory availability, or else something about the VPC environment, but I never confirmed this for certain.
At the time, I worked around it by connecting remotely, running profiler on my own machine. If this is a low-spec machine / VPC, it may be worth trying this, or else closing all apps on the machine before using profiler.
I think we need more info to help you here.
Yup happens to me all the time - the easiest way to get it back is to kill the connection.