VB6 IDE Session Timeout

[Guest]

We are using Vault 3.01 and I have one VB6 project where I am having difficulty connecting to Vault from within the IDE. When I open the project, I receive a message box with "SourceGear Vault" in the title bar and the text "You may now perform the intended operation with the new session token." When I press the OK button, the message box is dismissed and then reappears. At this point, the only way out is to kill the process via the Task Manager.

VB6 seems to only look at the file attributes at project startup time. If a file is marked read only, it won't let you edit the file. If you remove the read only attribute, you have to restart the IDE before VB6 will allow you to write to the file. As a result, using the Vault GUI is painful since you have to exit and restart the IDE whenever you check out a file.

[dan]

You might try working in CVS mode outside the IDE, if that working style works for you. When it retrieves files, it marks them read-write right away, and then the Vault client will scan files and mark them edited when they've changed. That way, you can edit any files you want without having to change their read-write status first, and then check in just the changed ones from the Vault GUI client.

[Guest]

I kind of like the idea of read only files so that something does accidentally get changed.

Any idea regarding the session timeout message?

[dan]

Sorry - I just noticed the title talks about session timeout. Yes, that is probably the culprit for the other strange error about the session token.

At what point do you start getting error messages (before/after login), and can you post screen shots?

[staffantj]

I get the same behaviour when attempting to access our SouceVault from within VC++ 6.0 across a VPN link.

The message comes up a number (approx 10-15 times) in 2 places.

1) In between the signon and the 'do you want to update to the latest source' dialogs
2) After the query dialog, but before the listbox with the file list from the server

Any ideas as to what might be happening?

[dan]

If you are on 3.0, I'd recommend upgrading to 3.0.7. The session token message was bogus and we were dropping the real exception. The problem was somewhere in getting file status. You'll need to upgrade to 3.0.7 to get the real error - sorry for the inconvenience...