Running 1.93 Final.

I converted over my roles from my current forums. I did not have any of the roles set as the starting group. When I registered a user they had no groups. I went to delete that user and this is what I got:

Hi, already segnaled here from me, with the solution!
:wink:

Bug... Fixed. Will re-release here today.

EDIT: Re-released.

Hi, I know this is probably the stupidest question you've ever had. But here goes anyway...

I have the same problem, in this post you have said that their is a fix for this bug, and that it will be re-leased here today. All I'd like to know is re-released where? As I have no idea where to get the fix from.

Well, "today" was April 25, and he's likely referring to the 1.9.3 "final" release available for download.

If you download the latest and install from that, you shouldn't have the problem.

Hello, I installed from the 1.9.3 FINAL as a brand new clean install, as we have not used YAF before. But I am still receiving the error when trying to delete users from the admin.

Here is the error I am receiving

Server Error in '/' Application.

---

Invalid object name 'dbo.yaf_IgnoredUser'.
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.Data.SqlClient.SqlException: Invalid object name 'dbo.yaf_IgnoredUser'.

Source Error:

The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:

1. Add a "Debug=true" directive at the top of the file that generated the error. Example:

<%@ Page Language="C#" Debug="true" %>

or:

2) Add the following section to the configuration file of your application:







Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.

Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.

Stack Trace:


[SqlException (0x80131904): Invalid object name 'dbo.yaf_IgnoredUser'.]
System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) +925466
System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +800118
System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +186
System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) +1932
System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) +149
System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async) +1005
System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result) +132
System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe) +149
System.Data.SqlClient.SqlCommand.ExecuteNonQuery() +135
YAF.Classes.Data.DBAccess.ExecuteNonQuery(SqlCommand cmd, Boolean transaction) +147
YAF.Classes.Data.DB.user_delete(Object userID) +280
YAF.Classes.Utils.UserMembershipHelper.DeleteUser(Int32 userID) +56
YAF.Pages.Admin.users.UserList_ItemCommand(Object source, RepeaterCommandEventArgs e) +817
System.Web.UI.WebControls.Repeater.OnItemCommand(RepeaterCommandEventArgs e) +105
System.Web.UI.WebControls.Repeater.OnBubbleEvent(Object sender, EventArgs e) +66
System.Web.UI.Control.RaiseBubbleEvent(Object source, EventArgs args) +35
System.Web.UI.WebControls.RepeaterItem.OnBubbleEvent(Object source, EventArgs e) +117
System.Web.UI.Control.RaiseBubbleEvent(Object source, EventArgs args) +35
System.Web.UI.WebControls.LinkButton.OnCommand(CommandEventArgs e) +115
System.Web.UI.WebControls.LinkButton.RaisePostBackEvent(String eventArgument) +132
System.Web.UI.WebControls.LinkButton.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) +7
System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) +11
System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) +177
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1746

---

Version Information: Microsoft .NET Framework Version:2.0.50727.1433; ASP.NET Version:2.0.50727.1433

Has anybody got any suggestions? Not being able to delete users is a big problem for the company I work for.

I don't know if it will help but can you enable debugging and post the full error page?

Add the compilation debug=true to the web.config as shown in the bit you pasted.

Offhand I'm not sure why you'd get that error when deleting a user - I'm using 1.9.3 and can create/delete users at my whim.

Tho I see the problem (I think)..

The table name is yaf_IgnoreUser

The error references yaf_IgnoredUser

note the extra D.

Looking through existing code, seems the problem would lie within one of the stored procs.

I looked through the .sql scripts for 1.9.3 and do not see any misspellings of Ignore versus Ignored when referencing the tables, so I'm wondering if you modified the database after installation?

To help you track it down, load up SQL Studio and run this against your YAF database:


It will bring up all stored procs that might reference that table. From that list, open them up individually and take a look around - you're looking for references to the table itself that might have been misspelled accidentally.

If you see any that reference the table as Ignored, fix them to Ignore instead of Ignored and you should be good.

Thanks Imukai! I did make the changes you suggested and I am now able to delete users. So thanks again, everything seems to be working fine now...

Any idea how the misspelling snuck its way into your DB procs?

I installed from the newest 1.9.3 FINAL version. But I did run a script from another post in this forum that fixed an issue where I was unable to add a new board, but I wouldn't have thought this would have made the changes :roll: