LabVIEW 2011 starts with an error every time on OS X

[ScottH]

I get this error dialog every time I start LabVIEW 2011 on my Mac.

OS X 10.6.8

LabVIEW 11.0 Student edition

+Control system toolbox

+MathScript RT

[P@Anand]

That is because when you close the LabVIEW in an improper way like killing it and if you have any vi open then you will get that prompt. You can disable that prompt in Tools>> Options as shown below

[ScottH]

I'm not closing LabVIEW in an improper way or leaving any VIs open. I get the error if I open and close LabVIEW without even opening a VI. It clearly has something to do with a license issue.

I know I can not prompt to investigate internal warnings, but I shouldn't be generating them in the first place. 

Thanks,

-Scott

[rolfk]

What do you click on that dialog? It seems you had some issue at one point when starting up LabVIEW and it was stumbling over an unexpected error/bug in the license manager, maybe because of some corruption of the registration data? And for some reasons that crash report stays lingering on your machine. One reason for this to stay lingering around would be to dismiss the dialog with the red dot on the left top side which is just like a Cancel. Or selecting "investigate later" and closing it with continue. Or there is a problem with permissions on the crash file that the actual user does not have proper write/delete rights on the file, when you close the dialog with one of the other two selections.

[ScottH]

It has given this error every time LabVIEW has started up. This is a fresh install and it has done this every time.

Here is the log file:

####
#Date: Fri, Jun 22, 2012 1:01:30 AM
#OSName: Mac OS X
10.6.8

#OSVers: 10.6.8
#OSBuild: 10K549

#AppName: LabVIEW.app
#Version: 11.0
#AppKind: FDS

6/22/12 1:01:31.544 AM
DWarn 0xAFBF5C57: LabVIEW not initializing for Pro, Full or Student Edition. Undefined behavior may result.
LVLicenses.cpp(485) : DWarn: LabVIEW not initializing for Pro, Full or Student Edition. Undefined behavior may result.
$Id: //labview/branches/2011/dev/source/licensing/LVLicenses.cpp#9 $
0x0014D8D3 - __Z13CallErrorInfoPKclS0_17_DebugOutputLevelmS0_ + 49
0x021DAADB - _DebugOutputCallHandler + 45
0x021DA958 - __ZNK11DebugStream7ProcessEv + 3E
0x00B669CF - __ZN11CLVLicenses25CheckNonNILMFunctionalityEv + 3B5
0x00B66F43 - __ZN11CLVLicensesC1Ev + 41
0x00B66FB2 - __ZN11CLVLicenses26InitializeLVLicensesGlobalEv + 42
0x00B6723E - __ZN16LVLicenseService4InitEv + C
0x00710834 - __Z7InitAppv + BE
0x0071D2AC - __Z13AppInitializev + 85E
0x00723C09 - __Z15LVMainEventProcP6WEventl + 1B41
0x01638D90 - __Z17InternalEventProcP6WEvent + 20
0x0163FEB6 - _WSendEvent + 27E
0x00007844 - __Z13InitializeAppl + 54
0x00007136 - __Z6MGMainlPKPKc + 17E
0x000074E2 - _CommonMacMain + 1B8
0x00002C02 - <unknown> + 2B11
0x00002B29 - <unknown> + 2A38
0x00000002 - <unknown> + FFFFFF11

[ScottH]

Here is what I get when I choose to send the log file to NI.

"There are no possible solutions to the question you have asked." Crazy.

-Scott

[ScottH]

Here is what I get when I choose to send the log file to NI.

"There are no possible solutions to the question you have asked." Crazy.

-Scott

[Jon_S.]

Hey Scott,

I looked into the CAR database and found that this has been reported as CAR 315828.  It only occurs when using the Mac Student Version.  I don't believe that this has any bad side effects as there isn't anything listed about it in the CAR.