Collation Errors for Installation in Australia

[Former Member]

We are getting a collation error when we try to use our application on a Windows 7 OS on a computer in Australia.  We have over 1,000 users of our product in North America.  95% of them run local server.  We have one installation of our product in the UK.  We have ZERO issues with these installations.  We are trying to get an installation up and running in Australia.  When our application first started after installation we received errors that indicated a 5175 error message.  We then tried to open our database in Advantage Data Architect and we received the same error message when we tried to open any tables.  ADA suggested reindexing.  Which we did.  We could then open the tables but we are unable to add new/change data via ADA.  So we have removed our application from the equation by using ADA and we still cannot work with the data.

Does anyone have experience with building and using applications that are to be run in Australia?  We are a North American company.

Thank you,

CPGood

[Former Member · Accepted solution]

When you try to add / change new data what error are you getting?

Or are the tables marked read-only?  For example if you open the table in ARC is the + and - on the navigation toolbar greyed out?

If the + and - is greyed out check that the user you are using to access the data has full control over the directory and files.  If you are using Local Server this is the user OS user that opens the application / ARC.  If you are using Remote Server this is the Local System Account by default.

[Former Member · Accepted solution]

Hi Edgar,

Thank you for your reply.  The + and - in ADA are not grayed out.  We are using Local Server.  Attached are the log files from our application.  I have also pasted them in below.

Thank you for helping me with this.

CPGood

2015-02-03 12:49:10,043 ERROR SetupData: Error getting SetupData

Advantage.Data.Provider.AdsException: Error 7200:  AQE Error:  State = HY000;   NativeError = 5175;  [iAnywhere Solutions][Advantage SQL][ASA] Error 5175:  The index file was created with a different collation sequence than is currently being used. Table name: Setup  AdsCommand query execution failed.

   at Advantage.Data.Provider.AdsCommand.ExecuteStatement(IntPtr& hCursor, String& strIndex)

   at Advantage.Data.Provider.AdsCommand.ExtecuteReaderInternal(CommandBehavior behavior, Boolean bExtendedReader)

   at Advantage.Data.Provider.AdsCommand.ExecuteReader()

   at hpCommerce.DataLayer.SetupData.GetSetupData()

2015-02-03 13:05:47,558 ERROR hpCommerce.SystemConfig.SalesTaxAddEdit: Error adding tax code

System.Data.UpdateException: An error occurred while updating the entries. See the inner exception for details. ---> Advantage.Data.Provider.AdsException: Error 7200:  AQE Error:  State = HY000;   NativeError = 5175;  [iAnywhere Solutions][Advantage SQL][ASA] Error 5175:  The index file was created with a different collation sequence than is currently being used. ** Script error information:  -- Location of error in the SQL statement is: 1  AdsCommand query execution failed.

   at Advantage.Data.Provider.AdsCommand.ExecuteStatement(IntPtr& hCursor, String& strIndex)

   at Advantage.Data.Provider.AdsCommand.ExtecuteReaderInternal(CommandBehavior behavior, Boolean bExtendedReader)

   at Advantage.Data.Provider.AdsCommand.ExecuteDbDataReader(CommandBehavior behavior)

   at System.Data.Common.DbCommand.ExecuteReader(CommandBehavior behavior)

   at System.Data.Mapping.Update.Internal.DynamicUpdateCommand.Execute(UpdateTranslator translator, EntityConnection connection, Dictionary`2 identifierValues, List`1 generatedValues)

   at System.Data.Mapping.Update.Internal.UpdateTranslator.Update(IEntityStateManager stateManager, IEntityAdapter adapter)

   --- End of inner exception stack trace ---

   at System.Data.Mapping.Update.Internal.UpdateTranslator.Update(IEntityStateManager stateManager, IEntityAdapter adapter)

   at System.Data.EntityClient.EntityAdapter.Update(IEntityStateManager entityCache)

   at System.Data.Objects.ObjectContext.SaveChanges(SaveOptions options)

   at hpCommerce.DataLayer.DataContext.SaveChanges(Entities entities, Boolean showWaitCursor)

   at hpCommerce.SystemConfig.SalesTaxAddEdit.AddTaxCode(Boolean& canceled)

Log.txt.zip

[Former Member · Accepted solution]

For Local Server, basically each application uses a different adslocal.cfg  Within this file there is an ANSI Character Set and OEM Character set.

As you are using Local Server each application is its own server so it is critical that each and every one matches across each app and each workstation (even ARC and your .Net app are likely using two different adslocal.cfg files).

The other issue is that by default I believe the ANSI Character Set is set to "use current character set".  Depending on the users if you have one set to Australian and another set to English, etc... it can cause this.

I would recommend setting these to Engl(Amer).  After making the change re-index into the current character set.

[Former Member · Accepted solution]

Hi Edgar,

Thank you!  At the moment this is a single user installation.  We do not have not since 2010 used an adslocal.cfg or an ads.ini file.  This has not caused us a problem.  Therefore I am not familiar with them.

I would assume that we need to create an adslocal.cfg text file in the root folder of our application and add the following lines to it:

; ANSI Character Set

; Default = Use the currently configured ANSI character set that is active

;          on the workstation.

; If you do not wish to use the ANSI character set that is active on the

;  current workstation, the available ANSI character sets to be used are:

;    Danish, Dutch, Engl(Amer), Engl(UK), Engl(Can), Finnish, French,

;    French Can, German, Icelandic, Italian, Norwegian, Portuguese, Spanish,

;    Span(Mod), Swedish, or Russian

ANSI_CHAR_SET=Engl(Amer)

;

; OEM/Localized Character Set

; Default = USA

; Options are:

;  USA, DANISH, DUTCH, FINNISH, FRENCH, GERMAN, GREEK437, GREEK851, ICELD850,

;  ICELD861, ITALIAN, NORWEGN, PORTUGUE, SPANISH, SWEDISH, MAZOVIA, PC_LATIN,

;  ISOLATIN, RUSSIAN, NTXCZ852, NTXCZ895, NTXSL852, NTXSL895, or NTXHU852

OEM_CHAR_SET=USA

Thank you for confirming the design of this file.

CPGood

[Former Member · Accepted solution]

Yes I would start with this.  Also, I believe that ARC by default creates one in it's directory so you  may check there as well.

Finally it may be helpful to use something like Process Mon from Microsoft's Sysinternals tools to verify that no other stray one is being used.