Make sure the machine is setup with ASP.NET, the client API Dlls are in the same directory as your own web service if that's what you are setting, and that the LocalSettings.Init()'s second parameter is a path to a location where the web service can write the settings.xml file.

If you're using UtilityService.AppSettings, what s the value of "UtilityService.AppSettings["VaultSettingsXMLFileLocation"]"?

I'm not sure that downgrading to version 6 would help this issue. I have one other user that had the same issue, but in his case, he was using version 6 and just moved to a different machine. It would work on one and not the other. I tested his code in-house on one of my machines and it worked here.

Do you have a different machine you could try your version 6 code on?

Try using a path that is the default location that other Vault clients would use. That path is C:/Users/your user name/appdata/local/Sourcegear. Is there any difference there?

We still have the old Windows 2003 server with V6 code running fine. The new Win2k8 with 7.1 is a different machine which we are migrating to, due to the old one being deprecated.

I tried to find out where the settings.xml file is on the old machine but had no success - couldn't find it

So,

As requested I changed the folder setting to:"C:\\Users\\serverlocaladmin\\AppData\\Local\\SourceGear"and"C:\\Users\\serverlocaladmin\\AppData\\Local\\"and"C:\\Users\\serverlocaladmin\\AppData\\Local"

These gave me this error on login:"Access to the path 'C:\Users\serverlocaladmin\AppData' is denied. "

I added IIS_USERS to permissions list on these folders - with Full Control:Then I received the different message:"Couldn't calculate a local settings path for settings.xml. Tried both "" and "SourceGear". "