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 ...Configuring SuperUser ErrorConfiguring SuperUser Error
Previous
 
Next
New Post
5/10/2008 11:08 AM
 

 

Hi all,

When i installing dotnetnuke in local server, it was installed successfully. But I get errors when I try to install it on a remote web server.

My user's database roles and schemas on the remote server are db_securityadmin, db_datareader, db_datawriter, db_ddladmin. I have read that these roles and schemas are the minimum permission for the dotnetnuke application. However, I guess that these are not enough permissions to install dotnetnuke.

I have the error below :


Version: 04.08.02

 

Installation Status Report

00: - Installing Version: 4.4.0
00: -   Executing Script: DotNetNuke.SetUp.SqlDataProvider Success
00:00:00.046 -   Executing Script: DotNetNuke.Schema.SqlDataProvider Success
00:00:03.015 -   Executing Script: DotNetNuke.Data.SqlDataProvider Success
00:00:04.250 - Installing MemberRole Provider:
00:00:04.250 -   Executing Script: InstallCommon
00:00:04.625 -   Executing Script: InstallMembership
00:00:05.281 -   Executing Script: InstallProfile
00:00:05.656 -   Executing Script: InstallRoles
00:00:06.046 - Upgrading to Version: 4.8.2
00:00:06.062 -   Executing Script: 04.04.01.SqlDataProvider Success
00:00:06.484 -   Executing Script: 04.05.00.SqlDataProvider Success
00:00:07.781 -   Executing Script: 04.05.01.SqlDataProvider Success
00:00:08.250 -   Executing Script: 04.05.02.SqlDataProvider Success
00:00:08.968 -   Executing Script: 04.05.03.SqlDataProvider Success
00:00:09.546 -   Executing Script: 04.05.04.SqlDataProvider Success
00:00:10.046 -   Executing Script: 04.05.05.SqlDataProvider Success
00:00:10.500 -   Executing Script: 04.06.00.SqlDataProvider Success
00:00:11.515 -   Executing Script: 04.06.01.SqlDataProvider Success
00:00:12.109 -   Executing Script: 04.06.02.SqlDataProvider Success
00:00:12.500 -   Executing Script: 04.07.00.SqlDataProvider Success
00:00:13.171 -   Executing Script: 04.08.00.SqlDataProvider Success
00:00:13.687 -   Executing Script: 04.08.01.SqlDataProvider Success
00:00:14.125 -   Executing Script: 04.08.02.SqlDataProvider Success
00:00:15.062 - Performing General Upgrades
00:00:15.765 - Loading Host Settings:
00:00:15.953 - Configuring SuperUser:

 


Server Error in '/nuke' 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>

 
New Post
5/10/2008 11:47 PM
 

Do what the error message says and set the  <customErrors mode="Off"/> .  Then post the error you are getting here. Without knowing what the exact error is,  everyone will just be guessing at the cuase and fix for the issue you are having.  If all the other scripts ran OK, I  would say that is a pretty good indication that the DB permissions are correct.

 
New Post
5/12/2008 11:00 AM
 

As Shawn mentioned I would check to see what the actual error is, however, it is most likely not going to be possible for you to see the error since during the install process, it is hard to get back unless you start over.

I typically use DBO permissions for my DNN user, as it just resolves any errors that might occur, however, since your scripts ran that created the DNN database, you should be fine.

My guess is that you have a thread aborting error or something like that.


-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
 
New Post
5/13/2008 1:14 AM
 

Version: 04.08.02

 

Installation Status Report

00: - Installing Version: 4.4.0
00: -   Executing Script: DotNetNuke.SetUp.SqlDataProvider Success
00:00:00.078 -   Executing Script: DotNetNuke.Schema.SqlDataProvider Success
00:00:03.328 -   Executing Script: DotNetNuke.Data.SqlDataProvider Success
00:00:04.578 - Installing MemberRole Provider:
00:00:04.578 -   Executing Script: InstallCommon
00:00:05.031 -   Executing Script: InstallMembership
00:00:05.625 -   Executing Script: InstallProfile
00:00:06.109 -   Executing Script: InstallRoles
00:00:06.546 - Upgrading to Version: 4.8.2
00:00:06.609 -   Executing Script: 04.04.01.SqlDataProvider Success
00:00:07.125 -   Executing Script: 04.05.00.SqlDataProvider Success
00:00:08.328 -   Executing Script: 04.05.01.SqlDataProvider Success
00:00:08.906 -   Executing Script: 04.05.02.SqlDataProvider Success
00:00:09.765 -   Executing Script: 04.05.03.SqlDataProvider Success
00:00:10.250 -   Executing Script: 04.05.04.SqlDataProvider Success
00:00:10.890 -   Executing Script: 04.05.05.SqlDataProvider Success
00:00:11.390 -   Executing Script: 04.06.00.SqlDataProvider Success
00:00:12.562 -   Executing Script: 04.06.01.SqlDataProvider Success
00:00:13.062 -   Executing Script: 04.06.02.SqlDataProvider Success
00:00:13.406 -   Executing Script: 04.07.00.SqlDataProvider Success
00:00:14.062 -   Executing Script: 04.08.00.SqlDataProvider Success
00:00:14.750 -   Executing Script: 04.08.01.SqlDataProvider Success
00:00:15.250 -   Executing Script: 04.08.02.SqlDataProvider Success
00:00:15.734 - Performing General Upgrades
00:00:16.390 - Loading Host Settings:
00:00:16.546 - Configuring SuperUser:

 


Server Error in '/nuke' Application.

Could not find stored procedure 'dbo.aspnet_CheckSchemaVersion'.

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: Could not find stored procedure 'dbo.aspnet_CheckSchemaVersion'.

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): Could not find stored procedure 'dbo.aspnet_CheckSchemaVersion'.]
System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) +925466
System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +800118
System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +186
System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) +1932
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) +1005
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) +149
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.GetSuperUser(XmlDocument xmlTemplate, Boolean writeFeedback) +357
DotNetNuke.Services.Upgrade.Upgrade.InstallDNN(String strProviderPath) +224
DotNetNuke.Services.Install.Install.InstallApplication() +391
DotNetNuke.Services.Install.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) +1436

 
New Post
5/13/2008 2:07 AM
 

Hi all,

I have the error following. When I check the database after this error occurs, there is no objects (stored procedures and tables) that their names begins with  "aspnet_" in my database. I found that all objects, their names start with "aspnet_", are also owned by "dbo" in the ".sql" installation files.

I guess that installation finds objects that are owned by "dbo" causes the error but my user schema and database role is not dbo. So I removed all "dbo" codes in files including InstallRoles, InstallMembership and InstallProfile after that installation. I changed "dbo.aspnet_getSchemaVersion" to "aspnet_getSchemaVersion" for example. Then I tried to install again, but I still get this error. Why installation finds the objects that are owned by "dbo".

In addition, the databaseOwner is my user name "mnecuser3" in the web.config file for all installation processes I've tried.

Installing DotNetNuke

Version: 04.08.02

 

Installation Status Report

00: - Installing Version: 4.4.0
00: -   Executing Script: DotNetNuke.SetUp.SqlDataProvider Success
00:00:00.078 -   Executing Script: DotNetNuke.Schema.SqlDataProvider Success
00:00:03.609 -   Executing Script: DotNetNuke.Data.SqlDataProvider Success
00:00:05.109 - Installing MemberRole Provider:
00:00:05.109 -   Executing Script: InstallCommon
00:00:05.468 -   Executing Script: InstallMembership
00:00:05.921 -   Executing Script: InstallProfile
00:00:06.468 -   Executing Script: InstallRoles
00:00:06.906 - Upgrading to Version: 4.8.2
00:00:06.921 -   Executing Script: 04.04.01.SqlDataProvider Success
00:00:07.359 -   Executing Script: 04.05.00.SqlDataProvider Success
00:00:08.890 -   Executing Script: 04.05.01.SqlDataProvider Success
00:00:09.640 -   Executing Script: 04.05.02.SqlDataProvider Success
00:00:10.265 -   Executing Script: 04.05.03.SqlDataProvider Success
00:00:10.828 -   Executing Script: 04.05.04.SqlDataProvider Success
00:00:11.296 -   Executing Script: 04.05.05.SqlDataProvider Success
00:00:11.859 -   Executing Script: 04.06.00.SqlDataProvider Success
00:00:13.109 -   Executing Script: 04.06.01.SqlDataProvider Success
00:00:13.531 -   Executing Script: 04.06.02.SqlDataProvider Success
00:00:13.937 -   Executing Script: 04.07.00.SqlDataProvider Success
00:00:14.578 -   Executing Script: 04.08.00.SqlDataProvider Success
00:00:15.218 -   Executing Script: 04.08.01.SqlDataProvider Success
00:00:15.890 -   Executing Script: 04.08.02.SqlDataProvider Success
00:00:19.140 - Performing General Upgrades
00:00:19.703 - Loading Host Settings:
00:00:20.093 - Configuring SuperUser:

 


Server Error in '/nuke' Application.

Could not find stored procedure 'dbo.aspnet_CheckSchemaVersion'.

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: Could not find stored procedure 'dbo.aspnet_CheckSchemaVersion'.

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): Could not find stored procedure 'dbo.aspnet_CheckSchemaVersion'.]
System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) +925466
System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +800118
System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +186
System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) +1932
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) +1005
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) +149
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.GetSuperUser(XmlDocument xmlTemplate, Boolean writeFeedback) +357
DotNetNuke.Services.Upgrade.Upgrade.InstallDNN(String strProviderPath) +224
DotNetNuke.Services.Install.Install.InstallApplication() +391
DotNetNuke.Services.Install.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) +1436

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Configuring SuperUser ErrorConfiguring SuperUser Error


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