Analyzing Application Log
The main purpose of the Application Log view is to help you understand if the enumeration, state checking and other service operations execution has succeeded and troubleshoot problems if any have occurred. Each entry in the application log has a severity icon, a title, and a description, and possibly a hint on solving the problem, if any. From the title, you can understand which operation has been performed and which resource has been operated; the description provides you with the result message, a hint is used to provide you with an advice on solving the problem, if any; and the severity icon can be used to quickly understand if the operation has fully succeeded.
For example, let us take a closer look at the following result set in the application log Pic 1.
The picture above displays the set of results we received after performing state check on a number of selected Machines. The results of checking the Machines are grouped by the Group the Machines are located in. In each group node, we can see how many Machines have been processed successfully, with warnings or not processed due to errors.
As we can see from the picture, most of the Machines have been processed successfully, but some of them have not. We need to find out what caused the problem and what should be done to avoid it in future. Also, it may be interesting to go through the warnings to see if anything wrong is going on. So, let us take a closer look at each problem.
For WVISTA-X86-SP1 we've got the following error message:
Could not ping the 'WVISTA-X86-SP1.Dreamlight.local (192.168.5.84)' Machine using the following timeout: 1500 ms. Ping reply was not received within the allotted time.
There are a few possible scenarios that may have caused such an error:
- The remote Machine is turned off. Hence that Machine should be turned on to be operated by Remote Installer.
- The remote Machine could not be contacted due to a hardware networking failure. In this case, you need to check the network environment.
- The ping functionality is disabled on the remote Machine. You should enable the Ping functionality on the remote Machine. If this is not applicable, go to the Scan Settings preference page and disable the Ping Machines using the following timeout (ms.) option. Please note that this may significantly decrease the performance.
The EMCO-PDC Machine returned another error:
Could not connect to the 'Emco-PDC.Emco.local (192.168.5.10)' Machine. The connection was performed using the current user credentials.
This means that the currently active user account has no right to access the remote Machine. To solve the problem, you must provide proper credentials to access this Machine in the Credentials view.
Finally, the operation on the LAB-PDC Machine did not succeed returning the following message:
Could not connect to the 'Lab-PDC.Lab.Dev.Emco.local (192.168.5.14)' Machine. The connection was performed using the specified credentials: 'admin@Lab.Dev.Emco.local'.
This means that the credentials provided in the Credentials view do not allow you to perform operations on the remote Machine. You must provide proper credentials to get rid of this error.
After the events have been reviewed and all the problems have been solved, you can run the operation again and ensure that it completes successfully.