using dnn 4.9.3 latest forum module.

suddenly after working ok now if I click new thread I get the following error

Error: Add/Edit Post is currently unavailable. DotNetNuke.Services.Exceptions.ModuleLoadException: Object reference not set to an instance of an object. ---> System.NullReferenceException: Object reference not set to an instance of an object. at DotNetNuke.Modules.Forum.PostEdit.Page_Load(Object sender, EventArgs e) --- End of inner exception stack trace ---

there is no tracking set for the user(host) in the my settings.

as this module is being used live in a community site it poses a problem. I know that previous versions of the module had this problem but I thought it would have been fixed in the latest update

any advice on how to overcome it.

Hi John,

sometimes searching the forum soles your problem.  Your issue is serveraltimes discussed and solved in this forum.  It is a issue with a post from you after a session timeout (Standard setting is 20 min.).

Go to my settings in your forum and subscript fo all Forums notificachtion.  SAVE.  Try a post.  After successfull post a new thread, you can unsubscript from forum notifications in my settings.

Some of your forum can be brocken about a NULL reference error of the post you postet after the timeout.  The  hostadmin can be solved it via SQL function.  A solution is allso posted in this forum.

Regards

Matthias

http://www.dotnetnuke.com/Community/Forums/tabid/795/forums/7/scope/threadsearch/Default.aspx?body=%20Add/Edit%20Post%20is%20currently%20unavailable&subject=%20Add/Edit%20Post%20is%20currently%20unavailable

 John,

Here is the solution that worked for me.  I am not sure how to avoid it in the future but my users are up and running again.  I had 2 uesrs who could not create a new thread.  They were both in the database table dbo.Forum_TrackedThreads.  I deleted both entries ad they work fine now.  It seems that there may be an issue with subscribing to a thread causes this to happen.  I will be testing this in a test environment to see if I can figure out a long term solution.

I keep looking forward to a new/updated forum module.  Maybe this will be handled in a future release.

Dan

I found a remedy for the situation at hand if you have access to your database. 

Go into your database and navigate to the dbo.Forum_TrackedThreads table.  In there you will see results that show

ForumID, ThreadID, UserID, CreatedDate and ModuleID

you will notice the UserID of the account not able to post in there. In my database there were 4 records, three of which I am sure were not able to post and am awaiting the forth user to log in and test the theory before i delete them.  The three users of the records I deleted are all able to post now.

Just delete that row, and voila, you can post again.

I know this is just a temporary work around, but will get you back up and posting faster than any other method mentioned.