Submit a ticketCall us

Webinar: Web Help Desk for HR, Facilities and Accounting Departments
This webinar will focus on use cases for HR, Facilities and Accounting.

Having a unified ticketing and asset management system for all the departments in your company can provide end-users with a seamless experience and make things easier for your IT team. Yet, with different business tasks and objectives, many departments don’t fully understand the capabilities of Web Help Desk and how the software can be customized for effective use in their departments.
Register Now.

Home > Success Center > Virtualization Manager (VMAN) > Possible errors during a Virtualization Manager and Orion integration

Possible errors during a Virtualization Manager and Orion integration

During the integration process of Virtualization Manager (VMAN) and Orion, both applications keep running and changes may occur in both environments. For example, nodes or data sources can be added or deleted. In these cases, it may happen that the data collected at the beginning of the synchronization process are no longer valid. The majority of these issues can be solved by resetting the integration process, and running the Synchronization wizard again.

The following sections list the errors that may occur during the integration process of VMAN and Orion, and provide explanations and possible solutions.

Issues with credentials

Error message

Explanation / Solution

Could not use credentials from Virtualization Manager/Orion. Incorrect integration data in Virtualization Manager/Orion. Reset Virtualization Manager integration and go through the Synchronization Wizard again.

If there is a change in VMAN or in Orion during the integration process, the integration data become invalid. Reset the integration process to load valid data. If the issue persists, check the error log for more information.

Could not use credentials from Virtualization Manager/Orion. Reset Virtualization Manager integration and go through the Synchronization Wizard again. If this error persists, check the error log for more information.

There is inconsistency in the database. Data related to processed nodes are missing. Use the Database Maintenance tool to clean up the database, and then reset the integration process.

Could not use credentials from Virtualization Manager/Orion. Check the error log for more information.

This message indicates a general error. Check the error log for more details.

Issues with importing nodes to Orion

Error message

Explanation / Solution

Could not import node to Orion. A node with the same name or IP address exists in the Orion database. Could not connect to this host by the given IP address.

A node with the same IP address exists in the Orion database, but it was not properly mapped to the existing node in VMAN. The IP address of the node was probed unsuccessfully. Check the node, and then start the polling manually. After the polling is finished, run the Synchronization wizard again.

Could not import node to Orion. Check the error log for more information.

This message indicates a general error. Check the error log for more details.

Issues with changing the Polling source

Error message

Explanation / Solution

Could not change Polling source to Virtualization Manager/Orion. Incorrect integration data in Virtualization Manager. Reset Virtualization Manager integration and go through the Synchronization Wizard again.

If there is a change in VMAN or in Orion during the integration process, the integration data become invalid. Reset the integration process to load valid data. If the issue persists, check the error log for more information.

Could not change Polling source to Virtualization Manager/Orion. Check the error log for more information.

This message indicates a general error. Check the error log for more details.

Reconfiguring node to poll from parent Virtual Center failed. Check the error log for more information.

If there is a change in VMAN or in Orion during the integration process, the integration data become invalid. Reset the integration process to load valid data. If the issue persists, check the error log for more information.

Issues with sending data to Virtualization Manager

Error message

Explanation / Solution

Sending integration data to Virtualization Manager failed. Reset Virtualization Manager integration and go through the Synchronization Wizard again.

The integration data collected in Orion during the synchronization process were sent to VMAN, but the communication between Orion and Virtualization Manager failed. Reset the integration process to load valid data. If the issue persists, check the error log for more information.

Issues with the Probe job

Error message

Explanation / Solution

Could not connect to node [NAME] ([IP address]) using credential '[Credential name]'.

This is an informational message that indicates that the connection to the IP address is successful, but the credential is invalid. The node will be added to Orion, but you should verify the node and its credential.

Could not connect to node [NAME] ([IP_ADDRESS]). + ERROR MESSAGE

The connection to the IP address is unsuccessful. The error message returned by the Probe job provides more details.

Last modified
06:28, 27 Sep 2017

Tags

Classifications

Public