Skip to Content Information Center
Lexmark C950

Lexmark C950

Application cannot be accessed message displays after pressing the release station icon

Issue description

An “Application cannot be accessed” error message appears on the control panel after pressing the Release Station icon of the Pharos Blueprint app.

This error indicates that the printer is experiencing communication issues with the collector or analyst server where the terminal is pointing to.


This may happen due to various reasons.

Settings mismatch between the Printer and Analyst setting



Check the following printer and app settings:

  1. Verify whether the Lexmark embedded Document Accounting Solution (eDAS) app is configured correctly. It should point to a collector or analyst server.

    Note:  You may try to point to a another collector or analyst server by changing the document accounting URL IP address or hostname. You may also compare the settings with a functional printer.

  2. Copy and paste the URL into a web browser and make sure it connects. This is the best way to check for misspellings

  3. Test the eDAS app.

    Note:  If it does not connect or the test fails, make sure the password is correct (pharos is the default password).

  4. If the hostname is used, replace the collector or analyst server entry with the equivalent IP address, and then verify whether the test passes.

  5. Go to the printer’s Embedded Web Server (EWS) > Settings > Network/Ports > TCP/IP, and make sure the Gateway and DNS are correct

    Note:  Access the printer EWS by typing the printer IP address into the URL field of your browser (e.g., Internet Explorer, Mozilla Firefox, Google Chrome, Safari). For example, enter http://MFP_IP_Address, where MFP_IP_Address is the IP address of the printer.

  6. Synchronize the printer and server (collector or analyst) date and time.


Check the Pharos Blueprint event browser on the collector or analyst server for error logs. To do so, search the IP address or the printer's terminal name.


Ping the printer from the collector or analyst server that the printer is pointing to.

Note:  Ping should also work if hostname is used in the configuration.


Check the printer and terminal settings on the analyst server.

  1. Go to the printer’s EWS > Settings > Network/Ports > TCP/IP, and take note of the printer's hostname.

  2. Open the Pharos Systems Blueprint Administrator, go to Device Management > Devices, and then verify whether the printer has a red flag next to its name.

  3. Highlight the printer and the following should be set:

    • Under the Device Details tab:
      • It should have a Device and Manufacturer/Model name (can be anything).
      • Model Confidence should be Verified.
      • MFD Functions depends on the printer model.
    • Under the Connectionstab:
      • Make sure that the correct IP address or hostname of the printer shows.
  4. Open the Pharos Systems Blueprint Administrator, go to Device Management > Terminals, and then highlight the terminal and the following should be set:

    • Under the Settings tab:
      • For Terminal, make sure this is the printer's hostname.
      • For Device LPR Queue, enter the LPR port used by the original print queue (can be IP address or hostname).
      • For Script, select the correct authentication script (e.g., BP_RegisterMe_42).
      • For Terminal Features, place a check on both Copy Tracking and Secure Release Here, and then click Apply.
  5. Open the Pharos Systems Blueprint Administrator, go to Secure Release Here > Print Groups, choose the print group, click the Managed Devices tab, and then verify whether the printer is added to the correct print group.

Note:  If not, click Add Managed Device button to add the printer.


Replace the IP address of the non-functional printer with a functional printer’s address to isolate the issue. To do so:

a. Go to the non-functional printer’s EWS > Settings > Network/Ports > TCP/IP, click on Set static IP address, and then set the IP address.


  • Use a printer of the same model on the same subnet to avoid network and compatibility issues.
  • Make sure to change the functional printer's IP address to avoid IP address conflict.
  • Use the non-functional IP address on the functional printer to further isolate whether the specific IP address is causing the problem.

Note:  The changes should take effect immediately; but should there be an issue, you may restart the printers.

b. After IP address modifications, open the Pharos Systems Blueprint Administrator, go to Device Management > Devices, highlight the printer, and then update the IP address under the Connections tab.

Note:  Perform this for both the non-functional and functional printers. Restart the Pharos ComTaskMaster service on the Pharos Blueprint analyst server and eDAS app via the printer’s EWS > Settings > Embedded Solutions or Device SolutionsSolutions (eSF) or AppsApps Management.


Rebuild the terminal.

Note:  See How to rebuild the terminal in pharos blueprint to view steps to rebuild the terminal.


Export the security and printer settings (.ucf files) from a functional printer of the same model and import these settings to the non-functional printer. To do so, go to the printer’s EWS Settings >Import/Export >Export Settings File and Export Security Setups File, and then Import Settings File and Import Security Setups File. Click here to view image.


Reinstall the Pharos Blueprint apps on the printer, especially when you encounter an HTTP 500 error during eDAS testing.

Note:  See How to reinstall Pharos Blueprint Apps to view steps to reinstall the apps.

Note:  Contact your next level of support or Lexmark Technical Support for assistance on checking pertinent log information.

Wrong Terminal type is used for a specific printer

This can verified when the Lexmark iMFP Configurationtab is missing in the Pharos Systems Blueprint Administrator > Device Management > Terminals.

The missing tab means a problem exists either in the .bat file configuration (InstallLexmarkTerminalType.bat) or the terminal type installed is incorrect.

Terminal types

Printer ModelTerminal Version

X64x, X772e, X782e, X85x, X94x


T656, W850, X86x, X73x, X65x, X46x


C748, C792, C925, C950, X548, 6500, X74x, X792, X925, X95x, MS610, MS810de, MS812de, MS911,CS510, CX410, CX510, MX410, MX51x, MX61x, MX6500, MX71x, MX81x, MX91x


To resolve this issue on the printers with terminal version 3.xx, upgrade and rebuild the terminal type from 3.0.0 to 3.0.10. To do so:



Copy the contents of the terminal installer folder to the \bin directory of the Pharos Blueprint 4.2 or 5.0analyst server.


In the command prompt, navigate to C:\Program Files (x86)\PharosSystems\Blueprint\bin.


Run the InstallLexmarkTerminalType.bat file from the bin directory.


After upgrading the terminal, see How to rebuild the terminal in pharos blueprint to view steps to rebuild the terminal.


Was this article helpful?