HTTP access to SQL Server Analysis Services on IIS 7.0

Introduction

Today, analysis services and IIS are not on the same machine, but on the same LAN.

Problem cause

As I used to remotely access the database, I opened the remote service of sqlserver... and failed to access the database. I always reported an error:

Microsoft. analysisservices. adomdclient. adomdconnectionexception: the connection either timed out or was lost. ---> system. io. ioexception: unable to read data from the transport connection: the remote host forces an existing connection to be closed .. ---> System. net. sockets. socketexception: the remote host forces an existing connection to be closed.

......

Solution
ReferBytes.

The following describes only the solution steps. For more information, seeHttp://technet.microsoft.com/zh-cn/library/gg492140.aspx#bkmk_copy

1. topology (clients, WebServices, and analysis services are distributed on different machines.)

The client accesses the database through WebService to obtain data. The client is deployed on machine 1, WebService is deployed on Machine 2, and analysisservices is deployed on machine 3.

IIS in Machine 2 is used to deploy WebService, and IIS in machine 3 is used to deploy a virtual directory pointing to msmdpump. dll (This is an ISAPI extension that runs on Internet Information Services (IIS ).ProgramSend data to the analysis services server).

2. Copy msmdpump. DLL to a folder on the Web server)

On the IIS server, create the following folder: <drive >:\ Inetpub \ wwwroot \OLAP

1. Copy the ISAPI folder on the analysis services computer to the \ Inetpub \ wwwroot \ OLAP folder you just created.

   The ISAPI folder is located in <drive >:\ Program Files \ Microsoft SQL Server \ <instance> \ OLAP \ bin \ ISAPI. It contains the following files and folders: msmdpump. dll, msmdpump. ini, and resources folder containing language resource files.

2. Make sure that the \ Inetpub \ wwwroot \ OLAP \ ISAPI folder on your Web server contains the following content: msmdpump. dll, msmdpump. ini, and resources folder.

3. Create an application pool and virtual directory in IIS, and add extension plug-ins (machine 3 operations)

Refer to the URL above to set authentication as "Anonymous Authentication"

4. Edit the msmdpump. ini file to set the target server (machine 3)

For more information, see the preceding URL. Set severname to localhost, because the topology above deploys the virtual directory and the analysis services server on the same machine.

5. Configure analysisservice)

Add a role to the database: Set the database permission to full control, and specify the user and group for the role in the member identity: iuser.

You can use IIS to access remote analysis services.

6. Deploy WebService on IIS (Machine 2 Operations)

Refer to the URL above to set authentication as "Anonymous Authentication"

7. How to access

1. If Microsoft SQL Sever management is used, the server name is http: // three machines or IP/OLAP/msmdpump. dll.

2. If you connect to WebService, connectstring = "Data Source = http ://Three machines or IP addresses/OLAP/msmdpump. dll; Catalog = database name ;";

Please submit the above shortcomings. Thank you!