This topic highlights possible problems that you may encounter with Windows Legacy Collection (LWC) and suggested solutions to these problems.
Protocol Restart Problems
If you see any of the following messages in the MessageBroker.log, you may have issues.
|Log Messages||Any message that contains "rabbitmq"|
|Possible Cause||RabbitMQ service may not be running.|
Port 5671 may not be opened.
|Solutions||Make sure that the RabbitMQ service is running.|
Make sure that port 5671 is open.
|Log Messages||Error: Adding logcollector user account.|
Error: Adding administrator tag to logcollector account.
Error: Adding Adding logcollection vhost.
Error: Setting permissions to logcollector account in all vhosts.
|Possible Cause||rabbitmq-server was not running when installer tried to create users and vhosts.|
Make sure that the RabbitMQ service is running and run below commands manually.
rabbitmqctl -q add_user logcollector netwitness
Windows Legacy Federation Script Issues
If you see any of the following messages in the federation script log, you may have issues.