| I received "Error 1722: The RPC Server is Unavailable" and Account Ability quits. Why? |
|
The PRINT SPOOLER SERVICE on your Windows server is probably disabled. |
 |
| Why do I get the message 'Unable to allocate a user socket' when trying to open a client file? |
If you exit Account Ability normally, then you should never see this message unless, of course, you truly exceed the number of licensed concurrent users of Account Ability.
To correct this error using version 2006 or prior,
(a) Have all users exit Account Ability
(b) Start Account Ability on one workstation
(c) Select 'Verify' from the Client Management 'Tools' menu.
To correct this error using version 2007 or later,
(a) Have all users exit Account Ability
(b) Start Account Ability on one workstation
(c) Select 'Logged Users' from the 'Module' menu
(d) Click the 'Verify' button. |
|
| Every time I start Account Ability from my server I get an "Open File - Security Warning" message. Is there a way to suppress this message? |
The "Open File - Security Warning" message is coming from Windows, not Account Ability. This behavior is new in Windows XP SP2 because of the addition of the Attachment Execution Services (AES). The easiest way to workaround this message is to change the SEE_MASK_NOZONECHECKS environment variable. Have your system administrator temporarily change the SEE_MASK_NOZONECHECKS environment variable to 1.
WARNING: It is suggested that you not use this as a permanent system environment variable because it will disable all Zone Checking. |
|
| I received a 5004 error when starting Account Ability. What does this mean? |
|
This error is coming from the Advantage Client Engine (ACE). Ensure that you have full rights to the Account Ability installation folder. If you do, try installing the latest service pack from Account Ability's Download Page |
|
| Why does the message "Version information is unavailable? Reinstall Account Ability." appear when I start Account Ability? |
Account Ability failed to retrieve its version number at startup. Although this should rarely happen, it has been known to occur on Novell servers. Try uninstalling and reinstalling the application.
SUGGESTION: If you are installing Account Ability to a Novell server, try installing to a shorter path name without spaces (e.g. F:\AA)
NOTE: Any existing data will not be lost. |
|
| I received error 5185 when starting Account Ability. What does this error mean and how can I correct it? |
Advantage Local Server connections are restricted when used from a web server, an application server, a terminal server, or any other type of middleware or server product used to access data on behalf of remote computers. If you receive this error, it is because Account Ability attempted to make a local server connection from one of these restricted environments.
Solution: Add the following lines to the end of the ADS.INI file
[SETTINGS]
MTIER_LOCAL_CONNECTIONS=1
NOTE: You will find the ADS.INI file in the Account Ability installation folder. This file can be edited using any text editor, such as Windows NOTEPAD.
IMPORTANT
Pursuant to iAnyWhere's licensing agreement, ... if an application is distributed to work without the Advantage Database Server (i.e., it uses the Advantage Local Server to access data), the application must act as a "client" that directly accesses and uses the data. To be specific, only computers that have the Advantage Local Server DLL loaded into memory can have access to the data that is obtained by that Advantage Local Server DLL. The application cannot act as "middleware" or as a "server" by having the data forwarded by any means to a separate computer. In other words, it is illegal to use the Advantage Local Server with a Web server, an application server, a terminal server, or any other type of middleware or server product to access data on behalf of remote computers. An Advantage Database Server (a.k.a. remote server) product must be purchased and used to allow this SOFTWARE PRODUCT to access data on behalf of applications running on remote computers. |
|
| Why do I get a "Re-allocating Database" message when starting Account Ability? |
Concurrent users on your network are probably referencing Account Ability's 2006 database via different mapped drive letters.
Solution: Follow these instructions to re-allocate the database using universal naming convention (UNC), not a mapped drive.
(a) Ensure that Account Ability is not active on any workstation.
(b) Start Account Ability on your workstation.
(c) From the Module menu, select Re-allocate
(d) From the sub-menu, select Account Ability's 2006 Database
(e) Browse to the installation folder using universal naming convention (UNC), not a mapped drive.
(f) Open the 2006DATA folder and double-click the AA2006.ADD dictionary file.
(g) Exit and restart Account Ability. |
|
| I received error 7077 when starting Account Ability. What does this error mean and how can I correct it? |
You are probably running an older version of the Advantage Database Server (ADS). Users complaining of this error were running ADS version 6.2 with CCH software.
Solution: Either update ADS to version 8 or force Account Ability to use the Advantage Local Server (ALS), which ships with Account Ability. |
|
| Why do I get an I/O Error when exiting Account Ability? |
Some users have complained of an I/O Error xxx, where xxx is 123, 51, 53, etc., when exiting the 2005 version of Account Ability, and their PC locks up. Since this error occurs on some PCs, but not all, it is a tough one to diagnose. To correct this error, download the latest Service Pack from the 'Download' page.
Click here if you would like to visit the 'Download' page now. |
|
| Why do I get a 'File not found' error when exiting Account Ability? |
Some users have complained of a 'File not found' error when exiting the 2005 version of Account Ability, and their PC locks up. Since this error occurs on some PCs, but not all, it is a tough one to diagnose. To correct this error, download the latest Service Pack from the 'Download' page.
Click here if you would like to visit the 'Download' page now. |
|
| Why do I get a 'File not found' error when starting Account Ability? |
You probably lack sufficient permissions to the Account Ability installation folder. Have your network administrator create a Local Group (e.g. Account Ability Users) that grants administrative (supervisor) rights to the Account Ability installation folder. Then, add your user account to the group and see if this resolves the problem.
NOTE: Instructions for setting up a Local Group under Windows XP Professional can be found in the section on Network Considerations. |
|
| Why do I get the error "Index does not exist: ix_code" when starting Account Ability? |
|
Older versions of the Borland Database Engine may generate this error when Account Ability is installed to its default location (e.g. C:\Program Files\Account Ability\Tax Form Preparation\...). The resolution is to uninstall and reinstall Account Ability to a shorter pathname (e.g. C:\AA or F:\AA). |
|
| When starting Account Ability I get a $2108 error initializing the Borland Database Engine. What does this mean and how can I correct it? |
This error indicates that there is a problem locating the library IDAPI32.DLL on your PC. The BDE requires this library to function properly. Here's a solution that seems to work well (this solution requires working with the system registry and should be performed by a system administrator).
(a) From the 'Start' menu select 'Run...'
(b) Enter the command 'REGEDIT'
(c) Open the HKEY_LOCAL_MACHINE group
(d) Open the 'Software' group
(e) Open the 'Borland' group
(f) Rename the 'Database Engine' folder to 'Database Engine Old'
(g) Shutdown and restart your PC.
(h) Reinstall Account Ability
(i) Restart your system. |
|
| Why do I get the error 'Interface mismatch. Engine version different.' when starting Account Ability? |
This error indicates that there is a problem in the Borland Database Engine (BDE) on your PC. Here's a workaround that seems to work well (this workaround requires working with the system registry and should be performed by a system administrator).
(a) From the 'Start' menu select 'Run...'
(b) Enter the command 'REGEDIT'
(c) Open the HKEY_LOCAL_MACHINE group
(d) Open the 'Software' group
(e) Open the 'Borland' group
(f) Rename the 'Database Engine' folder to 'Database Engine Old'
(g) Shutdown and restart your PC.
(h) Reinstall Account Ability
(i) Restart your system. |
|
| I installed Account Ability on a NovellŪ server. Every time I start the application I get the message 'Invalid index ix_code' and the application terminates. What's wrong? |
Either NovellŪ is having a problem with the path to which you installed Account Ability or the user lacks sufficient rights to the installation folder.
Try the following:
(a) Uninstall the server license and reinstall it to a folder with a shorter name containing no spaces
(b) Have your network administrator create a group for users of Account Ability granting Supervisor rights to the installation folder
(c) If you are using Novell's Client32 for Netware networks, ensure that you have the most recent version. |
|
| When starting Account Ability the message 'An error occurred while attempting to initialize the Borland Database Engine (error $251E)' is displayed. What does this mean? |
|
An error code of $251E indicates that there is 'Insufficient shared memory available'. If you are running many applications in the background, try shutting down a few in order to free up some system resources. If you are running an older version of Windows, say Windows 95, it may be time to upgrade! If you failed to disable any anti-virus software during installation, (a) uninstall Account Ability from your system's Control panel, (b) disable any anti-virus software that may be running, (c) reinstall Account Ability. You will not lose any data by reinstalling! If the problem persists, contact IDMS Technical Support at 1-800-582-5831 or 1-888-IDMSINC. |
|
| When starting Account Ability I get an 'Index out of date' error. How can I correct this? |
You should rarely see this error, however, here's a possible immediate solution:
(a) Have all users exit Account Ability
(b) Browse to the folder YYYYdata (YYYY=reporting year)
(c) Delete the following files:
Client.PX
Client.XG0
Client.XG1
Client.YG0
Client.YG1
DO NOT DELETE Client.DB or Client.MB
(d) Start Account Ability
(e) Open the Client (Filer) Management module
(f) Select 'Reindex' from the 'Tools' menu
(g) Select 'Verify' from the 'Tools' menu.
If the error persists, download the free Data Verification Utility from the download page. This utility can be used to verify and repair any file within the Account Ability database.
NOTE: When using the Data Verification Utility you will be prompted to 'Select Table to Repair'. Browse to the folder YYYYdata, where YYYY is the reporting year, and 'Verify Table Integrity' for each of the .DB files displayed. If an error is found, select 'Rebuild Table' to correct the error. If the problem persists, repeat this same procedure for each of the folders listed within YYYYdata. |
|
| When starting Account Ability I get the message '...header is corrupt...' and the application terminates. What does this mean and how can I correct it? |
This is an indication that at least one file in the Account Ability database is corrupt. File corruption generally results from
Program lockups
System crashes
Abnormal program termination
Unexpected system reset
Power failure.
To correct this problem, download the free Data Verification Utility from the download page. This utility can be used to verify and repair any file within the Account Ability database.
NOTE: When using the Data Verification Utility you will be prompted to 'Select Table to Repair'. Browse to the folder YYYYdata, where YYYY is the reporting year, and 'Verify Table Integrity' for each of the .DB files displayed. If an error is found, select 'Rebuild Table' to correct the error. If the problem persists, repeat this same procedure for each of the folders listed within YYYYdata. |
|
| When starting Account Ability I get the message 'This program is controlled by another .NET file...'. How can I correct this? |
Have all users exit Account Ability. From the Window's 'Start' menu, select 'Search' or 'Find -> Files or Folders', whichever applies to your operating system.
Search your system for each of the following files,
Paradox.Lck
Pdoxusrs.Lck
Pdoxusrs.Net
Delete all occurrences of each of these files when found.
Try restarting Account Ability.
NOTE: If the problem persists there may be a permissions problem for at least one user of Account Ability. Have your system administrator ensure that each user of Account Ability has administrative rights to the Account Ability installation folder. |
|
| When starting Account Ability I get the message 'File is controlled by another Pdoxusrs.lck file...'. How can I correct this? |
Have all users exit Account Ability. From the Window's 'Start' menu, select 'Search' or 'Find -> Files or Folders', whichever applies to your operating system.
Search your system for each of the following files,
Paradox.Lck
Pdoxusrs.Lck
Pdoxusrs.Net
Delete all occurrences of each of these files when found.
Try restarting Account Ability.
NOTE: If the problem persists there may be a permissions problem for at least one user of Account Ability. Have your system administrator ensure that each user of Account Ability has administrative rights to the Account Ability installation folder. |
|
