Solution
MAX has the ability to detect exceptions thrown by internal plug-ins. Some of the exceptions are benign and do not negatively affect normal operation in MAX.
If this is the first time you've seen this error, restart your computer first. The error sometimes occurs after installing new NI software and not restarting the PC.
Here is a list of the current known exceptions. If the exception is benign and does not negatively affect your system, you may select
Do not show this error again in the error dialog to prevent it from displaying again.
| # | Plug-In | Exception | Benign? |
|---|
| 1 | NI-DAQmx | CpcCopierProxy::GetSourceItemsIfNecessary | Yes |
| Can occur when you import a .nce file to a remote RT target. Upgrade to NI-DAQmx 9.0, or later, to resolve. |
| 2 | niFPui.mxx | CmxRSFrameworkObserver::NotifyObjectRemoving | Yes |
| Can occur when you delete multiple FieldPoint targets. |
| 3 | niVISAui.mxx | CmxAggregateItemUI::GetPopupMenu | Yes |
| Can occur when you highlight/click a VXI instrument in MAX. |
| 4 | imaqcfgui.mxx | CmxAggregateItemUI::FinalRelease | No |
| Can occur when MAX is closed. If MAX is upgraded from 4.6.2 or earlier to 4.7 and NI-IMAQ is not upgraded, this exception will be returned. Upgrade to the latest version of NI-IMAQ to resolve. |
| 5 | niHDVUI.mxx | CmxProviderWrapper::Initialize | No |
| Can occur when opening MAX. If MAX is upgraded from 4.6.2 or earlier to 4.7 and LabVIEW DSC is not upgraded, this exception will be returned. Upgrade to LabVIEW DSC 2010 or later to resolve. |
| 6 | nipalsys.dll | CmxSysExpertManager::InitializeExpert | No |
| Can occur when opening MAX. This exception will be thrown (in addition to other possible errors) on systems with Physical Address Extension enabled. See NI Software Fails When Physical Address Extension is Enabled to resolve. |
| 7 | niPXIui.mmx | CMXAggregateItemUI::GetViews, CPXIObject::FindParent | No |
| Can occur with PXI Platform Services versions before 3.0 and is related to an inability to load all or some parts of configuration for PXI chassis. Update to PXI Platform Services 3.0 or later to resolve. |