Showing posts with label interface. Show all posts
Showing posts with label interface. Show all posts

Monday, March 12, 2012

migraiton from Analysis Service 2000 to 2005

I get this error during migraiton from Analysis Services 2000 to 2005

Unable to cast COM object of type 'System.__ComObject' to interface type 'Interop.Dso.IDbGroup90Ex'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{CE55E9E9-9597-4214-B21F-30C7683467B1}' failed due
to the following error: No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE)).

IMRAN

Recently I successfully migrated OLAP database from 2000 to 2005 didn't see this error even I had to run few times migration wizards. Best guess, may be some thing not installed or configured correctly. However if you give at what step of migration you get this error that will help.

-Ashok

|||Databases:
FoodMart 2000
Data sources:
FoodMart
Dimensions:
Account
Category
Customer Pattern
Customers
Department
Education Level
Employees
Gender
HR^Pay Type
Marital Status
Position
Product
Promotion Media
Promotions
Store
Store Size in SQFT
Store Type
Time
Warehouse
Yearly Income
Years in the Company
Cubes:
Budget
HR
Sales
Trained Cube
Warehouse
Warehouse and Sales
Mining models:
Customer Pattern Discovery
Member Card RDBMS
Unable to cast COM object of type 'System.__ComObject' to interface type 'Interop.Dso.IDbGroup90Ex'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{CE55E9E9-9597-4214-B21F-30C7683467B1}' failed due
to the following error: No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE)).|||

Try upgrading your AS 2005 to SP2.


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

migraiton from Analysis Service 2000 to 2005

I get this error during migraiton from Analysis Services 2000 to 2005

Unable to cast COM object of type 'System.__ComObject' to interface type 'Interop.Dso.IDbGroup90Ex'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{CE55E9E9-9597-4214-B21F-30C7683467B1}' failed due
to the following error: No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE)).

IMRAN

Recently I successfully migrated OLAP database from 2000 to 2005 didn't see this error even I had to run few times migration wizards. Best guess, may be some thing not installed or configured correctly. However if you give at what step of migration you get this error that will help.

-Ashok

|||Databases:
FoodMart 2000
Data sources:
FoodMart
Dimensions:
Account
Category
Customer Pattern
Customers
Department
Education Level
Employees
Gender
HR^Pay Type
Marital Status
Position
Product
Promotion Media
Promotions
Store
Store Size in SQFT
Store Type
Time
Warehouse
Yearly Income
Years in the Company
Cubes:
Budget
HR
Sales
Trained Cube
Warehouse
Warehouse and Sales
Mining models:
Customer Pattern Discovery
Member Card RDBMS
Unable to cast COM object of type 'System.__ComObject' to interface type 'Interop.Dso.IDbGroup90Ex'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{CE55E9E9-9597-4214-B21F-30C7683467B1}' failed due
to the following error: No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE)).|||

Try upgrading your AS 2005 to SP2.


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

Wednesday, March 7, 2012

Microsoft.Jet.OLEDB.4.0 Linked Server Transactions

Hi All,

I am writing an interface between SQL Server and Access. I have chosen to use a linked server using the Microsoft.Jet.OLEDB.4.0 provider. One of the requirements is to have multiple SQL statements in one transaction, which is where I am encountering the problem. (see below)

BEGIN TRAN

INSERT INTO ACCES...Table

Msg 7390, Level 16, State 2, Line 2

The requested operation could not be performed because OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "HES" does not support the required transaction interface.

I am having a really really hard time finding documentation on the Microsoft.Jet.OLEDB.4.0 provider, specifically I want to know for sure if it supports the ITransactionJoin interface.

The main question is - does MS Access linked servers support transactions?

Thank you for your help,

I have exausted all resources available to me in finding out the answer.

Thanks,
Eric

Hi,

as far as I can remember Access does not support DT.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||

Thanks Jens,

This really is bad news for me. The previous interface was just dropping a file on the network and then access had a utility to import and update, however this methodology was horrible. If any step errored then it was a nightmare to clean up the mess and restart, and the data is so out of sync it is ridiculous. I am trying to find a more ACID way.

Maybe I can use the linked server to prepare some temp tables, then write a utility in C#.net to do the update. I bet the connection in .net can support non-distributed transactions.

Microsoft, I love you and hate you.