December 4, 2008 at 10:13 am
George Dickson (12/4/2008)
I finally did get the AdventureWorks.mdf and AdventureWorksDW.mdf installed. Now I am having problems loading the solution (AdventrueWorks Analysis Services Project\Standard) for Analysis Services. It is giving me trouble with the OLE DB connection. SQL 2005 is not my default it is a version of SQL 2000 that is the default. I know this is kind of a new subject so I'm not sure if I should start a new post?
Doesn't matter, we can keep this thread going, George.
Does the solution error while it's opening? Or just when you try to deploy/process the cube?
Assuming the solution opens normally and 2005 isn't the default instance, you'll have to edit the data source in the solution before you try to deploy it.
December 4, 2008 at 10:32 am
The instructions that I am following say to open up the AdventureWorks Solution (Adventure Works.sln) in SQL BIDS in the Enterprise or Standard folder of where the Samples were put. The select Deploy or Process. I chose Deploy. It displays Processing Dimensions in the Deployment Progress window (Sales Channel, Sales Order Details, Sales Summary Order Details, ... Forecasting ~MC-Model Region) and I get the dollowing:
Error1Internal error: The operation terminated unsuccessfully.00
Error3OLE 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 [2]. ; 08001.00
Error4Errors in the high-level relational engine. A connection could not be made to the data source with the DataSourceID of 'Adventure Works DW', Name of 'Adventure Works DW'.00
There seems to be the same messages for the rest of the Dimentions. I checked and the setting for remote connections is set to allow them.
December 4, 2008 at 10:53 am
George, that smells like the server\instance name in the project data source is still incorrect. Are you sure the connection string has updated correctly and tested successfully?
December 4, 2008 at 11:05 am
That was exactly my suspession but I checked and double checked (maybe not enough times for me LOL) but the data source = my pc name and the connections tested with a good connection? I tried changing a letter so that the data source would be wrong and the connection failed the test so I thought I had the right one?
Viewing 4 posts - 16 through 18 (of 18 total)
You must be logged in to reply to this topic. Login to reply