Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2005 Forums
 Analysis Server and Reporting Services (2005)
 cant Deploy AdventureWorksDW

Author  Topic 

sbprasadrao
Starting Member

2 Posts

Posted - 2009-01-04 : 10:43:00
I am having trouble deploying AdventureWorksDB.
I am getting error as below. I get this error sometime are 60 secs while running deployment and DB gets created partially.

I have tried setting ExternalConnectionTimeout, ExternalCommandTimeout, and DatabaseConnection* properties to 0, for the analysis server instance but still the problem exists

I have successfully deployed other sample cube like computer sales.

Machine: Vista
DB Instance: local


Error 1 OLE DB error: OLE DB or ODBC error: Login timeout expired; HYT00; An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.; 08001; Named Pipes Provider: Could not open a connection to SQL Server [53].

Any Ideas

Thanks

sbprasadrao
Starting Member

2 Posts

Posted - 2009-06-06 : 17:06:40
Finally got resolved, Issue was using with wrong instance of server
thanks


quote:
Originally posted by sbprasadrao

I am having trouble deploying AdventureWorksDB.
I am getting error as below. I get this error sometime are 60 secs while running deployment and DB gets created partially.

I have tried setting ExternalConnectionTimeout, ExternalCommandTimeout, and DatabaseConnection* properties to 0, for the analysis server instance but still the problem exists

I have successfully deployed other sample cube like computer sales.

Machine: Vista
DB Instance: local


Error 1 OLE DB error: OLE DB or ODBC error: Login timeout expired; HYT00; An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.; 08001; Named Pipes Provider: Could not open a connection to SQL Server [53].

Any Ideas

Thanks

Go to Top of Page
   

- Advertisement -