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 ...Connection String issues - I think?Connection String issues - I think?
Previous
 
Next
New Post
10/26/2012 4:24 PM
 

We're trying to migrate our DotNetNuke installation and our horrible former vendor is now refusing to assist further (I'll save you the rant). 

I've got the database moved, except for the view "Forum_vw_ForumUsers", but I suspect I can get further than we are without rectifying that part right away - correct me if I'm wrong. :)

You can see what we're getting here:
http://d76462.u42.multacom.com/Defaul...


This site is currently Unavailable

Please check back later

If I understand correctly, that should be a connection string issue, but I just can't find where I'm going wrong there...
Below is what we've got for the web.config connectionStrings and appSettings. We're migrating on to SQL Server 9.0.5000 - is there anything obvious I'm doing wrong or missing below?


<connectionStrings>
    <add name="SiteSqlServer" connectionString="Server=SERVERNAME;Database=DBNAME;uid=DBUSER;pwd=PASSWORD;" providerName="System.Data.SqlClient"/>
  </connectionStrings>

  <appSettings>
    <add key="SiteSqlServer" value="Server=SERVERNAME;Database=DBNAME;uid=DBUSER;pwd=DBPASSWORD;"/>
    <add key="InstallTemplate" value="DotNetNuke.install.config" />
    <add key="AutoUpgrade" value="false" />
    <add key="UseInstallWizard" value="true" />
    <add key="InstallMemberRole" value="true" />
    <add key="ShowMissingKeys" value="false" />
    <add key="EnableCachePersistence" value="false" />
    <add key="HostHeader" value="" />
    <add key="RemoveAngleBrackets" value="false" />
    <add key="PersistentCookieTimeout" value="0" />
    <add key="InstallationDate" value="3/3/2011" />
  </appSettings>

 
New Post
10/26/2012 10:25 PM
 
Both Connection strings looks fine on your sample. But it could have other reasons with SQL Server settings.

Please check if the databaseOwner property is set as the same as the default Schema on teh SQL Server.

Be sure the DBUser have is set to the Default Schema of the SQL Server, and is mapped to the database. If you have also a dbo user on your database be sure after the restore the Login user is mapped.

After a restore of a database most times the on the database security/User tab the dbo user have not mapped to a Login Name.

Make sure the SQL Server allows remote connections, and is configured using TCP/IP protocoll.
 
New Post
10/27/2012 4:55 AM
 
please make sure, your sql server user is mapped to the database with dbowner permission granted.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
10/29/2012 4:53 PM
 
As far as I can tell the user is mapped, but I've asked the hosting provider to double check for me from their end. It's very difficult trying to work on this remotely.

I am pretty sure now that the connection strings are good. I installed a fresh DNN without issue after the host made some tweaks from their end this morning. I'm using the same strings, with only the database name changed, when trying to configure this migration.


A little more detail on our scenario:

I'm restoring our database from a .BAK on my local SQL server, then Exporting it over to the new hosting through SQL Management Studio. Since our old host is not cooperating in the least, it's unfortunately my only option. Files are uploaded from a full copy made by the old host as well.

Data appears to have been moved over okay, except I had to re-create each view manually, as they wound up as tables when exported automatically.
 
New Post
10/29/2012 10:17 PM
 

I hope the file backup is from the same date as the dtabase backup, otherwise it could not work.  The file Version and database Version must be the same (check Version table on database and the Version no. of your DoNetNUke.dll).  Check your pysical permissions on the DNN root Folder the IUser(IUsers) have read permissions and your application pool user have full Access! 

on your MS SQL Server, Check if the database user is part of the Database\Security\Logins and have to correct password.  Check on this user Setting if the user is mapped to the database with the Default Schema Name as the value of the databaseOwner into your web.config file.  Check on your Database Security\users the username have a Login Name!

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Connection String issues - I think?Connection String issues - I think?


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