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 ...dbo.GetPortalAliasByPortalID Doesndbo.GetPortalAliasByPortalID Doesn't Exist While Installing
Previous
 
Next
New Post
3/18/2008 8:37 PM
 

I'm new to the whole DotNetNuke thing, so please excuse my ignorance.

When I try installing DotNetNuke, I get the following error...


The stored procedure 'dbo.GetPortalAliasByPortalID' doesn't exist.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.InvalidOperationException: The stored procedure 'dbo.GetPortalAliasByPortalID' doesn't exist.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[InvalidOperationException: The stored procedure 'dbo.GetPortalAliasByPortalID' doesn't exist.]
System.Data.SqlClient.SqlCommand.DeriveParameters() +878648
System.Data.SqlClient.SqlCommandBuilder.DeriveParameters(SqlCommand command) +88
Microsoft.ApplicationBlocks.Data.SqlHelperParameterCache.DiscoverSpParameterSet(SqlConnection connection, String spName, Boolean includeReturnValueParameter, Object[] parameterValues) +212
Microsoft.ApplicationBlocks.Data.SqlHelperParameterCache.GetSpParameterSetInternal(SqlConnection connection, String spName, Boolean includeReturnValueParameter) +303
Microsoft.ApplicationBlocks.Data.SqlHelperParameterCache.GetSpParameterSet(String connectionString, String spName, Boolean includeReturnValueParameter) +154
Microsoft.ApplicationBlocks.Data.SqlHelperParameterCache.GetSpParameterSet(String connectionString, String spName) +36
Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, String spName, Object[] parameterValues) +200
DotNetNuke.Data.SqlDataProvider.GetPortalAliasByPortalID(Int32 PortalID) +87
DotNetNuke.Entities.Portals.PortalAliasController.GetPortalAliasByPortalID(Int32 PortalID) +35
DotNetNuke.Entities.Portals.PortalSettings.GetPortalAliasLookup() +74
DotNetNuke.Entities.Portals.PortalSettings.GetPortalAliasInfo(String PortalAlias) +14
DotNetNuke.HttpModules.UrlRewriteModule.RewriteUrl(HttpApplication app) +3349
DotNetNuke.HttpModules.UrlRewriteModule.OnBeginRequest(Object s, EventArgs e) +1172
System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +92
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +64


Any special reason why this is happening?

 
New Post
3/18/2008 11:54 PM
 

Something interrupted the installation. There can be many dfifferent reasons, although they are usually related to file permissions and web.config settings, especially connection strings and objectQualifier. If anything failed, you end up with an incomplete installation.

There are different techniques depending on what version of DotNetNuke you are using, but the guaranteed solution is to delete the database and recreate it, then delete all the files in your virtual folder and reinstall them, including editing web.config.

Then browse to your DotNetNuke site and you should be off and running.

I hope this is of some help to you.


Dwayne J. Baldwin
 
New Post
3/18/2008 11:54 PM
 

(this post was duplicated by accident)


Dwayne J. Baldwin
 
New Post
3/19/2008 9:17 AM
 

Seems like it's a common problem and has been causing trouble for years.

I've just installed 4.8.2 using the Typical option and it got stuck whilst installing the scripts, the red progress bar just kept on going.

I checked the database and it had created one table and a couple of SPs but I killed it in the end.

Anyhow started from scratch as suggested above and this time I selected the Auto option as suggested by other threads and it workd fine.

Regards,

Matt

 
New Post
3/19/2008 12:25 PM
 

I think the biggest secret is to get the web.config settings right the first time around.

You can't launch your site and say "whoops" I meant this database or I'll just fix the permission problem that caused that.  It's way too late.

The second biggest secret is to use app_offline.htm.

Just because you are installing your site does not mean that someone or somebot can't come along and trigger the install without your knowledge. You are in the middle of editing your web.config when your friend refreshes the page to see how it looks. Bam! Someone just found your site on a search engine. Bam! A bot happens to examine the domain. Bam! What information from web.config gets used? Is it correct? Did it install to a different server or use a different objectQualifier? Were the machine keys correct?

I believe the live, online nature of websites is the second largest contibuting factor to problems with DotNetNuke, especially upgrades. By far, the most popular problem is for people to RTFM.

Perhaps we need an install/upgrade checklist that must be used before before launching or taking off.

Many simply attempt to fly by the seat of their pants, then can't understand why they crash. They prefer to blame it on something mechanical.


Dwayne J. Baldwin
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...dbo.GetPortalAliasByPortalID Doesndbo.GetPortalAliasByPortalID Doesn't Exist While Installing


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