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 ...Problem Install DNN 4.4.1Problem Install DNN 4.4.1
Previous
 
Next
New Post
2/2/2007 6:30 AM
 
Hello!
I'm a newbie to asp.net 2.0 and DNN 4.4.1. I have experience to install 3.x version on both local and host. My problem now is that I tried to install a clean DNN 4.4.1 at my webhotel and it failed several times. So I have these info and questions and maybe someone can help:
- I set up a subdomain in the controlpanel (at my host)
- I configured that domain to have Frontpage Extensions, ASP, ASPNET and directory index is set to default.aspx
- The database was correctly set up
- I also renamed release.config to web.config. I made the configuration to connectionstrings and appsettings as well with the correct databasesettings. My host offer MS SQL databases, so I commented out the settings for SQL Express, both in connectionstrings and appsettings. I also experimented with settings in databaseOwner="" and tried with dbo and without dbo (you see, in my experience with dnn 3.x I have several times tried without dbo and that was successful).

Is there more settings I have to consider in the web.config? When I tried: http://www.testsubdomain.testweb.no/Install/Install.aspx?mode=Install, it fails and come up with this:

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 <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.

<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>

which is giving me no indication of what is wrong. So now I wonder if there is some more considerations I should take a closer look at?

Thanx in advance
 
New Post
2/2/2007 10:46 AM
 
Eric,
    You will need to ask your host to browse the default.aspx file from IIS so that you can see the true error. Once you get that, you can post that and we can help further.
 
New Post
2/5/2007 6:33 AM
 
Hi again!
Seems that my host had to upgrade to version 2.0 .NET Framework. I thought that was build in but it was not. So now I know that. Tried again but now I've got the following error:

Installing DotNetNuke

Version: 04.04.01



Installation Status Report

00:00:00.078 - Installing Version: 4.4.0
00:00:00.171 - Installing Script: DotNetNuke.SetUp.SqlDataProvider Success
00:00:00.203 - Installing Script: DotNetNuke.Schema.SqlDataProvider Error! (seeD:\hshome\portaltj\nuke4test.portaltjenester.no\Providers\DataProviders\SqlDataProvider\DotNetNuke.Schema.log for more information)
00:00:06.202 - Installing Script: DotNetNuke.Data.SqlDataProvider Error! (seeD:\hshome\portaltj\nuke4test.portaltjenester.no\Providers\DataProviders\SqlDataProvider\DotNetNuke.Data.log for more information)
00:00:12.576 - Installing MemberRole Provider:
00:00:12.576 -   Installing Script: InstallCommon.sql
00:00:13.076 -   Installing Script: InstallMembership.sql
00:00:13.560 -   Installing Script: InstallProfile.sql
00:00:13.701 -   Installing Script: InstallRoles.sql
00:00:13.966 - Upgrading to Version: 4.4.1 Success
00:00:14.154 - Performing General Upgrades
00:00:14.497 - Loading Host Settings:
00:00:14.560 - Configuring SuperUser:

 


Server Error in '/' Application.

EXECUTE permission denied on object 'aspnet_CheckSchemaVersion', database 'portalt_nukebase', owner 'dbo'.

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.Data.SqlClient.SqlException: EXECUTE permission denied on object 'aspnet_CheckSchemaVersion', database 'portalt_nukebase', owner 'dbo'.

Source Error:

The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:

1. Add a "Debug=true" directive at the top of the file that generated the error. Example:

  <%@ Page Language="C#" Debug="true" %>

or:

2) Add the following section to the configuration file of your application:

<configuration>
   <system.web>
       <compilation debug="true"/>
   </system.web>
</configuration>

Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.

Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.

Stack Trace:

[SqlException (0x80131904): EXECUTE permission denied on object 'aspnet_CheckSchemaVersion', database 'portalt_nukebase', owner 'dbo'.]
System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) +857466
System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +735078
System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +188
System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) +1838
System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) +149
System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async) +886
System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result) +132
System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe) +415
System.Data.SqlClient.SqlCommand.ExecuteNonQuery() +135
System.Web.Util.SecUtility.CheckSchemaVersion(ProviderBase provider, SqlConnection connection, String[] features, String version, Int32& schemaVersionCheck) +367
System.Web.Security.SqlMembershipProvider.CheckSchemaVersion(SqlConnection connection) +85
System.Web.Security.SqlMembershipProvider.GetUser(String username, Boolean userIsOnline) +1491
System.Web.Security.Membership.GetUser(String username, Boolean userIsOnline) +81
System.Web.Security.Membership.GetUser(String username) +6
DotNetNuke.Security.Membership.AspNetMembershipProvider.GetUserMembership(UserInfo& user) +21
DotNetNuke.Entities.Users.UserInfo.get_Membership() +69
DotNetNuke.Services.Upgrade.Upgrade.ParseSuperUser(XmlNode node) +243
DotNetNuke.Services.Upgrade.Upgrade.InstallDNN(String strProviderPath) +1305
DotNetNuke.Framework.Install.InstallApplication() +1171
DotNetNuke.Framework.Install.Page_Load(Object sender, EventArgs e) +274
System.Web.UI.Control.OnLoad(EventArgs e) +99
System.Web.UI.Control.LoadRecursive() +47
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1061

I'm used to set the databaseowner to none in version 3.x of DNN, like this: databaseowner="". .. and it always succeeded. But in version 4.x and above, is there a different configuration from 3.x versions? I have read all documentation but cannot find it. Hope the error over here is enough to decide from the experts what is wrong.

Thanx in advance
 
New Post
2/5/2007 9:46 AM
 
You could try re-installing it but setting the database owner to "dbo" in the web config when you install it again. I have not come across this issue before.
 
New Post
2/5/2007 11:15 AM
 
The database error you are receiving is due to the user account that is connecting to the database not having the proper permissions to execute the stored procedure.  You can either grant that user specific rights to ALL stored procedures that exist or you can simply grant that user Database Owner permissions on the database.

-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.
LinkedIn Profile

Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Problem Install DNN 4.4.1Problem Install DNN 4.4.1


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