My client has been getting 1013 errors in OE, with increasing frequency...now they are occurring in AP.
No read/write problems reported by syscheck
Latest versions of software, Jan 2013 SysUpdater

Ideas?

Hi Tony,

According to the development notes I have access to, an error 1013 represents 'permission denied opening data file'. In other words, the account the program is running under has insufficient rights to open the file for reading and writing, but can open the file as read only.

You mentioned that there are no read/write errors reported by ChkSys, but that doesn't check every single data file, just the data folder in general.

The only report of this specifically in OE was in 2008 and had to do with the version of ADS32 - and you indicated that the most current one was downloaded.

Can you indicate what the user(s) were doing in OE and AP when they receive the error?
Does the 1013 error happen if the same process is run in sample data - to attempt to point the issue to either the data directory or the program folders?

In addition to rights, it could be an overzealous anti-virus software. Another posting on this forum for error 1013 could be a bad network card.

I'm afraid I can't get much more specific that that.

The problem is intermittent, which causes me to lean more towards a hardware failure. The client also has 3 datasets operating concurrently and only experiences the problems in one (the other two are considerably smaller). They are even getting these errors when running integrity checks, normally with the adjunct "Unable to read unopened file [insert random file name here]".
The errors have been occurring randomly (making it hard to reproduce) in OE with increasing frequency for some time, they have only just started occurring in AP.
I am currently running a full set of integrity checks locally on a separate computer...but the dataset is over 2GB, so that may take some time...

Here is a final follow up to this problem...

In an act of straw-clutching I had them turn OpLocks (back) off...and lo, there was the sound of a heavenly choir and verily, the problem doth disappear and plague us no more.

Now one wonders...is the intimated speed increase worth it?

Tony:

It's a double edge sword. The speed improvement can be substantal. The risk is even bigger. The client gets all of the benefit and the dealer gets all of the risk.

I will only implement OpLocks = On if my client has all Windows 7 Pro (or better) workstations and Windows 2008R2 server. No peer to peer and no older equipment connected to the network allowed (even if not used for Adagio).

This policy is purely based upon my experience with my large client base. Sometimes OpLocks will work in a lesser environment but I've been burned by this often enough that I can no longer afford the risk.

Doug:

Since turning OpLocks back off, the client hasn't noticed a terrible decrease in speed...they do have a 2.2GB dataset, so waiting for a report isn't that unusual for them...lol!

They do have a new server with the latest Windows Server software (and all the updates), all the machines are Win7, the hardware and wiring are also new.

They only experienced the errors in the large dataset, two smaller datasets never exhibited any of the behaviour.

Such is life, I'm just glad to have found a/the solution and felt it important enough to share.

If the client is using a Domain Controller, and are running it on a virtual machine with insufficient horsepower, then the failure of the domain controller to properly authenticate a file access in the requisite time will result in denial of access (as though the network cord has been unceremoniously yanked from the machine). This makes Adagio VERY unhappy, and it doesn't have many ways to complain about a file suddenly "disappearing".

A virus checker insisting on scanning a large database can make it appear to "disappear" to the application. Again, this makes Adagio very unhappy.

Tony:

Based upon your comments, then the server doesn't have sufficient horsepower to run a large database (which can be exasperated in a virtual environment). Most likely this will be from incorrectly provisioned hard drives.