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

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Upgrading the DNN website database from sql2000 to sql2005Upgrading the DNN website database from sql2000 to sql2005
Previous
 
Next
New Post
5/25/2012 8:09 AM
 
I have 2 DNN websites - both were running off databases from SQL2000 and have just been upgraded to SQL2005.
(running on different web servers).

The first one was upgraded sucessfully. However, I have a problem with the second one. The website doesn't load when trying to connect to my SQL2005 database.
Error message just says: Site Unavailable (default DotNetNuke message).

I followed the very same steps both databases:

1. Backed up sql2000 db.

2. Placed a copy of the above .BAK file on the SQL2005 server (in the same path/location as above.

3. Created a new database on the SQL2005 server (with the same name)

4. Restored the database (on SQL2005) using the copied .BAK file from the SQL2000 back up (from step 2 location)

5. Re-created the database user (which is the same for both, lets call the user NIGEL) and given dbo rights to the database user

6. Checked for any orphaned users, by using this script below:
EXEC sp_change_users_login 'Report'

7. Used this script to fix orphaned users:
EXEC sp_change_users_login 'update_one', 'NIGEL', 'NIGEL'

NOTE: in both databases - I did get NIGEL listed as an orphaned user, and the above script fixed it.

8. Re-run the script in step 6 again to check that orphaned users have gone.

9. Changed the connection string to point to the IP address of the new SQL2005 server (in web.config file).

SQL2005 INFO:
* Both databases have the db user 'NIGEL' listed under the database >> security >> users.

* Under the properties of this user on General Tab the username and default Schema is the same and db_owner is checked.

* Under the Securables Tab >> Execute permissions have been granted.

SECURITY >> LOGINS >> PROPERTIES >>
>> SERVER ROLES: Public is checked
>>User Mapping : User and Default Schema is the same for both
>> Status: Grant and enabled - are selected.

FURTHER INFO:
* I can ping the SQL2005 server ok from both web servers.
* If I replace the IP address in web.config back to the old SQL200 address the site runs ok.

I don't know what to check next.
Any ideas?

thanks in advance,
mark.
 
New Post
5/26/2012 4:24 AM
 
did you enable tcp/ip protocol for sql client on both web servers?
what do you get displayed when calling /install/install.aspx?

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
5/28/2012 7:56 AM
 
yes, tcp/ip is enabled on both web servers (it was running ok, connecting to the old sql200 database and still runs ok if i change the IP in the web.config file back to sql2000 ip address).

If I run the install file it gives me this error:

Installing DotNetNuke
Upgrade error: ERROR: Could not connect to database specified in connectionString for SqlDataProvider


(this also changes the machine config too, so I just replace it back the original machine config name)
 
New Post
5/28/2012 10:47 AM
 
there is definately a twist in your database connection - hard to tell where without access to your site. make sure to edit BOTH uncommented connection strings in your web.config file simualtaneously.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
5/28/2012 11:16 AM
 

thanks for your reply.

here is a sample of my web.config:

<add name="SiteMyNamedServer connectionString="Data Source=123.45.67.89;Initial Catalog=NIGEL;user ID=NIGEL;Password=MyPasswd" />
</connectionStrings>

<appSettings>
 <add key="SiteMyNamedServer value="Data Source=123.45.67.89;Initial Catalog=NIGEL;user ID=NIGEL;Password=MyPasswd" />

Do you think its related to the web.config file?
I can't understand why - with my first upgrade I only had to change the IP address in the web.config file.
So I was thinknig it might be something to do with sql2005, perhaps permissions or something.

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Upgrading the DNN website database from sql2000 to sql2005Upgrading the DNN website database from sql2000 to sql2005


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