Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 8 of 8 total
Thread Migrator problem
Tue, Jan 25 2011 6:01 AMPermanent Link

Hershcu Sorin

Hello

I upgrade to ver 2.05b2 and the "create database migrators" link on the
edbmngr doesn't work

Thanks
Sorin

Tue, Jan 25 2011 6:30 AMPermanent Link

Hershcu Sorin


> I upgrade to ver 2.05b2 and the "create database migrators" link on the
> edbmngr doesn't work

Sorry the migrators remain registered on the new version but the problem is
further
When I press on the Migrate Database link it's raise the error #202



Thanks
Sorin

Tue, Jan 25 2011 6:56 AMPermanent Link

Jan Ferguson

Data Software Solutions, Inc.

Team Elevate Team Elevate

Sorin,

What version did you upgrade from? If prior to version 2.04 you have to
now register the migrators yourself. EDBManager no longer does that
automatically. If you upgraded from 2.04 and beyond, there should have
been no issue. If that is your case, the migrator modules have some
kind of disconnect. Error #202 indicates that the module is having
problems loading.

You would have to DROP the migrators and once again register them. That
is the only way I know of to get them back.

FWIW, I have not had to re-register my migrators since installing them
in version 2.04 when it was first required to register them manually
and they still work properly through v2.05B2 (I tested it before
answering this post..)

--
Jan Ferguson [Team Elevate]


Sorin H wrote:

>
> > I upgrade to ver 2.05b2 and the "create database migrators" link on
> > the edbmngr doesn't work
>
> Sorry the migrators remain registered on the new version but the
> problem is further When I press on the Migrate Database link it's
> raise the error #202
>
>
>
> Thanks
> Sorin
Tue, Jan 25 2011 7:27 AMPermanent Link

Hershcu Sorin

I just upgrade from previous version 2.05b1 and before from 2.04b4.

Yes I thing I have to drop and register again but I don't find the link to
drop them

Thanks
Sorin

> What version did you upgrade from? If prior to version 2.04 you have to
> now register the migrators yourself. EDBManager no longer does that
> automatically. If you upgraded from 2.04 and beyond, there should have
> been no issue. If that is your case, the migrator modules have some
> kind of disconnect. Error #202 indicates that the module is having
> problems loading.
>
> You would have to DROP the migrators and once again register them. That
> is the only way I know of to get them back.
>
> FWIW, I have not had to re-register my migrators since installing them
> in version 2.04 when it was first required to register them manually
> and they still work properly through v2.05B2 (I tested it before
> answering this post..)

Tue, Jan 25 2011 8:05 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Sorin


Just DROP MODULE and whatever the name is whilst in Configuration

Roy Lambert [Team Elevate]
Tue, Jan 25 2011 12:35 PMPermanent Link

Hershcu Sorin


> Just DROP MODULE and whatever the name is whilst in Configuration

"Error #201 ... cannot br dropped.. it is still referenced by the migratror
bde in the configuration EDBConfig"

How I remove the migrator from the edbconfig?

Thanks Roy

Tue, Jan 25 2011 1:35 PMPermanent Link

Jan Ferguson

Data Software Solutions, Inc.

Team Elevate Team Elevate

Sorin,

DROP the migrator first, then DROP the module. When you register the
migrator, do the opposite. First CREATE the module, then CREATE the
migrator.

--
Jan Ferguson [Team Elevate]


Sorin H wrote:

> "Error #201 ... cannot br dropped.. it is still referenced by the
> migratror bde in the configuration EDBConfig"
>
> How I remove the migrator from the edbconfig?
Wed, Jan 26 2011 3:17 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Sorin,

<< Sorry the migrators remain registered on the new version but the problem
is further When I press on the Migrate Database link it's raise the error
#202 >>

You can use the Session node's task link called "View Installed Modules" to
see which modules are registered, and their path names.  However, prior to
2.05 B1, examining the system Modules table would raise an error if one of
the modules didn't exist in its defined location:

http://www.elevatesoft.com/incident?action=viewrep&category=edb&release=2.05&incident=3367

This was fixed in 2.05 B2.

--
Tim Young
Elevate Software
www.elevatesoft.com
Image