I attempted to introduce the Power BI Analysis Services Connector, and ran into a couple of issues (and discovered a few arrangements). I thought it'd be great to share them, on the off chance that anybody runs into similar issues. So here's my account of introducing Power BI Analysis Services connector - meant a rundown of discoveries and arrangements/workarounds. Peruse on!
As expressed over, this is somewhat the 'establishment story' with Analysis Services Connector (earlier dispatched as Data Management Gateway) at my present manager. Here are the issues we experienced:
Administration account is nearby as a matter of course (no real way to change this during arrangement)
The ASC (Analysis Services Connector) administration is as yet called DMG (Data Management Gateway)
Intermediary usefulness is broken (at any rate during arrangement/setup)
Arrangement wizard crashes subsequent to composing in Federated AD login
Not all issues are major (truth be told, IMHO just one of them is: the absence of careful intermediary support), yet all issues should be handled before the Analysis Services Connector worked here. Here's our story:
**Administration account is neighborhood (minor) **
Subsequent to having introduced the ASC, the help is arranged consequently utilizing a nearby assistance account1. Rather than SQL Server, during arrangement you don't get the chance to change the assistance account.
At our organization, non-space accounts don't have network access. So albeit the arrangement offers to design the entryway when the arrangement is done, truth be told this is quite futile in our circumstance: we first need to change the help account prior to having the option to arrange the passage. With SQL Server you'd do this utilizing the SQL Server Configuration Manager, with the ASC/DMG administration this is beyond the realm of imagination: you need to change this through the Windows Services exchange (services.msc) - which raises our next part with MSBI Course to understand it
**The ASC administration is as yet called DMG (minor)
**
When beginning the Services discourse, abruptly it appeared I neglected to uninstall the old DMG. Abnormal, to the furthest extent that I could recollect the ASC wouldn't introduce as long as the DMG was as yet introduced. However, no - the genuine case is that albeit the sent item is presently called ASC (and will be called Enterprise or Personal Gateway), the assistance running in the background actually is called 'Information Management Gateway':
**AS Displayed as DMG **
So to change the record running the ASC2, change the client running the DMG administration. Make sure to restart the assistance in the wake of changing the record!
Intermediary not working as expected for the arrangement wizard (major)
In any case, with a substantial area account set up, the wizard continued showing the following window:
AS Connector No Internet Connection
Subsequent to examining our firewall logs, we could see the design wizard disregarded the intermediary settings we set up in Windows. We attempted to set the intermediary on a few spots:
Signed in as the Power BI help account, we changed Windows' intermediary settings
We added the accompanying code to all current .config records in the ASC folders3:
<system.net>
</system.net>
This without much of any result - ASC continues attempting (in any event during the 'login' step of the config wizard) to explore to the favored DNS Server, without reaching the intermediary first. We turned to changing the favored DNS worker to the intermediary worker's address4, trailed by a 'ipconfig/flushdns'.
**Arrangement wizard crashes subsequent to composing Federated AD account (minor)
**
The following issue that seemed was a mistake message subsequent to composing in my organization Power BI record (yet prior to composing in my secret word) - it resembled this (interpretations added by me):
**AS connector mistake signing in
**
After some examination I read this post in the Power BI gatherings, which depicted an issue that looked a lot of like our own. In short: the reason for this mistake is the utilization of Federated AD with Azure, with just Windows validation upheld as confirmation technique. It turns out the arrangement wizard doesn't uphold this (yet?), so we needed to change our validation strategy and empower the Forms Authentication as well:
On the ADFS worker, open the ADFS snap-in, click Authentication Policies from the left tree route.
In the Authentication Policies area on the correct board, pick Edit Global Primary Authentication.
Under the Intranet area, check the Forms Authentication choice.
Save the changes.
ADFS Add Windows Authentication
After this, login was not an issue any longer.
Break while enlisting entryway
In conclusion (when the wizard's practically completed) the accompanying mistake message showed up:
**AS Timeout **
In online documentation of the Personal Gateway something is referenced about machines with just 1 processor - however our VM has two centers.
The answer for us was to change 'diahost.exe.config' such that the intermediary was implemented for this cycle (as well). To do that, change the accompanying line in diahost.exe.config5
<system.net>
into:
<system.net>
</system.net>
Remember to restart the DMG administration after this change!
Victory!
After these means, the wizard proceeded with the typical way.
**AS Finished **
Two Last Things to remember
As of now you don't see the ASC inside the 'Door Management' segment in Power BI. This is to some degree confounding, however I think you'll see just the Personal and Enterprise Gateways here - for my situation, I actually see the accompanying screen in spite of the fact that I have effectively three Analysis Services Connectors designed:
**No EG **
You can't 'just' associate with your SSAS worker from inside Power BI through the ASC. You can interface with your SSAS models twoly:
Make a disconnected report (for instance in the Power BI Desktop) and interface that to your neighborhood SSAS worker. When you transfer that report to Power BI, you can stay chipping away at the nearby SSAS example inside the online Power BI climate.
Fitting into the SSAS model straightforwardly by means of the online Power BI climate. Pick Get Data > Databases > SSAS (Thanks @DaveRuijter for bringing up!)
Conclusion
We needed to sort a few things out about the ASC. Fortunately we oversaw - with the assistance of the local area, docs and regular information about systems administration - to move them. Anticipating when everything simply works - up to that point, we'll blog about our answers
