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 ...CanCan't install - database script error
Previous
 
Next
New Post
7/8/2009 10:57 PM
 

I am installing a fresh install of DNN on a Windows 2003 SP 2 server, with SQL 2005.

When the script runs to create the database, I get the following error:

Installing Database - Version 05.00.00...Success
Upgrading Database to Version 05.00.01...Success
Upgrading Database to Version 05.01.00...FAILURE ERROR: (see 05.01.00.log for more information)

The 05.01.00.log file is empty.  (in fact all the .log files are empty)  If I delete the .log files, they do get re-created with each try.

When I try again, I have to delete the database and re-create it, go back to the previous page (with connection info), and click Next to try again.  Every time I get the same error message.

If I don't delete the database, the page appears to be stuck in a loop showing a bunch of Success messages installing the database.

I'm out of ideas, can anyone help?

 
New Post
7/9/2009 5:42 AM
 

please clear the database and all files before retrying install.

also make sure to validate, full file system permisisons have been granted to ASP.Net account ("Network Service" by default) for the installation folder and all subdirectories.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
7/9/2009 6:21 PM
 

 I cleared the database, cleared the folder, reset IIS.  Still same error.

Some more information:

 

Running SQL Profiler, the last successful command was

exec dbo.GetHostSettings

The command before that was:

exec dbo.PurgeEventLog

I noticed this error in the event log, but PurgeEventLog does exist in the database and I was able to execute it: 

Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 7/8/2009 10:58:43 PM
Event time (UTC): 7/9/2009 2:58:43 AM
Event ID: 09d22ea10aef4ccebcb3e82c661eceba
Event sequence: 5
Event occurrence: 1
Event detail code: 0

 

Application information:

    Application domain: /LM/W3SVC/1697751234/Root-3-128915819200000000

    Trust level: Full

    Application Virtual Path: /

    Application Path: C:\DotNetNuke\

    Machine name: THERIEN-SQL

 

Process information:

    Process ID: 564

    Process name: w3wp.exe

    Account name: NT AUTHORITY\NETWORK SERVICE

 

Exception information:

    Exception type: SqlException

    Exception message: Could not find stored procedure 'dbo.PurgeEventLog'.

 

Request information:

    Request URL: 

    Request path: 

    User host address: 

    User: 

    Is authenticated: False

    Authentication Type: 

    Thread account name: NT AUTHORITY\NETWORK SERVICE

 

Thread information:

    Thread ID: 6

    Thread account name: NT AUTHORITY\NETWORK SERVICE

    Is impersonating: False

    Stack trace:    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)

   at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)

   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)

   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)

   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)

   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)

   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)

   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)

   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()

   at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(SqlConnection connection, CommandType commandType, String commandText, SqlParameter[] commandParameters)

   at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(String connectionString, CommandType commandType, String commandText, SqlParameter[] commandParameters)

   at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(String connectionString, CommandType commandType, String commandText)

   at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(String connectionString, String spName, Object[] parameterValues)

   at DotNetNuke.Services.Log.EventLog.DBLoggingProvider.Data.SqlDataProvider.PurgeLog()

   at DotNetNuke.Services.Log.EventLog.DBLoggingProvider.DBLoggingProvider.PurgeLogBuffer()

   at DotNetNuke.Common.Initialize.LogEnd()

   at DotNetNuke.Common.Global.Application_End(Object Sender, EventArgs E)

 

 

Custom event details:

 

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

 

 

 
New Post
7/11/2009 1:42 AM
 

 Well it turned out to be a permission issue.  The Network Service account needed write permission to C:\Windows\Temp.

I determined this by downloading the source code and doing my own debugging.  I did find that the upgrade database scripts do not write errors to the .log files as the error suggested.  Instead, they are loggend to the EventLog table.  If I had know that, I would of had this running two days ago.  The log had the exception recorded in an XML formatted column.

Another note, the Human Friendly URLs don't work.  I'm assuming it was because I was using a different port from 80.

 
New Post
7/14/2009 5:05 AM
 

I have the same problem and have also spent days trying to sort this out, in fact I have been trying to get a new installation of DNN on our server since v5 first came out in December.  It was a dream when we first installed v4.9 so I thought adding v5.0 (with a fresh SQL Server 2000 database) so that we could eventually decomission the old v4.9 would be easy, how wrong I was.

The server event log always has an entry:

Exception information:
    Exception type: SqlException
    Exception message: Could not find stored procedure 'dbo.PurgeEventLog'.

after each unsuccessful attempt at installation even though that stored procedure is clearly amongst the numerous stored procedures. I have even tried installing DNN v4.9 (which is always successful) and upgrading to 5.0 or 5.1 and still no luck. There are bugs in the SQLDataProvider as far as I can see.

I'm getting sick of cleaning out the database and installation files so we might have to keep using v4.9 indefinately which is a real shame.

Unfortunately giving write permission for the Network Service account to the Windows/Temp folder didn't help.

I don't suppose you have any other suggestions.

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...CanCan't install - database script 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