![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
#3
| |||
| |||
|
|
. |
|
Alfred, All the default setting for deployment (certainly samples and such) point to the default instance, so if you want to deploy to a named instance you need to modify the properties of the project or solution in BI development studio. On the properties tab of the project (solution explorer) choose deployment from the configuration properties and change the Target Server to the correct named instance. After that you should be able to deploy. Dirk |
#4
| |||
| |||
|
|
Dirk, Thanks much for your suggestion. I changed Target Server for the deployment to the correct instance 'Koforidua\SQL2005Dev' and I get the following error when I try to process dimensions and facts: Error 1 The project could not be deployed to the 'Koforidua\SQL2005Dev' server because of the following connectivity problems : A connection cannot be made to redirector. Ensure that 'SQL Browser' service 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. Incidentally, I am able to see the correct instance 'Koforidua\SQL2005Dev' in BI development studio but I get the following error when I try to connect to the object browser: TITLE: Microsoft SQL Server Management Studio A connection cannot be made to redirector. Ensure that 'SQL Browser' service is running. (Microsoft.AnalysisServices.AdomdClient) ADDITIONAL INFORMATION: No connection could be made because the target machine actively refused it (System) . Please let me know if you have other suggestions. Thanks, alfred "Dirk" <dvdstraeten (AT) gmail (DOT) com> wrote in message news:1139825750.434495.120760 (AT) g44g2000cwa (DOT) googlegroups.com... Alfred, All the default setting for deployment (certainly samples and such) point to the default instance, so if you want to deploy to a named instance you need to modify the properties of the project or solution in BI development studio. On the properties tab of the project (solution explorer) choose deployment from the configuration properties and change the Target Server to the correct named instance. After that you should be able to deploy. Dirk |
#5
| |||
| |||
|
|
Sorry I left out one additional information. I have checked and both the Analysis servicer and SQL Browser services are started. "Alfred" <aakiti (AT) voltasolutions (DOT) com> wrote in message news:OYHEnBLMGHA.2992 (AT) tk2msftngp13 (DOT) phx.gbl... Dirk, Thanks much for your suggestion. I changed Target Server for the deployment to the correct instance 'Koforidua\SQL2005Dev' and I get the following error when I try to process dimensions and facts: Error 1 The project could not be deployed to the 'Koforidua\SQL2005Dev' server because of the following connectivity problems : A connection cannot be made to redirector. Ensure that 'SQL Browser' service 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. Incidentally, I am able to see the correct instance 'Koforidua\SQL2005Dev' in BI development studio but I get the following error when I try to connect to the object browser: TITLE: Microsoft SQL Server Management Studio A connection cannot be made to redirector. Ensure that 'SQL Browser' service is running. (Microsoft.AnalysisServices.AdomdClient) ADDITIONAL INFORMATION: No connection could be made because the target machine actively refused it (System) . Please let me know if you have other suggestions. Thanks, alfred "Dirk" <dvdstraeten (AT) gmail (DOT) com> wrote in message news:1139825750.434495.120760 (AT) g44g2000cwa (DOT) googlegroups.com... Alfred, All the default setting for deployment (certainly samples and such) point to the default instance, so if you want to deploy to a named instance you need to modify the properties of the project or solution in BI development studio. On the properties tab of the project (solution explorer) choose deployment from the configuration properties and change the Target Server to the correct named instance. After that you should be able to deploy. Dirk |
![]() |
| Thread Tools | |
| Display Modes | |
| |