I have a report on CRM 2016 which runs perfectly when it is launched with admin user. However, when we launch it with a normal user, all the datasets are displayed perfectly, except for 1 dataset (which was added lately to the report). To note that all the stored procedures used by the datasets (including this new one) have the same security roles on the SQL database. In addition, when I run the report from the visual studio, all the datasets are displayed as well. Can someone please help?
Solved. It was a security role issue on the business unit level
Related
Specifically for my connection to an Azure SQL Server Database after upgrading to Azure Data Studio v1.41.
When I connect into my Server/Database, and expand the Tables section from the left side menu, none of my tables appear. (Also my Views and Stored Procedures are not visible.)
They do still exist. They appear when the Manage option is selected, and I can access the data.
This means I am without access to Table Design for existing tables and other quick actions that would appear there.
Please help, it was all there when I had v1.40 installed earlier!
I have tried to log in using different accounts (server admin, Azure AD and another user account), none of which showed the tables under server connection. I have also restarted, refreshed and tried the Insider v1.42 build, all with the same outcome.
This has been fixed in the latest release of Azure Data Studio 1.41.1:
Bug fixes in 1.41.1
New Item
Details
Connection
Fixed a bug causing incorrect Azure account tenant selection when connecting to server through the Azure view.
Object Explorer
Fixed a regression which caused Object Explorer to not show database objects for Azure SQL DB Basic SLO.
I can confirmed, as well, that the regression no longer occurs:
Error Code
When trying to run this report out of our EHR, we are getting this error code. It seems to not find the table, but I know it is there and verified everything through Crystal Reports and DBeaver. We have the report setup as a subreport for just the list of medications, but users cannot run it from the EHR. I double checked their ODBC drivers, and they are able to run other reports. Just not this one. Any ideas?
Check permissions on that table.
If that was not the issue, open the report in Crystal Designer and use the menu options of Database, Verify Database... to ensure the report is in sync with the database.
Ask one of the other users to log in to your machine and test.
If they can still connect, the problem is with your permissions.
If they can't, the problem is with connectivity setup on your machine (database driver, ODBC DSN, etc.)
I have a data model in Power BI desktop. I'd like to publish it to the server, but I'd also like to have an internal report run MDX (or DAX) queries against it. Is this possible? Can I just create a connection string and connect to Power BI like to a SSAS Cube? Maybe using the REST APIs?
Edit:
Thanks for your answers. Kyle gave me the best answer to my question, so I accepted his, but all of you made me clear that I'd better just use SSAS. This is what I did, with some hassle of seeing up HTTP bridge, but it works like a charm now.
It actually is possible in a literal sense - every time you run PowerBI, it creates a behind-the-scenes instance of SSAS Tabular that you can connect to and run queries against. Obviously this isn't directly supported by Microsoft, but I leave these steps in case anyone else wants to know how:
Navigate to %user%/AppData/Local/Temp/Power BI Desktop
Open your PowerBI Desktop model
A new folder will appear in the temp folder, inside that is a folder called AnalysisServicesWorkspace1111111111 (numbers at end are random)
Inside that folder is a file, msmdsrv.port.txt, which contains the port number (portnum) on which the SSAS Tabular model is running
You can open SSMS and connect to Analysis Services server localhost:portnum
The specific database instance you can find either via SSMS or the name of the GUID folder in the workspace folder (it'll be something like "33df46dd-8c77-46eb-bf01-8d545f626723.0.db")
Or you can use this as the server / catalog in an SSAS connection string i.e.
Provider=MSOLAP.5;Integrated Security=SSPI;Persist Security Info=True;
Initial Catalog=databasename;Data Source=localhost:portnum;
MDX Compatibility=1;Safety Options=2;MDX Missing Member Mode=Error
Also, for devs of note, inside that *.db folder is a SQLite database which contains all the PowerBI model metadata, you can modify it via code and have it persist as long as you do something trivial in the UI such as select add calculated column and then click away.
To my knowledge this is not possible. Whether there is a workaround or not, I don't know.
You're probably better served using SSAS and connecting to a model in that both from Power BI with the AS Connector and for whatever DAX queries you need to run against it.
By publish, if you mean to put it out on SharePoint, then, YES there is a way to access it.
PowerPivot for SharePoint actually consists of two components. First, there is the Service Application that runs in the SharePoint farm that is responsible for performing data refreshes, and usage analytics. The main part however is actually an instance of Analysis Services using the tabular engine. It’s properly referred to as Analysis Services SharePoint Mode, and as of SharePoint 2013/SQL Server 2012 SP1, it can be installed standalone. However, it is most commonly installed on SharePoint front end servers.
In the case above, the SharePoint front end server is named NautilusSP. You can also see that there is a model being hosted by the server already. The model is named by taking a workbook, and adding a GUID to it. This is done by Excel Services the first time that a model is interacted with. For example, if we add the file Health.xlsx, which contains an embedded PowerPivot model, and immediately refresh the object explorer in Management Studio, we will see that nothing has changed. However, if we then interact with the model at all, by clicking a slicer, or opening a pivot table category, we will see that the model has been automatically created for us.
Caveats:
These models are temporary. If they haven’t been used for a period of
time, they get deleted. Also, if the source workbook is updated, a new
model is automatically create upon first interaction. This can be seen
if we edit, and save our Health.xlsx workbook, and then open it in the
browser and interact with it.
The original model will be deleted in a garbage collection process. We
therefore cannot reliably target these models, as any reference will
become invalid relatively quickly.
The better and actually scalable option is to create a tabular model(we are talking SSAS here) and import this PowerPivot model into it.
While running the FetchXML reports from BIDS(Business Intelligence Development Studio), all of them work fine with all filters applied.
But, when the same report is deployed to MSCRM Online, they throw a generic error message(message: error occurred, contact administrator). These deployed reports work fine when only few values are selected for specific filters(in online deployment). But they fail when all values are selected in filter. For ex, Account Performance Dashboard report has this issue. When we select Account filter up to 250 with all Finplan groups selected, it is working fine whereas it fails for more than 300+ accounts.
Conceptually whatever executes successfully in BIDS should execute successfully when deployed also. But this is not happening. Can I simply go to Microsoft Connect and raise bug? Or is there any step which I am missing?
Also the same query works fine in Advanced find, but it throws error in report(having selection more than 250) which works fine in BIDS.
I found it myself!
CRM online has restrictions and limits. Refer the below links. We cannot design huge query reports for MSCRM Online 2011
http://social.technet.microsoft.com/wiki/contents/articles/12601.crm-2011-timeouts-and-limits.aspx
http://blogs.microsoft.co.il/blogs/rdt/archive/2012/08/31/microsoft-crm-2011-timeouts-and-limits.aspx
http://msdn.microsoft.com/en-us/library/gg334634.aspx
In this document you will find general information about limits which could be put on place on a CRM Environment, I hope you will find this useful:
http://www.microsoft.com/en-us/download/details.aspx?id=27139
I am new to SSRS and have deployed several reports. When I force windows authentication, everything works fine, but when I do this:
I am getting this error:
An error has occurred during report processing. (rsProcessingAborted)
Query execution failed for dataset 'DataSet1'.
(rsErrorExecutingCommand) Login failed for user 'DWH_Reporting_User'.
I've configured the DWH_Reporting_User like this:
here are the details on DWH_Reporting_User for the ReportServer database:
here is the security on the server:
when i try to set security for that specific folder:
i am getting this error msg:
is there something obviously wrong with the way I've configured things?
The answer to this question was a series of comments. I went ahead and put it in the chat as well as an answer.
Go to the security of the server not the database and map the user to that database.
Can you recycle the application pool on the server where reporting services is running? Or reboot the IIS server if possible.
Another thing that comes to mind, when you launch this report it goes into the report server "Portal". Does this user have access to the actual report to view it? Click the details section of this "Portal" and assign this user as a content manager role.
DWH_REPORTING_USER is this an admin account on your domain?
Local admin on the server, so did you grant \COMPUTER_NAME\DWH_Reporting_User rights as a content manager in the roles section? Why dont you use a domain admin account?
So how do you access the actual report - that is your issue.
Do me a favor aprem, write up a stored procedure or sql query in the first tab of reporting services and run it using that user. Meaning in the shared data source it should be using this user DWH_Reporting_user. Test the connection then write a small sql statement to retrieve some data. Run the SQL script from within RS do you see any data?
#Aprem look at the three tabs at the top of rs, its the first tab to define datasets, this is where you can create an SQL query (and run it using the red exclamation mark). – JonH 20 mins ago
i defined a new dataset as "select top 1000 * from mytable", i rebuilt the project, deployed it, and now what do id o? – Артём Царионов 16 mins ago
In the "Shared Datasets" you have a dataset right? Double click on it and go to "Query Designer" it is a button on this form. Click on it and "Execute" the query (red exclamation mark). You dont need to deploy it right now, just do it on a test machine.ago
You specify the user in the datasource section "Shared Data Sources", that account is the account being used to "pull" the data. You really need to experiement with RS some more or read some material on it. This is as basic as it gets.
*Ok aprem do you understand your issue now, the user you are using to get the data has no issues, in addition, it is functioning correctly. Now you have to view the report. To view the report is to view the webpage, and to view a web page means you need to either use "Anon" access or windows authentication. So you need a domain or local WINDOWS account to view the report. This account needs to be setup on the RS portal as a content manager role. *
You are dealing with two beasts, one is the database (db server) and one is IIS (web server) each serve a specific purpose. The database serves to allow you to pull data while the web server hosts the pages.
The reportserver database is very important, it keeps a listing of all your reports and the meta data associated with your reports in the database. It also stores job ids and subscriptions associated with your reports. Basically it is the backend database for all reporting services stuff like reports, datasets, and datasources. Think of it this way when you create a new "Report Project" you are allowed to create reports, datasets, and datasources. Without the reportserver database how would the system remember your datasets, datasources, and report names? It is the heart of rs.
your data set is not used to connect to the reporting services databse, it is used to connect to the database you are getting the data to display on your report.
Does that user exist on the database the report is accessing?