We are experiencing the following:

Sales Analysis 8.0A when printing report:

"Access violation at address 0049A8F9 in module SRWin.exe, Read address 00173008."

also in SA, AR (8.1A) and IC (8.1A)when printing reports:

"Cannot open file F:\Softrak\Data\Our data set\SRTM0052.XXX";

"One of the files is not accessible. It's been locked"; and

"The data is locked"

and when doing back ups:
"Unable to lock data set exclusively" when there is actually no one else using the dataset. Even with everyone else completely out of the programs, the errors occur. Only when the workstation is completely rebooted are we able to complete the tasks.

We have 15 Lanpaks (more than enough) which were recently upgraded to 9.0A.

Data Integrity is good in AR and SA. IC has a few invalid unit of measure errors.

Just now it is reported to me that an error message "Critical error: [1] Unknown error deleting dataset" has occurred when attempting to post an IC adjustment." But it did post.

We did install anti virus software in the last couple of days, although it doesn't seem like that should be relevant.

Something is wrong. Please advise.

Thanks
Jody

What anti-virus software did you install?

Norton is known to be a poblem at may sites. Make sure that the Adagio data and program directories are excluded from the anti-virus scanning. Norton delays opening the file while it does its scan (each time the file is opened). Sometimes this makes the software trying to open the file think it has "disappeared" unexpectedly.

Note that Softrak folder on workstation should be excluded as well as Softrak folder on server.

When someone closes a program via task manager, files can be left open on the server. Could it be that a network card is failing so a workstation intermitently loses connection to the server, leaving some files open? Rebooting the workstation will close those files.

I see that your data path has spaces in it. I wonder if that makes a difference. Can you duplicate the errors when printing the same report based on the sample data in \softrak\srwin\samdata?

If the EZSEMTAB file in the data directory is not cleaned up by the system, then this might make Adagio think a user is doing something when in fact they are not. Try getting all users out of Adagio and delete this file from the data directory.

The last 'critical error 1' message you reported is generic and tends to report that the program wanted to write/access/delete a data file and was prevented from doing so. Anti-virus software could potentially get in the way of this, but there could be other reasons as well.