Dialogue Cloud

On Premises

Power BI template Operation Basics

Introduction

In this document the basic elements of managing the AnywhereNow software are described.

Trouble shooting

When connecting with Power BI to SQL Server, you could get an error message. The best way to resolve this is by searching for the error message online. Below a list of possible messages and steps you can take:

Message

Possible Solutions

"An error happened while reading data from the provider: 'Could not load file or assembly 'System.EnterpriseServices, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. Either a required impersonation level was not provided, or the provided impersonation level is invalid. (Exception from HRESULT: 0x80070542)'"
  1. Please try starting Power BI as Administrator.
  2. Please try reinstalling .Net Framework

Microsoft SQL: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error 0 - The wait operation timed out.)
  1. Please make sure the Server \ Instance are correctly entered. (use the FQDN FDQN stands for Fully Qualified Domain Name and specifies the exact location in the tree hierarchy of the Domain Name System (DNS). An example for [hostname].[domain].[top level domain] is [www].[microsoft].[com])
  2. Please make sure your database engine is configured to accept remote connections.
  3. Please make sure that you create an exception on the firewall for the SQL Server instance and port you are using.
  4. Please check if your SQL server services is up and running properly.
  5. Please make sure that you enable TCP/IP in SQL Server Configuration

Microsoft SQL: A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)"
  1. Please check that if you have added the TCP port and UDP port(1434) in the inbound rule of the Windows Firewall, and you can verify TCP port in SQL Server Configuration Manager.