I am trying to move my DNN SQL database to a new database server and I am getting a connection error.  The exact error I get is "Invalid Connection".  My DotNetNuke website is unchanged.  I just change the connection string in the web.config file to point to the new database.  I just "Detached" the database from the original SQL server and then copied it our to the new SQL server and then "Attached" it again.  Everthing looked fine (I could open and edit tables).  I am fairly confident that I am using a proper connection string. 

What am I missing?  Is there a test I can do to see if the connection string is valid?

A little more background:

1. Original SQL Server v8.0.2273

2. New SQL server SQL Express 2005

WEBCONFIG FILE:

<configuration>
  <!-- application specific settings -->
  <appSettings>
    <!--<add key="connectionString" value="Server=localhost;Database=DotNetNuke;uid=sa;pwd=;" />-->
    <add key="ConnectionString" value="Server=76.12.35.56;Database=PortalSports;UID=gmaggioli;PWD=XXXXX;" />
    <!-- database connection details -->
  </appSettings>
 
 
  <system.web>

    <httpModules>
      <add name="HTTPHandler" type="DotNetNuke.HTTPHandler, DotNetNuke" />
    </httpModules>
    <!-- set debugmode to false for running application -->
    <compilation debug="true" />
    <!-- permits errors to be displayed for remote clients -->
    <customErrors mode="Off" />
    <!-- forms or Windows authentication -->
    <authentication mode="forms">
      <forms name=".DOTNETNUKE" protection="All" timeout="60" />
    </authentication>
    <!--
        <authentication mode="Windows">
            <identity impersonate="true"/>
        </authentication>
        -->
    <!-- allow large file uploads -->
    <httpRuntime useFullyQualifiedRedirectUrl="true" maxRequestLength="8192" />
    <!-- Adapter configuration for mobile controls used in the portal -->
    <mobileControls>
      <device name="PortalHtmlDeviceAdapters" inheritsFrom="HtmlDeviceAdapters">
        <control name="DotNetNuke.MobileControls.TabbedPanel, DotNetNuke" adapter="DotNetNuke.MobileControls.HtmlTabbedPanelAdapter,DotNetNuke" />
        <control name="DotNetNuke.MobileControls.LinkCommand, DotNetNuke" adapter="DotNetNuke.MobileControls.HtmlLinkCommandAdapter,DotNetNuke" />
      </device>
      <device name="PortalChtmlDeviceAdapters" inheritsFrom="ChtmlDeviceAdapters">
        <control name="DotNetNuke.MobileControls.TabbedPanel, DotNetNuke" adapter="DotNetNuke.MobileControls.ChtmlTabbedPanelAdapter,DotNetNuke" />
      </device>
      <device name="PortalWmlDeviceAdapters" inheritsFrom="WmlDeviceAdapters">
        <control name="DotNetNuke.MobileControls.TabbedPanel, DotNetNuke" adapter="DotNetNuke.MobileControls.WmlTabbedPanelAdapter,DotNetNuke" />
      </device>
    </mobileControls>
    <!-- Mobile device filters used for customizing portal -->
    <deviceFilters>
      <filter name="isJScript" compare="javascript" argument="true" />
      <filter name="isPocketIE" compare="browser" argument="Pocket IE" />
      <filter name="isHTML32" compare="preferredRenderingType" argument="html32" />
    </deviceFilters>
    <pages enablev13wstat3Mac="true" validateRequest="false" />
      <!--Gregg Added to fix the A potentially dangerous Request.form value.. error-->
  </system.web>
</configuration>

 

I've always used this method when moving the database:
After restoring or reattaching the db,
Create a new user in SQL Server and give it dbo access to the newly restored db
Change the connection string to use the new user

SQL Server has a problem using existing users in the db, since it doesn't match the users on the new server.

CSmith is exactly right.  It's what I'm currently in the process of doing.

Another thing to watch out for if you're moving to a newly built server.  Make sure that Computer Name of the new server has been finalized.  Renaming the server AFTER installing SQL will cause all sorts of problems.