Try one or more of the following:
Check the proxy, firewall, and other network settings across the LDD system.
The Log On properties of the following must be set to the domain account that has access to the Microsoft SQL Server database:
Lexmark Apache Agent service
Lexmark Solutions Application Server
Try one or more of the following:
For more information on obtaining licenses, see Obtaining licenses. For more information on adding licenses after installation, see Adding licenses to an existing server.
Check the proxy, firewall, and other network settings across the LDD system.
Multiple non-communicating servers may affect system performance. If you do not expect a non-communicating server to reestablish communication quickly, then remove it.
On each computer where a server is installed, launch LMC by using the URL. is the IP address of the computer where the server is installed.
Remove the server that is not communicating. For more information, see Viewing and changing server status.
Launch LMC by using the URL, where is the IP address of the computer where the load balancer is installed.
On each computer where a server is installed, launch LMC by using the URL. is the IP address of the computer where the server is installed.
Click the System tab.
From the System section, select System Status.
From the main section, uninstall the server that is not communicating.
Reinstall the server.
Launch LMC by using the URL, where is the IP address of the computer where the load balancer is installed.
If the load balancer is installed on the same computer as the database, then use the FQDN of the computer. If the IP address or FQDN is incorrect, then uninstall and reinstall the load balancer and all the servers.
Try one or more of the following:
If the server is installed on the same computer as the database and the load balancer, then use the FQDN of the computer. If the IP address or FQDN is incorrect, then uninstall and reinstall the applicable servers.
If the load balancer is installed on the same computer as the database, then use the FQDN of the computer. If the IP address or FQDN is incorrect, then uninstall and reinstall the load balancer and all the servers.
Try one or more of the following:
From the command prompt shell, type the following:
Where:
The argument is the node that the script must connect to. This argument can be the address of the remote node.
The argument is the cluster virtual IP address.
The argument is the Windows service that must be monitored.
The argument is the file that must be called from the URL specified in the script.
Using Windows Task Scheduler, run the custom script regularly on all cluster nodes that run the LDD load balancer component.
From Task Scheduler, click Create Basic Task.
Configure the settings.
Click Actions > New.
In the Action menu, select Start a program.
In the "Program/script" field, type .
In the "Add arguments" field, enter the same argument from the command prompt shell. The following is a sample argument:
In the "Start in" field, type .
Click OK.
Try one or more of the following:
It may take several minutes to start all services when the system is first booted. If the system is recently booted, or the load balancer is overloaded, then wait a few minutes, and then try again.
For more information, see Viewing and changing server status.
Check the proxy, firewall, and other network settings across the LDD system.
From LMC, click the Solutions tab.
Select the solution that you are trying to access from the printer.
If the solution does not appear, then install the solution. For more information, see Uploading solutions to the LDD system.
From the Tasks section, select Summary.
From the Summary section, in the Device Groups column, check that the device group that contains the printer appears.
If the device group does not appear, then make sure that the printer is added to the device group.
Check that the solution has been deployed to the device group. For more information, see Deploying solutions to a device group.
Perform a policy update. For more information, see Updating policies for device groups.
For more information, see Viewing the Embedded Solutions diagnostic log.
From the Embedded Web Server, do one of the following:
For e-Task 5 printers, click Apps, and then click AP Bundle.
For e-Task 4 printers, click Settings > Apps > Apps Management.
For e-Task 3 printers, click Settings > Device Solutions > Solutions (eSF).
For e-Task 2+, e-Task 2, or e-Task printers, click Settings > Embedded Solutions.
Make sure that the first two segments of the version number for AP Bundle match the version number of the LDD system. For version 4.6, the version of the AP Bundle must be 4.6.x.
For more information, see Updating policies for device groups.
From the Embedded Web Server, do one of the following:
For e-Task 5 printers, click Apps, and then click AP Bundle.
For e-Task 4 printers, click Settings > Apps > Apps Management.
For e-Task 3 printers, click Settings > Device Solutions > Solutions (eSF).
For e-Task 2+, e-Task 2, or e-Task printers, click Settings > Embedded Solutions.
Browse to the ap.fls file in the \Lexmark\Solutions\apps\wf-ldss\firmware\ folder where an LDD server is installed.
Click Install or Start Install.
Sometimes, Advanced Prompt bundle communication fails because connection to the LDD load balancer is set to secure. (first HTTPS call between the device and the LDD load balancer).
From the Embedded Web Server, click Apps > Advanced Prompt > Configure.
Clear Secure connection to load balancer.
Try one or more of the following:
If the time is not synchronized, then do the following:
Uninstall all components.
Using an NTP server, synchronize the time on all computers that are used in the LDD system.
Reinstall all components.
Try one or more of the following:
To log Kerberos debug messages from the Java Virtual Machine on each server, add the line to the HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Procrun 2.0\Tomcat7\Parameters\Java\Options Windows registry path.
If you are using a 64-bit Windows operating system such as Windows Server 2008 R2 x64, then HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Apache Software Foundation\Procrun 2.0\Tomcat7\Parameters\Java\Options is the Windows registry path.
Debug messages are logged in the tomcat7-stdout.yyyy-mm-dd.log file in the \Lexmark\Solutions\tomcat\logs\ folder where the LDD server is installed.
Try one or more of the following:
From the printer home screen, navigate to another screen and then return to the home screen.
For more information on customizing the home screen for a device group, see Customizing the home screen for a device group. For more information on customizing the home screen on specific devices, see Customizing the home screen on specific devices.
For more information, see Deploying solutions to a device group.
For more information, see Updating policies for device groups.
From the Embedded Web Server, do either of the following:
For e-Task 5 printers, click Settings > Device > Visible Home Screen Icons.
For e-Task 4, e-Task 3, or e-Task 2+ printers, click Settings > General Settings > Home screen customization.
Select the item that corresponds to the missing icon.
Click Save or Submit.
From the Embedded Web Server, configure the printer access controls.
For e-Task 5 printers, do the following:
Click Settings > Security > Login Methods.
From the Public section, click Manage Permissions.
Expand Function Access and Device Management, and then select Create Profiles and Remote Management, respectively.
For e-Task 4, e-Task 3, e-Task 2+, e-Task 2, or e-Task printers, do the following:
Click Settings > Security > Security Setup > Access Controls.
Expand Management and Function Access, and then set Remote Management and Create Profiles or Use Profiles to No Security, respectively.
Click Submit.
From LMC, perform a policy update. For more information, see Updating policies for device groups.
For more information, contact your Lexmark representative.
Try one or more of the following:
For more information, see Configuring printer security.
From the Embedded Web Server, configure the printer access controls.
For e-Task 5 printers, do the following:
Click Settings > Security > Login Methods.
From the Public section, click Manage Permissions.
Expand Function Access and Device Management, and then select Create Profiles and Remote Management, respectively.
For e-Task 4, e-Task 3, e-Task 2+, e-Task 2, or e-Task printers, do the following:
Click Settings > Security > Security Setup > Access Controls.
Expand Management and Function Access, and then set Remote Management and Create Profiles or Use Profiles to No Security, respectively.
Click Submit.
From LMC, perform a policy update. For more information, see Updating policies for device groups.
Try one or more of the following:
From the Embedded Web Server, do one of the following:
For e-Task 5 printers, click Apps, and then click AP Bundle.
For e-Task 4 printers, click Settings > Apps > Apps Management.
For e-Task 3 printers, click Settings > Device Solutions > Solutions (eSF).
For e-Task 2+, e-Task 2, or e-Task printers, click Settings > Embedded Solutions.
Check if the AP Bundle is enabled.
For more information, see Configuring printer security.
From the Embedded Web Server, configure the printer access controls.
For e-Task 5 printers, do the following:
Click Settings > Security > Login Methods.
From the Public section, click Manage Permissions.
Expand Function Access and Device Management, and then select Create Profiles and Remote Management, respectively.
For e-Task 4, e-Task 3, e-Task 2+, e-Task 2, or e-Task printers, do the following:
Click Settings > Security > Security Setup > Access Controls.
Expand Management and Function Access, and then set Remote Management and Create Profiles or Use Profiles to No Security, respectively.
Click Submit.
From LMC, perform a policy update. For more information, see Updating policies for device groups.
For more information, see Updating policies for device groups.
From the Embedded Web Server, do one of the following:
For e-Task 5 printers, click Apps, and then click AP Bundle.
For e-Task 4 printers, click Settings > Apps > Apps Management.
For e-Task 3 printers, click Settings > Device Solutions > Solutions (eSF).
For e-Task 2+, e-Task 2, or e-Task printers, click Settings > Embedded Solutions.
Browse to the ap.fls file in the \Lexmark\Solutions\apps\wf-ldss\firmware\ folder where an LDD server is installed.
Click Install or Start Install.
Try one or more of the following:
For more information, see the documentation that came with the printer.
Try one or more of the following:
From the Embedded Web Server, click Settings > Fax > Analog Fax Setup > Fax Receive Settings > Admin Controls.