Advantage Developer Zone

 
 
 

Advantage Knowledge Base Items




Recently Added / Updated Advantage Knowledge Base Items



Subscribe!

Subscribe using these popular web rss readers:

Add to Google  Add to My Yahoo!

 View the Feed XML



Current Feed Items

Error 5170 Returned when Pre 8.1 Delphi Client Attempts to Reindex a Table With Triggers on 8.1 or Newer Server

Sun, 05 May 2013 17:00:00 GMT
Reference Number: 130501-2609

Last Modified: Monday, May 06, 2013

Title:
Error 5170 Returned when Pre 8.1 Delphi Client Attempts to Reindex a Table With Triggers on 8.1 or Newer Server

Description:
After adding a trigger to a table or modifying an existing trigger using the Advantage 8.1 or newer server (either REMOTE or LOCAL) and attempting to re-index the table with a pre 8.1 client using Delphi (i.e. TAdsDataset version 7.1), the following error is returned:
5170 AE_DATABASE REQUIRES_NEW_SERVER

Solution:
Upgrade the client to 8.1 or later.

When using a pre 8.1 client the following workaround will correct this situation.
In Delphi, ensure that after the table is open to reset the AdsTableOptions.AdsIndexPageSize to 0 prior to calling AdsReindex.


64-bit programs built with Delphi XE2 may handle Money fields incorrectly

Tue, 02 Apr 2013 17:00:00 GMT
Reference Number: 130402-2607

Last Modified: Wednesday, April 03, 2013

Title:
64-bit programs built with Delphi XE2 may handle Money fields incorrectly

Description:
64-bit programs compiled with Delphi XE2 (or RAD Studio XE2) may have problems with Money fields in ADT tables. The following behaviors have been observed:
1) Money fields containing "large" values may be displayed incorrectly.
2) Large values for money fields may be posted to the ADT table incorrectly.
3) Posting some valid Currency values may produce Exceptions.

These behaviors only appear when using the 64-bit compiler.

Solution:
These behaviors are a result of a series of defects identified by Embarcadero. (See Embarcadero QC numbers 103589 and 103857.)

These issues are resolved in Delphi XE3. Customers affected by these defects should upgrade as soon as possible, or rebuild affected projects as 32-bit projects.


Error 7181 Being Returned When Not Exceeding User Count

Tue, 26 Mar 2013 17:00:00 GMT
Reference Number: 130327-2606

Last Modified: Wednesday, March 27, 2013

Title:
Error 7181 Being Returned When Not Exceeding User Count

Description:
The error 7181, maximum users exceeded, is being returned when the "Total Users" is not exceeding the configured limit.

Solution:
The "Total Users" count is a sum between the number of users connected, and the Web Platform Users. The Web Platform User is a new feature that was introduced in ADS 11.

In one instance, the total users was at 2 and a workstation was receiving error 7181 when connecting. The number of Web Platform Users was set at 1, so the maximum number of connected users (Not using Web Platform) was 1. Setting the number of Web Platform Users to 0 enabled the database to accept 2 users from the application.


Using ARC to Import Numeric Fields from MS SQL Server Fails with Error 5012

Tue, 26 Feb 2013 16:00:00 GMT
Reference Number: 130220-2602

Last Modified: Wednesday, February 27, 2013

Title:
Using ARC to Import Numeric Fields from MS SQL Server Fails with Error 5012

Description:
When importing data from an MS SQL Server database using the Advantage Data Architect (ARC) the import may fail with a 5012 (AE_INVALID_FIELDDEF) error if the table contains a NUMERIC column.

Solution:
This is a bug in the Advantage Data Architect 11.1 and earlier. It is planed to be addressed in the next update.

As a workaround, if possible, alter the table from NUMERIC to another appropriately typed column in the MS SQL Server database. Once imported, the column can be altered back to a NUMERIC in Advantage.


ADS Install Fails with "Advantage server file open failed. Reinstall and try again."

Wed, 20 Feb 2013 16:00:00 GMT
Reference Number: 130218-2601

Last Modified: Thursday, February 21, 2013

Title:
ADS Install Fails with "Advantage server file open failed. Reinstall and try again."

Description:
When installing ADS, the installation mostly finishes, but presents an error at the end of the installation. The error message presented is "Advantage server file open failed. Reinstall and try again."

Solution:
This may happen if an antivirus or malware prevention program is running. Try running the Advantage installer as an administrator (Right Click -> Run as Administrator). If the install still fails, disable antivirus/malware software and run the install again.

Note: Be sure to reenable the antivirus/malware software after installation. Also, configure the software to exclude any database files during system scans.


6401 Error In Windows Environment

Wed, 30 Jan 2013 16:00:00 GMT
Reference Number: 130131-2600

Last Modified: Thursday, January 31, 2013

Title:
6401 Error In Windows Environment

Description:
An ADS application within a Windows XP environment is receiving 6401 "Invalid Socket Handle" errors.

Solution:
This issue was resolved by removing all intrusive anti-virus software from the server, resetting both the IP stack and Winsock catalog, and restarting the computer. Some anti-virus software packages will sometimes inject (replace) standard Windows DLLs with custom built libraries to more closely monitor internet traffic and socket level connections. In this case, there was a delay in establishing a Winsock connection for the database server process, and the anti-virus software took that as a possible threat, so it closed the socket prematurely.

For directions on how to reset the IP stack:

http://support.microsoft.com/kb/299357

For directions on how to reset the Winsock catalog on Windows XP:

http://windowsxp.mvps.org/winsock.htm


Error 9073 TPS Commit Failed When Performing An Online Pack

Sun, 27 Jan 2013 16:00:00 GMT
Reference Number: 130128-2599

Last Modified: Monday, January 28, 2013

Title:
Error 9073 TPS Commit Failed When Performing An Online Pack

Description:
Receiving error 9073 "TPS commit failed" when performing an online pack (sp_PackAllTablesOnline()).

Solution:
This error can come up if ADS attempts to perform an online pack on a view or temporary table, this includes both the sp_PackTableOnline() and sp_PackAllTablesOnline() system procedures. ADS server builds 11.10.0.3 and higher contain the fix.


Error 5139 or 5177 Whenever an Operation is Attempted on a Table

Mon, 21 Jan 2013 16:00:00 GMT
Reference Number: 130122-2598

Last Modified: Tuesday, January 22, 2013

Title:
Error 5139 or 5177 Whenever an Operation is Attempted on a Table

Description:
An Adt table in a data dictionary with replication but no referential integrity produces a 5139 error when trying to perform any action on the table, including deletion. 5177 was alternatively occassionally produced.

Recreating the .ai file did not produce any noticeable results.

Solution:
The issue may be resolved by freeing the table from the data dictionary (via Tools -> Free Data Dictionary Bound Table ), re-indexing, and then re-adding the table to the data dictionary.


Error 7078 - Windows Server Environment

Thu, 17 Jan 2013 16:00:00 GMT
Reference Number: 130118-2597

Last Modified: Friday, January 18, 2013

Title:
Error 7078 - Windows Server Environment

Description:
Error 7078 occurs within a new Windows Server environment although the application has been deployed to many other Windows Server environments without issue.

Solution:
One possible resolution is double-checking the drive in which the shared application/data directory is being stored on and modifying the connection path to include that drive letter:

Original Path: \\ServerName\application_folder
New Correct Path: \\ServerName\C\application_folder

This situation comes up on new Windows Server installations where the OS drive wasn't properly setup to be the "C:\" drive/partition.


Error 1506 - The Requested File Could Not Be Found

Thu, 17 Jan 2013 16:00:00 GMT
Reference Number: 130118-2596

Last Modified: Friday, January 18, 2013

Title:
Error 1506 - The Requested File Could Not Be Found

Description:
Receiving 1506 errors spontaneously after a period of time on an existing client/server deployment.

Solution:
This error can come up in situations where the client ACE library expects to use a collation/Unicode related file, but its missing from the installation, or was not packaged as part of the deployment. As of ADS version 10.x ensure that the following redistributable files are within the same directory as the ace32/64.dll on both the server and client side:

adscollate.adm
adscollate.adt
aicu64/32.dll
icudt40l.dat

This error may not be triggered until Unicode characters are queried from the database.