SourceGear Support

Just an update on this. The developer in question reported

In order to get around the error, I renamed the QSSReportsFin Vault file to _frmJ251S1.frm, then added frmJ251S1.frm as a new file. The new one works fine for checkout/in.

Tim

One of our users started getting an error on check-in today. The client reports an error "A database error has occurred (FailDBInsert)." We narrowed it down to one file, and he was able to check everything else in. Things are working fine for other developers, and for him with other files....

We just recently upgraded from 3.5 to 4.1 (4.1.0.16216 to be exact.) Within VisualBuild, we have a step that is supposed to check out *.vbp in a project directory that had previously been working fine. The command line was as follows: "C:\Program Files (x86)\SourceGear\Vault Client\vault.exe&qu...

Well, here's a good early on troubleshooting step that could have saved a lot of frustration:

Visit update.microsoft.com and install all available .NET packages.

After I asked him to do that, he reported successful operation of Vault.

Tim

Any update after the last information? This developer is severly affected by this situation.

Is it possible to get the debug symbols for the client? I could then have him create another exception and provide another Dr. Watson report with more detailed information on the fault.

Thanks,
Tim

Is it possible for you to attach images of the error messages? Also, I noticed earlier that you couldn't open projects from source control. If you started over with an empty project, and you add that project to source control? And if so, does it still crash when you go to retrieve it? The error mes...

Not much to go on here. The vault version is 3.1.8. It is Windows XP Professional, 32bit. No logs are generated as it receives the fatal exception as it tries to launch. The Dr. Watson error didn't provide any insight into the function that was causing the fault in the vault ide DLL? (The Dr. Watso...

I had him reinstall Vault, after reinstalling and verifying operation of VSS, and it still exhibits the exact same behavior (exception.)

Terence wrote:Could you try one more test for us please. If you uninstall Vault, and install VSS. Does version control work with VB6 and VSS on this machine?

Uninstalled Vault, reinstalled VSS, and he was able to use it (Visual Source Safe) without any issues.

Tim

Any update on this?

Working with the developer in question, I performed a variety of steps including removing all VB6 and VisualStudio 6 related programs, directories, and registry entries, then reinstalling everything after a reboot. He still gets the same problem. It is VB6.EXE throwing an exception when you try and ...

Received that popup again, so I cancelled it, collected the requested logs, and emailed them to the support address.

Thanks,
Tim

lbauer wrote:If this reimport has problems, I'd like to see both the import log and the Vault server log for the time of the import. It's sgvault.log in the %windir%\temp\sgvault directory on the server machine.

Ok, this may take a while, but either way I'll report back.

I am trying something else too... I've deleted everything from the copy of the database on the second machine, am reimporting from an archive, and then will give it a go again in case there was something the analyze didn't catch.

Tim

the earliest errors seen are as follows: Created ($/Companions/PDA Line/PDA100Palm/frmLoading.frx) at 5/1/2002 3:36:56 PM(Links: $/Companions/PDA Line/PDA100PPC/frmLoading.frx $/Companions/PDA Line/PT01PPC/frmLoading.frx $/Companions/PDA Line/PT01Palm/frmLoading.frx ) Change set type: AddFile Adding...