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
8/1/2006 7:15 PM
 

Yeah it sucks that it happend, but it did. And it's problably a situational error. Like x, y, and z conditions have to be met for this error to occur so it doesn't happen for everyone. Anyone that has ever developed software has ran into this sort of thing. It's impossible to test for every possible configuration.

I would relay that to your client, and call the host and ask them if they can restart IIS. Most decent hosts would be happy to do so.

Good Luck!

 
New Post
8/3/2006 7:06 AM
 

I can confirm that I had this error when upgrading from 4.0.3 to 4.3.3.
The cause in my case was as people mentioned in this thread the SQL in the provider file "03.02.06.SqlDataProvider" was correct but didn't seem to have been applied to the database.

Basically the original version of the following Stored Proc was still in the database:
"AddPortalInfo" - this original version still has EXTRA variables passed in to it namely:

@FirstName          nvarchar(100),
@LastName           nvarchar(100),
@Username           nvarchar(100),
@Password           nvarchar(50),
@Email              nvarchar(100),

These need to be removed from the stored procedure - it then works fine

It is worth noting that in the Code Behind (Source Code) there is the following comment which explains that this is a quite recent ammendment:

[cnurse]    05/10/2006  Removed unneccessary use of Administrator properties.

I have the advantage of being able to manage my database directly so I could just edit the Stored Proc. If you rely on the DNN interface I would suggest running just the Create Procedure part of the code (Remembering that the top part i.e. the DROP part of the SQL is important):

Remember to change the {databaseOwner} to the owner (if logged in as host you may be able to remove it. Also you can probably remove {objectQualifier} so the statement might look like: "if exists (select * from dbo.sysobjects where id = object_id(N'dbo.[AddPortalInfo]') and OBJECTPROPERTY(id, N'IsProcedure') = 1)").


Relevant Code From "03.02.06.SqlDataProvider"

if exists (select * from dbo.sysobjects where id = object_id(N'{databaseOwner}[{objectQualifier}AddPortalInfo]') and OBJECTPROPERTY(id, N'IsProcedure') = 1)
    DROP PROCEDURE {databaseOwner}[{objectQualifier}AddPortalInfo]
GO

CREATE PROCEDURE {databaseOwner}[{objectQualifier}AddPortalInfo]
    @PortalName         nvarchar(128),
    @Currency           char(3),
    @ExpiryDate         datetime,
    @HostFee            money,
    @HostSpace          int,
    @SiteLogHistory     int,
    @HomeDirectory        varchar(100)

as
DECLARE @PortalID int

insert into {objectQualifier}Portals (
  PortalName,
  ExpiryDate,
  UserRegistration,
  BannerAdvertising,
  Currency,
  HostFee,
  HostSpace,
  Description,
  KeyWords,
  SiteLogHistory,
  HomeDirectory
)
values (
  @PortalName,
  @ExpiryDate,
  0,
  0,
  @Currency,
  @HostFee,
  @HostSpace,
  @PortalName,
  @PortalName,
  @SiteLogHistory,
  @HomeDirectory
)

SET @PortalID = SCOPE_IDENTITY()

IF @HomeDirectory = ''
BEGIN
    UPDATE {objectQualifier}Portals SET HomeDirectory = 'Portals/' + convert(varchar(10), @PortalID) WHERE PortalID = @PortalID
END

SELECT @PortalID
GO





 
New Post
8/15/2006 2:29 PM
 
I can confirm that there is a bug with a missing script.

While laurencepostgate has correctly identified the script that failed to run - this is actually because 4.0.6 is missing the text in 3.2.6.  Users upgrading from 4.0.x will never run any 3.x scripts.  For the most part the scripts 3.2.x are identical to similar 4.0.x script.  Unfortunately 4.0.6 is not the same as 3.2.6, and therefore the "upgrades" required are never run.  Please see Gemini Issue 3866

I also provide more information in my Blog

Thanks again to laurencepostgate for correctly identifying the problem and the solution.


Charles Nurse
Chief Architect
Evoq Content Team Lead,
DNN Corp.

Want to contribute to the Platform project? - See here
MVP (ASP.NET) and
ASPInsiders Member
View my profile on LinkedIn
 
New Post
8/15/2006 6:03 PM
 

 recently upgraded from 4.0x to 4.3.4. I am running Windows Server 2003

Attempts to create a portal resulted in "Error Creating Portal"

I ran the script and there were no errors.

I created a new portal and the result was a "The page cannot be found" page instead of logging me into the new portal.

The new portal is listed on the host/portals page, but clicking on the link under "Portal Aliases" sends me to the same "The page cannot be found" page.

Any thoughts?

Thanks in Advance

 
New Post
8/16/2006 1:26 AM
 

Charles, thank you for paying attention to this issue and working the fix into the next release.

rognoid you are experiencing a different issue altogether.  Most likely the problem is either that you aren't able to resolve the host address, or that it needs to be added to the host headers in IIS for your web site but either way it's almost certainly a server configuration issue and not a DNN issue.



Shane Miller
Call Centers 24x7
 
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