What is my Windows password?

The Windows login and password is usually set up by your IT department. If you are using an AMS machine that we sent to you, it was most likely set up with an Administrator login of "administrator" and no password. Your IT department usually changes this for security purposes. For help with you Windows password, please speak to your IT department as we are unable to provide a backdoor password for Windows.

AMS also requires a password for certain functions. For more information on your AMS password, see the Setup Menu section.

What does “The Archive Drive has not been Setup or the Archive drive and directory cannot be accessed” mean?

When AMS is started, it verifies that the archive database can be located. This message at startup indicates that one of the following has occurred:

1. The archive drive was never setup. To correct this, do the following:
   1. Start AMS. Click on OK when the warning message is displayed.
   2. Select System — Setup menu option. You will be required to enter the AMS administrator password to access this function.
   3. Select Archive Setup function on the Drive and File Locations page.
   4. Change the drive and/or directory if necessary. In most cases, the default drive and directory are satisfactory. You may also set the permanent archive drive (the drive used to write permanent archive floppy disks — typically set to A) and the number of days that data should be aged before being moved to the archive database.
   5. Click on OK to have AMS create the archive database in the displayed location. AMS will create the directory if it does not already exist.
   6. Click on Save Setup to save any changes you have made to the setup.
2. The archive database is located on the network server but the server cannot be accessed. To correct this, do the following:
   1. Make sure the server is running. If it is not, turn it on then shutdown and restart your workstation.
   2. Make sure the workstation AMS installation setup is set to "Workstation" and the server drive is correctly mapped.
   3. Make sure the AMS Archive Setup is correct on your workstation. Check this using the System — Setup — Drive and File Locations — Archive Setup function.
3. The archive database has been deleted. To correct this, do the following:
   1. Locate the most recent backup of the Archive Database. This backup must have been created using the AMS Backup function.
   2. Select the System — Setup — Drive and File Locations — Archive Setup function to recreate the archive database.
   3. If you are using AMS Version 2.0 or later, use the AMS Data menu Restore function to recover the data from your backup disk(s).
   4. If you are using an AMS Version prior to 2.0, insert your AMS Installation CD. Select the Upgrade function from the Setup menu. Select the Recover option from the Upgrade menu and follow the prompts to recover your archive data from the backup disk(s).

What does “You are attempting to run an unknown version or the network server cannot be accessed” mean?

When AMS is started, it verifies that the shared database on the server can be accessed and that the AMS version you are accessing is correct. This warning message is typically caused by one of the following:

1. The shared database is located on the network server but the server cannot be accessed. To correct this, do the following:
   1. Make sure the server is running. If it is not, turn it on then shutdown and restart your workstation.
   2. Make sure the workstation AMS installation setup is set to “Workstation” and the server drive is correctly mapped.
   3. Make sure the network is operating correctly.
2. The AMS version installed on the server and the AMS version installed on the workstation do not match. To correct this, you must install the same AMS version on both the Server and Workstation using the AMS Installation CD.

What does “Invalid Configuration File” mean?

When AMS is started, it verifies that the configuration file is in the correct format. If it is not, AMS rebuilds the configuration file and all settings are reset to the defaults. If this occurs, you must reset the AMS setup for your location including remapping the server drive before resuming work in AMS.