SAP SQL Anywhere 17 - Server must be upgraded to start database

[former_member1100594]

Hello,

I'm running into quite the puzzling error:
Connection failed: Unable to start specified database: Server must be upgraded

I have already cross-referenced the following links:
SQL Anywhere Help Portal Errors

Database cannot be started -- server must be upgraded to start (capability 40 missing)

In my particular instance though, I am attempting to use the ODBC connection to use SQL Anywhere 17 (v 17.00.04.2053) to access a Sybase 17.0 database through Access. Normally, I would use a "newer" version of SQL Anywhere, but I have the newest version that is available to developers. What am I missing? Any assistance would be greatly appreciated.

[chris_keating]

To expand on Volker's response, SQL Anywhere has both the software version (the version of engine binaries) and a database version. Generally, databases are always forward compatible - you can run an older database file format version on a newer database engine. However, running a newer database file format may not work

• a database created in a newer major release will not run on a previous major release engine
• a database created in a newer build of a major release will not run on an older engine build if there was features that requires a rebuild or upgrade to support.

There have been several file format changes made during the SQL Anywhere 17 cycle. The database that you are trying to use was created in a newer version than 17.0.4. To use this database, you will need a newer server version or a recreating the database in 17.0.4 or earlier.

[former_member194571]

Hi Josh,

this is an unpleasant aspect of the current policy of SAP wrt SQL Anywhere Updates. They continue to be kind of "free" in that afaik every SAP support customer ("S- User") has access to SQL Anywhere software updates. However, for such an account, you need to have a support contract for ..something... I found that the cheapest way to get it was to buy a small SQL Anywhere license (I have a 5 user server, maybe even a single user license is sufficient).

For the technical aspect: In recent v.17 builds, the db file format was changed (don't currently have the exact details @ hand). The technical workaround for your issue would be to ask the source of the db file to dbunload it with his version and either send you the unload result or load it into an empty DB you have provided. If the issue you're looking at is related to the physical .db file you're trying to look at, neither of those will help, unfortunately.

I don't know if a person who has access to an S- User account is violating the regulations if sHe passes a recent EBF to you, but I'm afraid that this is the case.

HTH anyway...

Best regards

Volker
DB-TecKnowledgy