Just upgraded to latest nightly build, and getting the following error:

TestCase 'NNet.Config.D4Site.CreateSite' failed: TestFixtureSetUp failed in D4Site
TestFixture failed: System.ArgumentOutOfRangeException : Specified argument was out of the range of valid values.
   at Xtensive.Storage.Building.Builders.DomainBuilder.CreateHandlerFactory()
   at Xtensive.Storage.Building.Builders.DomainBuilder.BuildDomain(DomainConfiguration configuration, DomainBuilderConfiguration builderConfiguration)
   at Xtensive.Storage.Upgrade.UpgradingDomainBuilder.BuildStageDomain(UpgradeStage stage)
   at Xtensive.Storage.Upgrade.UpgradingDomainBuilder.Build(DomainConfiguration configuration)
   at Xtensive.Storage.Domain.Build(DomainConfiguration configuration)
   at NNet.AbstractTest.FeatureSetUp() in D:\Project\NNet-Web\NNet-Test\AbstractTest.cs:line 304

I paired the code down to its bare essentials and still getting error:

Xtensive.Storage.Configuration.DomainConfiguration d4config = new Xtensive.Storage.Configuration.DomainConfiguration("mssql2005://NNetTest:NNetTest@localhost/NNetTest");
d4config.UpgradeMode = Xtensive.Storage.DomainUpgradeMode.Recreate;
//d4config.NamingConvention.NamespacePolicy = Xtensive.Storage.Configuration.NamespacePolicy.Synonymize;
// d4config.NamingConvention.NamingRules = Xtensive.Storage.Configuration.NamingRules.UnderscoreDots;
//d4config.NamingConvention.NamespaceSynonyms.Add("NNet.Model", "n");
//d4config.NamingConvention.NamespaceSynonyms.Add("NNet.Model.Config", "n.c");
d4domain = Xtensive.Storage.Domain.Build(d4config);

I tried it with a memory configuration and it works:

            Xtensive.Storage.Configuration.DomainConfiguration d4config = new Xtensive.Storage.Configuration.DomainConfiguration("memory://localhost/DO40-Tests");

This thread was imported from our support forum. The original discussion may contain more detailed answer. Original topic by Anonymous.

asked Jul 24 '09 at 20:02

Editor's gravatar image


One Answer:

Alex (Xtensive) wrote:

We'll try to fix it ASAP. We'll contact you in case of any problems with repeating the issue.

Bug report to track: http://code.google.com/p/dataobjectsdot ... ail?id=310

Dmitri Maximov (Xtensive) wrote:

Hello Tony,

Recently we made huge refactoring in Xtensive.Sql layer and protocol names have been changed also. They became more generalized, server version independent, e.g.: mssql2005, mssql2008 => sqlserver pgsql, postgres => postgresql

Just update your connection url and that's it.


P.S. Yes it is a breaking change, and certainly we are going to properly highlight it in the upcoming DataObjects.Net 4.0.3 (4.0.5) release.

answered Jul 24 '09 at 21:04

Editor's gravatar image


Anonymous wrote: I did check that, but since all the tests and samples I checked were still using mssql2005 I did not try anything else.

(Jul 24 '09 at 21:04) Editor Editor's gravatar image

Hmm, it seems that we didn't update samples yet.

Anyway, give "sqlserver" protocol a try.

(Jul 24 '09 at 21:04) Dmitri Maximov Dmitri%20Maximov's gravatar image

Anonymous wrote: Now working

(Jul 24 '09 at 21:04) Editor Editor's gravatar image
Your answer
Please start posting your answer anonymously - your answer will be saved within the current session and published after you log in or create a new account. Please try to give a substantial answer, for discussions, please use comments and please do remember to vote (after you log in)!
toggle preview


Once you sign in you will be able to subscribe for any updates here



Asked: Jul 24 '09 at 20:02

Seen: 12,653 times

Last updated: Jul 24 '09 at 20:02

powered by OSQA