Sorry i don't kwow what a ObjectQualifier is?
I've tried a few minutes to update at home this time it works :). Here i have a win 2003 server with sql server 2000 at work is a 2003 server with sql server 2000 and sql server 2005, the database is also running under sql 2000.
No i notice something strange at home in the web.config.
Here the difference in the web.config backup and the new one.
The backup web.config
<connectionStrings>
<!-- Connection String for SQL Server 2005 Express -->
<add name="SiteSqlServer"
connectionString="Data Source=(local);Initial Catalog=DotNetNuke;Integrated Security=True"
providerName="System.Data.SqlClient" />
<!-- Connection String for SQL Server 2000/2005
<add
name="SiteSqlServer"
connectionString="Server=(local);Database=DotNetNuke;uid=;pwd=;"
providerName="System.Data.SqlClient" />
-->
</connectionStrings>
the new web.config
<connectionStrings>
<!-- Connection String for SQL Server 2005 Express -->
<add name="SiteSqlServer"
connectionString="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;"
providerName="System.Data.SqlClient" />
<!-- Connection String for SQL Server 2000/2005
<add
name="SiteSqlServer"
connectionString="Server=(local);Database=DotNetNuke;uid=;pwd=;"
providerName="System.Data.SqlClient" />
-->
</connectionStrings>
At work i´ve only seen that the part of the 2000/2005 connection string was the same, now i see that at home with no 2005 server it still uses the connection string from 2005 express. Tomorrow i will check at work of this is also the problem there.
Anyone a clue how this is possible because for me this is pretty confusing.
Thanx for the help