One of my clients is experiencing a whole host of reoccuring errors when running batch style processing on Arev.

The errors can be:

- not enough filehandles

- FS1009 file open errors

- FS133 unknown read problem (reading a DOS file)

- IDX_SETS errors

- System crash due to read failing on 0 record in index

Usually when the system is restored and processing re-run the errors disappear.

We have upgraded their server and memory but this does not seem to have solved the problems. Current set up is as follows:

Server:

Processor P3 1.13Ghx

Ram - 1152MB

Disks 3 * 18 GB Raid 5

Operating System - Windows NT4

Bios A05

Revelation Service - 1.50

Arev - 3.12

Network is 100 Mbps

Filehandles set to 200 on all PCs and server

Revparam file is set to ServerOnly=True

18 PCs on XP and 5 on Windows 98 Second Edition

Does anyone have any information which could help solve these errors as this is causing major business problems for my client and we have run out of ideas?

Thanks

Q1. Are you performing frequent PDISKS?

Q2. Have you ensured that *all* REVPARAM files have at least one blank line underneath the SERVERONLY=TRUE line?

Q3. Have you disabled write-behind caching on the Win98 box?

Q4. Have you checked that the service is actually working / record locks are working?

Peter - where are you located? You're welcome to call me if this assists any.

[email protected]

Thanks Steve, I have spoken with the client and it looks like we don't have those blank lines in all the revparams, so they will change that and we'll see if it makes any difference.

For the other questions, Yes, we do perform frequent PDISKS, but we have several clients on the system and they don't all have these problems.

I think all the write-behind caching has been disabled as we have known about this problem for a while, but they will re-check (apparently they are going to be moving 100% to XP boxes in the next week or so anyway).

Checking that the service is working - we know record locking works if there is more than one user attempting to access the same record - is there anything else we should check on this?

We are located in the UK. Thanks for the offer of phone help - I may yet need to take you up on that!

See how you go with the revparam change.

Steve

Hi Steve

Still no joy. They are getting errors almost everyday, especially the filehandles and the FS133 errors.

The FS133 is trying to read a DOS file from the server.

Any further ideas?

What are the shortcut settings for ARev?

If you have a batch file, what are the command line options for just the AREV.EXE portion?

The Sprezzatura Group

World Leaders in all things RevSoft

Are the errors after a period of time, or intermittent?

One workstation or multiple workstations?

If the PDISKS are to route jobs to one of multiple printers, consider using a batch file to run AREV, set up lpt1,2 and 3 as your target printers (once) using NET USE LPTx …. /PERSISTENT:YES ahead of the arev.exe startup, and then route the jobs using AREV's SETPRINTER command.

Pdisk duplicates the file handle, as I understand it, and I've had (many years ago) the problem where AREV can run out of file handles.

If you're printing to file using PDISK repeatedly then I can't really suggest an option - consider using OSBWRITEs to file instead of PRINT statements and then PERFORM "SUSPEND EXIT COPY /B filename lptx" from your RBASIC program.

Steve

Thanks for everyone's help. Sorry for delay in response but I've been on holiday!

In fact, I asked my client to check again on the blank line after ServerOnly=True, and this does seem to have solved the problems so far.

In answer to the other queries, the Arev command line is

AREV username /XM4096

We are not using PDISKS for different printers, simply to print the spooled file.

But let's hope that it's solved.

Thanks,

Peter

View this thread on the forum...