Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

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 ...DotNetNuke 4.3.4 Intall ErrorDotNetNuke 4.3.4 Intall Error
Previous
 
Next
New Post
8/31/2006 7:59 PM
 
Gary Alguire

Joined: 5/15/2006
Posts: 8

After creating the Web Site, I browse to the webpage and receive the following error, noting that Database_log.ldf does not even exist in that directory:

 

DotNetNuke Upgrade Error

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

ERROR: Could not connect to database.

Cannot open user default database. Login failed. Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. File activation failure. The physical file name "E:\wwwroot\ddosin\App_Data\Database_log.ldf" may be incorrect. The log cannot be rebuilt when the primary file is read-only.

Thanks,

Gary
 
New Post
9/1/2006 5:30 PM
 
Fuji Nguyen

Joined: 5/31/2003
Posts: 219

Does your 'NT AUTHORITY\NETWORK SERVICE' have write access to folder "E:\wwwroot\ddosin\App_Data\Database_log.ldf". 

You should give write access to E:\wwwroot\ddosin for DNN to modify web.config and module installation (create folder/files etc.)

Fuji Nguyen
FREE Visitor Hit Counter
Visit opensource.indyneinc.com for detail.
 
New Post
9/2/2006 2:56 AM
 
Gary Alguire

Joined: 5/15/2006
Posts: 8

Thanks for the reply!

Not sure if this is progress, but after changing the security settings as suggested, I am now getting this error:

 

DotNetNuke Upgrade Error

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

ERROR: Could not connect to database.

Cannot open user default database. Login failed. Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. File activation failure. The physical file name "E:\wwwroot\ddosin\App_Data\Database_log.ldf" may be incorrect.

There are only two files in that directory:

Database.mdf and PlaceHolder.txt

Thanks again,

Gary
 
New Post
9/2/2006 7:55 AM
 
IT Guru 1998

www.pdmlogin.com
Joined: 5/15/2005
Posts: 175

Make sure you are logging into the database first.  Are you using windows authentication or SQL?  Try to use SQL authentication on your SQL Server Enterprise Manager. 

Also make sure this App_Data folder has write access for your .mdb file that should be inside.  To do this you must click on the ddosin folder and go to tools > folder options

 

Click the View tab and scroll down to uncheck "Use simple file sharing (recommended)"

 

   This will now enable the "Security" tab when you right-click the ddosin folder and goto "Sharing and Security..."

Click on the "Security" tab.  You must give the permissions here to access the folder for 'NT AUTHORITY\NETWORK SERVICE' group.

 

I forgot to ask .... was this a failed installed from a previous attempt?  And what DNN version, SQL are you using?
 
New Post
9/3/2006 3:05 PM
 
Gary Alguire

Joined: 5/15/2006
Posts: 8

Once again, thanks for the reply!

I don't seem to have a group called  'NT AUTHORITY\NETWORK SERVICE',

but I did give access to the group: 'NETWORK SERVICE'

This is the initial install of DNN 4.3.4 and am running SQL 2005 Standard Version.

Here is the web.config and I did verify the sql username and password:

type="DotNetNuke.Framework.Providers.ProviderConfigurationHandler, DotNetNuke" />
    </sectionGroup>
  </configSections>
  <connectionStrings>
    <!-- Connection String for SQL Server 2005 Express -->
    <add
      name="SiteSqlServer"
      connectionString="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;"
      providerName="System.Data.SqlClient" />
    <!-- Connection String for SQL Server 2000/2005
    <add
      name="SiteSqlServer"
      connectionString="Server=(local);Database=ddosin;uid=sa;pwd=password;"
      providerName="System.Data.SqlClient" />
   -->
  </connectionStrings>
  <appSettings>
    <!-- Connection String for SQL Server 2005 Express - kept for backwards compatability - legacy modules   -->
    <add key="SiteSqlServer" value="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;"/>
    <!-- Connection String for SQL Server 2000/2005 - kept for backwards compatability - legacy modules
    <add key="SiteSqlServer" value="Server=(local);Database=ddosin;uid=sa;pwd=password;"/>
    -->
    <add key="InstallTemplate" value="DotNetNuke.install.config" />

Here is the error:


Error Installing DotNetNuke

Current Assembly Version: 04.03.04

ERROR: Could not connect to database specified in connectionString for SqlDataProvider

thanks

Gary
 
 Page 1 of 3
123Next 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...DotNetNuke 4.3.4 Intall ErrorDotNetNuke 4.3.4 Intall 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