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.
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)
We have an update that is crashing on data that has a degree symbol. I have attached a sample of the data.
Advantage Data Architect and Orion have no trouble displaying the character. From what I can tell, .NET strings are utf-16. I have attached a Notepad file with the category copied from ADA in case that is helpful. I am using the Newtonsoft Json library to serialize and deserialize the objects sent to / received from Yellow Hat. I can't find anything useful about converting encoding on strings.
The error that I receive indicates an encoding issue.
Please help me if you know of a reason why Advantage is having a tough time with the degree symbol and how I can get around it.
Thank you,
CPGood
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.
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
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.
Beginning with ADS 10 when using Unicode Advantage uses UTF-16
But I think it has more to do with what field type you are using.
A CHAR, CICHAR, VARCHARFOX, MEMO are all ASCII field types.
A NCHAR, NVARCHAR, NMEMO are Unicode field types
Where is the crash? Is it in the .Net Dataprovider or ACE?
Maybe you can provide a bit of code that can duplicate the crash? For example are you storing the value or are you reading the value from ADS? Are you using a DataReader or DataAdapter/DataSet?
Thank you,
Edgar
Hi Edgar,
Here is the input you requested. Thank you for taking a look at this:
the error appears to be happening when trying to save the data to Advantage. We are using Entity Framework with the .NET data provider. The error appears to be coming from Advantage:
2015-02-10 09:01:14,323 ERROR hpCommerceWindowsService.MotorStateIntegration.PartImportProcessor: Error importing part updates
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 = 5211; [iAnywhere Solutions][Advantage SQL][ASA] Error 5211: There is an error converting Unicode string to or from code page string. Some Unicode characters cannot be converted to code page characters. ** 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.Import.MotorState.MotorStateImport.ImportPartUpdates(Entities entities, List`1 partUpdates, Nullable`1 skipDate, Boolean useVerboseLogging, LogException logPartUpdateException, LogInformation logPartUpdateInformation, String auditUsername, Int32& itemsUpdated, Int32& itemsCreated, Int32& plcsCreated, Int32& itemsSkipped)
So the error you are receiving is 5211 There is an error converting Unicode string to or from code page string. Some Unicode characters cannot be converted to code page characters.
What this tells me is that your base column is likely a CHAR field. (ASCII). Unfortunately we could not convert the character into an ASCII equivalent. ADS uses the OS to perform the conversion.
Since we are using the extended ASCII it should be possible to covert the character? How are you reading the file into your .Net application?
For example, the following will return the 5211 error when inserting into ADS
string readText = File.ReadAllText(path);
....
cmd.ExecuteNonQuery();
But, if you set the encoding properly the insertion is successful
string readText = File.ReadAllText(path, Encoding.Default);
....
cmd.ExecuteNonQuery();
Hi everyone,
I'm a D&T rep based out of Atlanta. One of my accounts has inquired about the latest pricing for Sybase ADS. Can you supply me with an updated list or tell me where to go to get one?
Thanks!
- Trey Owings
On the main SAP page (sap.com) There should be a contact us on the right hand side. It will present you with options such as chat, e-mail, phone (1-800-872-1727).
You can ask for the Advantage Database Server Sales team (I recommend not using the ADS acronym) or the OEM Sales team.
If you have any trouble feel free to privately message me your contact info and I can forward it to a sales contact I have.
Edgar
So we will need start upgrading installs from Advantage Database Server (ADS) version 9 to ADS version 11. Is there a set of best practices? Certain procedures? How do we gracefully fall back if it doesn't work? Does anyone have experience with the dual install setup of ADS 9 and ADS 11? Did anyone else run into any issues with this upgrade path?
Thanks in advance!
Rodney
Rodney,
My first recommendation is to read the "Effects of Upgrading" section of the help file. I put the links below.
Effects of Upgrading to Version 10
Effects of Upgrading to Version 11
Effects of Upgrading to Version 11.1
The server will always work with an older client so I would recommend upgrading the server and testing it with your current application. The next step would be to upgrade the client and re-compile your application. I wouldn't anticipate any issues other than those outlined in the effects of upgrading.
You can install multiple instances of Advantage, beginning with version 10, on the same machine. Keep in mind that only one instance, the first one installed, will be discoverable. To connect to other instances you will need to use <IP Address>:<Port> in the connection string. Details on installing additional instances of Advantage are here
Chris
When performing the upgrade install will it automatically remove all of the version 9 items or will it default to a side by side install? Do we need to / should do an uninstall first?
Thanks
Rod
It will automatically remove the version 9 components and "upgrade" to the newer version.
Side by side is something special that needs to have some extra items run so it won't affect the existing.
Doing an uninstall / re-install won't hurt, but it shouldn't be needed. I do usually stop the ADS Service before upgrading so I can make sure it goes down cleanly.
Hello,
I'm from Germany, so sorry for my English first.
I got the error "Unknown field type (28) encountered." when I run
a simple "SELECT * FROM system.functions" on my ADD-Database.
The solution for this problem is found in the KBA 2145730.
If I use the ADS DLLs v. 11.10.0.22 I got the error, but if I use the
ADS DLLs v. 9.10.0.35 everything is fine.
For solving other problems I think it would be better to use the newest
version, but in this case I can't. At this time it is not a problem, because
I can't find any real reason so that I must update for now, but nevertheless
I'd like to know, why this error occurs. What is type 28? Or (what real
would be great) can I make changes to my software, so that I can
avoid this problem? I hope you can help me with this "riddle" and wish
all of you a great day.
Greetings from Germany,
Gerit Freericks
For backwards compatibility the server will send different field types (i.e. char vs varchar, ansi vs unicode, etc).
The server determines this based on the ACE (Advantage Client Version). By swapping in new DLLs you are telling the server that you are running a newer client and it can send the newer field types etc for the system tables.
In addition to swapping the DLLs re-build the application with the new TDataSet (re-compile) and this should resolve your issue.
For the field types look at ACE.pas (or ACE.h) in the TDataSet (on the latest). It looks like 28 is an NMEMO (Unicode Memo field)
Hello Mr. Sherman,
Thanks for your reply!
I'm toying with the idea of appending missing fields in the source,
like described in the comment in the ace.pas, but I think I have to wait
until all of our customers can be updated to v.11 and
install the updated components the "right" way.
Greetings from Germany,
Gerit Freericks
Does anyone know if this webcast from March 12, 2013 by Chris Franz is still available online anywhere?
Have a situation where we currently are using SQL Server 2005 to connect to SQL Server 2008 r2 running ADS 10.10. We are using stored procedures with open query, linked server and data source connection to data dictionary. This been working fine for years
Now moving to a newer server, from the SQL Server 2005 to a SQL Server 2008 r2, we are having issues connection to the same ADS database, we are having issues getting connected through the linked server and not able to run the stored procedures. Looks like the server comes
to a hault when trying to test connection
The configuration of the linked servers are exactly the same (MS OLE DB provider for ODBC drivers), data sources are the same and stored procedures are all the same. Tried even using the Advantage OLE DB Provider without any luck.
My question is: Have others experienced issues connecting from SQL Server 2008 r2 to another SQL server 2008 r2 running ADS 10.10? We seem not to be able to figure out what is wrong, whether it is on the ADS side or the side we are running SPs from. Any input would be appreciated.
Thank you all.