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 ...SqlExpress - could not connect to database specified in connectionString for SqlDataProviderSqlExpress - could not connect to database specified in connectionString for SqlDataProvider
Previous
 
Next
New Post
8/16/2007 5:13 PM
 

Yeah.  Let me ask...is the database created already?  If not, try creating an empty database, with the name you specify in the connection string, instead of letting the install process create it.  I have found this usually works every time during installation.  It leaves me to believe there is a permission or security context problem with database creation through install.  I might mention that the problem always occurs (even if the database is created) if no log file exists.  Make sure both database files exist and then run install again.  DNN will populate the empty files.

 
New Post
8/17/2007 11:35 AM
 

Yes the database is already created. ( i think the database permissions were set to the computer name and not server/aspnet) - the folder for the website however was always set to aspnet.

Now,

After getting a 'connection success' message in installwizard i got these errors:

Installing DotNetNuke
Version: 04.05.05
-------------------------------
Installation Status Report
00:00:00.093 - Installing Version: 4.4.0
00:00:00.265 -   Executing Script: DotNetNuke.SetUp.SqlDataProvider Success
00:00:01.109 -   Executing Script: DotNetNuke.Schema.SqlDataProvider Success
00:00:06.765 -   Executing Script: DotNetNuke.Data.SqlDataProvider Success
00:00:10.484 - Installing MemberRole Provider:
00:00:10.484 -   Executing Script: InstallCommon
00:00:14.297 -   Executing Script: InstallMembership
00:00:16.156 -   Executing Script: InstallProfile
00:00:16.765 -   Executing Script: InstallRoles
00:00:17.734 - Upgrading to Version: 4.5.5
00:00:17.828 -   Executing Script: 04.04.01.SqlDataProvider Success
00:00:18.265 -   Executing Script: 04.05.00.SqlDataProvider Success
00:00:20.453 -   Executing Script: 04.05.01.SqlDataProvider Success
00:00:20.906 -   Executing Script: 04.05.02.SqlDataProvider Success
00:00:21.578 -   Executing Script: 04.05.03.SqlDataProvider Success
00:00:21.859 -   Executing Script: 04.05.04.SqlDataProvider Success
00:00:22.047 -   Executing Script: 04.05.05.SqlDataProvider Success
00:00:22.141 - Performing General Upgrades
00:00:23.281 - Loading Host Settings:
00:00:23.453 - Configuring SuperUser:
00:00:24.078 - Installing Modules:
00:00:24.094 -   Installing Module File Adsense_01.00.01_Install:  Success
00:00:25.000 -   Installing Module File HTML_04.05.00_Install:  Error!
00:00:25.344 -   Installing Module File Links_03.03.07_Install:  Success
00:00:26.031 - Executing Additional Scripts:
00:00:26.047 -   Creating Portal: My Website
00:00:26.547 -   Error: Error configuring Child PortalAccess to the path 'C:\Inetpub\wwwroot\DotNetNuke\website\Portals\0\' is denied. at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.Directory.InternalCreateDirectory(String fullPath, String path, DirectorySecurity dirSecurity) at System.IO.Directory.CreateDirectory(String path, DirectorySecurity directorySecurity) at DotNetNuke.Entities.Portals.PortalController.CreatePortal(String PortalName, String FirstName, String LastName, String Username, String Password, String Email, String Description, String KeyWords, String TemplatePath, String TemplateFile, String HomeDirectory, String PortalAlias, String ServerPath, String ChildPath, Boolean IsChildPortal)
00:00:26.547 -   Portal failed to install:Error!
00:00:26.547 - Installing Optional Resources:
00:00:26.578 -   Installing Module File Adsense_01.00.01_Install:  Success
00:00:26.703 -   Installing Module File HTML_04.05.00_Install:  Error!
00:00:26.828 -   Installing Module File Links_03.03.07_Install:  Success
---------------------------------------------

Then in InstallWizard (auto) mode I get an error at line 106:

Line 104:      -->
Line 105:      <codeSubDirectories>
Line 106:        <add directoryName="HTML" />
Line 107:      </codeSubDirectories>
Line 108:    </compilation>

 

thanks

 
New Post
8/17/2007 1:24 PM
 

I have seen module installation failures as well.  In a few cases I just downloaded the latest version of the module and did a standard module install.  I have even had failures on default modules like Text/HTML.  When you checked permissions on the root directory in IIS did you check the whole tree and all the files?  You might want to flush permissions throughout the tree and then make sure inheritance is turned on at the root for all children.

I might mention there is a "BIG" environmental something going on here.  I have had a perfect install on my development server fail on another server using the same zip and options.  Authentication is NOT exactly the same across all Microsoft Servers (there are known bugs in the Windows 2000 implementation specifically that I have had to code around that have no failures on XP, NT or 2003) so authorization can be tricky.  Add various versions of accounts  to run under (ASP.net vs Network Service) and you have additional problems.  Since this install works "most" of the time, I think we are seeing untrapped errors returned from the deployment environment or because after a failure, the system wasn't flushed fully before retrying (files closed, tasks and processes ended).

If you get a failure, make sure you reboot (if possible) or completely wipe the previous install and shut down all processes attached to it.  If your using a HOST then delete the whole tree and database before retrying.  If this is an upgrade then things again get really tricky.  The "account version" and actual "file permissions" become even more of an issue to troubleshoot.  My advise is to VERIFY EVERYTHING before starting an upgrade.

 
New Post
9/3/2007 12:37 PM
 

Hi,

thanks for the advise.

I have tried a re-install and re-created the database.

Now I get this error message...

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.Web.HttpException: The path '/DotNetNuke/App_GlobalResources/' maps to a directory outside this application, which is not supported.

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.

Server Error in '/DotNetNuke' Application.

The path '/DotNetNuke/App_GlobalResources/' maps to a directory outside this application, which is not supported.

 

 
New Post
9/4/2007 10:51 AM
 

Try running the repair process on your .Net installation.  This issue probably isn't a DNN install problem but has to do with the installation order of IIS and .Net since App_GlobalResources is an installed ASP.Net directory.

Once you have run repair and installed DNN, check the IIS Default Web Site Properties -> Home Directory -> Local Path. Make sure that there is no "\" symbol at the end of the directory. IIS automatically adds one and this can cause problems if one is entered during installation.

Check the Default Web Site Properties -> ASP.NET -> File Location for actual setting information.

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...SqlExpress - could not connect to database specified in connectionString for SqlDataProviderSqlExpress - could not connect to database specified in connectionString for SqlDataProvider


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