BugNET

Open source issue tracking & project management
Welcome to BugNET Register | Login |

BugNET Forums

 
  Forum  Support  Upgrading probl...  0.67 -> 0.7 beta 1
Disabled Previous
 
Next Next
New Post 11/14/2006 6:28 AM
User is offline LogicallyRogue
6 posts
www.dovetailinternet.com/
No Ranking


0.67 -> 0.7 beta 1 

I just downloaded the latest bugnet, and am attempting to upgrade my instance of BugNet.

When visiting http://My.IP.Add.Ress/Install/Install.aspx, I get the following:

Upgrading BugNET
Upgrade Status Report
Upgrading To Version: 0.7.719.0


Then it just sits there.  After updating the web.config to put log4net.txt in a location writable by NT AUTHORITY\NETWORK SERVICE, I found this error in the file:

log4net:ERROR [AdoNetAppender] Exception while writing to database
System.Data.SqlClient.SqlException: Invalid object name 'Log'.
Statement(s) could not be prepared.
   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 log4net.Appender.AdoNetAppender.SendBuffer(IDbTransaction dbTran, LoggingEvent[] events)
   at log4net.Appender.AdoNetAppender.SendBuffer(LoggingEvent[] events)

Any thoughts?

 
New Post 11/14/2006 8:25 PM
User is offline admin
641 posts
bugnetproject.com
1st Level Poster




Re: 0.67 -> 0.7 beta 1 
Have you given the Network service account read, write on the bugnet directory itself?

Davin Dubeau
BugNET - Core Developer

 
New Post 11/14/2006 8:39 PM
User is offline LogicallyRogue
6 posts
www.dovetailinternet.com/
No Ranking


Re: 0.67 -> 0.7 beta 1 

Yes, the "Network Service" account and the "IUSR_MACHINE" account both have read, write, modify on the physical directory.

In case it was a SQL issue, I made sure that the local IIS_WPG group has db_owner permission to the database.  "NT AUTHORITY\NETWORK SERVICE" is a member of IIS_WPG.

 
New Post 11/14/2006 8:52 PM
User is offline admin
641 posts
bugnetproject.com
1st Level Poster




Re: 0.67 -> 0.7 beta 1 
 LogicallyRogue wrote

Yes, the "Network Service" account and the "IUSR_MACHINE" account both have read, write, modify on the physical directory.

In case it was a SQL issue, I made sure that the local IIS_WPG group has db_owner permission to the database.  "NT AUTHORITY\NETWORK SERVICE" is a member of IIS_WPG.



Do all your users have a unique username and password?  

You can try setting the requiresUniqueEmail="true"  membership property to false to see if that is the cause.

Davin Dubeau
BugNET - Core Developer

 
New Post 11/16/2006 3:01 PM
User is offline MarkM
2 posts
No Ranking


Re: 0.67 -> 0.7 beta 1 
I am also having issues upgrading from 0.67.  I am able to install the new version without doing an upgrade, so my environment appears to be setup correctly.  I was looking at the install.aspx code and tried to detect what order the SQL install scripts are being run.  Is it an option to just run the scripts directly?

Looking at the install aspx, it looks like the scripts need to be run in this order: InstallCommon.sql, InstallMembership.sql, InstallProfile.sql, InstallRoles.sql, BugNET.Schema.SqlDataProvider.sql and BugNET.Data.SqlDataProvider.sql.  But I get errors with missing fields, etc. when attempting to run BugNET.Schema.SqlDataProvider.sql.  I tried running 0.7.719.0.SqlDataProvider.sql prior to that script, but I am getting various errors about inserting nulls, etc.  Am I missing something trying to run the scripts directly, perhaps I am running them in the incorrect order?  It appears that 0.7.719.0.SqlDataProvider.sql is needed but I am not seeing it called from the install routine?
 
Disabled Previous
 
Next Next
  Forum  Support  Upgrading probl...  0.67 -> 0.7 beta 1

Forum Policy

These Discussion Forums are dedicated to the discussion of the BugNET issue tracker.

For the benefit of the community and to protect the integrity of the project, please observe the following posting guidelines:
1. No Advertising.
2. No Flaming or Trolling.
3. No Profanity, Racism, or Prejudice.
4. Site Moderators have the final word on approving/removing a thread or post or comment.
5. English language posting only, please.