Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Assembly version does not match db version. what could this mean?Assembly version does not match db version. what could this mean?
Previous
 
Next
New Post
1/13/2007 8:59 AM
 
Please can somebody help me out here!

I am executing a clean install of DNN 4.03.07 via manual install as opposed to using the starter-kits installers, and always get the following confusing error message:

DotNetNuke Upgrade Error
The Assembly Version ( [ASSEMBLYVERSION] ) does not match the Database Version ( [DATABASEVERSION] )

ERROR: Could not connect to database.

Unable to open the physical file "C:\Inetpub\wwwroot\dotnetnuke\Website\App_Data\Database.mdf". Operating system error 5: "5(Access is denied.)". An attempt to attach an auto-named database for file C:\Inetpub\wwwroot\dotnetnuke\Website\App_Data\Database.mdf failed. A database with the same name exists, or specified file cannot be opened, or it is located on UNC share.


I am not upgrading but making a clean installation. My resources are as follows

An HP/Compaq nw8240 mobile workstation
xp pro(sp2)
IIS 5
sqlserverExpress 2005
I also have VS.Net2005 installed on the machine meaning that my wwwroot folder is shared for hosting ASP.Net pages
Also I have placed the dotNetNuke source folder inside wwwroot and am accessing it from a browser as a virtual directory which I have called dnn.

I have created web.config and seen to it that all the parameters listed out on the howto manuals and books are in place.
I have attached the APP_DATA/database.mdf file using ms SQL server Management studio Express.
Seen to it that the database_log.ldf file was duely created.
Given full file(permission) control to the administrator/user under whose Windows authentication login I am connecting the SQLserverExpress 2005
Made sure that this user called dnnuser has role as dbowner and maps to {servername}\Administrator also is registered via ms SQL server Management studio Express as the default owner of the database.
Yet I still keep getting the frustrating error messages above.

Below are the relevant parts of my web.config file which I haven't needed to change anything in since all the manuals indicate that those values would universally map to the relevant destinations, automatically(Is this wrong?)




<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>
  <appSettings>
    <!-- Connection String for SQL Server 2005 Express - kept for backwards compatability - legacy modules   -->
    <add key="SiteSqlServer" value="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;"/>
    <!-- Connection String for SQL Server 2000/2005 - kept for backwards compatability - legacy modules
    <add key="SiteSqlServer" value="Server=(local);Database=DotNetNuke;uid=;pwd=;"/>
    -->
    <add key="InstallTemplate" value="DotNetNuke.install.config" />
    <add key="AutoUpgrade" value="true" />
    <add key="InstallMemberRole" value="true" />
    <add key="ShowMissingKeys" value="false" />
    <add key="EnableWebFarmSupport" value="false" />
    <add key="EnableCachePersistence" value="false"/>
    <add key="HostHeader" value="" /><!-- Host Header to remove from URL so "www.mydomain.com/johndoe/Default.aspx" is treated as "www.mydomain.com/Default.aspx" -->
    <add key="RemoveAngleBrackets" value="false" /><!--optionally strip angle brackets on public login and registration screens-->
    <add key="PersistentCookieTimeout" value="0" /><!--use as persistent cookie expiration. Value is in minutes, and only active if a non-zero figure-->
  </appSettings>




Please can somebody help me out on this. Thanks in advance
 
New Post
1/13/2007 12:57 PM
 

Where you have already created and "attached" the database using SQL Server Management Studio, your web.config should be using the second form of the connection string (the one for SQL Server 2000/2005) not the one for SQL Server 2005 Express.  Currently the comment markers <-- and --> in the web.config are positioned such that the connection strings for SQL Server 2005 Express are the ones being used.

Try:

1. Repositioning the comment markers to activate the second form of the connection string. AND
2. Modify this connection string to include the correct values for Server=???; uid= ???, and pwd=???

From the values that you mentioned, it should be (with ??? being replaced by your password):

"Server=.\SQLExpress;Database=DotNetNuke;uid=dnnuser;pwd=???;"


Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
 
New Post
1/13/2007 3:21 PM
 
Thanks very much imagemaker. I did as you suggested and received the following reaction:

DotNetNuke Upgrade Error

The Assembly Version ( [ASSEMBLYVERSION] ) does not match the Database Version ( [DATABASEVERSION] )

ERROR: Could not connect to database.

The stored procedure 'dbo.GetPortalAliasByPortalID' doesn't exist.

Please also note the following :-
The database I attached is the database.mdf file which came with the source code and was placed in App_data folder. So I did not create the Db but made use of the .mdf file in the distribution.
After ataching it, it was listed in the databases tree in Management studio as Database.MDF.

so my new connection string and 'app settings' are as follows:

<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=.\SQLExpress;Database=Database.mdf;uid=dnnuser;pwd=obyno123;"
      providerName="System.Data.SqlClient" />
  
  </connectionStrings>
  <appSettings>
    <!-- Connection String for SQL Server 2005 Express - kept for backwards compatability - legacy modules  
    <add key="SiteSqlServer" value="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;"/> -->
    <!-- Connection String for SQL Server 2000/2005 - kept for backwards compatability - legacy modules -->
    <add key="SiteSqlServer" value="Server=.\SQLExpress;Database=Database.mdf;uid=dnnuser;pwd=obyno123;"/>
   
    <add key="InstallTemplate" value="DotNetNuke.install.config" />
    <add key="AutoUpgrade" value="true" />
    <add key="InstallMemberRole" value="true" />
    <add key="ShowMissingKeys" value="false" />
    <add key="EnableWebFarmSupport" value="false" />
    <add key="EnableCachePersistence" value="false"/>
    <add key="HostHeader" value="" /><!-- Host Header to remove from URL so "www.mydomain.com/johndoe/Default.aspx" is treated as "www.mydomain.com/Default.aspx" -->
    <add key="RemoveAngleBrackets" value="false" /><!--optionally strip angle brackets on public login and registration screens-->
    <add key="PersistentCookieTimeout" value="0" /><!--use as persistent cookie expiration. Value is in minutes, and only active if a non-zero figure-->
  </appSettings>


I hope all thses make meaning to you. Thanks a bunch.
 
New Post
1/13/2007 4:53 PM
 

Sorry about that - I mistakenly thought that you had created and set up the database using SQL Server 2005 Management Studio Express.  At this point I think there are two ways to proceed:

1. Use Management Studio to first DETACH the database then return to using the original connection strings. This may not work due to problems that have been reported in trying to connect to the database from DNN after any connection to it from Management Studio.  See Shawn Mehaffie's blog for more information: http://www.dotnetnuke.com/tabid/825/EntryID/1202/Default.aspx

or

2. Use Studio Management Express to create a new database setting it up so that dnnuser has dbowner privileges then modify the SQL 2000/2005 connection strings to reference the new database. Do not use the .mdf extension as part of the database name. Also make sure that SQL Server Express is set up for both SQL Server and Windows Authentication (not just Windows Authentication).  Your connection string should look like:

Server=.\SQLEXPRESS;Database=MyDataBaseName;uid=dnnuser;pwd=obyno123;

I would recommend the second approach!


Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
 
New Post
1/13/2007 5:58 PM
 

If you continue to have problems, try either one of these two methods and tell me where you get stuck

  • Setting-up the Environment (using IIS)
  • Setting-up the Environment (without IIS)


  • Michael Washington
    http://ADefWebserver.com
    www.ADefHelpDesk.com
    A Free Open Source DotNetNuke Help Desk Module
     
    Previous
     
    Next
    HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Assembly version does not match db version. what could this mean?Assembly version does not match db version. what could this mean?


    These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

    For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

    1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
    2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
    3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
    4. No Flaming or Trolling.
    5. No Profanity, Racism, or Prejudice.
    6. Site Moderators have the final word on approving / removing a thread or post or comment.
    7. English language posting only, please.
    What is Liquid Content?
    Find Out
    What is Liquid Content?
    Find Out
    What is Liquid Content?
    Find Out