Bug in SCC tools when checking in file

[DavidBoyd]

I think this is an old bug that may have resurfaced; I know that I reported it a few versions ago and thought it had been fixed in more recent LV releases.  At any rate, it's more of a minor annoyance than a show-stopper.

The environment: LabVIEW 8.5 PDS, configured SCC provider is MS Visual SourceSafe 6.0c.

When I check a VI back in using the Tools->Source Control menu, the checkin actually occurs, but the SCC interface throws an error.  The error text is:

Error 5 occurred at SCC_Global_OnCommand.vi.ProxyCaller

An error occurred trying to check in the specified file(s).

As I said, I remember seeing this before, and here's what I think is happening:  the SCC tool code completes the checkin by invoking a revert on the VI file in order to get it back to a readonly status.  The OS throws some kind of advisory that basically says, "hey, this file has changed", which is legitimate in this case since VSS, upon checkin,  does keyword expansion on the VI file (and I have a keyword tag in the VI for the VSS version).  The SCC tool code assumes the return code is a real error and reports it as such.

If I have time, I'll try to look up old emails I know I had with somebody at NI about this.  I think the last time, I was able to point to an SCC VI that needed a simple mod to discard the "error".

Dave

[TMC-NI]

Hi David,

I've been looking into this, and I do not find anything with that error code number.  Are you sure it is 5?  I do see some similar bug reports in the past that have longer error numbers, however.  I will look into this further, in the meantime, if you do find those emails, I'd be interested in reading that information.

[DavidBoyd]

Hi Tolga,

Thanks for replying.  Yes, it's definitely an error 5.  In fact the error text in my original post was a copy/paste out of the dialog.  I'll see what I can dig up out of my email archives and if I find anything I'll post it here for sure.

Best regards,

Dave

[DavidBoyd]

Tolga,

So far I found this in my email logs (a reply I posted to Info-LabVIEW).  It implies that I had reported this during the LabVIEW 7 beta.  Are those beta bug reports still available within NI?  (I'll keep looking for other info.)

Regards,

Dave

Fri 7/18/2003 10:31 AM

I'd noticed this too, but had chalked it up to having a 'non-standard' installation of VSS (running the .exe directly off the file server), and hadn't gotten around to trying to troubleshoot it.

Thanks, Nicola, for the link! Who knows how long I would've messed with that before giving up. The relevant VI is diagram-locked 😕

Now that I've got it back to working again, I see that an undesirable behavior I'd filed a bug report about is still there. (I thought this was addressed early on in the LV7 beta cycle, but apparently the fix just didn't make it to the release version of the PDS.)

If you put keyword expansion tags into your VIs (the fixed-length kind, of course), the subVI 'Source Code Control\_backend\WinAPI\WinAPI SCC Add Files.vi' throws an error when you check the file back in and the keywords are updated. The checkin happens, but the revert does not, and you're left with a LV SCC error dialog. The fix is to modify this VI, test for the 'File Already Open' (value 5) return from the SCC DLL, and force it to zero. I'm told that the 'File Already Open' return is just the MS SCCAPI's way of reminding the caller that the file needs to be refreshed in memory after keyword replacement.

Regards,

Dave

David J Boyd

Senior Test Engineer

Respironics

175 Chastain Meadows Court

Kennesaw GA USA 30144-3724

(V)770-429-2809 (F)770-423-2302