I tried to set up for the first time a database on a mapped drive (pointing
to a computer which is NOT the server). I get an error 11293, folder is
empty or invalid. The folder selection in the server administration finds my
mapped drive with no problems, the error occurs when I try to save the new
database. Any idea how this should be set up? Thanks.

Robert

Robert,

<< I tried to set up for the first time a database on a mapped drive
(pointing to a computer which is NOT the server). I get an error 11293,
folder is empty or invalid. The folder selection in the server
administration finds my mapped drive with no problems, the error occurs when
I try to save the new database. Any idea how this should be set up?  >>

Are you running the DBISAM database server as a service ?

--
Tim Young
Elevate Software
www.elevatesoft.com

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:808C5B2B-7FD1-4C18-A086-85758BE94932@news.elevatesoft.com...
> Robert,
>
> << I tried to set up for the first time a database on a mapped drive
> (pointing to a computer which is NOT the server). I get an error 11293,
> folder is empty or invalid. The folder selection in the server
> administration finds my mapped drive with no problems, the error occurs
> when I try to save the new database. Any idea how this should be set up?
>  >>
>
> Are you running the DBISAM database server as a service ?
>

Yes.

R

Robert.

obviously are the mappings of your computer and server different looking the
same target computer. You must set path for database on new computer
regarding the mappings from the server point of view as you were at the
server side.

Iztok Lajovic


"Robert" <ngsemail2005withoutthis@yahoo.com.ar> je napisal v sporoèilo
news:8051CF64-5E93-41F4-A0BA-077EC57FAA1F@news.elevatesoft.com ...
>I tried to set up for the first time a database on a mapped drive (pointing
>to a computer which is NOT the server). I get an error 11293, folder is
>empty or invalid. The folder selection in the server administration finds
>my mapped drive with no problems, the error occurs when I try to save the
>new database. Any idea how this should be set up? Thanks.
>
> Robert
>

"Iztok Lajovic" <iztok.lajovic@amis.net> wrote in message
news:029653FF-463E-46F1-A7CE-47D297C8821C@news.elevatesoft.com...
> Robert.
>
> obviously are the mappings of your computer and server different looking
> the same target computer. You must set path for database on new computer
> regarding the mappings from the server point of view as you were at the
> server side.
>

Not so obvious. I'm running the server admin program on the server. The
directory lookup finds the mapped drive. But  when I try to save it, I get
the 11293.

BTW, the same problem crops up if I use UNC instead of a mapped drive. This
was my first attempt at running with a database in a machine that is not the
server. There has to be a way to do this.

Robert

Robert,

If I am reading your problem correctly, the database folder is relative
to the server, not any other machine. So, if your data folder is on the
C:\ drive of the server in the "Apps\Data" folder, you should be
creating it in C:\Apps\Data. The data needs to be on the server
machine, not on another machine.

--
Regards,
Jan Ferguson [Team Elevate]


Robert wrote:

<<Not so obvious. I'm running the server admin program on the server.
<<The directory lookup finds the mapped drive. But  when I try to save
<<it, I get the 11293.
<<
<<BTW, the same problem crops up if I use UNC instead of a mapped
<<drive. This was my first attempt at running with a database in a
<<machine that is not the server. There has to be a way to do this.

Robert

"Jan Ferguson [Team Elevate]" <jbNOSPAMfergusonATgmailDOTcom> wrote in
message news:B090144F-AB30-4C6C-A3D2-01D65E19D72D@news.elevatesoft.com...
> Robert,
>
> If I am reading your problem correctly, the database folder is relative
> to the server, not any other machine.

I understand that.

So, if your data folder is on the
> C:\ drive of the server in the "Apps\Data" folder, you should be
> creating it in C:\Apps\Data. The data needs to be on the server
> machine, not on another machine.
>

Is your last statement true? Seems kind of odd, to place such a limitation.
If server1 has access to \\server2\..\data\dbisam, why is it that dbserver
and the server administration utility would not be able to access the data
on server2? Undertand that this has nothing to do with the workstations even
knowing about server2. The workstations talk to dbserver in server1.

I still think there has to be a way to do what I want. I'm missing some
critical piece of information. Or, there is a bug in the server
administration progrm (I doubt it).

Robert

Robert wrote:

<<<<So, if your data folder is on the
<<<<C:\ drive of the server in the "Apps\Data" folder, you should be
<<<<creating it in C:\Apps\Data. The data needs to be on the server
<<<<machine, not on another machine.
<<
<<Is your last statement true? Seems kind of odd, to place such a
<<limitation. If server1 has access to \\server2\..\data\dbisam, why is
<<it that dbserver and the server administration utility would not be
<<able to access the data on server2? Undertand that this has nothing
<<to do with the workstations even knowing about server2. The
<<workstations talk to dbserver in server1.

Yes...it is true. From the DBISAM Manual (Note the first sentence):

"Use the RemoteDatabase property to specify the database name on the
database server where the database tables are located for a
TDBISAMDatabase component. This property only applies to
TDBISAMDatabase components that are connected to a remote
TDBISAMSession component whose SessionType property is set to stRemote.
With remote sessions a database is synonymous with a logical database
name on a database server. For TDBISAMDatabase components that are
connected to local sessions you should use the Directory property to
specify the database."

You can find this reference here:
http://www.elevatesoft.com/manual?action=mancompprop&id=dbisam4&product=
r&version=2007&comp=TDBISAMDatabase&prop=RemoteDatabase

------------------
Regards,
Jan Ferguson [Team Elevate]

Robert,

<< Yes. >>

That's the issue, then.  By default, the account that services run under
does not allow for access to drives that are external to the server machine.
You'll need to specify a different account for the service to run under via
the service properties dialog, and that account will need to have the proper
rights to access the external drive.

--
Tim Young
Elevate Software
www.elevatesoft.com

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:A6B78573-2AF3-48DB-81DA-CBA47B2EBB06@news.elevatesoft.com...
> Robert,
>
> << Yes. >>
>
> That's the issue, then.  By default, the account that services run under
> does not allow for access to drives that are external to the server
> machine. You'll need to specify a different account for the service to run
> under via the service properties dialog, and that account will need to
> have the proper rights to access the external drive.
>

Thank you.

Robert