Troubleshooting FlexNet Agents
Check both the FlexNet Manager for Engineering Applications and FlexNet Agent logs when there are problems with the FlexNet Agent.
A FlexNet Agent may not start if:
| • | More than one license file managed by the agent contains a SERVER line with the same port number. |
| • | The options file path specified in a license file is incorrect. License files must contain fully qualified paths to options files and vendor daemon executables. |
| • | A license file location specified for one of the FlexNet Agent’s license servers is incorrect. |
If FlexNet Manager for Engineering Applications Admin and a FlexNet Agent are running, but cannot contact each other, there may be connectivity problems.
A FlexNet Agent may not report the correct license server status, or not start and stop license servers if:
| • | The FlexNet Agent is down. |
| • | More than one lmgrd managed by the FlexNet Agent is configured to run on an unspecified port in the default port range. |
| • | The FlexNet Agent attempts to register a license server whose license file has an invalid number of SERVER lines. The registration of the license server will fail in FlexNet Manager for Engineering Applications. Any subsequent registration requests for vendor daemons on this (unregistered) license server will also fail in FlexNet Manager for Engineering Applications and an ERROR will be logged in the FlexNet Agent log. However, FlexNet Agent registration will continue. |
| • | A license server name in a FlexNet Agent’s config.xml file is a duplicate of a license server name already registered by another FlexNet Agent with FlexNet Manager for Engineering Applications. This license server will not be registered (because doing so would result in a duplicate license server name in FlexNet Manager for Engineering Applications). None of the vendor daemons under this duplicate license server will be registered either. An ERROR log message is written to both the FlexNet Manager for Engineering Applications Admin’s log and the FlexNet Agent’s log. Registration of other (non-duplicate) license servers on the agent will proceed. |
If an existing FlexNet Agent is shut down and its host and port reused by another FlexNet Agent, the first agent will appear with a status of down in the FlexNet Manager for Engineering Applications user interface until it is removed using the Remove button on the Agent Summary page (in the FlexNet Manager for Engineering Applications user interface). If the first agent is started, it will have a port conflict with the second FlexNet Agent. If the second agent is stopped before the first agent is re-started, the second agent will appear with a status of down in the FlexNet Manager for Engineering Applications user interface until it is removed.