What s going on?
Solution: This typically is the result of installing Eventus in one user account (often the special login named Administrator in Windows XP Professional), then trying to use it from another without further ado. If you go back to the same login used for installation and find that you can successfully run Eventus, then only a few simple manual steps are needed to make Eventus available to other user accounts on the same computer. To make Eventus available to another user on the same computer, please close SAS and copy the following files from the first user’s My SAS Files folder (typically something like My Documents\My SAS Files\9.1) to the next user’s My SAS Files folder: formats.sas7bcat nyupdat.sas7bdat (if present) nyupdat.sas7bndx (if present) sasmacr.sas7bcat templat.sas7bitm If some of the above files exist, overwrite them with the newly installed copies, except in the rare event that the user has done advanced SAS programming to create stored compiled macros or custom SAS format
Solution: The most common cause is installing Eventus in one user account (such as an administrator account used only for installing software), then trying to use it from another without following the additional steps advised by the setup program. To make Eventus available to another user on the same computer, you may want to re-install Eventus in the account in which it will be used. (This advice is displayed at the beginning of the setup program). This is desirable because the user will then be able to check for and install hotfixes without switching accounts and manually copying files. If you are installing for multiple users or if the end user’s account is not allowed to install software, please try the following instructions. Please close SAS and copy the following files from the first user’s My SAS Files folder (typically something like Documents\My SAS Files\9.2) to the next user’s My SAS Files folder: formats.sas7bcat nyupdat.sas7bdat (if present) nyupdat.sas7bndx (if present)
