After completing an end-user upgrade installation (including Lanpaks and MC), I'm getting the following error in OE on one of the workstations when the user tries to access any order(s),

"Workstation unable to open data file OE Order Details (1213)"
OE and the OE Order Details file works fine when opened from the workstation where the application was installed / upgraded from. ie. I can access the data file from the installation w/s The problem occurs only from a secondary user's workstation.

Using OE V8.1C (090731)
Lanpaks seem to be in order
Allwkst run. Checksys utility shows 0 errors (1 warning)

Can you suggest how to fix or change the rights for that w/s? Thanks,
Cary R.

Check the file permissions for the files in the data directory. One or more data files may have been set to not be allowed access by some users. It's easier to set permissions on the folder and have it flow down to all files and sub-directories.

Your client should get the latest System Updater from our website. This will install the most current database interface.

Thanks for the suggestions. I followed everything.
Is there any reason why 3 files in the data directory are saying access denied?
OELIN'1, OELIN'R, OELITM'1
We were able to change the permissions for all the other files except for these three. O/E application is not in use. Did something happen during conversion? (Server has been rebooted)

Also, at this point I'm now getting a "product not registered within the 60 days and will not run" message when trying to start OE. (It's only been three days)
This happened after installing the latest System Updater. (I assume this will go away once we receive the new license?)

Perhaps these files are locked on the server? You did say that the server was rebooted.

You may need to restore the data pre-conversion and try again. There was an issue with a particular database interface version that did not properly assign permissions during a conversion, most often found during the Payable upgrade and data conversion. This has now been addressed, as long as the latest System Updater has been installed, as you indicated is the case.

If an unregistered Adagio product has the sign-on date changed to a date more than 60 days in the future, that can trigger the end of the non-registered period. Yes, this will go away when license number is received and entered.

Complete restore of the data seems to have done the job. For some reason there was no way to change the file attributes of those 3 O/E data files. (Had the networking guy look at it too).

The second conversion went through much smoother.
Thanks for your help! Great as always!

P.S. In A/R, after conversion all the users (customers) got set to inactive. Is that typical?

Cary:

I think you mean that all of the customers got set to inactive. The new version of AR is reportinjg customers that are inactive whereas older version just ignored these customers. This gives the appearence of customers having been set as inactive durring conversion but I have found by checking the preconverted data that these customers were inactive then as well.

Yes, customers. (duh)

AR 9.0A is setting active customers to inactive (for some reason). This includes customers who were active pre-conversion.

It isn't a big deal as the user is able to change them back to active quite easily.

Has anyone else noticed this?

Thanks Doug!

AR 8.1 did not really concern itself with whether customers were flagged as active or not. AR 9.0A does care. I think you'll find that your customers were actually marked inactive in 8.1. If you have the unconverted data around (and 8.1 available to check them), you might check a couple to see if this is true.

Interesting. Good answer.
Now you've got me curious..
Thanks Andy