Configure HTTP access to tabular on IIS

Last week, the network manager said that a colleague in a department used his own computer to work in the office. The operating system is the genuine Win8 family edition and cannot join the company domain to find out how to access the data warehouse.

I used to think that only users in the domain can use the data warehouse, and there is no way to solve the problem. Simply shirking it will not only affect the impressions of other departments, but also reduce work efficiency, so I started to ask for help. Dear Google, can I worship goagent here? What will it not be?

Okay. Let's talk less and continue with the question.

I started to perform silly Chinese search, and Ms had a solution.

According to Ms official instructions, that is, the link at the end of the article. After the operation, the connection fails... (Well, a smart person is often prone to 2 attacks. For example, I have not started running a website here ...)

In addition to the official documents, the Chinese record only has several identical blogs. Most of them are reposted, which is basically the same as the official documents.

Without discovering that the website was not enabled, I suddenly started searching in English. So I opened a YouTube video and continued to worship goagent.

Based on the re-detection and configuration process of the video, I finally found that my website was not opened. I really wanted to find my own website!

Now http: // Bi/OLAP/msmdpump. dll can be connected, but there is no data warehouse to be accessed, the problem should be that the permission is above.

Since anonymous access is used, I tried to add various accounts on the tabular service. After adding everyone, I can finally access DW. Is that a success? No, so that anyone can access it.

Therefore, the permission mode is modified. In website-authentication, anonymous access is disabled and Windows authentication is enabled.

After testing, you can directly access DW when logging on to the domain account. However, you cannot connect when you manually enter the domain account password. Therefore, you can continue to enable the basic identity authentication function, try entering the domain account password again!

 

The official documentation of MS has a text description, which is indeed very detailed. I will not repeat it here. In fact, the configuration is really simple, but it is too detailed, sometimes it is easy to give people a complicated feeling.

 

In addition, if you are prompted that you cannot access the Bi (Bi is the DW server's host name) service, it may be a DNS resolution problem, you can replace it with the server IP address.

 

The environment is as follows:

Server: Windows2003 Server

Database: sqlserver 2012

Official documentation: http://msdn.microsoft.com/zh-cn/library/gg492140 (V = SQL .110). aspx

YouTube video: https://www.youtube.com/watch? V = tjggyg1ddhy