Support

Here you can find resolutions to common Amicus issues, as well as links to information and other troubleshooting resources for Amicus. NOTE: These suggested solutions should be implemented by your designated administrator for Amicus.

ALSO: Except where noted, these tips apply to Amicus Versions IV and V.

For general computer troubleshooting tips, visit Tech After Hours

 
ISSUE:
In Amicus V/V+, when switching accounting systems in Amicus Administrator, you get a "too much text" error. This occurs because each time you make a change in the accounting system settings, the accounting configuration data file grows larger and, eventually, hits a size limitation.
RESOLUTION:
You'll need to have Amicus tech support fix the data file for you. In Amicus Administrator,
  1. hold down the CTRL and SHIFT keys while clicking Database | Utilities | Accounting Settings
  2. in the Accounting Settings window that appears, take note of the path displayed, or change the path to your Desktop, then click the "Save to file" button, making sure to leave the name of the file as "aa_acc.dat".
  3. e-mail this file to support@amicusattorney.com requesting that they assist in fixing the file. Tech support will then send back a corrected file, which you will:
    1. save to a temporary folder on the server hard drive
    2. in Amicus Administrator, hold down the CTRL and SHIFT keys while clicking Database | Utilities | Accounting Settings
    3. in the Accounting Settings window that appears, change the path to the location of the corrected aa_acc.dat file, then click the "Load from file" button
    4. check your accounting settings to make sure everything is correct (more particularly, the Amicus-PCLaw mappings for timekeepers)
 
ISSUE:
Amicus Administrator Version V exits improperly when you enter the team or attorney settings after enabling the TimeSlips (32bit) link for TimeSlips 10.5.
RESOLUTION:
Updated DLL files are needed. Download this zip file (1.633Mb), extract its contents (4 DLL files) into your c:\windows\system directory (after first exiting TimeSlips and the Amicus Administrator).
 
ISSUE:
How to implement the Amicus-QuickBooks link.
RESOLUTION:
Use the QuickBooks link guide
 
ISSUE:
How to implement the Amicus-TimeSlips link.
RESOLUTION:
For 16-bit (TimeSlips v8), use the TimeSlips 16-bit link guide
For 32-bit (TimeSlips v9 and later), use the TimeSlips 32-bit link guide
 
ISSUE:
When you start Amicus, you get a message that says, "You are now running offline."
REASON:
1. Your workstation is not connected to your network server, OR
2. Your workstation's network "drive mapping" for Amicus has been removed.
RESOLUTION:
1. You'll need to make sure your network wiring is secure and that your networking equipment is functioning properly. This is, most likely, a physical connection issue, so your network administrator may need to help you out.
2. You'll need to re-map the network drive on your workstation. Ask your network administrator to help you.
THEN
You'll need to force Amicus "online" by following the solution to the next Issue below.
 
ISSUE:
When you start Amicus, you get a message that essentially says, "You were running offline because your connection to the network was lost. Do you want to go back online?"
REASON:
The previous Issue above occurred or, unbeknownst to you, your network connection was temporarily lost during your last Amicus session (the equivalent of the previous Issue above), and it was resolved.
RESOLUTION:
Unless you worked extensively while offline (which you may not necessarily know), DO NOT CHOOSE TO GO BACK ONLINE. Instead, follow these steps:
  • Exit out of Amicus.
  • Make a backup copy of the file "aa40.ini" (or "aa50.ini" for Version V) located in your Windows directory (e.g., C:\WINDOWS)
  • In Windows, click on Start | Run, then type "aa40.ini" (a a four zero dot i n i -- without the quotes) and click OK. This brings up the Amicus configuration file for your workstation in Notepad.
  • NOTE: BE CAREFUL AND MAKE ONLY THE CHANGES NOTED NEXT.
  • Search for the term "RunningOffline = 1" and change it to "RunningOffline = 0" (without the quotes, of course).
  • Near that line, change the term "AutoOffline = 1" to "AutoOffline = 0" (again, without the quotes).
  • Save the file and exit Notepad.
  • Re-start Amicus
  • As Amicus starts and reconnects with the central database, you may get the message "Processing xxxx transactions" (Version IV) or "Updating data" (Version V). This indicates that your local database is synchronizing with the central database.
    •  
    ISSUE:
    Contact, file or calendar information for your office, or for the office into which you are logged, seems to have disappeared.
    REASON:
    The central database indexes may have become corrupted, or your workstation's copy of the database has gone out-of-synch with the central database.
    RESOLUTION:
    First, from the Amicus Administrator, run a Scan of the database. All users must be logged out of Amicus to perform this routine.
  • Have all users exit out of Amicus.
  • At the Amicus Administrator, click on Database | Utilities | Scan Database.
  • Depending on the amount of data in your database, this process may take a few minutes.
  • Once the Scan utility has completed, everyone can get back into Amicus.

    • If the Scan utility does not correct the problem, you'll need to regenerate the local database for the affected workstation by following these steps:
  • Exit out of Amicus.
  • At the Amicus Administrator, click on Users | User Management | Status to bring up a user status list.
  • Highlight (click on) the name of the user whose workstation's local database needs to be regenerated.
  • Click on Users | Recovery Functions | Rebuild User Data. This sets a flag so that the next time this user starts Amicus, his/her local database will be synchronized with the central database.
  • Re-start Amicus on the appropriate workstation. Depending on the amount of data, that process may take five minutes or more.
  • NOTE: If you set multiple users' data to be regenerated and two or more restart Amicus at the same time, the data rebuild process will be much slower.
    •  
    ISSUE:
    When you try to access a particlar file, event, contact or other information, that information is either locked (note the padlock icon) or you are given a message that the information is in use by another user; however, that other user is not viewing that information.
    REASON:
    A record lock failed to release when the other user exited viewing the information.
    RESOLUTION:
    You'll need to unlock the data of both users by following these steps:
  • Both users should exit out of Amicus.
  • At the Amicus Administrator, click on Users | User Management | Status to bring up a user status list.
  • Highlight (click on) the names of the users affected, holding down the CTRL key in order to hightlight multiple names.
  • Click on Users | Recovery Functions | Unlock Records.
  • You will be prompted to confirm. Proceeding will actually perform the unlocking process there at the Amicus Administrator, which may take up to five minutes for each selected user.
  • Re-start Amicus on the appropriate workstations.
    •  
    ISSUE:
    When you start Amicus, you get a message that says, "Could not connect to Amicus."
    REASON:
    You are using Amicus Client/Server Edition, and the Amicus Administrator is not running on the server.
    RESOLUTION:
    Start the Amicus Administrator on the server, then restart Amicus at your workstation.
     
    ISSUE:
    When you try to execute a Scan Database from the Amicus Administrator in a Novell environment with Amicus IV Client/Server, you get an error, in effect, saying "Could not rebuild index; Administrator will be shut down." The reason for your wanting to perform a Scan Database may be apparent missing information.
    REASON:
    An unknown problem is preventing the Scan Database from executing. You will need to perform a manual procedure. Contact us if you would like assistance performing this procedure.
    RESOLUTION:
  • Make sure everyone is logged out of Amicus
  • Shut down the Amicus Administrator
  • Shut down the Amicus NLM on your Novell server
  • Copy the the entire Database subfolder from the Team40 folder on your Novell server onto the fastest workstation in your network
  • On that workstation, get to a DOS prompt and navigate to the Database folder that you just copied from the server
  • At the DOS prompt, execute the RBLDINDX.bat file to perform the actual index rebuild; it may take some time to complete
  • At the end of the index rebuild process, take note of any error messages reported, then exit the DOS prompt
  • On your Novell server, rename the original amicus.db file residing in the Database subfolder of the Team40 folder to something like "amicus.402" (indicating this represents an old copy of the database as of April 2002)
  • Copy only the amicus.db file from the Database folder on the workstation back to the Database subfolder of the Team40 folder on your Novell server
  • Delete any .FCS files that exist in the Database subfolder of the Team40 folder on your Novell server
  • Reload the Amicus NLM on the Novell server
  • At the workstation where Amicus Administrator is installed, start the Amicus Administrator while at the same time holding down the CTRL key, and continue holding down the CTRL key until a dialog box appears indicating that a regeneration of the database is in progress
  • These procedure may take some time to complete, so don't be concerned if your Task Manager indicates that Amicus Attorney is "Not Responding"
    •  
    OTHER VERSION IV ISSUES:
    You can find additional help for Version IV issues here:
  • Advanced Edition FAQ
  • Client/Server Edition FAQ
  • Organizer Edition FAQ
  • Version IV Known Issues

    • VERSION III ISSUES:
    You can find help for Version III issues here:
  • Version III (PC)
  • Version III (Mac)

    • VERSION V ISSUES (NEW!):
    You can find help for Version V issues here:
  • Version V Known Issues

    •  


    Consulting | Web Design | Web Hosting | Contact | Support | Home

    This site best viewed with Internet Explorer v4 or later.
    Copyright © 2004 Mongiardo Enterprises LLC