Howto configure LabVIEW with MKS Source

[HackyJ]

How do i configure LabVIEW to work with  MKS 2007 Source?

[Mathan]

quick search

[HackyJ]

I set up MKS 2007 Client to handle MS Visual Studio 2005.

I then found MKS SCC Integration in LV SCC Provider.

I received the above error at selecting this.

[HackyJ]

Additionally i tried this with various LV Version. LV8.2.1 gives some more information and

tells, that it cannot access mksapi.dll.

This file is located in the installation directory of MKS/bin.

So i assume that the link where LV searches this DLL is missing.

Can anyone tell how LV searches the mksapi.dll.

[HackyJ · Accepted solution]

I solved my problem:

Error -2901; The registry Entry was missing or wrong.

[HKEY_LOCAL_MACHINE\SOFTWARE\Mortice Kern Systems\Integrations\SCC\IDEs\National Instruments LabVIEW]"DllName"="use base""IDESccName"="National Instruments LabVIEW"

Error -2902;
a) The Project name in LabVIEW needs to be the same as in MKS.

b) The Local Project Path MUST contain a project.pj e.g. the Sandbox must be created.

[Mathan]

Thanks for posting back the solution. Good this will help somebody. Keep it up.

[pachook]

Hi HackyJ,

how did you manage to get along with the Error -2973 problem? I tried the solution with register editing and still have nothing ...

Thanks in advance

PacHOOk

[HackyJ]

Hi pachook,

 i add my notices i collected in the meanwhile. Hope this helps.

i once got the -2973 error but this wasnt reproducible to me.

The Point is that you need to have a project in MKS and exported as a sandbox.

There you refer to the Project and the path.

Also i got errors because i wasnt able to connect to the server itself. So my MKS wasnt fully set up properly.

Dont try to establish SCC with LabVIEW if you are not in  the situation that you have a project in your sandbox.

Hope this helps. Please add feedback for the others poor guys like us.

[pachook]

Hello HackyJ,

Thanks for your effort, unfortunatelly your hints did not help (i.e. I am still getting the -2973 error) I am not sure, but maybe solution is a little bit different, while I am using LV 2009 and MKS integrity client 2009. I think that maybe for that version use base as dll key is not the proper one.

I tried to change the registry input for the one from VC++, and it also didnt work. Let me just add, that the project itself is already on the mks server and I am mainly working on files located in sandbox. Now I cant just choose the sourceControlProvider - not to mention specifying project.

I attach the Error I recived from LV.

[HackyJ]

Hello back,

here my setup with MKS 2009