LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

SourceGear Vault with LabVIEW 2009 gives error

Hi,

I try to evaluate SourceGear Vault for version control in LabVIEW 2009.

At their website they say that Vault is compatible with Microsoft SCC interface, but as soon as I select  "SourceGear Vault Classic Client" as provider in LabVIEW I get the error "Error -2924 occurred at prefPage_Source Control.vi".

 

Does anyone successfully use Vault with LabVIEW?

Any ideas of things I might need to do to get i to work?

0 Kudos
Message 1 of 6
(2,977 Views)
0 Kudos
Message 2 of 6
(2,972 Views)

Yes, but it relates to a slightly different error, an older LabVIEW and doesn't give any clear answers whether it works or not.

 

I was hoping that someone had make it work, or that someone can confirm that its impossible to make them work together (i.e. integrated in LabVIEW). Of course I can always use Vault externally.

0 Kudos
Message 3 of 6
(2,962 Views)

I don't know if this helps but I found the followinf error in my system's event log:

 

Event 1000, Application Error

Faulting application name: LabVIEW.exe, version: 9.0.1.4011, time stamp: 0x4b47e0ad
Faulting module name: VaultIDE.dll, version: 5.0.3.18802, time stamp: 0x4b6904df
Exception code: 0xc0000005
Fault offset: 0x00006a0a
Faulting process id: 0x454
Faulting application start time: 0x01cae69ec743166f
Faulting application path: C:\Program Files\National Instruments\LabVIEW 2009\LabVIEW.exe
Faulting module path: C:\Program Files\SourceGear\Vault Client\VS2003_Client\VaultIDE.dll
Report Id: 141bba26-5292-11df-b41c-ba763b99c846

0 Kudos
Message 4 of 6
(2,949 Views)
The text of the error is "An error occurred while opening a source control project or accessing a file. The specified path is invalid." Some providers are expecting certain values in parameter calls based on assumptions on how they will be used by various IDEs (mainly Visual Studio). It is possible that valid information passed by LabVIEW to SourceGear's provider does not match what they expect. This would require testing on both LabVIEW's and SourceGear's side to determine what is going on. It would probably be a good idea to start with SourceGear's support to see if they can identify what is invalid.
George M
National Instruments
Message 5 of 6
(2,935 Views)

Ok, I'll try with them first...

 

thanks!

0 Kudos
Message 6 of 6
(2,933 Views)