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 ...Issues after moving DNN site to GoDaddy (installation)Issues after moving DNN site to GoDaddy (installation)
Previous
 
Next
New Post
3/10/2011 9:56 AM
 
Dear ALL,

I have a Web site hosted with a provider since 4 years (www.imposition.com).
We are now moving everything to GoDaddy.

I copied all files to GoDaddy, in the SAME directories and sub-directories;
I backed up the database and used Database Puslishing Wizard to move the database to GoDaddy.
During the publishing, I keep getting 1 error, as follows:

TITLE: SqlPubWiz

------------------------------

 

An error occured while trying to publish the following script:

/****** Object:  Table [dbo].[PortalDesktopModules]    Script Date: 03/08/2011 15:20:45 ******/

IF  EXISTS (SELECT * FROM sys.objects WHERE object_id = OBJECT_ID(N'[dbo].[PortalDesktopModules]') AND type in (N'U'))

DROP TABLE [dbo].[PortalDesktopModules]

 

 

------------------------------

ADDITIONAL INFORMATION:

 

Could not drop object 'dbo.PortalDesktopModules' because it is referenced by a FOREIGN KEY constraint. (System.Web.Services)



How can I resolve this error?  Is it important at all?


Also, it seems my web.config has issues because I also get the following error when I try to access the website on a new location (temporary) (www.impositionforum.com):

DotNetNuke Error: - Version 04.05.01


A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)


Thanks in advance for your help!!
Ray
 
New Post
3/10/2011 3:27 PM
 
Added information: connection string, etc...

<connectionStrings>
   <add name="SiteSqlServer" connectionString="Server=104509223556.db.7435434.hostedresource.com;Database=imp1104509223556;uid=******;pwd=******;" providerName="System.Data.SqlClient" />
  </connectionStrings>
  <appSettings>
    <add key="SiteSqlServer" value="Data Source=104509223556.db.7435434.hostedresource.com;AttachDbFilename=imp1104509223556;Integrated Security=True;User Instance=True" />
    <add key="InstallTemplate" value="DotNetNuke.install.config" />
    <add key="AutoUpgrade" value="true" />
    <add key="UseInstallWizard" value="fasle" />
    <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-->
    <add key="InstallationDate" value="5/8/2007" />
  </appSettings>
 
New Post
3/11/2011 9:12 AM
 
There is an error in your second (legacy) connection string which must match the information of the first (primary) connection string. In the following, the selection in yellow must be changed to be the  same as that in light green:

<connectionStrings>
   <add name="SiteSqlServer" connectionString="Server=104509223556.db.7435434.hostedresource.com;Database=imp1104509223556;uid=******;pwd=******;" providerName="System.Data.SqlClient" />
  </connectionStrings>
  <appSettings>
    <add key="SiteSqlServer" value="Data Source=104509223556.db.7435434.hostedresource.com;AttachDbFilename=imp1104509223556;Integrated Security=True;User Instance=True" />

However, that issue is not the cause of your initial publishing error and most likely not the reason that the site does not come back up following the move. Can you check the database on GoDaddy to see if any of your existing database tables were actually published. Generally if you receive a database "publishing" error that occurs as the script to publish the database is being built and before database objects are re-created in the database to which you are publishing. In regards to the specific error you received, it may also be caused by the GoDaddy database to which you are trying to publish not being empty - perhaps from previous attempt to publish or from trying to use the database that GoDaddy may have created during an automatic install of DNN.

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
3/11/2011 12:32 PM
 
Thanks Bill.

I got somewhere...

Database: I erased the database on GoDaddy and created a new one.  I then published my DNN database with DPW and all was OK (success).
So, the database for my Website seems to be complete and OK now.

web.config: I made the changes you indicated and saved it to the proper location.

I still have the save error so the site does not lauch:

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)


If you have suggestion for something else to look for in terms of configuration(s), let me know.
Thanks much,
Ray
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Issues after moving DNN site to GoDaddy (installation)Issues after moving DNN site to GoDaddy (installation)


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