August 5, 2008 at 9:52 am
This is first time I am using SSAS.
I have created a cube and now,I want to deploy it. But I am having problems in achieving the same.
We use SQL server authentication, SO while defining data source, I used SQL server Authentication and then later I used 'use current credentials' for impersonation information.
I JUST LEARNED THAT SQL SERVER AUTHENTICATION IS NOT POSSIBLE IN SSAS. Is it so?:(
Now when I try to deploy, i get following error message:
The project could not be deployed to the 'myservername' server because of the following connectivity problems : A connection cannot be made. Ensure that the server is running. To verify or update the name of the target server, right-click on the project in Solution Explorer, select Project Properties, click on the Deployment tab, and then enter the name of the server.
I don't know what should I do under deployment tab of Project properties. By default,server name was 'local host' and some default for database.
I tried putting 'myservername' and similarly,I tried to put name of an existing databse..
But I still get same error.
Please suggest me how can I deploy the cube.
Thanks
August 5, 2008 at 10:14 am
you've raised a couple of different things here, not all as related as you might think...
"We use SQL server authentication, SO while defining data source, I used SQL server Authentication and then later I used 'use current credentials' for impersonation information."
That's fine to use SQL authentication for the data source, this is used when reading the data from the data source in to the cube. Selecting to use current credentials means that you'll use the credentials of the current user to access/read the data in to the cube. Neither of these impacts your users access to the final cube.
I JUST LEARNED THAT SQL SERVER AUTHENTICATION IS NOT POSSIBLE IN SSAS. Is it so?
Correct. SSAS uses Windows Authentication, period.
re: your deployment error, is SSAS running on your target server and do you have permissions (eg you're an admin) on that server? Remember when you're deploying, it's deploying to the AS server NOT SQL server, so i'm assuming that when you said you're using the name of an existing database, you prob meant a SQL DB. Try using SSMS to connect to your SSAS server, see if you can connect (ie it's running and you have some level of permissions). After that, try entering that servername in to the project properties and try deploying again.
HTH,
Steve.
August 5, 2008 at 10:35 am
Thanks for quick response.
It has cleared many doubts.
well,i don't have admin rights but now,i know in which direction to proceed..
thanks
August 5, 2008 at 10:38 am
In case you're working in a tight SOE place, getting admin rights (as in local admin on the machine) is somewhat overkill. Technically, you just need to get someone to give you 'server role' rights on the SSAS service/application which they can do via SSMS, right click on the connected AS server, select properties and then go to the security tab.
Steve.
August 6, 2008 at 7:42 am
Steve,
I was caught up in some other issues, hence, slow in responding..
Thank you so much for your invaluable inputs.
August 14, 2008 at 7:02 am
Hi Steve,
I have a question. I don't have much experience with SQL server..so, I am not sure about my conclusions. I would appreciate if you have any inputs for me here.
While reading some literature & articles, I figured out ways to deploy & access cube. So, as with Management studio, it is our one-stop shop. We can do everything(accessing, querying etc) related to Analysis services project. I tried it on my Laptop & all worked.
However, at workplace, scenario is bit different. The policy is not to install SQL services on local machines. so,when I checked SQL server configuration manager for services running, it shows me a blank page. Apparently, there isn't any instance/sql service installed.
I didn't know about this information earlier.
Since Analysis Services, uses only Windows Authentication, I don't know how should I go about helping my cause.
just FYI, this is error message when i try to connect to AS.
TITLE: Connect to Server
------------------------------
Cannot connect to "IP ADDRESS"
------------------------------
ADDITIONAL INFORMATION:
A connection cannot be made. Ensure that the server is running. (Microsoft.AnalysisServices.AdomdClient)
------------------------------
Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. (System)
------------------------------
An existing connection was forcibly closed by the remote host (System)
If my understanding is correct, the way to resolve the issue is to get SSAS installed on local m/cs.
btw, this particular server does has AS installed and running.
If you get time, please let me know what you think about this.
Thanks,
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply