Tim P (TimP (AT) discussions (DOT) microsoft.com) writes:
I was thinking that the problem may lie with .Net Fx 2.0, but you seem to
have reinstalled that one as well. In any case, in your previous post
you gave the version number 2.0.50727.3074. Myself I have 3053, so it is
not that the upgrade gave you an arcane version of .Net. Possibly you got
a too new one, but they wouldn't do that, would they?

And you upgraded from SP1 of Vista Business to SP1 of Ultimate, did you?

As last-ditch attempt could be to nuke
"C:\Users\sommar\Application Data\Microsoft\Microsoft SQL
Server\90\Tools\Shell\RegSrvr.xml",
but I don't have too much hope on it.

I guess opening a support case is not really an option for you.

But you could try submitting a bug on
http://connect.microsoft.com/SqlServer/Feedback, including any stack
traces you get. Not that this really seems to be a bug with SSMS, rather
with Vista.



--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx

Hi guys

Thanks for the ideas.

Yes, I updated Business SP1 to Ultimate SP1.

I tried deleting RegSrvr.xml very early in the problem, but that didn't make
any difference.

I have now tried backing up every db, completely removing SQL Server and
Visual Studio, deleting the remaining folders, reinstalling.

It still does it.

The guy who reported that this didn't work on another forum was quite
right....

This is beginning to really seriously hack me off!

The only solution I can think of is to wipe my hard drive and completely
start again, but as that would mean several days work, I don't really want to
do it.

I really don't know what else to do.

Regards

Tim

Thinking this through further, I removed SQL and trahsed all the sql server
folders in the Program Files folder. But when I reinstall and need to connect
to a server, all the previous servers are remembered. So SSMS must store its
server list somewhere else other than in its own folder, which could well be
the file I need to nuke.

Anybody know where this is, please?

On Vista - those are stored in your Documents folder. If you have not moved
them, it would be

C:\Users\<username>\Documents\SQL Server Management Studio
C:\Users\<username>\Documents\Visual Studio 2005

The Visual Studio 2005 folder contains the settings for BIDS.

"Tim P" <TimP (AT) discussions (DOT) microsoft.com> wrote

Jeffrey

Thanks for the reply.

I haven't moved the folders (although I'd like to, it irritates the hell out
of me when apps insist on cluttering up your docs folder and won't let you
configure them to be elsewhere).

But when I look in them, I can find vsettings files, but when I look at them
in notepad they contain no reference to server registrations. Lots of other
settings, but not these.

However, in the same place I found a folder called Backup Files, containing
a folder called Solution1. Inside this were two .sql files
(Recovered-Feb-19-2009-0246PM.~vsDD7C.sql and
Original-Feb-19-2009-0246PM.~vsDD7C), which I opened (in ssms, by default).
They didn't seem very interesting, so I closed them again.

Then, miracle of miracles, next time I opened ssms I got the usual error
message but also my Registered Servers window had content again - a Database
Engine tree. Now I can re-register my servers and the problem is gone!!!!!!

I really don't know how it happened, but never mind. It may have been
something to do with the original/recovered files. Who knows.....

Anyway, thank you very much to all who contributed.

Regards

TP

Actually, for the sake of completeness in the event that anyone has the same
problem in the future, I should record the other thing I did at the same time
which may have contributed. One of the error messages refers to being unable
to create a file in c:/Windows/Temp, so I looked at the permissions in that
folder. I noticed that my main Windows account didn't have full control and
neither did SQLServerReportServerUsers$DESKTOP$MSRS10.MSSQLSER VER, so I gave
both these accounts full control. I applied and tried again, without any
change. However, it was only five minutes later that all came good, so who
knows what did it.....