LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

No connection to perforce SCC in application

Hi,

 

in my project i am using Perforce as source code control provider. Currently i can check-out and check-in VIs in the projectexplorer. Also i can check-out and check-in different files programmatically with the Labview SCC-VIs. This works fine in Development mode but in my built application an error occures: The Open SCC Proveder.vi returns -2983 (No access to source control provider).

 

I already copied the SCC Tokens SCCConfigData, SCCProviderName, SCCProviderLocation from the Labview.ini to my project.ini.

 

Michael

0 Kudos
Message 1 of 5
(2,940 Views)

I would start by including Either the P4CMD directory "....vi.lib\SourcControl\Providers\P4CMD"

or the WinCI directory "....vi.lib\SourcControl\Providers\WinCI"

 

depending on which interface you have your SCC configuration set up to. The SCC vis make dynamic calls to the various providers required to support the different SCC platforms and thus need the specific provider files specified discretely. The Report Generation Toolkit works very similarly to this.

 

This will most likely solve the issue.

 

Greg Sussman
Sr Business Manager A/D/G BU
0 Kudos
Message 2 of 5
(2,931 Views)
I included the WinCI folder (NI_SCC_WinCI.lvlib) to the exe, but it still doesn't work. I know that if i want to call a vi dynamically, i have to fit the path specially for the runtimesystem. Does the application builder do that to the dynamic call of the WinCI-VIs without the need for fitting it manually?
0 Kudos
Message 3 of 5
(2,921 Views)

The path for the SCC vis should be transparent to your application. The NI code takes care of handling that internally.

 

You also need to include the WinCIWrap.dll into your build. The calls that access it are dynamic, the dll most likely does not get included automatically.

Greg Sussman
Sr Business Manager A/D/G BU
0 Kudos
Message 4 of 5
(2,919 Views)
The WinCIWrap.dll is already included in NI_SCC_WinCI.lvlib and i can see it in the support folder of the build results. Thus WinCIWrap.dll should be already included i think.
0 Kudos
Message 5 of 5
(2,916 Views)