1
Vote

The transaction specified for TransactionScope has a different IsolationLevel

description

Hi,

This module seems to do exactly what I need for redirecting some legacy pages from the old to the new URLs. I test the rule in Simulations and it checks out ok but then when trying on the site I get:

The transaction specified for TransactionScope has a different IsolationLevel than the value requested for the scope.

The error is on line 23 of TransactionManager.cs:

void ITransactionManager.Demand() {
        if (_scope == null) {
            Logger.Debug("Creating transaction on Demand");
            _scope = new TransactionScope(
                TransactionScopeOption.Required, 
                new TransactionOptions { 
                    IsolationLevel = IsolationLevel.ReadCommitted 
                });
        }
    }
I am running version 1.5.1 of Orchard and have tried the very latest version of the module, plus 1.2.2 just to see if it was a new issue.

Secondly, does this module require anything specific setup on the hosting server? Target hosting platform is IIS6.. will this just work?

Any pointers appreciated. Keep up the good work with Orchard!

Rich

comments

rawsharklives wrote Oct 4, 2012 at 9:02 AM

It seems as if this error only happens when running in Visual Studio. Just tried it with local IIS and it works fine. Is this to be expected? I will check that the rules work when deployed on to your server (IIS6).