Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 5 of 5 total
Thread Am I doing something wrong?
Sun, Dec 17 2006 10:33 AMPermanent Link

"J. B. Ferguson"
Is anyone having the same issues as me? Just working with the EDB
server and EDB Manager in WinXP Professional SP2 and everytime I try to
either create a database, a table, a user, drop any of these or migrate
a DBIsam v4 database, I get some kind of error (either a EDB 600 error,
9999 error or others.)  Most of the time when I perform one of these
tasks I get the error and if I exit from EDB manager then reenter it
and connect to the session, the changes I made, which created the
error, are there.

I'm now trying to tackle migrating a DBIsam v4 database on a remote
server. The EDB Server is on a server machine (not my development
machine) and is the same one I run DBIsam server v4.24 on. I can ping
it and there are no permission issues (I have administrator
privileges.) The migration module shows all the DBIsam v4 tables and
all are checked to migrate over to EDB so I know it is reading the
server. Whether I create the folder (on the server machine) or try to
have EDB create it I get an EDB #600 File Manager (Cannot create file
Z:\Apps\MyApplication\MyApplication..edbcat (OS Error: The system
cannot find the path specified.) I have UNC naming as well as a mapped
drive (as illustrated here) but I always get this error. The catalog
does not seem to get created.

Tim...anyone...any suggestions?

--
Regards,
Jan Ferguson
Sun, Dec 17 2006 10:36 AMPermanent Link

"J. B. Ferguson"
Oops...should read

"I have *tried using* UNC naming as well as*using* a mapped drive (as
illustrated here) but I always get this error. The catalog does not
seem to get created."

Jan
Sun, Dec 17 2006 11:56 AMPermanent Link

"J. B. Ferguson"
Just a further FYI, when I stated that I have Administrator privileges
I fear I was a little ambiguous. I am referring to the OS as well as
EDB.

--
Regards,
Jan Ferguson


J. B. Ferguson wrote:

<<I'm now trying to tackle migrating a DBIsam v4 database on a remote
<<server. The EDB Server is on a server machine (not my development
<<machine) and is the same one I run DBIsam server v4.24 on. I can ping
<<it and there are no permission issues (I have administrator
<<privileges.) The migration module shows all the DBIsam v4 tables and
<<all are checked to migrate over to EDB so I know it is reading the
<<server. Whether I create the folder (on the server machine) or try to
<<have EDB create it I get an EDB #600 File Manager (Cannot create file
<<Z:\Apps\MyApplication\MyApplication..edbcat (OS Error: The system
<<cannot find the path specified.) I have UNC naming as well as a mapped
<<drive (as illustrated here) but I always get this error. The catalog
<<does not seem to get created.
Sun, Dec 17 2006 5:09 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Jan,

<< Is anyone having the same issues as me? Just working with the EDB server
and EDB Manager in WinXP Professional SP2 and everytime I try to either
create a database, a table, a user, drop any of these or migrate a DBIsam v4
database, I get some kind of error (either a EDB 600 error, 9999 error or
others.) >>

There's a locate issue that exists with remote connections, so don't do any
DDL over a remote connection or you'll get an AV and then more errors.

<< I'm now trying to tackle migrating a DBIsam v4 database on a remote
server. The EDB Server is on a server machine (not my development
machine) and is the same one I run DBIsam server v4.24 on. I can ping it
and there are no permission issues (I have administrator privileges.) The
migration module shows all the DBIsam v4 tables and all are checked to
migrate over to EDB so I know it is reading the server. Whether I create the
folder (on the server machine) or try to have EDB create it I get an EDB
#600 File Manager (Cannot create file
Z:\Apps\MyApplication\MyApplication..edbcat (OS Error: The system cannot
find the path specified.) I have UNC naming as well as a mapped
drive (as illustrated here) but I always get this error. The catalog does
not seem to get created. >>

How are you creating the database ?  Also, are the double periods in the
catalog file name above from the actual message or is it a typo ?

--
Tim Young
Elevate Software
www.elevatesoft.com

Sun, Dec 17 2006 11:32 PMPermanent Link

"J. B. Ferguson"
Tim Young [Elevate Software] wrote:

<<Jan,
<<
<<<< Is anyone having the same issues as me? Just working with the EDB
<<<<server and EDB Manager in WinXP Professional SP2 and everytime I
<<<<try to either create a database, a table, a user, drop any of these
<<<<or migrate a DBIsam v4 database, I get some kind of error (either a
<<<<EDB 600 error, 9999 error or others.) >>
<<
<<There's a locate issue that exists with remote connections, so don't
<<do any DDL over a remote connection or you'll get an AV and then more
<<errors.

Oh...OK. Just trying to get a feel for the preview. No problem.

<<<< I'm now trying to tackle migrating a DBIsam v4 database on a
<<<<remote server. The EDB Server is on a server machine (not my
<<<<development
<<machine) and is the same one I run DBIsam server v4.24 on. I can ping
<<it and there are no permission issues (I have administrator
<<privileges.) The migration module shows all the DBIsam v4 tables and
<<all are checked to migrate over to EDB so I know it is reading the
<<server. Whether I create the folder (on the server machine) or try to
<<have EDB create it I get an EDB #600 File Manager (Cannot create file
<<Z:\Apps\MyApplication\MyApplication..edbcat (OS Error: The system
<<cannot find the path specified.) I have UNC naming as well as a
<<mapped drive (as illustrated here) but I always get this error. The
<<catalog does not seem to get created. >>
<<
<<How are you creating the database ?  Also, are the double periods in
<<the catalog file name above from the actual message or is it a typo ?

Using the "Create New Database" menu option. Most likely the problem is
because I am trying to do it remotely, not being aware of the locate
issue with remote connections. The double period is just a
typo...sorry. The rest of the message is verbatim (except the
"MyApplication" is substituted for my real database info.)

Jan
Image