Hmm, it looks like it doesn't like the word "IF", if I'm reading correctly (no pun intended)

Do you have the "ForceRedirect" column on your database?

If not, you could try running this command manually against it.

ALTER TABLE [icUrlTracker] ADD ForceRedirect bit NOT NULL CONSTRAINT DF_icUrlTracker_ForceRedirect DEFAULT 0

I'm not too sure if will get you around this issue though, since in theory it should still run the update, but worth a shot.

Obviously, do backup your database before executing this command.

Hi Daniel,

Thanks for the super quick response!

Just checked the SQL CE DB and yes it has the ForceRedirect column in the database.

Cheers Andy

Hi,

Just checked the live SQL CE database and that also has the ForceRedirect column so I think this is failing on the check to see if it needs upgrading.

The version prior to the upgrade is 3.12.43 and after upgrade would be 3.13.1.

The error is happening when the site first loads and prior to Umbraco going to it's upgrade DB screen.

Thanks

Andy

How odd!

Downgraded earlier and brought the site backup so connection string was correct prior to upgrade.

Guess there could be an issue in that version of Umbraco with SQL CE, oddly it does seem to think it's SQL CE on the exception:-(

System.Data.SqlServerCe.4.0

Yes it is.

Hi Dan,

I'll fork your code tomorrow and try and step through it.

Thanks Andy

Now this is even more confusing.

If I build a debug version of the DLL all works nicely, build a release version and it fails on exactly the same thing as before.

I've got to move to something else for the rest of the day, but will try and look again over the next few days.

Hi,

Think I've worked this out now. Basically looks like a timing issue in the Umbraco source. If you look at Umbraco.Core.DatabaseContext then the DatabaseProvider function:

 public virtual DatabaseProviders DatabaseProvider
    {
        get
        {
            string dbtype = Database.Connection == null ? ProviderName : Database.Connection.GetType().Name;

            if (dbtype.StartsWith("MySql")) return DatabaseProviders.MySql;
            if (dbtype.StartsWith("SqlCe") || dbtype.Contains("SqlServerCe")) return DatabaseProviders.SqlServerCE;
            if (dbtype.StartsWith("Npgsql")) return DatabaseProviders.PostgreSQL;
            if (dbtype.StartsWith("Oracle") || dbtype.Contains("OracleClient")) return DatabaseProviders.Oracle;
            if (dbtype.StartsWith("SQLite")) return DatabaseProviders.SQLite;
            if (dbtype.Contains("Azure")) return DatabaseProviders.SqlAzure;

            return DatabaseProviders.SqlServer;
        }
    }

In debug mode the Database.Connection is null and therefore uses ProviderName which is SQLCE. With the Release version of URL Tracker it looks like you call this after the DB Connection is set up, this then uses Database.Connection.GetType().Name which actually returns the name of the Class of Database.Connection which is ProfiledDBConnecton and therefore the code defaults to returning the Provider as SQL Server.

As I said I suspect this has come to light due to a timing issue, but looks like a bug with the Umbraco Code.

I'll raise an issue on Umbraco.

Thanks for the help.

Andy

See http://issues.umbraco.org/issue/U4-10577 for Umbraco issue.

is working on a reply...