Skip to Content Information Center
Markvision Enterprise

Markvision Enterprise

Communication error when trying to Push a Configuration from the same product release using MVE 3.x.x

Issue description

Customer created a configuration file from (2016 - 2018). Modify some of the settings and update login credentials. When pushing back the configuration file to the same generation printer, error occurs describing "unable to communicate to the printer".

The same issue occurs when running the check conformance despite the discovery and audit work reporting no issues.

Explanation

The problem is when manually creating a configuration for the affected devices, the custom supply notifications section contains the settings for both pre - 2016 and 2016-2018 printers. When the configuration is cloned from the printer, these settings are pulled in correctly. In the sample configuration snippet below, they're trying to set both for all of the cartridge values, which is causing this "fatal" error. Basically, those OIDs don't exist on the real device, so when trying to read or write those values, it will always fail - and the error that's bubbled up is a communication failure.

Printer EWS > MVE configuration file

The settings blocked out in the red box are the failing case and would apply to all of the cartridges. The valid settings are the Nearly Low and Low behaviors. The Very Low setting is "static", and it is set in the engine, so there's a corresponding setting in either case.

Affected products

  • Software / Solution: Markvision Enterprise (MVE) version 3.5
  • Hardware: All Lexmark Products Released Between 2016 - 2018

Solution

Uncheck the bad values (Early Warning Behavior, Early Warning Percent, Near End of Life Percent, etc.) and just use the ones that correspond to the settings in the EWS (Nearly Low Percent, Nearly Low Behavior, etc.).

Should the issue persist, please contact your next level of support for further diagnosis or possible escalation.

LEGACY ID: SO8953

Was this article helpful?
Top