One or our clients is generating an error upon logging into BankRec. "Unknown OS Error while opening BankRec AP Retrival, (1342)".
BANKREC 8.1A (070922)
I'm currently onsite. The problem can be replicated across users/across network. Data integrity check in both BR and AP reports no errors. The files touched upon logging are the BRGLOB, and the BRBRSCGL. Renamed the BRBRSCGL and tried to login again. New file was created, but error still exists...

Any ideas?

Also tried program re-install!.

Hi PWC,

AP creates one of these files for BankRec retrieval when checks are posted: BRAPRETR.dat or BRAPMCTR.dat (depending on whether multi-currency is enabled on the data or not).

It sounds like when attempting to open the data, the program is unable to read the data file. If this is the case, then reinstalling the program will not help, unless the problem was that a dictionary file was missing or out of date.

Can you open sample data successfully?
If you see either of these 2 data files above, can you rename the file and then open BankRec successfully?

If the above works, then there is some problem either with the file itself or the program's ability to read the file. The Integrity Check does not read this file, as far as I can see.

GridView can access this file - perhaps attempt to take a look and see if the information looks 'reasonable'.

Hello Softrak,

File BRAPRETR.dat was indeed the problem (site d/not have MC). Renamed and the error has disappeared. However, the now renamed BRAPRETR.old file contains data of checks posted in AP. I opened the file with GridView and it contains 35 transactions. Will they have to manually re-enter the data in BR???

If that file is corrupt, they will need to manually enter the checks in BankRec. We are unaware of any BankRec problems trying to read this file when it is not corrupted - it may be faster to print the GridView results out for them and get them manually entered.

The next time your client posts AP checks, this file will be recreated. You may want them to make a backup of their data prior to posting AP checks, in case the problem re-occurs.

Hi,

We are with PwC @ the moment. This error has occurred on our system again, and we're trying to determine if there's something we are doing wrong that's causing the problem...

Westrading...

Is this the first time you have tried to access BankRec since Mar 11th? Or have you been able to retrieve AP checks between then and now? If this issue is sporadic then it may be difficult to track down.

If this is the first time accessing BankRec since then, the issue is likely replicatable and thus potentially easire to isolate. In this case, if PWC can make a 'related data' backup from BankRec and send to Softrak support (either by email for a smaller file, or upload to our website for a file > 5Mb), we could try to isolate this. The situation could be either AP creating the file, or BR trying to read it.

Softrak,

I'm emailing a related dataset backup of Westrading's data. It appears they were able to create one AP batch after the BRAPETR file was created and were also able to successfully retrieve the entries into BRec. However, the very next AP/BR transaction batch caused the error to re-occur.

I'm emailing the backup file to you so you can look @ this and will provide further details.

Of Note: Even with their data, I'm unable to re-create the error on my system.

Thanks for the data. I cannot duplicate the problem on my system either. The file contained AP checks from Feb 2008 and posting sequence 9, though there are posting sequences in AP up to 18.

There are dozens of orphaned batches in their AR/AP/GL/BR data (what you sent) and I suspect that data had been restored on top of existing data. There is more to this situation that what is on the surface.

After some further investigation, this error likely was due to a restriction in Windows permissions, more specifically with the network 'share' permissions'. When the domain administrator logged onto the workstation, they did not get the error when opening BankRec. But the user did, meaning that user did not have sufficient rights.