Hi,
I just attempted an install of 3.01.00 and recieve a failure half-way through. The database tables are created, but then the installation fails. What would cause this? It seems access to create the database tables would be the hardest part to get working.
I don't have the "{Server}/NetworkService user account must have Read, Write, and Change Control of the root application directory ( this allows the application to create files/folders ) " permission set yet, but I was under the impression that it would install without this, just not let me upload files, etc..
I do have a request in to my ISP to have this permission set, I just need to wait for them to do it. I was hoping I might get it running (partially) without it.
Here's the output of the install page:
Installation Status Report
00:00:00.031 - Installing Version: 3.1.0
00:00:00.031 - Installing Script: DotNetNuke.SetUp.SqlDataProvider
00:00:00.046 - Installing Script: DotNetNuke.Schema.SqlDataProvider
00:00:01.937 - Installing Script: DotNetNuke.Data.SqlDataProvider
00:00:03.656 - Installing MemberRole Provider:
00:00:03.656 - Executing InstallCommon.sql
00:00:03.890 - Executing InstallMembership.sql
00:00:04.109 - Executing InstallProfile.sql
00:00:04.203 - Executing InstallRoles.sql
--------------------------------------------------------------------------------
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>