Help! I can’t close the Power BI Desktop Splash Screen!



"The target location you specified is not supported by the report server" message when configuring SSRS in SharePoint Integrated mode


 

Client kept getting "The target location you specified is not supported by the report server" message every time they try to run a SQL 2005 report manually deployed to SharePoint document library (MOSS). This same error also showed up when we go to "Set Server Defaults" (in the top section) page in Central Admin .

 

This same report worked fine when a subscription is enabled and the subscription runs in un-attended mode.

 

Within "Manage Integrated settings" page, the authentication mode is set to "trusted account" as Kerberos is not enabled.

 

The cause for this message was because there was another Alternate Access Mapping (AAM) set up for Central Admin.

 

Once the extra AAM was removed, the error disappeared and issue was resolved.

 

Here is the link that helped resolve this issue https://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2991956&SiteID=1

 

Per Shawn Feldman (a colleague of mine), the reason for this is due to Reporting Services in SharePoint Integration mode does not support multiple zones. That's why it errors out when one has a second AAM.


When trying to build an OLAP cube, we kept getting "Your permissions on the server computer do not allow you to administer this analysis server".


 

Technologies involved

Project Server 2007 (SP1, Infrastructure Update)

SQL Server 2005 SP2

 

 

Issue

When trying to build an OLAP cube, we kept getting "Your permissions on the server computer do not allow you to administer this analysis server".

 

In our environment, we wanted to configure Analysis Services to use SQL DB, not Jet database.

 

After ensuring the security permissions and related steps (https://technet.microsoft.com/en-us/library/cc197489.aspx), we still kept getting this issue.

 

Turns out that the error message "Your permissions on the server computer do not allow you to administer this analysis server" is a catch all message and the final resolution turns out to be a poorly documented step.

 

Resolution

It is very important to ensure that  all security settings have been applied as documented within https://technet.microsoft.com/en-us/library/cc197489.aspx (especially verifying that ssp service login can access the Analysis services)

 

If you still keep getting this message, the most likely cause is the missing additional steps listed below.

 

Note: This is just valid for Analysis services repository residing in SQL database (not Jet database)

 

  1. Follow the steps listed below (copied from https://technet.microsoft.com/en-us/library/cc197552.aspx)

Create a shared folder for the repository

You must create a shared folder in SQL Server 2005 Analysis Services where the repository will be located. You also must make the shared folder accessible to accounts that will need to access it.

Create the shared folder

1.    In Windows Explorer, browse to the folder containing the Analysis Services installation. By default, it is located at: C:\Program Files\Microsoft SQL Server\MSSQL.X\OLAP

2.    In this folder, create a new folder and name it DSO9.

Note

If the subfolder MSSQL.2\OLAP does not exist, use the \OLAP folder in one of the MSSQL.X subdirectories.

3.    Right-click the DSO9 folder, and choose Sharing and Security.

4.    On the Sharing and Security page, in the Sharing tab, select Share this folder. In the Share Name box, type MSOLAPRepository$ as the share name for the folder.

5.    In the Security tab, in the Group or user names list, select SQLServer2005MSOLAPUser$SERVERNAME$MSSQLSERVER. Select the Allow check box next to the Full Control item in the Permissions list, and then click OK.

6.    Click Add. On the Select Users, Computers, or Group page add the account running the Project Server Queue service on the Project Server application server. Click OK.

Note

  To verify this account, on the Project Server application server, click the Start menu, click Programs, click Administrative Tools, and then click Services. Double-click Microsoft Office Project Server Queue Service and note the account on the Log On tab.

7.    In the New Folder Properties page, click OK.

 

  1. For MSOLAPRepository$ share, please ensure that SSP service login also has full control over the share
  2. Within In addition to DSO\RemoteRepositoryConnectionString as well as DSO\RepositoryConnectionString (Configure Analysis Services to use a SQL Server repository database Pasted from <https://technet.microsoft.com/en-us/library/cc197552.aspx> ) also fill in values DSO\RemoteLockDirectory (for e.g. set it to "\\AS_Server_Name\MSOLAPRepository$") and DSO\LocksDirectory (for e.g. set it to "C:\Program Files\Microsoft SQL Server\MSSQL.X\OLAP\DSO9)

 

 

Hopefully after performing the above 3 steps, you should be able to build the cube.


Hello world!


Welcome to Developer Network. This is your first post. Edit or delete it, then start blogging!


Calculating the difference between two dates in YEARS, MONTHS, and DAYS in Power BI or Excel


How do I calculate an employee's tenure given their start date?

How can I determine a person's age given their birth date?

In a customer conversation this week, I was asked to help solve this question in Power BI. Interestingly, I was intrigued by this topic almost 5 years ago when I wrote a blog entry to solve this in TSQL, but now it is time to solve it in DAX for use in Excel or Power BI. The challenge with this question is that it sounds so simple, yet turns out to be a bit tricky. There are likely several other creative ways to solve this. If you have found another way, please share it in the comments below.

Let's start with a list of employees and their start dates:

Calculate Date Difference in Power BI

Now create a measure to represent today's date (or whatever date you want to use as the end date for the calculation).

TodaysDate = FORMAT(TODAY(),"mm/dd/yyyy")

I am using YEARFRAC as the basis of the year/month/day calculations. YEARFRAC returns the number of years in a fractional format between two dates. From this value, we can use additional math functions, such as FLOOR() and MOD() to break out the individual year/month/day components.

Create the following columns in Power BI (or formulas in Excel):

Years = FLOOR(YEARFRAC(Source[StartDate],[TodaysDate]),1)

Months = FLOOR(MOD(YEARFRAC(Source[StartDate],[TodaysDate]),1) * 12.0,1)

Days = SWITCH(DAY(Source[StartDate]) > DAY([TodaysDate]),
TRUE(), (DAY(EOMONTH([TodaysDate],-1)) - DAY(Source[StartDate])) + (DAY([TodaysDate])),
FALSE(), (DAY([TodaysDate])-DAY(Source[StartDate])))

Using these calculations, we can display the date difference in years, months, and days:

Calculate Date Difference in Power BI

The sample .pbix file can be downloaded here to explore on your own.

Thanks,
Sam Lester (MSFT)


Comparing Table Styles in Power BI


Tip: Use table styles to improve the look of your table data in Power BI

As I continue to work with customers who are new to Power BI, a common pattern I'm noticing is that people aren't aware of the table style option in the format pane. The following screen shot shows the 9 different options, all in 10 point font to get a quick comparison on the look and the amount of space each option requires. These all use the default color scheme, but the colors can be modified.

I tend to use the Alternating Rows style or the Condensed style depending on the amount of space I have to work with, but it's just a preference. Feel free to comment on which style you prefer.

Table Styles in Power BI

Thanks,
Sam Lester (MSFT)


Connecting to SSRS through Management Studio throws "Invalid Namespace" Error


When connecting to a SQL Server Reporting Services instance through Management Studio, I encountered the following error:

SSRS Connection Error - WMI Provider Error

Report Server WMI Provider error:
Invalid namespace (Microsoft.SqlServer.Management.UI.RSClient)

It turns out that I was trying to connect to SSRS 2012 through SQL Server Management Studio 2014. Once I launched SSMS 2012, I was able to connect successfully, so it was a simple resolution to a somewhat confusing WMI provider error message.

Thanks,
Sam Lester (MSFT)


Creating a New Project in Visual Studio fails when FIPS is enabled


While testing application compatibility on Windows 10, one of my customers encountered an issue creating a new project in Visual Studio 2015 when FIPS was enabled. A new project could be completed successfully one time, but all future attempts to create a new project failed with an error message stating "Object reference not set to an instance of an object".

 

Visual Studio FIPS Error

 

We isolated the issue to the FIPS security hardening requirement included as part of the Windows 10 Security Technical Implementation Guideline. For additional details, see the following link:
https://www.stigviewer.com/stig/windows_10/2016-06-24/finding/V-63811

With this information, we then worked with the Visual Studio product group to collect trace/stack information, and the developer was able to isolate the problem to a known issue in the "Application Insights for Visual Studio" extension. The bug has already been fixed, which allowed us to perform the following steps to resolve the issue on our development machine:

  1. Uninstall the "Application Insights for Visual Studio" extension through Tools -> Extensions and Updates. Since the code path that is causing the issue is in this extension, removing the extension made the problem go away. NOTE: This must be uninstalled with an elevated account. Many enterprises do not allow "normal users" to have administrative rights on their machines, so this uninstall will require additional elevated privileges.
  2. (Optional) Reinstall the "Application Insights for Visual Studio" extension. When you reinstall the extension, you get the latest version of the code, which includes the fix. If you aren't using the extension, you do not need to reinstall it. However, if you are using the extension, you can reinstall it without reintroducing the issue on your machine.

Visual Studio FIPS Error

Without elevated privileges, the disable button is grayed out and the uninstall does not successfully uninstall the extension.

Visual Studio FIPS Error

Running in elevated mode allows you to uninstall the extension. Restart Visual Studio to see the change and you are able to create new projects again successfully.

Visual Studio FIPS Error

Special thanks to the amazing Joie Andrew, John Gardner, and Bertan Aygun for the great assistance on identifying, analyzing, and testing the scenario and solution.

Thanks,
Sam Lester (MSFT)

 

Additional note: If you are working in an environment that requires FIPS to be enabled, we also identified a FIPS related bug in Power BI Desktop that has now been fixed.