DOS Error 64

Post Reply
User avatar
cdmmaui
Posts: 653
Joined: Fri Oct 28, 2005 9:53 am
Location: The Woodlands - Dallas - Scottsdale - London
Contact:

DOS Error 64

Post by cdmmaui »

I have a client receiving a strange DOS error 64. They have installed server 2003 standard edition without active directory. However they copied data from another server 2003 standard edition running active directory. Is it possible permission rights are causing a problem?

Thank you,
*~*~*~*~*~*~*~*~*~*
Darrell Ortiz
CDM Software Solutions, Inc.
https://www.cdmsoft.com
User avatar
cdmmaui
Posts: 653
Joined: Fri Oct 28, 2005 9:53 am
Location: The Woodlands - Dallas - Scottsdale - London
Contact:

Post by cdmmaui »

Hi Enrico,

Thank you. I did look up the code but I wanted to find out what caused the message in the first place.
*~*~*~*~*~*~*~*~*~*
Darrell Ortiz
CDM Software Solutions, Inc.
https://www.cdmsoft.com
User avatar
Antonio Linares
Site Admin
Posts: 37481
Joined: Thu Oct 06, 2005 5:47 pm
Location: Spain
Contact:

Post by Antonio Linares »

Darrell,

Are you using \\machine_name\... somewhere in your app ?
regards, saludos

Antonio Linares
www.fivetechsoft.com
User avatar
cdmmaui
Posts: 653
Joined: Fri Oct 28, 2005 9:53 am
Location: The Woodlands - Dallas - Scottsdale - London
Contact:

Post by cdmmaui »

Dear Antonio,

Yes, we are using UNC to access databases. We have created the share name name and set the permissions on the server. For example \\njprosvr\winpack\mr.dbf to open database.

Regards,
*~*~*~*~*~*~*~*~*~*
Darrell Ortiz
CDM Software Solutions, Inc.
https://www.cdmsoft.com
Randal
Posts: 250
Joined: Mon Oct 24, 2005 8:04 pm

Post by Randal »

cdmmaui wrote:Dear Antonio,

Yes, we are using UNC to access databases. We have created the share name name and set the permissions on the server. For example \\njprosvr\winpack\mr.dbf to open database.

Regards,
Did you find a cause and/or resolution for this problem? I have a customer that recently upgraded to our FWH/xHarbour app from the FW 16-bit version and they are getting this error regularly. We are not using UNC names but a mapped drive to access the server.

Thanks
Randal
Post Reply