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 ...ERROR: Could not connect to database.ERROR: Could not connect to database.
Previous
 
Next
New Post
10/5/2006 4:54 AM
 
Hi,

I've been trying to install DNN 4.3.5 for about a week now, without success.

I've tried using the source, install and starter kit methods and all produce the same failure.  Each time I attempr to reinstall I create a new
database, virtual directory and source code directory.

I've tried following the standard instructions & I've followed the new set of instructions by Krishna Murthy - I've tried really hard - honest!

When I first navigate to my DNN page the following message is displayed;

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

    ERROR: Could not connect to database.

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


This would seem to indicate that the database connection strings have been set incorrectly - but I've tested them manually and they seem OKay.  
See below;


    <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=AmeyCMS;uid=DNN;pwd=password;" 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=AmeyCMS;uid=DNN;pwd=password;"/>
        <add key="InstallTemplate" value="DotNetNuke.install.config"/>
        <add key="AutoUpgrade" value="true"/>

I can see that the database has been accessed, as a new table has been created, and a few stored procedures are created.

Any help would be appreciated.

Mr T
 
New Post
10/30/2006 8:36 AM
 
Is there nobody able to suggest a solution to this problem?

It's a bit strange and the database is being accessed by DNN, but the error message says it isn't.  I think this is a spurious error message (although I don't know what the real error is!), the error message is:


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

    ERROR: Could not connect to database.

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


My web.config contains this:


<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=CMS;uid=CMS;pwd=CMS;"
      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=CMS;uid=CMS;pwd=CMS;"/>

    <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>

Any ideas would be gratefully received.

Mr T
 
New Post
10/30/2006 12:42 PM
 

I have the same problem. I am trying to debug the project in Visual Studio environment and I run into the same error

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

    ERROR: Could not connect to database.

Login failed for user 'xyz'

Any help is appreciated. I used the installer to install the 4.3.5 version. I am with this problem for past two days! Thank you

RSB


My connection strings as follows:  I have used Windows security just for testing purposes.

<connectionStrings>

<!-- Connection String for SQL Server 2005 Express

<add name="SiteSqlServer" connectionString="Server=(local);Database=DotNetNuke3;Trusted_Connection=True;" providerName="System.Data.SqlClient" /> -->

<!-- Connection String for SQL Server 2000/2005 -->

<add name="SiteSqlServer" connectionString="Server=(local);Database=DotNetNuke3;Trusted_Connection=True;" providerName="System.Data.SqlClient"/>

</connectionStrings>

<appSettings>

<!-- Connection String for SQL Server 2005 Express - kept for backwards compatability - legacy modules

<add key="SiteSqlServer" value="Server=(local);Database=DotNetNuke3;Trusted_Connection=True;" />-->

<!-- Connection String for SQL Server 2000/2005 - kept for backwards compatability - legacy modules -->

<add key="SiteSqlServer" value="Server=(local);Database=DotNetNuke3;Trusted_Connection=True;"/>

<add key="InstallTemplate" value="DotNetNuke.install.config"/>

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...ERROR: Could not connect to database.ERROR: Could not connect to database.


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