Compiler error when "Save All" on project: copy cvt, csrs=0x32

[BertMcMahan]

So I just started getting this error when trying to save my project:

"Compiler error. Report this problem to National Instruments Tech Support.

copy cvt, csrc=0x32".

I can open my project from disk, then immediately try to do a Save All, and I get this error. As far as I can tell nothing changes when I open the file. I haven't got the foggiest idea how to even track down what's throwing the error, and the message given above doesn't help much. I don't have anything in my project called "cvt". Any thoughts? I can revert to an older version (as I finally started using SCC ) but I'd rather not lose a day's worth of work- plus it's not the first time I've gotten a similar error and I'd rather figure out the root cause.

Most of my searching indicates people having problems with VI's that they can fix- but this is happening in the *project* environment.

Unfortunately I can't post the project due to NDA's, and it has over a thousand elements anyway (the Actor Framework plus a bunch of accessors means the whole project has a bazillion VI's!)

[BertMcMahan]

Can't see a way to edit my previous post, sorry.

I restarted LabVIEW a few times which didn't fix anything, but restarting my computer gave me a popup:

'Investigate Previous Internal Error or Warning" with the message "The last time you ran LabVIEW, internal warning 0x2F74C063 occurred in gencode.cpp."

Choosing to Investigate this code gives me a log file, with a few entries for the following followed by a dump of some kind:

"2/2/2018 3:52:52.379 PM
DWarn 0x2F74C063: copy cvt, csrc=0x32
e:\builds\penguin\labview\branches\2016\dev\source\diagram\gencode.cpp(4117) : DWarn 0x2F74C063: copy cvt, csrc=0x32
minidump id: 4313252c-b81b-411d-9ba1-321cfc1d54a7
$Id: //labview/branches/2016/dev/source/diagram/gencode.cpp#6 $"

I have no clue what e:\builds\penguin... etc. is. I have no e drive- I suspect that's the internal path that NI uses when they compiled the code, perhaps?

[Bob_Schor]

It's an internal error, the information that you call NI Tech Support (866 275-6964 in the US -- I've used it enough I know it from memory) and log a Support Request.  If you got a Crash message, you should also have gotten something saying "Do you want to send this to NI?" -- answer "Yes".  The AEs (Application Engineers) are usually pretty helpful ...

Bob Schor

[BertMcMahan]

It was weird Bob, I didn't get a crash report window- just a popup with that message and an OK button.

I ended up reverting back a revision from my repository- it was quicker than calling NI, sending in the problem code, and waiting for a fix. Not a great solution but sometimes you just have to keep going 🙂

I was hoping this would be one of those oddball "Oh yeah you have to update [some unrelated piece of software] to fix it" issues, but no such luck. Ah well!