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 ...Problems moving database from one physical machine to a new oneProblems moving database from one physical machine to a new one
Previous
 
Next
New Post
9/2/2008 9:49 PM
 

Google this, "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." and you will find your solution.

 

Stuart


Hilbert Solutions, LLC
Owner, Hilbert Solutions, LLC
http://www.HilbertSolutions.com
A DNN Service Provider
From Module Development to DNN Upgrades, your one stop DNN Shop
 
New Post
10/6/2008 10:13 PM
 

New error!

It never gets old...

Here is what I get now after moving the DB, attaching it, recreating users, checking web.config, moving website files exactly as they were, etc.

Server Error in '/' Application.
--------------------------------------------------------------------------------

Login failed for user 'theburbblog.com'. The user is not associated with a trusted SQL Server connection.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Data.SqlClient.SqlException: Login failed for user 'theburbblog.com'. The user is not associated with a trusted SQL Server connection.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. 

Stack Trace:


[SqlException (0x80131904): Login failed for user 'theburbblog.com'. The user is not associated with a trusted SQL Server connection.]
   System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) +437
   System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +82
   System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +105
   System.Data.SqlClient.SqlConnection.Open() +111
   Microsoft.ApplicationBlocks.Data.SqlHelperParameterCache.DiscoverSpParameterSet(SqlConnection connection, String spName, Boolean includeReturnValueParameter, Object[] parameterValues) +204
   Microsoft.ApplicationBlocks.Data.SqlHelperParameterCache.GetSpParameterSetInternal(SqlConnection connection, String spName, Boolean includeReturnValueParameter) +303
   Microsoft.ApplicationBlocks.Data.SqlHelperParameterCache.GetSpParameterSet(String connectionString, String spName, Boolean includeReturnValueParameter) +154
   Microsoft.ApplicationBlocks.Data.SqlHelperParameterCache.GetSpParameterSet(String connectionString, String spName) +36
   Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, String spName, Object[] parameterValues) +200
   DotNetNuke.Services.Log.EventLog.DBLoggingProvider.Data.SqlDataProvider.GetLogTypeConfigInfo() +68
   DotNetNuke.Services.Log.EventLog.DBLoggingProvider.DBLoggingProvider.GetLogTypeConfigInfo() +108
   DotNetNuke.Services.Log.EventLog.DBLoggingProvider.DBLoggingProvider.GetLogTypeConfigInfoByKey(String LogTypeKey, String LogTypePortalID) +62
   DotNetNuke.Services.Log.EventLog.DBLoggingProvider.DBLoggingProvider.AddLog(LogInfo objLogInfo) +72
   DotNetNuke.Services.Log.EventLog.LogController.AddLog(LogInfo objLogInfo) +176

 
 

 
New Post
10/8/2008 7:57 PM
 

Tried again from scratch, and still get the above error. Only from host machine, everywhere else is a dnn page that says the site is not available.

Here are my steps:

  • add new aliases
    • in the dnn host section, select the site icon at the top, and add any testing aliases that will be used on the new machine until DNS settings are
    • changed and the site can return to it's regular domain name.
  • back up everything before making any changes.
    • zip up webroot folder
    • backup database
  • stop your web service
    • in ISS- find the website to move, and stop it.
  • find DB files
    • in the database management software, lookup where the database files are located
  • detatch database
    • in the database management software, right click on the database, and detatch it.
  • copy db files
    • copy over the files (at least 2) that were discovered in step 4 to the new machine
  • copy site files
    • copy over zip file created in step 2, and unzip it into it's new home
    • ensure iis and folder settings are consistent with the fresh dnn install guide
  • attach db files
    • on the new machine in database management software, right click on databases, and select attach.  point the software to the .mdf file, and it should detect the log file
  • start iis on new machine
    • fire up the new site, and see if it works!
 
New Post
10/20/2008 9:34 AM
 

I would really appreciate some additional help on this issue.

I know that DNN is free- but I have been an advocate of it for quite a while, getting other people to use it- helping them where I can.  This seems to be a major drawback to me.  I simply can not get this thing moved from one physical machine to another.  I'm not using any shared hosting plans- I have full access to the two machines.  I would love to be able to move this- to help someone else run a DNN instance on their home PC for testing, and move it to a live server when it's ready.  I don't know where else to look to for help.  At this point, I am paying $150/month to keep two sites up, because I can't get them moved.  My other DNN sites running were small enough that I just gave up and used the amazing copy/paste method to move them.  What kind of techie does that make me?  So please help.  Even if it's just pointing me in the right direction.  DNN is getting WAY too expensive for a free-open-source product at this point.  Had I known it would take me this much time and money to get a single site (or multiple sites) moved, I never would have used DNN in the first place.  I feel that with every step I've taken, I'm just a few simple clicks or config files away.  I think once my issues are ironed out, I can be a moving machine, and get 50 sites moved a day if I needed to.

Let me know what additional info you need to help solve this.  If someone is daring enough to do a confrence call with me, and some sort of desktop sharing, I will set it up!  Anything that will cost me less than $150 per month to get this issue resolved.

 
New Post
10/21/2008 1:21 AM
 

The following the the method I've always used, but this is because both sql servers can see each other on the network:

1.  Create a blank database on the second server.

2.  Launch the the copy data wizard with enterprise manager from the database you've just created.

3.  Choose the source database from the other sql server, and it defaults to your blank database as the destination database.

4.  Choose to copy all data objects and their dependancies.  Replace existing data.

5.  I don't copy users or object level permissions if users does not exist in both servers.  [Edit] from the look of your most recent error message, you should check the destination server properties to make sure it is enabling the type of security you are using.

6.  Let her rip, and in a matter of a couple of minutes, all done...  Database copied.

 

 

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Problems moving database from one physical machine to a new oneProblems moving database from one physical machine to a new one


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