Can't check in using Dreamweaver 8

[mpeterson]

We've installed Vault v3.5 on a trial basis and one of my co-workers has set up Dreamweaver to integrate with Vault. He can check files out, and undo checkouts, but when he tries to check files in, he gets the following error message (index.aspx is the file he's checking in):

Started: 11/1/2006 11:55 AM



index.aspx - error occurred



File activity incomplete. 1 file(s) or folder(s) were not completed.



Files with errors: 1

index.aspx



Finished: 11/1/2006 11:55 AM

[jclausius]

The error message is definitely lacking. Let's see if a client side log file will help.

To create a log file, while the user is logged in, go to the following key within the registry. Add the key "Dreamweaver" if it is missing.

HKEY_CURRENT_USER\Software\SourceGear\Vault\Client\Dreamweaver

Next, create a new string value under that key named "LogFile". The value data will be the path to a file that you want created. For example, "c:\temp\dwlog.txt"

Restart Dreamwever and repeat the same steps as before.

When you have the log, post it back to the forum.

[mpeterson]

Here's the log you requested. Thanks!

[jclausius]

While I go over this log, can I ask for some more information?

- Who is the user? Louis?

- Afte the checkout, does the file give the green check mark within Dreamweaver?

- If you start up a Vault client, go to the change set tab on the bottom. Does the index.* files have edited for the status?

- Check the working folder of the file within the Vault client. Does this match the place where it exists within Dreamweaver?

[mpeterson]

-Yes, the user is Louis.

-After checkout, Dreamweaver shows a green check mark next to the file in Remote View. In Local View, it has a red check mark.

-In Pending Change Set, the status is "Modified", but in the main window in the Vault client, the status is "Edited", and it shows that it's checked out by Louis exclusively.

-The working folder in Vault matches that in Dreamweaver.

Thanks!

[jclausius]

Can I ask one more thing?

Can you uninstall Vault 3.5 and then download/install the Vault 3.5.1 client on Louis machine?

There was a small fix related to checkin status. Since Louis should see a "green" check mark in the local view, I want to eliminate this possibility as the source of the problem.

[mpeterson]

Louis uninstalled 3.5.0 and installed 3.5.1, but the behavior is exactly the same.

[jclausius]

In the local view, what is the path shown at the top?

[jclausius]

Or better yet, let's try another test.

Create a new Site - remove the old one.

On the site, put something like c:\vaulttest for the local path. For the remote server, try a new location in the repository create $/vaulttest/.

Next try the same test as you did before. Create the files locally, "Put" them to the remote sever. Try a check-out. Do you still get a red checkout on the local view?

[mpeterson]

I put a Vault project on the root of c: on the server and Louis created a Dreamweaver local folder on the root of c: of his PC, both folders named the same thing. Same behavior. Everything works fine except for checking in, which doesn't work. Since we've tried this with 2 different versions of Dreamweaver and 2 different builds of Vault, I suspect this is a problem with your implementation. If you have any fixes, or configuration changes we can try, please let me know.

Thanks,

Melanie

[jclausius]

I had hoped the solution would be an easy one.

Would you be willing to generate a more robust log from the .Net side of things? To do so, you sould need to do the following:

a) Copy devenv.exe.config file in "C:\Program Files\SourceGear\Vault Client" to Dreamweaver.exe.config (assuming Dreamweaver.exe is the name of the executable binary).

b) Make the following changes in Dreamweaver.exe.config

* Set value to "true" for "enableLogging" (ex: "<add key="enableLogging" value="true" />" )

* Set value to "ide" for "classesToLog" (ex: "<add key="classesToLog" value="ide" />" )

* Add the following key to the same configuration section
<add key="logFilePath" value="C:\temp\VaultdwIDElog.txt" />

c) Save the Dreamweaver.exe.config file,

d) Restart Dreamweaver.

e) Repeat the same steps.

This should generate a full log feature. Please post that log file along with a new dwlog.txt so I can get a good look at what is going on.


Also, what was the name of the path you used on disk as well as the path of the repository? What I need to do is recreate this problem.

We've seen it happen before - http://support.sourcegear.com/viewtopic.php?t=6613 , but then after the user set up another site definition, the problem went away.

[mpeterson]

OK, Louis installed Dreamweaver 8 and Vault 3.5.1 on a completely newly imaged PC, no difference. He then followed your instructions below, but no C:\temp\VaultdwIDElog.txt gets generated, just the dw.log file (attached).

The site I created was c:\cmintake, which was also the name of the working folder on Louis's machine.

[jclausius]

Is the name of the file Dreamweaver executable, Dreamweaver.exe? I

I also think I missed a step. Could you please copy the Dreamweaver.exe.config file to the same directory as the Dreamweaver.exe and re-try the same steps?

[mpeterson]

Yes, the Dreamweaver executable is Dreamweaver.exe. Also, Louis tried your procedure with Dreamweaver.exe.config in the folder with the Vault client and in the folder with Dreamweaver.exe. He restarted Dreamweaver after moving the config file. Behavior didn't change.

[jclausius]

Melanie:

During the first run using Dreamweaver.exe.config was in the \Vault Client directory was that correct? Was Dreamweaver completely shut down at the time? Were there any other instances running? The default behavior is the exe.config file is located within the \Vault Client directory. This allows the log file to be created.

We could try trouble shoot this in house, as we want to fix the problem.
Is this a sample project? Would you and Louis be willing to upload the test project so we can try it on in house machines?

Thanks.