Migration Wizard Fails Interop.DSO.IDBGroup90Ex

I am attempting to convert several 2000 AS databases to AS 2005. I have not been able to successfully convert any databases. The error message is:

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)).

I have attempted to convert the FoodMart sample database and it also fails to convert. I have unregistered and registered all DSO related dlls. The problem still persists. I have attempted to convert at least 4 other databases and they all fail. The failure point occurs during the conversion of the Cubes.

Thanks

Ron Cotton

Problem solved. Unfortunately, I am not sure which step actually solved the problem. I will state both here.

1. I registered all of the dlls associated with DSO, which reside in the directory: C:\Program Files\Common Files\Microsoft Shared\DSO using regsvr32. BTW, I don't believe that this solve the problem, but I have state it here because of item 2.

2. I downloaded and installed Service Pack 2 for SQL 2005. The Service Pack installation forced a reboot so I not exactly sure that it was the cure. My gut says that it was an not option 1.

Anyway, I hope that this helps anyone that has been struggling with this issue.

Thanks

Ron Cotton

Migrating Sybase to SQL Server 2000

I'm currently involving in a project in migrating from
Sybase to SQL Server 2000. I've been able to
successfully (and conveniently) import my tables/data.
My question involves the Stored Procedures. Can these
stored procedures be import w/ a wizard (i.e. the way my
tables/data have been converted)? Or must I manually
create new SP's in SQL Server, making the necessary
changes (Rollback trigger, transaction isolation levels,
etc.) on the fly?I think that you must to do the necessary changes.
The sybase code is not totally compatible with sql2k.
After this forget sybase, please.
<anonymous@.discussions.microsoft.com> escreveu na mensagem
news:16a0801c4481a$7b9a8410$a401280a@.phx.gbl...
> I'm currently involving in a project in migrating from
> Sybase to SQL Server 2000. I've been able to
> successfully (and conveniently) import my tables/data.
> My question involves the Stored Procedures. Can these
> stored procedures be import w/ a wizard (i.e. the way my
> tables/data have been converted)? Or must I manually
> create new SP's in SQL Server, making the necessary
> changes (Rollback trigger, transaction isolation levels,
> etc.) on the fly?|||Hi,
Have a look into the below article from MS:-
http://www.microsoft.com/resources/documentation/sql/2000/all/reskit/en-us/p
art2/c0661.mspx
Thanks
Hari
MCDBA
<anonymous@.discussions.microsoft.com> wrote in message
news:16a0801c4481a$7b9a8410$a401280a@.phx.gbl...
> I'm currently involving in a project in migrating from
> Sybase to SQL Server 2000. I've been able to
> successfully (and conveniently) import my tables/data.
> My question involves the Stored Procedures. Can these
> stored procedures be import w/ a wizard (i.e. the way my
> tables/data have been converted)? Or must I manually
> create new SP's in SQL Server, making the necessary
> changes (Rollback trigger, transaction isolation levels,
> etc.) on the fly?|||Yes, you must make the changes manually, but there should not be a whole lot
of changes...They are doc'd in the article mentioned previously.
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
<anonymous@.discussions.microsoft.com> wrote in message
news:16a0801c4481a$7b9a8410$a401280a@.phx.gbl...
> I'm currently involving in a project in migrating from
> Sybase to SQL Server 2000. I've been able to
> successfully (and conveniently) import my tables/data.
> My question involves the Stored Procedures. Can these
> stored procedures be import w/ a wizard (i.e. the way my
> tables/data have been converted)? Or must I manually
> create new SP's in SQL Server, making the necessary
> changes (Rollback trigger, transaction isolation levels,
> etc.) on the fly?