Select Page

MetaServer > Help > Troubleshoot > No MetaServer found

When opening the Client and when trying to select a MetaServer, I get the following message: No MetaServer found

You open the MetaServer Administration Client or Operator Client and you get the following message:

Or there are no MetaServer services found and you have an empty list and the following message:

This problem can be related to the following things:

Check your network connectivity or contact your IT department. After the network issues are resolved, try to select your MetaServer again.

Close the client and restart MetaServer by going to your desktop, open the MetaServer folder and press the Start or restart MetaServer icon. Restart the client.

If the previous solutions don’t work, it may be related to the firewall settings of the machine running MetaServer.

Below firewall adjustments only need to be applied on the Server not on the computers running the MetaServer Operator or Admin client(s).

Step 1) Go to your control panel -> Windows (Defender) Firewall -> Allow an App or feature through Windows (Defender) Firewall.

The screenshot below already shows the resulting list after allowing the service.

Step 2) Press the Allow another app… button and browse to MetaService.exe. You can normally find it under C:\Program Files (x86)\CaptureBites\Programs\MetaServer.

Step 3) Next you need to define Inbound Rule for Port 8733. Go back to Windows (Defender) Firewall -> Advanced Settings

Step 4) Select Inbound Rules and press New Rule…

Step 5) Go through the New Inbound Rule Wizard and select the following options:

Step 6) Give the inbound Port Rule a meaningful name and press Finish.

The inbound port rule is now defined and enabled.

Step 7) In case your Operator Client needs to connect to an ODBC-connected DB or SQL Server DB during Validation, you also need to add an inbound port rule for that database's port.

If the previous solutions don’t work, or you also experience issues running or installing the MetaServer Operator or Admin Client, it may be related to the Anti-Virus settings of the machine running MetaServer or one of the clients.

For this case, please add the following folders to the Anti-Virus software's exceptions list:

C:\ProgramData\CaptureBites
C:\Program Files (x86)\CaptureBites
C:\CaptureBites\

If the problem persists, please try temporarily disabling the Anti-Virus software and try running / installing the service or client again.

Another reason that the MetaServer service can't be found, is because the MetaServer Admin or Operator Client is running outside the domain where the MetaServer service is running.

The system running the Admin or Operator Client needs to be able to communicate with the system running MetaServer (e.g. through VPN).

You can test this by browsing to the server’s IP address or friendly name with your File Explorer. For example, “\\CAPBITES-VM” or “\\109.188.31.168”. If this is not possible, please contact your IT department to grant you access to that server.

You can find more detailed instructions on how to connect clients to a central MetaServer here:
https://www.capturebites.com/metaserver/help/connect-multiple-clients-to-central-metaserver/#02-02

 

If this still does not solve the issue, please contact us through our online support form.

CaptureBites Newsletter - Subscribe


Please check the box below to agree to the privacy policy and continue *


NOTE: if you're experiencing trouble with submitting this form, please try again using another browser.