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 ...Migration problem with DNNMigration problem with DNN
Previous
 
Next
New Post
7/24/2008 10:08 AM
 

Hi,

I installed a copy of DNN on a win xp pro computer with sql server express and created my site just fine.   Upon migrating this site, my plan was to zip up my entire public directory, which includes the database.mdf and database_log.ldf files and extract it on the public directory of a server running IIS 6 ans SQL Server 2005.   After extracting those files, I imported the Database.mdf file using a CREATE TABLE FOR ATTACH command, and I updated the web.config file and altered the query string in the <connectionString> tag as well as in the <appSettings> tag.  Finally I updated the PortalAlias table so that the host ip would reflect the new server.

Now, I'm getting the following error:  An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005,  this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.... Error Locating Server: Instance Specified

I used the connection string in another application, and it works fine, so I'm not sure what the problem can be.   Can anyone help?

Note: here's my connection string:


    <add
      name="SiteSqlServer"
      connectionString="Server=S6;Initial Catalog=dnn;User Id=dnnuser;Password=******;"
      providerName="System.Data.SqlClient" />



thanks!

 
New Post
7/24/2008 10:38 AM
 

I've seen the first part of your error but I don't remember see that it couldn't find the server.

I did a quick google search on your error "SQL Server does not allow remote connections.... Error Locating Server: Instance Specified" and found a lot of returns. Here are some of the returns and might help you get this solved: http://bytes.com/forum/thread524548.html http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=747709&SiteID=1 http://www.mydatabasesupport.com/forums/ms-sqlserver/156653-error-26-error-locating-server-instance-specified.html

 
New Post
7/24/2008 12:51 PM
 

Well the problem is that none of these explain why that connection string works on other applications on that server.   I've been searching around on google and I really couldn't find anything.  Am I migrating my information the wrong way?   Are there other settings that need to be modified that is normally automated in the installation process?

thanks for your reply,
Greg

 
New Post
7/24/2008 1:35 PM
 

I didn't see in your first post that you were using that connection string for other applications.

The way you laid it out would be pretty much the way I would do it (or how I do it when I'm pulling a production version to my dev system) except I don't use the .mdf file on my DNN installs. I've always gone in using the SQL Management tool to create databases or back them up.

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Migration problem with DNNMigration problem with DNN


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