July 10, 2015 at 4:55 am
Dear all
I am migrating from server A to Server B an entire SSAS project with different cubes. The server A will remain my deployment server and the new server B will by my production server.
On Server B, SSAS is up and running and I can connect with SSMS (using /net only approach).
Now, I modified on Server A the target host to "server B" and I try to deploy from A to B but I i still receive this error:
"The project could not be deployed to the 'ServerB' 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.00"
Server A and Server B are distincts, obtained coning A, but they are not on a speficic domain.
Please can you help me to figure out how to procede?
Thanks!
Roberto
July 14, 2015 at 4:59 am
kamamusic (7/10/2015)
Dear allI am migrating from server A to Server B an entire SSAS project with different cubes. The server A will remain my deployment server and the new server B will by my production server.
On Server B, SSAS is up and running and I can connect with SSMS (using /net only approach).
Now, I modified on Server A the target host to "server B" and I try to deploy from A to B but I i still receive this error:
"The project could not be deployed to the 'ServerB' 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.00"
Server A and Server B are distincts, obtained coning A, but they are not on a speficic domain.
Please can you help me to figure out how to procede?
Thanks!
Roberto
To get yourself up and running you could just backup your AS database on server 1 and restore it on server 2. Going forward with deployments a few questions (I guess you're talking about deploying from BIDS/SSDT): Is the new AS server a named instance? Is it the exact same version (sometimes this can cause an issue if it's not)? Does it have the same security profile (does the account you are using to deploy have the same rights)?
To be honest with you when deploying to production I think the backup>restore option is safer. Imagine developing your cube in BIDS/SSDT and hitting deploy only to discover that you have the incorrect server entered (or you are using your "Production" configuration)? You could cause some serious issues.
July 15, 2015 at 11:20 am
Hi
the destination server B is a kind of black box for me, I can't do restore but I can interact only trough xmls scripts.
I have found the way RUNAS /netonly "devenv.exe", it's nice but what about when dealing with automatic process?
I can't figure out how to deploy/process trough Invoke-ASCmd in powershell.... do you have any idea?
Thanks
Roberto
July 15, 2015 at 11:38 am
Quick thought, normally I would script out A, do whatever modificarions needed and then run the scripts on B and full rebuild.
😎
July 15, 2015 at 11:50 pm
Hi,
I agree with you but... I don't have control on the Server B, I have only a login for SSAS and server are both out of domain.
I think the last solution is to enable http, does anyone tried with success usng remote PowerShell?
Many thanks for all the help you can provide me.
Roberto
July 16, 2015 at 1:01 am
kamamusic (7/15/2015)
Hi,I agree with you but... I don't have control on the Server B, I have only a login for SSAS and server are both out of domain.
I think the last solution is to enable http, does anyone tried with success usng remote PowerShell?
Many thanks for all the help you can provide me.
Roberto
I think the issue may be that you are trying to use devenv.exe (Visual Studio) on the "B" server to deploy your cube. You don't need to. As Eirikur mentioned you can do it all with XMLA scripts - then all you'll need is an account on the SSAS instance with deployment rights. As for Powershell, I found this article which describes the process: http://vaniecastro.com/2014/06/04/deploy-a-sql-server-analysis-services-project-using-powershell/
Note that devenv.exe is used here but only on the host server and only to generate XMLA. I hope that helps.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply