We have found that quite frequently when we connect to servers/cubes - SQL
management studio (SQLWB.exe) - freezes.
Even if you run SQLWB.exe on the same machine as the server - it just
hangs - the CPU shows no activity - however if you leave it in the "hung"
state after maybe 20-30 minutes the process connects correctly and you can
carry on as normal.

During this time if you submit say an MDX query from a different client -
you get no response from the server.
It is as though the server has got itself into some strange introverted
state where it won't talk to anything else!
You just have to wait until it has finished its "sulk".

This is incredibly frustrating as no progress can be made in the meantime.
Are others experiencing this behaviour? Is it documented? What can we do
to avoid it?

TIA

Andy

Andy, I am having the same issues, exactly. I have removed and
re-installed SQL 2005 and did not fix the issue. I removed all sever
registrations thinking that it was trying to connect to a server that
was not on-line and timing out. I do see that the sqlWb.exe is taking
40% CPU in task manager with no disk I/O at all. There must be others
having this issue. I also reset the IP stck thinking there was an issue
but no success. I will continue to research this because it is a real
pain on my development system.

Andy wrote: