Analysis Services Migration

Hello, I'm trying to Migrate all of my SQL 2000 Analysis Services to
SQL 2005 but get a weird error after the first step in the migration.
It asks me for a Source and Destination server and when I specify my
old and new server and click Next I get this error:
Source server: Cannot connect to the repository.
Analysis server: myoldserver.com
Error:
Cannot open database "xxx" requested by the login. The login failed.
I know my login should work since my login credentials are the same
between servers. It would be nice if there was an option in the
migration wizard for specifying your login method. Does anyone know
what the problem could be? Thanks much
-Adam
Yeah the AS stuff is on the same machine as the database is. I'm
trying to get that data to get moved to our new SQL2005 server, with no
luck.
Thanks
-Adam
|||Did you use Migration wizard?
Where do you have your fact and dimesnion tables? Have you migrated that
first to Sql Server 2005.
First migrate OLAP design(Fact and Dimesion table's) to Sql Server 2005. Try
to mirate that DB itself. As we create Cube in Sql Server 2000 we specify
DataSource as this DB. And when we try to migrate Cubes directly it may fail
as it wont find the OLAP DB.
Try this and let me know. We faced the same issue when we tried this it
worked. Let me know whats the cause of yours.
Thanks,
Sree
"Adam Plocher" wrote:

> Yeah the AS stuff is on the same machine as the database is. I'm
> trying to get that data to get moved to our new SQL2005 server, with no
> luck.
> Thanks
> -Adam
>
|||Thanks Sree, that helped but now I'm receiving another error. By
copying the database over to the new server and running the migration
wizard again, I now get the following error:
Source server: ActiveX component can't create object
This occurs at the same place as the previous error I was getting;
right after you specify a source and destination server and click Next.
I've done a lot of searching around for this error and almost all
occurences are from MS Access (not all though). This migration wizard
is starting to bug me.
Anyway, do you (or anyone else) know what this error could mean and
what I could do to fix it? I've tried re-registring my dao dll on both
the source and destination - although that's probably an Access
specific thing.
Thanks!
-Adam