Connection Problems¶
Fix problems connecting the MetaMiner Client (MMC) to the MetaMiner Server (MMS), and MetaMiner to SAP BusinessObjects.
The MMC talks to the MMS over one TCP port (default 49714). The MMS talks to each BusinessObjects CMS through the
BusinessObjects SDK and the Web Intelligence RESTful web service. 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 license 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 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 the client and the server. See Ports.
What to send support. The exact message, the host and port you entered, the result of the
Test-NetConnection command, 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. This usually means 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. This happens after the server was upgraded and the client was not, or the other way round.
Fix. Install the MetaMiner Client from the same release as the server, then start the MMC again. Check the server version in the MMA (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 on its port but has not finished starting its services. 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 persists for more than a few minutes, follow Startup and Upgrade Problems.
What to send support. slc.log and server.log from server\logs\.
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 turned on in the MMA, 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 turned on for the MMS port and the certificate chain is not trusted by the Java runtime that the MMC uses. The MMC does not read the Windows certificate store; it uses the trust store of its own Java runtime.
Fix. Do not accept the prompt as a permanent fix. Add the issuing CA certificate to the trust store that the MMC uses, 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 and closes the connection when it stops arriving. Network devices that close idle connections can cause this.
Fix. Reconnect from the Connection Manager. If the service restarted, slc.log on the server shows the stop
and start. If the 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 from the server.
MetaMiner to BusinessObjects¶
Environment validation: Can not resolve host / Host is not found or down
Symptom. When you add or validate a BusinessObjects environment in the MMA, the status shows Can not resolve host, Can not reach host, or "Host ... is not found or down."
Cause. The MetaMiner server cannot resolve or reach the CMS host name you entered.
Fix. Run nslookup <cms-host> and Test-NetConnection <cms-host> -Port 6400 on the MetaMiner server. Use the
CMS name and port exactly as the BusinessObjects cluster advertises them. Open the CMS port and the request ports
of the BusinessObjects servers in the firewall. See Ports.
What to send support. nslookup and Test-NetConnection output and admin.log from server\logs\.
Environment validation: Authentication failed for host
Symptom. The MMA shows "Authentication failed for host ..." or Connection validation failed with a logon error.
Cause. The BusinessObjects account, password or authentication type is wrong, or the account is locked or disabled in the CMC.
Fix. Log on to the CMC or BI launch pad with the same account and authentication type. Correct the credentials in the environment dialog and validate again. See Connection and Logon and Accounts and Permissions.
What to send support. The authentication type, the error text, and admin.log.
Environment validation: Unable to detect the CMS version / no access to Public Folders
Symptom. The MMA shows Unable to detect the CMS version, User has no access rights to the Public Folders root, or "User should belong directly to the Administrators group."
Cause. The account can log on but lacks the rights MetaMiner needs to read the repository.
Fix. Use a dedicated account that is a direct member of the BusinessObjects Administrators group. See Accounts and Permissions.
What to send support. The account's group memberships and admin.log.
Log on to BusinessObjects: BusinessObjects logon failed
Symptom. In the MMC, the Log on to BusinessObjects dialog reports "BusinessObjects logon failed for:" one or more environments.
Cause. The environment requires each MMC user to log on with their own BusinessObjects account, and the logon was refused (wrong password, wrong authentication type, or the account has no access).
Fix. Check the Authentication type in the dialog and try the same logon in BI launch pad. If you cancel the dialog, that environment stays disabled for the current connection. See BusinessObjects User Logon.
What to send support. The environment name, authentication type, the time of the attempt, and client logs.