"MC" <marko.NOSPAMculo@gmail.com> wrote in message
news:eLbBmUZFIHA.284@TK2MSFTNGP02.phx.gbl...
> Try entering the full name of the server instead of localhost.
>
>
> MC
>
>
> "Frank Doosey" <nospam@rightanswers.com> wrote in message
> news:Oo9Vj7XFIHA.280@TK2MSFTNGP03.phx.gbl...
>> Hello,
>>
>> I am learning how to use the BI tools with SQL Server 2005. I am
>> following the tutorials on creating an SSAS project. My connection string
>> tests successfully and all SQL Server services are running, but when I
>> try to analyze a cube or deploy the package, I get the following error:
>>
>> Error 1 The project could not be deployed to the 'localhost' 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.
>>
>> Any idea as to what's causing this to occur? SQL is running on my
>> machine, I have admin rights and the DB is there and viewable.
>>
>> Thanks in advance,
>>
>> Frank
>>
>
>

"Frank Doosey" <nospam@rightanswers.com> wrote in message
news:Oo9Vj7XFIHA.280@TK2MSFTNGP03.phx.gbl...
> Hello,
>
> I am learning how to use the BI tools with SQL Server 2005. I am following
> the tutorials on creating an SSAS project. My connection string tests
> successfully and all SQL Server services are running, but when I try to
> analyze a cube or deploy the package, I get the following error:
>
> Error 1 The project could not be deployed to the 'localhost' 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.
>
> Any idea as to what's causing this to occur? SQL is running on my machine,
> I have admin rights and the DB is there and viewable.
>
> Thanks in advance,
>
> Frank
>