Moving Able 706 with AC2000 SQL schema crashes on SQL 2014

[AbleMods]

I'm moving web hosting clients to a new platform as part of my hosting upgrades this year. I hit an older Able 7.x install that refuses to run on the new platform.

The only difference I can see is the Help->About shows the SQL schema as the old AC v2000 flavor. The new platform is running SQL 2014.

Has Able done any testing of old SQL2000-schema installs on SQL 2014?

I've got other 7.x installs running fine, but they're all the newer SQL v2005 schema. So I have a feeling that's my issue.

Thoughts?

Here's the error upon spinning the site up the first time:

Incorrect syntax near '@errorNumber'.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Data.SqlClient.SqlException: Incorrect syntax near '@errorNumber'.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:


[SqlException (0x80131904): Incorrect syntax near '@errorNumber'.]
System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) +1960538
System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +4890735
System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +194
System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) +2412
System.Data.SqlClient.SqlDataReader.ConsumeMetaData() +59
System.Data.SqlClient.SqlDataReader.get_MetaData() +83
System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) +293
System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async) +954
System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result) +162
System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) +32
System.Data.SqlClient.SqlCommand.ExecuteScalar() +139
CommerceBuilder.Data.Database.a(DbCommand A_0) +90
CommerceBuilder.Data.Database.ExecuteScalar(DbCommand command) +82
CommerceBuilder.Users.User.BaseSave() +2653
CommerceBuilder.Users.User.Save() +1194
CommerceBuilder.Users.UserDataSource.a(String A_0) +524
CommerceBuilder.Users.UserDataSource.LoadForUserName(String userName, Boolean createMissing) +191
CommerceBuilder.Common.Token.InitUserContext(HttpContext context) +322
CommerceBuilder.Services.c.b(Object A_0, EventArgs A_1) +138
System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +68
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +75

Version Information: Microsoft .NET Framework Version:2.0.50727.8009; ASP.NET Version:2.0.50727.8015

[AbleMods]

Aha! Found the solution.

There is a SQL script in the original install files that upgrades the schema from SQL2000 to SQL2005. So you have to copy those files into the /install/ folder and hit the /yoursite/install/upgradeschema.aspx page.

It threw a few errors because FTS was enabled in the store. But it fixed it enough to let me into the admin so I could turn FTS off. Then I re-ran the script and it ran all the way through with no errors.

The site lights up just fine now. Whew !!