Paradox 5 and Novell

[carstenFH]

Hi

I have a major problem, migrating from Novell 5.00.09
to Novell 5.60.03 made my paradox go bananas

When I try to open a *.db file, I am getting this error:
Not enough space available at M:\test\paradox.dir

But there is plenty of space, more 5 GB and the path
'paradox.dir', well it don't exist.

Any ideas how to solve it ?

Best Regards
Carsten

 

[nawtykitty]

It sounds like your users do not have their private directory defined and that your database directory is the default directory they're using when they fire up the program. When this happens, Paradox typically assigns the working directory as the user's private directory. This will then also work against you because it will lock the file as well. Try resetting your user's working private directory under their personal workstations first. More than likely that should help you skirt the mapped drive error message.

Basis for my reason
*I believe the root of your problem is that Paradox thinks that it needs to use M:\test\paradox.dir as a sort of swap file. That is generally not such a great idea when networking. You want the workstation to handle the file-swapping then update the tables as you work. So you'll want to redirect your users to their own system for a working directory.

 

[carstenFH]

Both working and private directory are defined to point at
the workstation.
Working dir: c:\test
Private dir: c:\test\priv

After starting Paradox my application starts and I
define alias for m:\test, this have been working fine
for more then 5 years, but suddenly it works no more.

Carsten

 

[footpad]

Carsten,

If you've checked the common things (and it sounds like you have), then it's time to check the uncommon ones:

1) Have everyone exit Paradox and then see if there are stray .LCK left over. If so, delete them.

2) Verify the table structure. If it passes, try deleted and recreating the indexes. If the problem still occurs, then rebuilt the table directly.

3) Make *certain* everyone's using the same .NET file and that everyone has full r/w access to that directory. Also, people need full r/w access to their private directories as well.

4) Verify all connections, cables, and required terminators.

5) If the files were restored from a read-only medium (e.g. a CD/DVD), make certain you've cleared the read-only flags after copying them to the server.

6) Verify the packet buffer sizes are larger than your typicaly table block size, e.g. 4KB as opposed to the default 1.5KB.

7) Scan Novell's site to see if there are any preported problems for your version of Client32. If you can't find any, try rolling back to the previous minor release. They have periodically introduced buggy versions of Client32 that are later patched.

That's about everything I can think of.

 

[nawtykitty]

I have not been in the Novell environment since 4.11. For some reason after upgrading our servers from 3.12 to 4.11, some of the users and database folders had their r/w status changed. I personally had thought it was a hiccup from a pre-existing problem (or the user behind the keyboard during the upgrade process). I just double-checked the r/w status on the folders and moved on. I never researched if that was a known issue or not. However, Footpad has made a good point in double-checking the r/w status on your database's folder. It may have inadvertantly had its r/w settings changed during the upgrade process, and that could explain your users having a "space error". This issue may have popped-up for you now that you have upgraded to 5.60.03.

 

[carstenFH]

Footpad >> Thanks a lot for your help, your steps 1-6 I've already done them 2 weeks ago, haven't tried no. 7 yet, but believe me I will.

nawtykitty >> The same to you - thanks a lot.
My r/w settings are unlimited, I've tried to rename the database folder and make a new one, restoring all files to the new folder, but I can't r/w *.db files at that drive.
If I create a folder on my workstation, it works perfectly.

Well, after upgrading there no problems for 2 weeks, then somebody removed some old pdoxdos 4 files - we didn't need them anymore, thats when the crash happen.
We tried to restore the files, but so far no good.

A nice weekend to both of you.
Carsten

 

[carstenFH]

>>>We tried to restore the files, but so far no good.

What I meant by that is, we succeded in restoring the files, but it didn't do any good.

 

[dcpking]

Carsten,

look back at your post:

"My r/w settings are unlimited, I've tried to rename the database folder and make a new one, restoring all files to the new folder, but I can't r/w *.db files at that drive.
If I create a folder on my workstation, it works perfectly."

Your first statement is flatly contradicted by your subsequent paragraph. In addition, your required settings for Paradox data directories and Net Directory are NOT "r/w", but "r/w/c/d" - you need to create and delete lock and other files during operation, no matter who you are !

Mike

PS you'll also find more Paradox info, including all the FAQs, at

mirwin.homestead.com

 

[carstenFH]

LeMike

I know it sounds wierd, so lets take it from the top

1. Over a month ago we setup a new server and opgrading Novell.
2. The directory structure is the as the old server infact it's a true copy.
3. For 3 weeks everything works perfectly, smooth and faster, even Paradox.
4. But 2 weeks ago I had to move my application directory back to the old server, from where I'm running it now.
5. Every user's NET DIR are still pointing at the new server.
6. The only changes made to the new server in that period is, deleting som old Paradox DOS files.

I know it sounds like an r/w/c/d problem, but every user can still write to pdoxusrs.net (new server), but maybe our problem could be the filesystem, it's NTFS at our new server and FAT32 at the old one

But I can very well be wrong.

LeMike - thanks for your comments.

Regards
Carsten

 

[carstenFH]

I see that is was easy to misunderstand what I was writing !

LeMike postet this
>>>"My r/w settings are unlimited, I've tried to rename the database folder and make a new one, restoring all files to the new >>>folder, but I can't r/w *.db files at that drive

Of source, who gets the point of that - what I meant was that my r/w/c/d settings are unlimited, and I can restore all files to the new directory, BUT THROUGH PARADOX I can't open/create *db files in that new directory.

 

[dcpking]

Hi Carsten,

Firstly, don't panic - I've seen these before, and they're _usually_ (tho' not always) due to file system problems.

Could you test things and answer these questions for me, please:

1. Log in as yourself (administrator group, I suppose) at your own workstation and create these directories:

c:\pdx\work
c:\pdx\priv

2. Launch Paradox as follows:

c:\Program Files\...\pdxwin32.exe -c -wc:\pdx\work c:\pdx\priv

(all on one line!)

3. using Windows Explorer, create a new file directory beside the one where you're having problems

4. try creating, opening, and editing a table there.

 

[carstenFH]

Hi LeMike

No problem in step 1 to 3, but step 4 gives me trouble
I still can't create/open *.db files.

But one more thing - I don't have a pdxwin32.exe, but a pdoxwin.exe

Carsten

 

[carstenFH]

Hi LeMike

I overlooked something at first.

My Paradox installation directory: C:\pdoxwin

Your command in step 2 sets my working dir to: c:\pdx\work
but sets my private dir to: c:\pdoxwin\private

Carsten

 

[dcpking]

That's ok - the last bit should have been preceded by "-p", but it doesn't really matter, as you'll always have rights to your home directory !

More to the point, you should have been able to access the new directory and create/edit new tables there.

However, what worries me is that you say

"I don't have a pdxwin32.exe, but a pdoxwin.exe"

indicating that you're using a 16-bit version of Paradox. The last time one of these was released was in early 1995, so it's REALLY time to upgrade. However, for now, things to look for are as follows:

* you never said what OS you're using locally; if you are using Windows 2000 or XP then you MUST set up compatibility for Paradox (apcompat.exe on the Windows 2000 CD; right-click the program icon and choose Compatibility in XP)

* you say that you have 5 GB or so free. Reduce that to less than 2 GB - or, even, 500 MB - in some way (try reading/writing to a Zip disk or floppy, or to a 128 MBy USB disk) to test things out.

hth

Mike

 

[carstenFH]

Hi Mike

Well - we never opgraded Paradox and possibly never will, I'm writing the same application in Java on top of a MySQL db, but it will take me another 3-4 month to finish it.

Our Paradox version is from the early days of windows 3.1, so it's definitly a 16-bit version.

There is another thing - I can see that I didn't read all the words in your post Oct 19, 2003(I skipped the last word in step 4), which means that I CAN create tables in c:\pdx\work\, but not on our new server!
Sorry - sorry !

The OS locally is win98 and XP depending on workstation.

I still hope for proposal.

Carsten

 

[dcpking]

One last possibility: check that your workstations have the latest Novell client software installations - from Novell, not MS !
If it still doesn't work, and if you _are_ using compatibilty on the XP machines, and if there is only a small amount of disk available (5 GB may well cause any 16-bit app to choke), then I'm afraid that you'll have to refer the problem to your Novell admin, as it's almost certainly the Novell system that's stopping you from writing. Something may have been changed on the Novell side or with the group permissions that concern the Paradox users.

Mike

 

[nawtykitty]

I am going to have to agree with Mike on his last post. If all bases are covered on the client side, then the problem must reside on the Novell Server. Like I had written before, I had to double-checked the r/w/etc status of all of my files and folders after upgrading. Once that was done, everything began to work properly. Another thing to consider is that the database may have become corrupted over the course of the past few weeks. Basically what it boils down to is this:

1.) Before the Novell Upgrade --> Database worked fine
2.) After the Novell Upgrade --> Database acts poopie

You might want to contact Novell about the version you have upgraded too and see if there are any compatability issues with your version of Paradox. Your version of Paradox may be looking for a certain aspect in your Novell server that may no longer exist due to the upgrade. Just a point to consider

 

[carstenFH]

Well - I get the picture!

If I figure out something I'll post it here.

Thanks for Your help soo far.

Regards
Carsten