Client Connection Problems¶
Fix problems connecting the MetaMiner Client (MMC) to the MetaMiner Server (MMS), and signing in to Power BI from the MMC.
The MMC talks to the MMS over one TCP port (default 49714). The MMS, not the MMC, calls the Microsoft APIs for collection. Some MMC features (workspace access changes, restore, export to a Fabric lakehouse) also use your own Microsoft sign-in. Start with the symptom that matches the message you see.
Image of the MMC Connection Manager with the Connection Failed dialog open
../../images/help/mmc-connection-failed.png
MetaMiner Client to MetaMiner Server¶
Connection Failed: the connection to MetaMiner Server has failed
Symptom. The Connection Manager shows Connection Failed with the text "Connection to MetaMiner Server using host ... and port ... has failed."
Cause. The MMC cannot open a TCP connection to the MMS. Common reasons: wrong host name or port, the MetaMiner service is stopped, a firewall or VPN blocks the port, or the licence has expired so the service did not start.
Fix.
- On the server, open the MetaMiner Administrator (MMA) and check that the service is running. See Start and Stop the Server.
- Confirm the port in the MMA under Preferences > Settings > General > Server Port (default
49714). - From the client machine, test the port:
- If the test fails, open the port in the Windows firewall on the server and in any network firewall between client and server. See Ports and Endpoints.
What to send support. The exact message, the host and port you entered, the Test-NetConnection result, and the client logs (File > Open MetaMiner Log Folder in the MMC).
Connection Timeout
Symptom. The Connection Manager shows Connection Timeout for the server.
Cause. Packets to the MMS port are dropped instead of refused: a firewall, proxy or VPN silently blocks the port, or the host name resolves to an address that does not answer.
Fix. Resolve the host name from the client (nslookup <mms-host>) and confirm it returns the server's address. Then run the Test-NetConnection check above and ask your network team to allow the MMS port.
What to send support. nslookup and Test-NetConnection output, and the client logs.
This client software version and the MetaMiner Server version are not compatible
Symptom. After connecting, the MMC reports "This client software version ... and ... MetaMiner Server version ... are not compatible."
Cause. The MMC and the MMS must come from the same MetaMiner release.
Fix. Install the MetaMiner Client from the same release as the server, then start the MMC again. The server version is in the MMA under Help > About. See Install the Client.
What to send support. Both version numbers shown in the message.
The server is still starting up and cannot accept sign-ins yet
Symptom. The MMC reports "The server ... is still starting up and cannot accept sign-ins yet."
Cause. The MMS is listening but has not finished starting. Startup includes starting the MetaMiner Database (MMDB) and applying database updates, which can take several minutes after an upgrade.
Fix. Wait and connect again. If the message stays for more than a few minutes, check slc.log and server.log in server\logs\.
What to send support. slc.log and server.log.
Login and password required to connect to this MetaMiner Server
Symptom. The MMC asks for a login and password, or refuses the connection with this message.
Cause. User-based security is on, so every MMC user signs in with a MetaMiner account.
Fix. Enter your MetaMiner user name and password. An administrator creates accounts in the MMA. See User-Based Security.
What to send support. Only if a valid account is refused: the user name (not the password) and the time of the attempt.
A certificate prompt appears when connecting (SSL)
Symptom. The MMC shows "This CA Root certificate is not trusted because it is not in the Trusted Root Certification Authorities store. Do you want to continue?"
Cause. SSL is on for the MMS port and the certificate chain is not trusted by the Java runtime the MMC uses. The MMC does not read the Windows certificate store.
Fix. Do not accept the prompt as a permanent fix. Add the issuing CA certificate to the MMC's trust store, then reconnect. See Client to Server SSL and Trusted Certificates.
What to send support. The certificate chain (issuer and subject of each certificate) and the client logs.
Connection to the MetaMiner Server has been lost
Symptom. While you work, the MMC shows "Connection to the MetaMiner Server has been lost!" and returns to the Connection Manager.
Cause. The MMS restarted or stopped, or the network dropped the connection. The MMC expects a regular keep-alive from the server; network devices that close idle connections can interrupt it.
Fix. Reconnect. If the service restarted, slc.log shows the stop and start. If drops repeat without a restart, ask your network team whether a firewall, proxy or VPN closes long-lived connections to the MMS port.
What to send support. The time of each drop, client logs, and slc.log plus server.log.
The Power BI environment is missing in the Connection Manager or the MMC
Cause. The environment is disabled in the MMA, has not validated, or user-based security is on and your role on that environment is No Access.
Fix. Ask an administrator to enable the environment and assign you a role. See Edit, Disable or Remove and Users and Roles.
Power BI sign-in from the MetaMiner Client¶
Some MMC features act in Power BI as you, not as MetaMiner's service principal: managing workspace access, restoring content, the tenant admin view and exporting to a Fabric lakehouse. They use the Power BI sign-in dialog ("Sign in to "environment" with Microsoft."). See Delegated User Sign-In.
Image of the MMC Power BI sign-in dialog with Sign in with Microsoft, and after sign-in 'Signed in as user@contoso.com' with Switch account and Sign out
../../images/help/mmc-pbi-sign-in.png
"Sign-in failed." in the Power BI sign-in dialog
Cause. Microsoft refused the sign-in, the browser window was closed, or the app registration is not set up for delegated sign-in (redirect URI or delegated permissions missing).
Fix. Sign in again with Sign in with Microsoft, or Use another account.... If it keeps failing, ask the administrator to check the delegated sign-in setup of the app registration.
"This feature requires PBI SSO Login. Enable via MetaMiner Admin > Security > Enable Power BI SSO"
Cause. Managing workspace access needs Power BI single sign-on, which is off.
Fix. An administrator enables it in the MMA (Security > Enable Power BI SSO). See User-Based Security.
"Export to Fabric Lakehouse requires Power BI interactive sign-in - please ask your MetaMiner administrator to enable it."
Cause. Interactive Power BI sign-in is turned off on the server (pbi.interactive.login.enabled=false in server\MetaMinerServer.properties).
Fix. Remove the setting (the default is on) and restart the MetaMiner Server.
Tenant Admin View shows "No Access" for workspaces
Cause. The MMC shows: 'Tenant Admin View: "No Access" below means the Power BI admin API denied your signed-in account - it is likely not a Fabric administrator.'
Fix. Sign in with an account that holds the Fabric administrator role. See Tenant Admin View.