Error in Processing Cubes SSAS2005

I am trying to deploy and process cubes to production server, i got this error with processing failure

Errors in the back-end database access module. OLE DB reported the '' status, which is unknown, for column 1.

So deployment works fine. I have deployed and processed and the same cube to Development and Test server, it goes through pretty well without any errors.

Any one has an idea what this error means?

Thanks

This error means Analysis Server for some reason couldn’t instantiate OLEDB provider to connect to relational database.
Several reasons:

1. For some reason your production sever cannot access relational database. Check Analysis Server service account. Does it have privileges to access relational database?

2. Installation or configuration gone wrong. See if you can fix the problem by re-installaing Analysis Server.

3. Another suggestion for you to use Synchronization functionality to move database from test to production.

Hope that helps

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

Error in Processing Cube while ROLAP Storage

Hello,

When I process the Cube having ROLAP storage, it gives the error as below, any thoughts on this would be greatly appreciated.

Errors in the back-end database access module. ROLAP partition with the Name='Fact One' Id='Fact One' can not have aggregations at the (all, all, ... ) level. Aggregaion skipped. OLE DB error: OLE DB or ODBC error: Cannot create index on view "TESTROLAP.dbo.Agg_Fact One_0_1_1_1_1_1" because it references derived table "dbo_Fact_One" (defined by SELECT statement in FROM clause). Consider removing the reference to the derived table or not indexing the view.; 42000.

Thanks,
Nasir

Nasir wrote:

Hello,

When I process the Cube having ROLAP storage, it gives the error as below, any thoughts on this would be greatly appreciated.

Errors in the back-end database access module. ROLAP partition with the Name='Fact One' Id='Fact One' can not have aggregations at the (all, all, ... ) level. Aggregaion skipped. OLE DB error: OLE DB or ODBC error: Cannot create index on view "TESTROLAP.dbo.Agg_Fact One_0_1_1_1_1_1" because it references derived table "dbo_Fact_One" (defined by SELECT statement in FROM clause). Consider removing the reference to the derived table or not indexing the view.; 42000.

Thanks,
Nasir

Above Cube runs these two Queries while processing:

Query 1 succeeds and Query 2 fails, here are both of them:

Query 1

CREATE

VIEW [Agg_Fact One_0_1_1_1_1_1] ( [Amount_0],[_1],[TimeID_2], [COUNT_BIG_7673aff6-2445-4ef6-a4c9-7bf3d93bd42a] ) WITH SCHEMABINDING AS

(

SELECT SUM ( [dbo_Fact_One].[dbo_Fact_OneAmount0_0] )

AS [dbo_Fact_OneAmount0_0],

COUNT_BIG ( [dbo_Fact_One].[dbo_Fact_One0_1] )

AS [dbo_Fact_One0_1],[dbo_Fact_One].[dbo_Fact_OneTimeID0_2] AS [dbo_Fact_OneTimeID0_2], COUNT_BIG(*) AS [COUNT_BIG_7673aff6-2445-4ef6-a4c9-7bf3d93bd42a]

FROM

(

SELECT [Amount] AS [dbo_Fact_OneAmount0_0],1 AS [dbo_Fact_One0_1],[TimeID] AS [dbo_Fact_OneTimeID0_2]

FROM [dbo].[Fact_One]

)

AS [dbo_Fact_One]

GROUP BY [dbo_Fact_One].[dbo_Fact_OneTimeID0_2]

)

Query 2

CREATE

UNIQUE CLUSTERED INDEX [Agg_Fact One_0_1_1_1_1_1] ON [Agg_Fact One_0_1_1_1_1_1] ( [TimeID_2] )

Error in Processing Cube (Microsoft Analysis Services)

Hi,
I am processing one cube using Full Process option and it's giving
following error.

Analysis Server Error: Internal error [Object does not exist] '11948' ;
Time:1/8/2004 6:11:11 PM

Error(-2147221421): Internal error (Internal error [Object does not
exist] '11948' ); Time:1/8/2004 6:11:11 PM

Can anyone help me on this.If you are using shared dims, process your dimensions, then the cube and see if that fixes it.

GO COLTS!!

HTH

Error in metadata manager processing sample database/cubes

I've just installed SQL Server 2005 with Analysis Services and the sample AdventureWorks databases. When I try to process the database via SQL Server Management Studio, I get the following error - see below. I did check the xml file referenced by the name of the error and I do see the dimension listed Order Date key but not any attribute called Name of Date. Is there any workaround to enable processing of the database and cubes?

I did bump up to Sp1 and this did not fix my problem. I also tried installing the samples from the downloads section of microsoft.com. Alas, no success.

Any help appreciated,

Mairead

Errors in the metadata manager. The dimension with ID of 'Order Date Key - Dim Time', Name of 'Date' referenced by the 'Adventure Works' cube, does not exist.
Errors in the metadata manager. An error occurred when loading the Adventure Works cube, from the file, '\\?\D:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Data\Adventure Works DW.0.db\Adventure Works DW.2.cub.xml'.
(Microsoft.AnalysisServices)

Program Location:

at Microsoft.AnalysisServices.XmlaClient.CheckForException(XmlReader reader, XmlaResult xmlaResult, Boolean throwIfError)
at Microsoft.AnalysisServices.AnalysisServicesClient.Discover(IMajorObject obj, ObjectExpansion expansion)
at Microsoft.AnalysisServices.Server.Refresh(IMajorObject obj, ObjectExpansion expansion)
at Microsoft.AnalysisServices.Server.SendRefresh(IMajorObject obj, ObjectExpansion expansion)
at Microsoft.AnalysisServices.MajorObject.Refresh()
at Microsoft.AnalysisServices.Server.Connect(String connectionString, String sessionId)
at Microsoft.AnalysisServices.Server.Connect(String connectionString)
at Microsoft.SqlServer.Management.SqlMgmt.CDataContainer.Init(XmlDocument doc)
at Microsoft.SqlServer.Management.SqlMgmt.CDataContainer.Init(XmlDocument doc, IServiceProvider site)
at Microsoft.SqlServer.Management.SqlMgmt.DefaultLaunchFormHostedControlAllocator.AllocateDataContainer(XmlDocument initializationXml, IServiceProvider dialogServiceProvider)
at Microsoft.SqlServer.Management.SqlMgmt.DefaultLaunchFormHostedControlAllocator.Microsoft.SqlServer.Management.SqlMgmt.ILaunchFormHostedControlAllocator.CreateDialog(XmlDocument initializationXml, IServiceProvider dialogServiceProvider)
at Microsoft.SqlServer.Management.SqlMgmt.LaunchForm.InitializeForm(XmlDocument doc, IServiceProvider provider, ISqlControlCollection control)
at Microsoft.SqlServer.Management.SqlMgmt.LaunchForm..ctor(XmlDocument doc, IServiceProvider provider)
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ToolsMenuItem.OnCreateAndShowForm(IServiceProvider sp, XmlDocument doc)
at Microsoft.SqlServer.Management.SqlMgmt.RunningFormsTable.RunningFormsTableImpl.ThreadStarter.StartThread()

Here is simple way out of your situation

1. Stop Analysis Service.
2. Delete everything in your D:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Data\Adventure Works DW.0.db folder.
3. Start the service
4. Re-deploy your sample project.

Hope that helps

Edward Melomed.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

Thanks Edward, I finally did get everything working again by completely uninstalling/reinstalling and redeploying the samples again. I did try your workaround but still could not get the samples processed successfully.

Mairead

error handling while processing a cube

hi

in analysis services when i process a cube i got an error that
data from the fact table isnt exists in the dimenstion table
for example : fact table sales has column suplier that one of its row
has data(suplier id = 170) that doesnt match with the dimension table ( in the dimension table there isnt such supier id)
how can i handle this error ?
can i insert instead someyhing else so that the proccess can continue and not failed ?

Thanks

Eyal

Ideally, you've addressed this problem in your data warehouse/data mart. I recommend to my clients they never allow NULLs in their foreign keys. This requires you to place a NULL member in each dimension -- we usually assign that member the surrogate key value of -1 -- and eliminates this issue.

It sounds like in your example, you have a valid key in your partition, so I would suggest you make sure you dimension is processed before you process your cube/partitions.

If that is not an option, you use use the UnknownMember and ErrorConfiguration properties in SSAS to handle this issue. In the dimension that is causing problems (the supplier dimension in your example?) set the UnknownMember property to either visible or hidden. It defaults to None which makes the UnknownMember inaccessible.

Then, on the measure group that points to this dimension table, change the error configuration to replace missing key values with unknown (using the KeyErrorAction and KeyNotFound properties). Be certain to also set the KeyErrorLimitAction property to Stop Logging when the max error is hit.

One important gotcha on this. If your dimension member lands in your dimensions, the facts assigned to the unknown member do not revert to your new dimension value. To line your facts up correctly with the values in your dimension, you will need to do a full reprocess of the partition.

B.