Dreamweaver - Vault remote folder changes by itself

[clancy]

When working within dreamweaver and using vaut integration, sometimes the remote folder will change, seemingly all by itself.

Symptoms:
When editing sites in Dreamweaver with vault source control integration, sometimes upon checkin, some or all files that you request to be checked in are not checked in. No error is returned. The only clue that this is happening is that the latest version of the files are not in Vault, and their checkout status is still checked out. Also, upon synchronise, sometimes dreamweaver will indicate that all the files in the site need to be synchronized, rather than just the few that have actually changed since the last edit.

Cause:
When either the checkin or synchronise problems as described above happen, if you check the Remote Info in your Dreamweaver site settings, click on the Settings button to view the remote folder in Vault, you will find that it has “forgotten” it’s remote folder location in Vault, it shows it’s remote folder as a different folder – usually a remote folder of a different site that you have recently modified and checked in files via Dreamweaver.

Frequency:
This problem happens intermittently. 75% of the time it works correctly. If you have only been editing one single site recently, it will work correctly. The problem occurs more frequently when you have been editing multiple sites within the same day or few days.

Work Around:
The current workaround we are using is: When we realize that the problem is occurring, we check the Remote Info in the Dreamweaver site settings, click on the Settings button to view the remote folder in Vault, select the correct remote folder location, then apply these setting changes, return to Dreamweaver and the checkin / synchronise will work correctly.

Solution?
We have not had this problem with sites that use the file server as the remote source. Has anyone else experienced this problem? Does anyone have a suggestion on what to try to remedy this situation?

Versions:
Vault: 4.0.4
Dreamweaver: 8.0
Vault_DWIDE.dll: 3.5.3 (from http://support.sourcegear.com/viewtopic ... 08de3531e5)

[jclausius]

Take a look in the following registry key - HKEY_CURRENT_USER\SourceGear\Vault\Client\Dreamweaver


Do you see sub key hives for each of site managed by Vault? If so, check the Profile, ServerPath and RemoteFolder string values. Do they have the correct repository folder info?


Note for other posters. There is a problem with Vault 4.0.6 (and previous versions) with Dreamweaver CS3 as Adobe changed some of the values where Site Information is stored. While this user's problem is not related to that, users of CS3 would find that Vault's DW IDE has problems as it cannot locate where local working folders are found.

[clancy]

My colleague and I took a look in the following registry key - HKEY_CURRENT_USER\Software\SourceGear\Vault\Client\Dreamweaver

Sub key hives exist for each site managed by Vault. The Profile, ServerPath and RemoteFolder strings have correct values.

Profile is the same for each hive as is ServerPath. RemoteFolder has the correct folder specified in each instance.

The only item with differing vaules is AutoLogin. The majority of sub key hives have AutoLogin set to True but a couple of them have it set to False.
_______
Clancy

[jclausius]

That seems to be OK. Are you having issues with this setup by itself (with no new sites). FWIW, there will be an updated Dreamweaver client available in Vault 4.0.7. There were some issues fixed where working folders did not switch correctly with NEW sites created from the Manage Sites Dialog.

Do you know if any of the problems encountered were shortly after creating NEW sites from that dialog?

Also, I'll be looking for some Dreamweaver Beta Testers for the Vault 4.0.7 release. If anyone is interested, you can respond to this thread or mail support at sourcegear dot com with the subject of - Vault 4.0.7 Beta Tester.

Thanks.

[clancy]

We are having issues with the loss of remote folder info both when we add a new site and when the list of sites has been stable for some time.

We have been able to reliably reproduce the problem by creating a new site and then switching to an existing site to synchronise.

When the list of sites is stable, switching between sites and synchronising randomly loses the remote folder info. This is a case we can not consistently reproduce.

FYI, we are also experiencing a problem with the Vault Service restarting, causing all clients to lose their connection. Could a loss of connection to the Vault Service be responsible for losing remote folder info?

(As an asside that i don't expect to be addressed in this post, the session loss is another problem that seems to occur randomly. I have tried all the various server and IIS settings outlined in this forum to no avail. My best guess to the cause of the service restartnig is an exception occuring during the execution of a command. I have decided to put up with it and plan to upgrade to the latest release at some point.)
___________
Clancy

[jclausius]

The loss of Working Folders does sound like an issue I addressed in the fixes for the Vault 4.0.7 DW client. I'd still like to work out trying to get a pre-release of Vault 4.0.7's Dreamweaver bits to see if that does solve the problem. Let me know if that is something we could try.

In regards to the Vault Server restarts, check the Vault Server Log and Windows Event viewer (app and system). And post anything there in a new thread. We'll see if we can track down what is happening in regards to the restarts.

[clancy]

If you think the new Vault_DWIDE.dll will work with our 4.0.4 server then yes we would like to try it. Unfortunately we are not in a position to upgrade our Vault Server at the moment.
________
Clancy

[jclausius]

No. These would be just a 4.0.7 Vault Client for Dreamweaver. I'll post back to this thread when I've tested the changes.