hexagon logo

Strange Error affecting All CMMs: Critical Error

We have many CMMs in our shop, and almost every one gets this critical error every day (ref image). The content of the critical error all relates to memory issues. We have added the maximum amount of RAM within our PCs, and still see the error. To bypass the error, the computer is restarted, and everything works like normal until it pops up again. It seems to occur at the end of the program while generating a report, but I can't confirm it only happens then. For context, in 2025 we have reported 101 instances of this error. Has anyone gotten this error, or something similar? We do use a software to launch all our programs, and are investigating if this could be the cause, but it seems like a PC-DMIS issue since its occurring around report generation. Here is a snip of the header of this error, anyone have any ideas?

Parents
  • Check the Windows Event viewer to see if you can find anything related to this dialog. That might tell you where the error originates from, "your" software or PC-DMIS.

    System.Windows.Markup.XamlParseException:
    Represents the exception class for parser-specific exceptions from a WPF XAML parser. This exception is used in XAML API or WPF XAML parser operations from .NET Framework 3.0 and .NET Framework 3.5, or for specific use of the WPF XAML parser by calling 
    XamlReader API.

    Is your in-house app targeting .NET 3.0 or .NET 3.5?

Reply
  • Check the Windows Event viewer to see if you can find anything related to this dialog. That might tell you where the error originates from, "your" software or PC-DMIS.

    System.Windows.Markup.XamlParseException:
    Represents the exception class for parser-specific exceptions from a WPF XAML parser. This exception is used in XAML API or WPF XAML parser operations from .NET Framework 3.0 and .NET Framework 3.5, or for specific use of the WPF XAML parser by calling 
    XamlReader API.

    Is your in-house app targeting .NET 3.0 or .NET 3.5?

Children
  • .NET Framework 3.0 and .NET Framework 3.5 ... oh

    * Try to deactivate the PC DMIS homepage maybe this helps

    * Try disabling Word and Excel previews in Explorer. 

       There was a problem with a Windows update about seven months ago that caused pcDMIS to crash with similar error messages. 

       Don't ask me how that's related, but it helped at the time. (i think it was fixed in windows, currently I can have it back on)