Vault Locking

This forum is now locked, since Gold Support is no longer offered.

Moderator: SourceGear

Locked
jwebster
Posts: 15
Joined: Fri Jan 06, 2006 12:19 pm
Location: Cincinnati, OHIO

Vault Locking

Post by jwebster » Tue Jan 17, 2006 10:20 am

We are using your vault product. In vb6 when we say commit project to vault the vault login screen comes up but the screen is locked and the only field we can type in as the username field. It sets focus to that screen only and that field only and then we can do nothing unless we ctrl alt del. Please help.

Jim
Jim Webster

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Post by lbauer » Tue Jan 17, 2006 11:06 am

Is VB on Windows 2003 Server?
Linda Bauer
SourceGear
Technical Support Manager

jwebster
Posts: 15
Joined: Fri Jan 06, 2006 12:19 pm
Location: Cincinnati, OHIO

Post by jwebster » Tue Jan 17, 2006 11:16 am

Yeah! It is.
Jim Webster

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Post by lbauer » Tue Jan 17, 2006 11:34 am

This is a known issue with VB on Windows 2003 Server and the .NET Framework 1.1. It is a Microsoft bug.

One of our users recently provided us with this information:
Microsoft has confirmed that this is a bug. It is related to a fix that they included in a build of .NET 1.1 post SP1 which happened to be deployed on Windows 2003. This fix resolved an issue with using Form.Show() through COM interop, but also caused this problem with Form.ShowDialog(). This is why it only happens on Windows 2003.

Interestingly enough, this fix was missed in .NET 2.0, so the Form.Show() bug remains but Form.ShowDialog() works as expected. So, by installing the .NET 2.0 redistributable on the Windows 2003 and using the VB6.exe.config file to force the newer framework to be loaded the dialog will work as expected.

1. Install the .NET 2.0 redistributable on the Windows Server 2003 machine.
2. Create a file called VB6.exe.config in the same directory as VB6.exe and enter the following:
Code:
<?xml version="1.0"?>
<configuration>
<startup>
<supportedRuntime version="v2.0.50727"/>
<requiredRuntime version="v2.0.50727" safemode="true"/>
</startup>
</configuration>
We haven't tested this in house.

A possible work-around -- you might be able to use the tab key to change focus to the Vault "Connect to Server" text boxes and type in them, and also use the tab button to bring the OK button into focus. With the OK button in focus, hit "Return" to log in from VB 6.
Linda Bauer
SourceGear
Technical Support Manager

jwebster
Posts: 15
Joined: Fri Jan 06, 2006 12:19 pm
Location: Cincinnati, OHIO

Post by jwebster » Fri Jan 20, 2006 11:09 am

Linda:

Just wanted to let you know that I tested this scenario on two seperate windows 2003 servers here at TFX Aerospace and it seemed to work great.

Jim
Jim Webster

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Post by lbauer » Fri Jan 20, 2006 12:19 pm

Thanks for letting us know. We're glad to have a solution for our VB/Windows 2003 users. :)

(I'm assuming it was the .NET fix, rather than the workaround?)
Linda Bauer
SourceGear
Technical Support Manager

jwebster
Posts: 15
Joined: Fri Jan 06, 2006 12:19 pm
Location: Cincinnati, OHIO

Post by jwebster » Fri Jan 20, 2006 1:51 pm

Yes, installing framework 2.0 and creating the VB6.Exe.Config is the way to handle this. (The workaround option does not work. The tab only hits the buttons and the username field)
Jim Webster

Locked