Perforce SCC and Labview 8.5

[Zedd]

I have been using Perforce with LV for a couple of years now and until recently, all has been ok.

Trouble is I recently upgraded the PC that was running my SCC and upgraded my client installations, well I'm assuming thats part of the problem anyway.

On my client PC, I have the perforce root set to a folder on my D drive. Now, everytime I open LV 8.5, open a library file or code that uses a library file I get an error from Perforce telling me that path xxx.vi is not under client root folder.

Well, of course it isn't - it never was before, why does it need to be now?

when it's only 1 message it's an annoyance. when it's 20 or 30 that i need to acknowledge before I can get on it's a right royal pain the arse.

This behaviour is not seen on LV7, 7.1, 8.0 but it is on LV 8.2

Any ideas on how to resolve this? other than moving my client root folder of course, which I don't want to do.

Ta
Matt

[gmart]

What version of the Perforce client are you using? In LabVIEW, which SCC provider are you using? Do you have all the previous LabVIEW versions on the machine in question and the SCC integration works fine?

Have you tried performing operations on files in that client from Perforce's command line? It would be interesting to know if you can do a "p4 fstat" on a file from that client.

[Zedd]

I am using the latest release for winXP - client version P4SCC/NTX86/2005.1/85663

[gmart]

The latest client release of P4Win/P4 is 2007.3. The P4SCC plugin is at 2007.2 If you are using 2005.1, I believe some of the older versions had capitalization problems with drive letters. Perhaps you can try "d:\" instead of "D:\".

[Zedd]

Ooop - pressed the wrong button.

I am using client version P4SCC/NTX86/2005.1/85663 and server version 2007.3/143793. SCC provider is set to Perforce and yes, all the versions of labview I have tried this with are on the same client PC.

I haven't tried the P4 command line from my client PC - I'll give that a go and report back.

My initial thought given that it affects both 8.2 and 8.5 is that it has something to do with the way LV is interfacing with Perforce, but beyond that I'm at a loss. For example both 8.2 and 8.5 request and are given a 12 houre perforce ticket, which none of the other versions do (login expiration dialog under SCC options --> advanced, tab connection.)

M

[gmart]

Which SCC provider option are you choosing in LabVIEW - Perforce SCM or Perforce Command Line. It sounds to me like you are selecting Perforce SCM. If so, try your operations with Perforce Command Line.

[Zedd]

Ah - that seems to have cured it.

what's the difference between SCM and command line? I had just gone with what LAbview defaulted to.

M

[gmart]

Perforce SCM is a plugin to the Microsoft SCC Interface. Perforce wrote it so they control the behavior. Perforce command line is a plugin written with VIs that communicate to Perforce via their command line. The Vis are cross platform while the SCM is Windows only. Each has its pros and cons. Your original issue if I remember was errors for files not being on the client. I'm not sure why changing to the command line helped, but that points to some configuration issue with the SCM.