Matthias i believe u r right, that it may depend on the hosting providers setup, thats also my own conclusion.

Unfortunately i dint get to try and install after i reset the 2012 sql server db to 2008r2 compatibilty, maybe that wouldve fixed the whole issue.

I did go thru the everything aswell, like checking the usr setup in the 2012 db and compared it to working 2008 installation at the same provider, but there were no differences. :-/


However theres one major difference when i access a db on their 2012 environment and thats that i cant rightclick the database like i could in 2008.

In 2008 i would get the complete db list when accessing the db server, in 2012 i only see the db i have the proper rights to manipulate.

It would seem that the permissions are different, where in 2008 i had permissions to act at db lvl, where in 2012 i have only permissions from the db and down (if that makes sense) and therefore cant execute tasks on the db itself, like "Generate scripts" etc.

Im thinking maybe that limitation could be the cause, if the db script used by dnn to built the db require access at the db lvl and that also makes sense when the error i get from dnn install says "Login failed for user.....blablabla", thats the same error Sql Management Studio throws when i rightclick on a 2012 db.

I chked the Security>>Users and the db owner user is called domain_domainextension e.g. "xsb_dk" for the domain xsb.dk

By default the user's set as db owner and nothing further and in "owned schemas" hes also got the db owner and nothing further.

I compared it with their 2008 setup and thats the same thing, no differences. :-S


Hmm i dont understand what u mean by "Could it be that there is the Pleks used as the hostimng management ?" i dunno what "pleks" is? :-)

Oh i see. :-)
Well i dunno if theyre using that.

Yep it does look like their 2012 setup is causing the problems, yet im still gonna give it try later on whether itll work if i go reset the db settings to best match 2008r2 settings. :-)