We use a custom SQL user for accessing the DB in the connection string (i.e. NOT Windows integrated authentication) and the DB script failed (due to not being "NetworkService"?) but still updated the internal DB version number.
When I changed originally from "ApplicationPoolIdentity" to "NetworkService" after the script failed and re-opened Install.aspx, it reported the DB version as "1.5.256", which was actually incorrect then after script failed.
More error checking in the script required before updating the internal DB version perhaps?
When I changed originally from "ApplicationPoolIdentity" to "NetworkService" after the script failed and re-opened Install.aspx, it reported the DB version as "1.5.256", which was actually incorrect then after script failed.
More error checking in the script required before updating the internal DB version perhaps?