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 ...Error creating Portal (ver. 4.3.0)Error creating Portal (ver. 4.3.0)
Previous
 
Next
New Post
6/23/2006 12:20 PM
 

Here's a final follow-up

First - thanks for the tip about running the SQL in the portal window - I've never had occassion to use it, but I will now.

The pain continued for me (seemingly random errors, slow response too), so I got a bit more drastic. I did a parallel fresh install of DNN 4.3.1, then scripted out all of the SPs, since I figured my problems were in there somewhere. I ran the script in my original install and things got a lot better. No errors yet and it feels faster.

I still couldn't log in with admin accounts on some portals though, but I realized they were the portals created when the application name was changed (see above). I verified this idea by looking at the aspnet tables, but I fixed it by creating new admin users instead of manually trying to change the application GUID for the users - that seemed like a dangerous thing to me!

I then deleted the old users through the portals, which caused an error because the user and app name combination didn't exist in the aspnet tables. There are a few remnant users in there now, but I don't think it matters - they can't be deleted manually anyway.

I can now login with all my accounts and create child portals

 
New Post
6/23/2006 5:27 PM
 

Running the SQL provider file also fixed my problem with creating new portals on an upgraded 4.3.1 server.  However, I had to remove the comments sections in the the script to run it in the Host:SQL window.  Apparently running the scripts from the Host:SQL window replaced the user and object prefixes.

Nice trick!

 
New Post
6/24/2006 11:07 PM
 
Sorry guys... Happy to hear it has worked... I am noob at this, so...

Okay logged in as Host.
Under host menu selected "SQL".
In Textbox typed "03.02.06.SqlDataProvider"

Is this all I need to do?

Do I need to tick "Script" textbox? Type "GO" before???

Then just click on "Execute"?

Thanks again.
 
New Post
6/25/2006 6:27 PM
 
Anyone out there that can steer me in the right direction?

I gather it is a simple script that need to be run... just wishing to know what I should enter etc...
 
New Post
6/25/2006 9:44 PM
 
Okay the above couple of posts were not meant to be rhetorical questions... ... but a big thanks to the guys who posted previously. I now understand what was needed.

You take the text/code inside the file called "03.02.06.SqlDataProvider" and copy/paste it into the text filed provided. Then tick the checkbox for "Run as Script", and then click the "Execute" link and within seconds it finishes.

I tried this on 2 websites that had been upgraded from 4.0.3 to 4.3.1 and they can both now create child portals. Just wanted to add this in case it helps others. Thanks again for the posters above. Cheers.
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Error creating Portal (ver. 4.3.0)Error creating Portal (ver. 4.3.0)


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