Can anyone tell me what causes Access Violation errors? I seem to quite often encounter them.

Regards,

Suresh

Windows' Access Violations can occur for many different reasons - from an unexpected click or procedure being performed by the User, to actual program related problems or data conditions. They seem to be more common in the 32-bit Windows environments (NT, W2K, ME, XP etc), whereas "GPF's (General Protection Faults) were more prevalent in Windows 9x versions.

When you encounter them, can you determine if it always seems to occur during a specific procedure, in a specific program or when you have the same programs open at the same time?

Do you have current versions of Windows O/S service packs - ACCPAC Plus WSM and/or Adagio releases? Do you have NAV running in the background? Are you multi-tasking?

Have you encountered a GPF or other Windows related error, and not rebooted your PC?

Is this a new PC and/or O/S?

All these types of things need to be looked at, and before we can give an accurate response, we would need more specific information.

Thanks

Regards

[This message has been edited by Softrak Support (edited 12-11-2001).]

Whoa! that's a lot to get down. The next time I have an error occuring, I will take note and report all.

Just a couple of quick queries and comments, if I may:

1. I have Adagio installed on a partition on a local drive for testing purposes, and have a shortcut directly to the program itself on the desktop. I also ran the workstation setup (which I presume copies certain files onto the local drive). This is for the client-server setup for actual use. The local drive points to D: and the client-server pointer is set to T: . Is there a likelihood that errors can be caused from this setup?

2. Access errors seem to happen most often with the Adagio Inventory item queries.

[I have a Win2K Professional machine with all updates, NAV Corporate Edition running in the background, and Accpac Plus WSM SP2].

Regards

Suresh

Well, having Adagio installed locally as well as on the Server is not really the recommended setup, but if proper pathing (using the UNC) is used, and you have specified the correct EZTASKS and CURRENCY locations for the data you are using, then there should not be a problem. I am not really sure about how this would affect things on a partitioned drive (which is still all one local drive), but I have heard of problems when dual installs have been done where the pathing has not been specified correctly (this seems to be more of a problem on a Peer to Peer environment).

Access violations could occur as a result of this, but again, I cannot say for sure.

Are you using the current release of ICWIN? V6.8A (010710), as opposed to the first release?
I have W2K Professional as my O/S as well. What exact steps are you using to do the Item queries? I will see if I can duplicate those here.
Are you using multi-segmented items ? or one-segment? Do the item numbers use ALL of the 16-characters allowed (including any formatting characters)?
Were these items originally entered by ICWIN, ICDOS or were they imported from another application?

What you could do is some elimination testing...
Disable NAV in your taskbar, then use Adagio ICWIN that way for a day or two to determine if NAV is causing the conflict. We do know that having NAV (maybe only certain versions of it) installed and running affects the performance speed of Adagio especially when run from an NT Server. This may not be the case with Novell, however ? and to be fair, Access Violations are not a known result, just slowness.

If this does not prove fruitful, then perhaps reinstalling Adagio IC would help to put things back in order, maybe a program file to do with this function has become unstable or damaged in some way. If it is the Server ICWIN that does this, then rename the ICWIN program directory first, then reinstall it to the Server. By the same token, if this occurs only while using your local Adagio IC, then perform this same procedure on your PC.

Another thought ? if you have upgraded the Server version of ICWIN, you should ensure that any station that uses it, has the ALLWKST.exe performed again after upgrading, as this would install the newer version workstation files to that PC?s local drive. There could be problems if this crucial step is not performed after upgrading.

Thanks, Suresh

I have the latest version of Adagio installed. I've noted the questions that you have asked, and the next time I am able to get IC or another program to crash, I will get all information and send over to you.

I will also check the workstation setup to ensure that the latest version has been installed - it may quite likely be the reason for the crash.

Could you add this to the Wish List - that when a program is updated, the workstations can also automatically update itself when users log in.

Thanks again.

SS

I can certainly add your 'wish' to R&D's list, yes.

Regards