I am getting a strange error when creating Excel 2013 Power View sheets off an Analysis Services (SSAS) Tabular instance running on an Azure VM in the cloud. Here is the error:
Sorry, something went wrong while loading the model for the item or data source 'xxxxxx.cloudapp.net Tabular Model'. Verify that the connection information is correct and that you have permissions to access the data source.
The weird thing is that I can successfully create normal connected PivotTables from it; I only get the error when I try to make Power View sheets. Which would lead me to believe I am connecting to a multidimensional SSAS database, but I am not. Here are some things I have tried already:
Forwarded the default SSAS port 2383 in Azure and opened it in windows firewall (this allowed me to browse the cube with connected PivotTables)
Ensured my login has permissions on the SSAS database (I am not using windows authentication)
Checked the SSAS Tabular compatability version, it is 1103
Checked the SSAS Tabular SSDT project compatability level, it is also 1103
Made sure SQL Server Browser was running (I read somewhere that might be an issue)
Tried opening port 80 and 443 in case those were needed for something, didn't help...
Tried monitoring Excel's port usage to see if it was trying other ports, couldn't see anything besides 2383
Sucessfully connected to an intranet SSAS Tabular database (comparability 1101) and created a Power View sheet from it (which means there shouldn't be anything wrong with my Excel client)
Here are some details of my setup:
Server
Windows Server 2012
SQL Server 2012 SP1
SSAS Tabular default instance (compatability level 1103)
Client
Windows 8
Excel 2013 (15.0.4426.1017) MSO (15.0.4454.1002) 32-bit
Update (2/12/2013): I installed Excel 2013 on the server and can successfully create Power View sheets connected to the Tabular database. This implies that my tabular SSAS instance is setup just fine, but the problem still exists when trying to create sheets through the internet.
Update (2/15/2013): I updated my Excel to 15.0.4454.1503 with Windows Update to no avail. I had a coworker successfully connect with a slightly older version of Excel 2013. I am totally stumped. I also attempted installing a fresh copy of Excel on a VM that I updated to v 15.0.4454.1503 and it was giving me the same error.
Update (2/20/2013): I installed a fresh local VM with Windows Server 2012, SQL Server 2012, and SSAS Tabular compat 1103. I STILL cannot successfully make Power View reports from that server. I strongly believe there is some kind of bug with the Excel 2013 client.
Try starting Excel with different user. I was able to open remote SSAS Tabular in that way:
runas /netonly /user:SERVERNAME\Administrator "C:\Program Files\Microsoft Office\Office15\EXCEL.EXE"
This problem has something to do with Windows authentication. Maybe Power View don't have same kind of dialog to ask for password for remote login to SSAS.
According to this article http://blogs.msdn.com/b/analysisservices/archive/2013/05/31/power-view-connectivity-for-multidimensional-models-released.aspx
is not possible to connect excel to multi-dimensional models
I was having the same issue. I could not connect with powerview to a tabular cube using different credentials to the currently logged on user. Connecting with a normal pivot table worked fine. After installing CU7 and above for SQL 2012 SP1 this fixed the authentication problem. I then change the default port of my tabular instance and powerview could not connect again. I solved this by installing an app called portmapper. I mapped the default port 2383 to my server port. All works fine. It seems that powerview in excel expects the server to be on the default port and does not use the port specified in the connection.
Related
We've been using Power Query within Excel 2013 to access an Azure SQL Server (which isn't ours but we have access to - Vendors application). Not sure at what point there was a change and what the change might have been (and apparently our vendor is clueless as well) but now every time I try to create a new workbook and use Power Query I can't seem to pass authentication to connect to the server.
Oddly, all of my legacy workbooks continue to work and my connection to the server works fine when connecting through Management Studio. Is there some sort of special permission on SQL Server (or somewhere else in the Azure environment) that requires specific configuration to allow connections from Power Query? I don't understand why management studio and legacy queries work fine but I can't create new connections.
Thank you!
Am hoping i can count on skill set of the experts in the house.
I have a BI solution developed with Microsoft Analysis Services (aka SSAS) and am trying to connect to it via qlikview, the error thrown is
Ensure SQL Server browser is running
and upon ports opened it try to connect and endless asking for user credentials without browsing the cubes.
I have tried couple of suggested solutions such as :
Firstly, the SQL Server browser is running on the said server
Secondly, have opened up the port for SSAS using a fixed port as the instance is a named instance
Also, have opened up the port on which SQL Server browser runs.
Firewall has been switched off on the said port while remote connectivity has been allowed.
Yet the error persists.
Although I can connect with the SSAS database on the local machine.
The problem does lie with trying to connect to SSAS on a remote server connection.
N.B: Am using Qlikview version 11.20, SQL server 2012 while the remote server is Windows Server 2012 R2 Standard 64 bit
Kindly be of help here please.
MB
I am trying to create a Visual Studio SSAS Tabular project connecting to a remote workspace server without success. I have no problem creating and deploying using localhost.
However I need the remote server to deploy to production or shared development server. I get error: "Cannot deploy model to the deployment database server 'xxxx.cloudapp.net'. Reason: You are not an Administrator on the deployment database server 'xxxx.cloudapp.net'."
I know I am reaching the server as otherwise the error is about not connecting to the server. I am already running Visual Studio as mydomain\adminuser and added it to the Analysis Server to make it administrator. However I am still getting that error. I can also connect remotely to the Analysis Server in Management Studio using that same user.
All the examples I've seen use localhost but have not found any using a shared/remote server even though some say it is possible without showing how. By the way, I understand using a local instance is better for development but I still need to deploy to a remote server. Hope that makes sense. Please help.
I ran into the same issue when trying to deploy a SSAS Tabular model remotely. The corresponding MSFT docs further even discourages to deploy to production via Visual Studio.
But, a viable alternative is to deploy via XMLA:
Create your SSAS Tabular Model in Visual Studio and use your local SSAS instance for your workspace database
Launch SSMS connecting to your local SSAS instance
Right-click on your workspace database, and select Script > Script Database As > CREATE to > File
Open the generated XMLA file, and a) replace the temporary workspace database name with the database name on the deployment server, and b) search for the database connection string and re-add the password (see the note here)
Launch SSMS connecting to your deployment SSAS instance
Open the XMLA file, and Execute it (by pressing F5)
Refresh the list of databases, right-click on the new one, and select Process Database
In case you already have a deployed database, then you need to select the ALTER to option instead of CREATE to in step 3 above.
I read another article concerning this problem when getting the file in use message. I went into SQL Management studio and disconnected the database but still no success in connecting. Here's what's happening step by step:
I downloaded SQL Express 2014 and installed it. I created a DB called MyEntertainmentDB, then created a couple of files (Movies and Rating). I added some data to both. I fired up VS and in VB I created a form added various controls including a datagrid. The DB exists in the default location used by MS SQL. I clicked the Smart Tag and the data grid view tasks window appears. I click the choose data source drop down arrow and then add project data source. Database is highlighted and I click next. Dataset is highlighted and I click next. Now I click new connection and select Microsoft SQL Server Database File (Data provider is .NET Framework Data Provider for SQL Server (the only thing in that drop down box)) and I click Continue. Now I'm shown a window that has the data source as Microsoft SQL Server Database File (SqlClient) in the first box and I browse to where my database is located and select it (which is C:\Program Files\Microsoft SQL Server\MSSQL12.SQLEXPRESS\MSSQL\DATA\MyEntertainmentDB.mdf). Everything is going well and I'm using Windows Authentication. I click ok. Now it waits several minutes and I get this message:
The attempt to attach to the database failed with the following message: A network related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 50 - Local Database Runtime error occurred. Cannot create an automatic instance. See the Windows Application event log for error details.
I looked in theSQL Server log but nothing was mentioned shedding any light. I could not find any VS log. I checked the windows logs but could not find anything seemingly relevant. I'm at a loss for this problem and am about ready to trash MS SQL server and just go with MS Access 2010 or MySQL. Does anybody see where I'm going wrong? If so, please help, I've tried to be very specific and hope I've provided all info necessary.
First of all you must configure your MSSQL Express Server to respond.
To do that you must open SQL Server Configuration Manager (on Windows 8.1 just go in the upper right corner, hit Search and type: SQL Server Configuration Manager. If you are using Windows 7 you can find it on Start Menu).
On SQL Config Manager you must go to expand SQL Server Network Configuration and you'll see Protocols for (your DB instance). Click on that.
After you click on Protocols for (your DB instance) in the right window you will see Shared Memory, Named Pipes and TCP/IP. Double click on each and set them to Enabled = Yes.
Now your MSSQL Server must listen to standard port 1433. To do this double click on TCP/IP, select IP Addresses (Now you will see IP1 config, IP2 config, etc), scroll down to IPAll and set TCP Dynamic Ports to 0 and TCP Port to 1433.
Now restart your SQL Server Service. If don't know how to this, just reboot your computer. After reboot open command prompt and type netstat -a to see if your MSSQL is listening on port 1433.
Now in Visual Studio when you are connecting to your SQL Server on Server Name type server IP (your IP or 127.0.0.1) or you can select your SQL Server instance from dropdown list without any problems.
You can check this tutorial too: Allow SQL Server Express to accept remote connections
Alright, I finally solved the problem and not in a way people would think. First off, I want to thank everyone who responded with the intelligent answers, but we were off base on this one and I'm not sure why, but your responses ultimately led to my defeating this problem. I've been wrestling with this problem for the last 3 days almost exclusively - I don't like being beaten - and 1 entire night. I've uninstalled and re-installed several times and even got superstitious and waved a chicken bone - lol - at it but nothing worked! I've asked this question on several web sites and finally I went to a link that stated the .msi file was included with MS SQL Server 2012 Management objects I and was hesitant to download as they pertained to the 2012 version. So after tinkering to no avail I downloaded the 2012 CLR Types and Management Objects and looked in the Windows\assemblies folder and still no v 11. But I guess 2012 installation installed them in Program Files (x86)\Microsoft SQL Server\110\SDK\assemblies\Microsoft.SqlServer.Management.Sdk.Sfc.dll v11.0.2100.60. I ran VS 2013 and added the data source. After going through all this problem I'm wondering why Microsoft invents all these places to put things when one would work. Every version of windows from 3 to present has always been totally revised and I wonder for what. Improvements are okay but quit reinventing the wheel. Without your help I might not have ever found the solution and perhaps would have been an oracle or mysql guru or not. Your the men. Thanks all.
Do not connect to mdf, connect to the SQL Server and use MyEntertainmentDB database from there.
The MDF file is locked by the SQL Server for reading/writing data.
I created a VM using the gallery image, and got SQL server 2014 Standard template and got reporting services working correctly. My questions here are all about the Azure VM image, which I'm sure the community is using as well (no SSRS in Azure other than using a VM)
ReportBuilder however will not start from a remote client (401 unauthorized), and I'm sure I have to open another port or something to get it working but I can't seem to find the right article....
I'm also told that SQL Server Data Tools (SSDT) is installed on the server, in order to create reports via Visual Studio. However, I can't seem to find the right link on the server (damn this new Server 2014 interface! hard to loose the muscle memory of the previous os) What is the start up procedure for SSDT on the VM?
I've also tried using the Browser directly on the VM, but without JavaScript enabled, that wont' work as well. How do I drop (temp) all the constraints it's under?
In essence, how do you create a report on the Azure VM?
If you can access the report server from a browser in a remote client, for example, yourazurevm.cloudapp.net/reportserver, then you have already configured firewall correctly. Otherwise, refer to this article (http://azure.microsoft.com/en-us/documentation/articles/virtual-machines-provision-sql-server/#SSMS) to configure Azure SQL VM.
To create reports using ReportBuilder, install the standalone version of the ReportBuilder 3.0 from http://www.microsoft.com/en-us/download/details.aspx?id=6116. After you launch the ReportBuilder, you can configure it to connect to your Azure SQL report server in the lower left corner.
To create reports using Visual Studio and SQL Server Data Tools (SSDT), install SSDT-BI (not just SSDT) in the client where Visual Studio is installed. Then create a Report Server Project by going to File->New->Project->Installed->Templates->Business Intelligence->Reporting Services. Open the properties of the project, and set the Target Server URL to your Azure SQL report server.