change save settings directory on SSMS 2005

[misterstick]

when i exit sql server management studio i get the following error:

[tt]The automatically saved settings file '\\SERVER\DATA\Sql Server Management Studio\Settings\CurrentSettings-2006-09-21.vssettings' is not available for write. You can change this file on the 'Import and Export Settings' Tools Options page.[/tt]

i'm guessing this might be because of the corporate policy of pointing everyone's "My Documents" at a read-only folder.

i'd like to follow the advice on the dialog but unfortunately my Tools, Options dialog does not have an 'Import and Export Settings' page.

any ideas?



mr s. <

 

[Catadmin]

My Tools-> Options doesn't have that setting either and I'm running 2k5 Developer Edition. Sounds like an MS Beta error that never got set correctly when they changed the interface.

Post the problem on the MS Newsgroups to see if anyone there has an idea of why that error message is coming up for something that doesn't exist.

However, the current solution to your issue is to forward that error to your corporate help desk and explain to them that as a Developer, you need read/write access to that My Documents folder or you won't be able to job.



Catadmin - MCDBA, MCSA
"No, no. Yes. No, I tried that. Yes, both ways. No, I don't know. No again. Are there any more questions?"
-- Xena, "Been There, Done That"

 

[misterstick]

1. i've posted the problem on the Sql Server Tools General forum

http://forums.microsoft.com/technet/ShowPost.aspx?postid=748681&siteid=17

2. the read-only folder idea is that no documents should be saved to the user's local drive, everything should go in the proper client folder on the network. the network share is backed up, but the local drives are not. i agree with the idea behind it, but it's implemented clumsily, and just doesn't work. users have to navigate away from n:\ to get to where they want to be, changing drive is one more click. oh well. the policy has been in place since we moved over from windows 3.1 (nearly two years now) and is not going to change.


thanks for the response,



mr s. <

 

[misterstick]

i fixed it by changing "\\SERVER\DATA" to "c:\folder" in the registry. this isn't ideal, and i'd prefer to find a less potentially disastrous way to do this.


mr s. <

 

[Catadmin]

Sorry you had to do that. Let us know if MS comes up with anything on that error, K?



Catadmin - MCDBA, MCSA
"No, no. Yes. No, I tried that. Yes, both ways. No, I don't know. No again. Are there any more questions?"
-- Xena, "Been There, Done That"

 

[misterstick]

m$ forums said to post a bug in the visual studio space.

https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=208955

mr s. <