Bug report-Customer avail rel - 77.975.977
database compatibility level set to anything other than an unsupported level causes random/intermittent connection issues for customers.
How are customers generally impacted?
They are on an older release such as 11.7.
They have SQL 2005.
They came from SQL 2000 and imported the DB from SQL 2000 into SQL 2005.
They migrate or upgrade SQL in order to support a newer release(12.0).
The settings DB will reflect the version of SQL it came from, 2005 or 2000.
The production DB still retains level from SQL 2000.
Installer nor DB upgrade check the level, change the level, or flag on the level. This has been an issue for some as far back as 11.9 but becomes much more prevalent in 12.0.
None of our installation/upgrade documentation or system specs make mention to the requirement of checking DB level. This is not discussed in any documentation anywhere at this time.
Customers who report random/unreproduceable errors are found to have DB levels set at unsupported versions. Changing the levels to at least SQL 2008 often resolves or greatly reduces these problems.
How does this present itself in the UI?
Some instance of data entered into UI is no longer present after adding another line. User reports the record is perfect and up to date, they save. Another use recalls this record, it is missing lines/detail which must be added.
Another user reports they have a 12 line SO, they add line 8 and save, lines disappear. They change from detail to general tab, the customer is no longer displayed on general tab. Clicking add a line button causes a line to drop. The data is present in UI but not committed to DB.
Some report that JB just closes, they are not using Autovue integration when this occurs. JB just reports "has stopped working and must close".