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...Upgrading DNN P...Upgrading DNN P...Upgrade SQL and DNNUpgrade SQL and DNN
Previous
 
Next
New Post
2/10/2011 12:15 PM
 
Marc (ម៉ាក) Vanhemelryck (វ៉ាន់ហេមិលរីក) wrote:
haydenh wrote:
My situation is different than most thought. I am moving from SBS 2003 to SBS 2008 as well as upgrading from SQL Server 2000 to SQL Server 2008. Obviously, this is going to be a little more difficult and I understand that.

I can access the database fine through SQL Management Studio. I will do some more configuration and try some of the options you've suggested. Thanks for your comments. I wouldn't have even gotten this far without all the help thus far (for that I am appreciative).

 Your error is very unlikely related to the file system.

When you move a database, you do not move any other tables from the sql server. Logins and passwords are not stored in the database. When you move your database, your user id no longer refers to a valid login. That normally causes this error. But then again, if that is the cause, you should not be able to connect to the database in MSMS with that usernane/password combination.

Are the correct protocols enabled on the SQL server for the kind of access you want to make?

Have you tried using sa as user id in the web.config file (if you have that hevel of access.)? It's not a solution, but it can help figuring out where the problem lies.

A suggestion:
If you don't have sa level access, you still can go to your database, delete the user in security tab of your database and recreate the user using the wizard to select the login (the button with the three dots). Make sure dbowner is enabled in both list boxes.

Moving up: if your new version of MSSQL accepts the update, you should be okay. You may want to change compatibilty level (right-click on your database in MSMS and select properties).

If the upgrade process (2003->2008) produces errors, you're in for trouble, but I don't think it's fair to blame DNN for that. Yet it still is possible to install your database, but from what I read above, you didn't have SQL upgrade problems, so that should be good.

I think at first I was having an issue with the SQL login (orphaned I think is what I've heard people refer to it as.) Therefore, I ran a SQL statement to delete the orphan and recreated the original username and password. It seems that after I did that everything worked except for the new error I am getting which seems to be a portal alias problem.

 
New Post
2/10/2011 12:21 PM
 
Marc (ម៉ាក) Vanhemelryck (វ៉ាន់ហេមិលរីក) wrote:
A portal alias is another domain to access your portal. You allow certain urls to be processed by dotnetnuke through the bindings in your IIS settings. You can then direct one or more urls to a certain portal in the alias settings for that portal.

Instead of using the IP to access your dnn installation, use localhost if it refers to your own computer or link a domain name to the ip in your hosts file (in %windir%\system32\drivers\etc\) and use that for alias both in iis and in dnn.

 I went to http://localhost/ but got a 404 error. I will try adding localhost to the portal alias as well and see if that fixes the issue. To me though, it seems like putting in the IP of my new production server would work but I guess not.

 
New Post
2/10/2011 12:30 PM
 
Adding "localhost" to portal alias and still am receiving the same errors. Redirecting and 404 errors.

Inside IIS can I have a different "site" name or should I keep that the same? I kept the file directory structure in tack from old production server to new.

At this point, I've almost exhausted all my knowledge and time on this. Can anyone provide support for a fee? I really need to get this done ASAP.
 
New Post
2/11/2011 12:13 AM
 
Try to work systematically: it is a 3-step process.

(1) make sure the domain you use goes to the correct ip address. If you use localhost, that should be okay. Otherwise, add the domain to your hosts file. Flush your dns cache and use ping to check.
(2) make sure iis sends the request to dnn: if you use localhost, create an application under 'Default Web Site", Say you call this application MyDnnSite. You will then be able to connect to your dnn installation with http://localhost/MyDnnSite/ Make sure your permissions are set correctly during this step.
(3) make sure DNN knows which portal to bring up: make an alias for localhost/MyDnnSite

Then browse to http://localhost/MyDnnSite.

____________________________________
The one-eyed in the land of the blind.
 
New Post
2/11/2011 12:35 AM
 
The other procedure would be: say the domain name is MyPortal.com

(1) add 2 lines to your hosts file:
127.0.0.1 myportal.com
127.0.0.1 www.myportal.com

(2) create a website in iis for myportal.com. follow installation procedures.

You could then skip step 3 as your dnn installation is already configured for myportal.com

Browse to your website with http://myportal.com or http://www.myportal.com

____________________________________
The one-eyed in the land of the blind.
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...Upgrade SQL and DNNUpgrade SQL and 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