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 ...Manual Installation on GodaddyManual Installation on Godaddy
Previous
 
Next
New Post
3/25/2006 12:24 PM
 
Hi folks. As a newbie I think I posted this originally on the wrong thread. I need help.

I am attempting to install this into my root folder of my GoDaddy hosting account. I unzipped all of the the files into a local folder, made the following mods in the web.config file. THe first 2 changes are based on info gleaned from this thread:

add
name="SiteSqlServer" connectionString="whsql-v08.prod.mesa1.secureserver.net;Database=DB_49829;uid=Boisehigh1976;pwd=*****;"
providerName="System.Data.SqlClient"

add key="SiteSqlServer" value="Server=(whsql-v08.prod.mesa1.secureserver.net);Database=DB_49829;uid=Boisehigh1976;pwd='*****';"

And this change as gleaned from the ASP.NET thread:

customErrors mode="Off"

(I took the opening and closing tag characters out because in preview mode they were causing text to disappear. Rest assured those characters are actually still there).

I assume I then need to run the install.aspx.vb program located in the install folder (is that correct?). When I try to browse the site, I get

==========

Server Error in '/' Application.
Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a tag within a "web.config" configuration file located in the root directory of the current web application. This tag should then have its "mode" attribute set to "Off".

===========

Well, I already changed the customerErrors mode to "Off", so I don't understand why I don't see an error listing.

Can someone provide any suggestions?

P.S. - After I posted this the first time, I tried cleaning everything out of my account, and setting up a new folder called DNN. I tried the install to that folder, and a first got absolutely nothing, then later got the same message. I don't think I could have anything else in the web.config, but who knows.....
 
New Post
3/30/2006 4:38 PM
 
Hey Everyone,

I have followed the above directions to the letter and am still having a problem. Has anyone encountered this one?

DotNetNuke Upgrade Error

The Assembly Version ( [ASSEMBLYVERSION] ) does not match the Database Version ( [DATABASEVERSION] )

ERROR: Could not connect to database.

The stored procedure 'tbarnett.GetPortalAliasByPortalID' doesn't exist.
 
New Post
3/30/2006 11:33 PM
 

wwday3 wrote
Hi folks. As a newbie I think I posted this originally on the wrong thread. I need help.

Well, I already changed the customerErrors mode to "Off", so I don't understand why I don't see an error listing.

Can someone provide any suggestions?

Your custom errors component should look like this:

<!-- permits errors to be displayed for remote clients -->
    <customErrors mode="Off" />

Make sure that you have the the full line with the starting and ending tags.  If your custom error is set properly you can email your config, take out your username database and password, and I will take a look at it.

House keeping note; from a security perspective you shouldn't post your login id or database name.  It just isn't needed so don't tempt anyone with it.

 
New Post
3/30/2006 11:37 PM
 
concentre wrote
Hey Everyone,

I have followed the above directions to the letter and am still having a problem. Has anyone encountered this one?

DotNetNuke Upgrade Error

The Assembly Version ( [ASSEMBLYVERSION] ) does not match the Database Version ( [DATABASEVERSION] )

ERROR: Could not connect to database.

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

If I remember correctly this means that your portals folder was not created properly, it wasn't populated during the install.  If you are installing from scratch try removing the database and creating a new one, don't forget to change the relevent information in your webconfig file.  When you first access the site and it performs the install check if the portal is reported as installed or failed.  If it fails go back and double check the virtual folder permissions.

If you are upgrading your site, let us know as that is a different set of issues.

 
New Post
3/31/2006 6:27 PM
 
O.k., I wiped out everything and started over. I reinstalled from the package I downloaded off of your website, I edited my web.config file, created my 4 directories and database and finally everything seemed to work. It went through the install, seemed to finish correctly, but when I clicked to enter my site I got this:

Server Error in '/' Application.

Object reference not set to an instance of an object.

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.NullReferenceException: Object reference not set to an instance of an object.

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:

[NullReferenceException: Object reference not set to an instance of an object.]
DotNetNuke.Entities.Portals.PortalSettings.GetPortalSettings(Int32 TabId, PortalAliasInfo objPortalAliasInfo) +124
DotNetNuke.Entities.Portals.PortalSettings..ctor(Int32 tabId, PortalAliasInfo objPortalAliasInfo) +82
DotNetNuke.HttpModules.UrlRewriteModule.OnBeginRequest(Object s, EventArgs e) +3800
System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +92
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +64


Any thoughts?


 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Manual Installation on GodaddyManual Installation on Godaddy


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