Can't check in using Dreamweaver 8

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

mpeterson
Posts: 10
Joined: Mon Oct 23, 2006 10:10 am
Location: New York, NY

Testing our project in-house

Post by mpeterson » Mon Nov 13, 2006 3:08 pm

Yes, Dreamweaver was completely shut down. Louis tried putting the config file first in the Vault Client directory, and then in the local folder Dreamweaver created for the project. I can't give you the test project we've been working on because a) it won't run without connection to a SQL database, and b) it contains confidential information. However, I've created a dummy project that just has one almost empty HTML page. I've added it as a Vault project, but now we can't open the Vault client - it says we have too many users. I suspect this is because our trial install has expired, since I haven't added any more users. Would it be possible to give us one more week on the trial install so we can try to work this problem out?

Thanks,

Melanie Peterson

jclausius
Posts: 3706
Joined: Tue Dec 16, 2003 1:17 pm
Location: SourceGear
Contact:

Post by jclausius » Mon Nov 13, 2006 3:12 pm

Contact our sales department - sgstore at sourcegear dot com - If you mention your name and this posting, they will respond with an extension, as I've forwarded the request to them.
Jeff Clausius
SourceGear

mpeterson
Posts: 10
Joined: Mon Oct 23, 2006 10:10 am
Location: New York, NY

Here's a test project

Post by mpeterson » Tue Nov 14, 2006 4:30 pm

Hi there - Attached is a test project that's just one HTML page. I set it up in Vault and Louis tested it, with the same results as before. He can check out, but can't check in. I'm also attaching the latest log Louis generated.

Thanks for your help,

Melanie
Attachments
log.txt
(19.46 KiB) Downloaded 223 times
WebApplication1.zip
(14.39 KiB) Downloaded 226 times

jclausius
Posts: 3706
Joined: Tue Dec 16, 2003 1:17 pm
Location: SourceGear
Contact:

Post by jclausius » Wed Nov 15, 2006 11:52 am

OK. This worked for me. I wonder if this is a problem of configuration.

Below are the steps I took to test the project. Can you see if there is anything different here than the steps Louis took to set up the project?
  1. Created a directory on disk (c:\webapp).
  2. Created a virtual directory within IIS named WebApp
  3. Added all files and folders - except bin from your zip to the disk folder.
  4. Dreamweaver - New Site
    1. Local Info
    2. Site Name - WebApp
    3. HTTP Address - http://localhost/WebApp
    4. Site local root folder - c:\webapp
    5. Remote Info - left at None.
  5. Click Done on Site Info.
  6. Once site opened in Dreamweaver, I went back to Manage Sites dialog.
  7. Edit WebApp Site
  8. Edit Remote View
    1. Remote Info
    2. Access - SourceGear Vault
    3. Logged in.
    4. Clicked Settings.
    5. Asked to re-login.
    6. Choose Repository.
    7. Created / Choose Folder $/DreamWeaver/WebApp
  9. Went to Local View, selected all items, and then issued a "PUT". All files added a "lock" icon.
  10. Switched to Remote View to make sure the files existed there.
  11. Opened the Vault GUI, looked at $/DreamWeaver/WebApp to verify the working folder was set to c:\WebApp, and the files were in the correct state - values set for local version and date, no status of missing, edited, renegade, etc.
  12. Back to Dreamweaver to checkout $/DreamWeaver/WebApp/WebAppForm.aspx from the REMOTE view.
  13. Went to the Vault client to see if the file was checked out correctly.
  14. Back in Dreamweaver, switched to LOCAL view to make sure the file was checked out. Undid the checkout from LOCAL view. This worked.
  15. Checked out C:\WebApp\WebAppForm.aspx from LOCAL view.
  16. Added "TEST PAGE CHANGE 2" to the file.
  17. Saved file.
  18. Successfully checked in File from LOCAL view.
  19. Switched to Vault client to verify the file was at version 2.
Jeff Clausius
SourceGear

Post Reply