Showing posts with label unable. Show all posts
Showing posts with label unable. 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.Data.Odbc on 64-Bit Server

Hi!

Today we installed our ASP.NET Application on a 64-bit server for the first time. We got the error'Unable to find entry point named 'InterlockedIncrement' in DLL 'kernel32.dll''.

This error comes when we make a database query using Microsoft.Data.Odbc. I think it does not run on 64-bit machines.

Does anybody know something about this?

KaaN

I don't know why you need it with ODBC datasource but the link below Microsoft explains the reason for you error. Hope this helps.

(The variable pointed to by the Addend parameter must be aligned on a 32-bit boundary; otherwise, this function will behave unpredictably on multiprocessor x86 systems and any non-x86 systems.)

http://msdn2.microsoft.com/en-us/library/ms683614.aspx

|||

Thanks for your answer.

Actually I don't need this xxIncrement method, I only need the .Net Odbc Provider and probably this provider is using this function. Now I have to refactor my code to native providers or find another .Net ODBC Provider.

Microsoft Visual Studio is unable to load this document after SQL Server SP2 install.

Hello all,

Over the weekend, I loaded the SQL Server SP2 on to my production database after having it on my dev server for two weeks with out any problems.

After I did this, I went to check all my SSIS packages and found them not able to load.

I get this message “Microsoft Visual Studio is unable to load this document: The package failed to load due to error 0xC0010014 “One or more error occurred. There should be more specific errors preceding this one that explains the details of the errors. This message is used as a return value from functions that encounter errors”. This occurs when CPackage::LoadFromXML fails.

Now when I look at the errors I see:

Error 1 Error loading Master_Full_Weekly.dtsx: Error loading value "<DTS:LogProvider xmlns : DTS="www.microsoft.com/SqlServer/Dts" > <DTS : Property DTS:Name="ConfigString">SQL_TPMTSH_Datamart</DTS: Property><DTS : Property DTS:Name="DelayValidation">0</DTS: Property><DTS: Property DTS:Name="ObjectName">DTS Log Provider for SQL Serve" from node "DTS: LogProvider". D:\ETL\Projects\TPM\TPMTSH\Master_Full_Weekly.dtsx 1 1

Does anyone know what this is about and how I can go about fixing it?Anyone?|||

Could you try to register xml modules:

regsvr32 msxml3.dll

regsvr32 msxml6.dll

HTH.