Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 10 of 18 total
Thread Migrate problem
Thu, Sep 2 2010 12:40 PMPermanent Link

Hershcu Sorin

Hello

I move to ver. 2.04b4 and I want to migrate a bde database.
I replace the old edbmigratebde.dll with the new file but
when I try to open the migrate database option on elevate menager
it raise the error 401 the module edbmigratebde does not exist in the
configuration edbconfig.

The file exist on the applicaton directory where the edbconfig file reside.
Are there other places where it's expected to be?

Thanks
Sorin



I post here because i can't post on the general group. I don't know why.

Thu, Sep 2 2010 1:34 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Sorin,

<< I move to ver. 2.04b4 and I want to migrate a bde database. I replace the
old edbmigratebde.dll with the new file but when I try to open the migrate
database option on elevate menager it raise the error 401 the module
edbmigratebde does not exist in the configuration edbconfig.

The file exist on the applicaton directory where the edbconfig file reside.
Are there other places where it's expected to be? >>

Please read the release notes that accompany the release:

================================================

ElevateDB no longer automatically registers external modules that exist in
the configuration file path when a session is connected. There are new
CREATE MODULE, ALTER MODULE, DROP MODULE, and RENAME MODULE statements for
manually registering external modules in an ElevateDB configuration file.
This helps improve session connection performance and allows you to store
the external modules in any location that you wish, not just in the
configuration file path. You can use a query similar to the following to
determine if a module has been registered or not:

SELECT * FROM Configuration.Modules
WHERE Name='MyExternalModule'

If no rows are returned, then the MyExternalModule external module needs to
be registered.

================================================

--
Tim Young
Elevate Software
www.elevatesoft.com

Fri, Sep 3 2010 3:20 AMPermanent Link

Hershcu Sorin

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
> Please read the release notes that accompany the release:
>
> ================================================
>
> ElevateDB no longer automatically registers external modules that exist in
> the configuration file path when a session is connected. There are new
> CREATE MODULE, ALTER MODULE, DROP MODULE, and RENAME MODULE statements for
> manually registering external modules in an ElevateDB configuration file.
> This helps improve session connection performance and allows you to store
> the external modules in any location that you wish, not just in the
> configuration file path. You can use a query similar to the following to
> determine if a module has been registered or not:
>
> SELECT * FROM Configuration.Modules
> WHERE Name='MyExternalModule'
>
> If no rows are returned, then the MyExternalModule external module needs
> to be registered.

Thanks

I read and I run the option "Create Database Migrators" on my session but
when I try
to open the "Migrate Database" and move to bde it's raise the error the
module doesn't exist.

Then I try to run:
CREATE MODULE "BDE"
PATH 'C:\Program Files\ElevateDB Additional\Version 2\libs\edbmigratebde
DESCRIPTION BDE Migrator'
and this raise the error (#202 ... is not a valid ElevateDB module)

the path is correct

So what I'm missing?

Thanks
Sorin

(the path is correct)

Fri, Sep 3 2010 6:00 AMPermanent Link

Jan Ferguson

Data Software Solutions, Inc.

Team Elevate Team Elevate

Sorin,

Actually the path statement is not syntactically correct. It should
look like:
PATH 'C:\Program Files\ElevateDB Additional\Version
2\libs\edbmigratebde.dll'

You forgot the ".dll" portion as well as the closing single quote mark
(unless it was a typo here in the NG.) That's why it is telling you
that it is not a valid Elevate DB module.

Also, unless it was a typo in the NG, you forgot the opening single
quote mark in the DESCRIPTION statement.

--
Jan Ferguson  [Team Elevate]


Sorin H wrote:

> Then I try to run:
> CREATE MODULE "BDE"
> PATH 'C:\Program Files\ElevateDB Additional\Version
> 2\libs\edbmigratebde
> DESCRIPTION BDE Migrator'
> and this raise the error (#202 ... is not a valid ElevateDB module)
>
> the path is correct
>
> So what I'm missing?
Fri, Sep 3 2010 8:01 AMPermanent Link

Hershcu Sorin

"J.B. Ferguson" <jnobspamfergnospamusonatgnospammaildotcom> wrote in message
> Actually the path statement is not syntactically correct. It should
> look like:
> PATH 'C:\Program Files\ElevateDB Additional\Version
> 2\libs\edbmigratebde.dll'
>
> You forgot the ".dll" portion as well as the closing single quote mark
> (unless it was a typo here in the NG.) That's why it is telling you
> that it is not a valid Elevate DB module.
>
> Also, unless it was a typo in the NG, you forgot the opening single
> quote mark in the DESCRIPTION statement.

Thanks
The installation pass and can see the bde migrator on the "View installed
modules"
but still if I try to open the "Migrate Database" and the bde it raise the
#401 error.

Thanks
Sorin

btw what mean NG?

Fri, Sep 3 2010 12:26 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Sorin,

<< The installation pass and can see the bde migrator on the "View installed
modules"
but still if I try to open the "Migrate Database" and the bde it raise the
#401 error. >>

This is most likely because the migrator is referring to the module called
"edbmigratebde", but you called the module "BDE".  Use this to fix the
issue:

DROP MODULE "BDE"

CREATE MODULE "edbmigratebde" PATH 'C:\Program Files\ElevateDB
Additional\Version 2\libs\edbmigratebde'
DESCRIPTION 'BDE Migrator'

<< btw what mean NG?  >>

It's an abbreviation of <N>ewsSmileyoup

--
Tim Young
Elevate Software
www.elevatesoft.com
Fri, Sep 3 2010 6:14 PMPermanent Link

Jan Ferguson

Data Software Solutions, Inc.

Team Elevate Team Elevate

Thanks Tim...I missed seeing that error in his statement.

--
Jan


Tim Young [Elevate Software] wrote:

> Sorin,
>
> This is most likely because the migrator is referring to the module
> called "edbmigratebde", but you called the module "BDE".
Sat, Sep 4 2010 3:07 AMPermanent Link

Hershcu Sorin

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message

> DROP MODULE "BDE"
>
> CREATE MODULE "edbmigratebde" PATH 'C:\Program Files\ElevateDB
> Additional\Version 2\libs\edbmigratebde'
> DESCRIPTION 'BDE Migrator'

Thanks but it raise the error:

ElevateDB Error #202 An error occurred with the module edbmigratebde (The
module C:\Program Files\ElevateDB
Additional\Version 2\libs\edbmigratebde is not a valid ElevateDB module)

Thanks
Sorin

Sat, Sep 4 2010 10:06 AMPermanent Link

Jan Ferguson

Data Software Solutions, Inc.

Team Elevate Team Elevate

Sorin,

As before, you did not enter the path correctly. You need to include
the entire file path, including the extension (.dll in this case).
"edbmigratebde" is not a file while "edbmigratebde.dll" is a file. Your
path statement should read:

PATH 'C:\Program Files\ElevateDB Additional\Version
2\libs\edbmigratebde.dll'

Don't confuse the module name of "edbmigratebde" (not needing the
extension) with the file name of "edbmigratebde.dll" (with the
extension.)

--
Jan Ferguson  [Team Elevate]


Sorin H wrote:

> "Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in
> message
>
> > DROP MODULE "BDE"
> >
> > CREATE MODULE "edbmigratebde" PATH 'C:\Program Files\ElevateDB
> > Additional\Version 2\libs\edbmigratebde' DESCRIPTION 'BDE Migrator'
>
> Thanks but it raise the error:
>
> ElevateDB Error #202 An error occurred with the module edbmigratebde
> (The module C:\Program Files\ElevateDB Additional\Version
> 2\libs\edbmigratebde is not a valid ElevateDB module)
>
> Thanks
> Sorin
Sat, Sep 4 2010 10:27 AMPermanent Link

Hershcu Sorin


"J.B. Ferguson" <jnobspamfergnospamusonatgnospammaildotcom> wrote in message
>
> As before, you did not enter the path correctly. You need to include
> the entire file path, including the extension (.dll in this case).
> "edbmigratebde" is not a file while "edbmigratebde.dll" is a file. Your
> path statement should read:
>
> PATH 'C:\Program Files\ElevateDB Additional\Version
> 2\libs\edbmigratebde.dll'
>
> Don't confuse the module name of "edbmigratebde" (not needing the
> extension) with the file name of "edbmigratebde.dll" (with the
> extension.)

Thanks

I use this statement following the example given on the manual and on the
previous Tim answer.

I try your example on diferent version '...\libs\edbmigratebde.dll'  or '...
\libs\edbmigratebde\edbmigratebde.dll'
and both return the #202 error

Thanks
Sorin


Page 1 of 2Next Page »
Jump to Page:  1 2
Image