Cannot update my thread by marking answer, or reply

Instead of asking for bugs, perhaps you could shorten the list by asking for feedback from people who haven't experienced a bug.

In the last week or so, I have been encountering the following message with more and more frequency. For example, I have a thread out there, and when people respond with an answer, if I click the "Mark as Answer" button, I wait and wait and wait and wait and wait and wait and wait and then get this ***...

Unknown Error

We apologize, but an unknown error has occured in the forums.

This error has been logged.

The same thing happens if I try to reply to someone who posted in my thread. I have not attempted to reply to others threads, so I don't know if the problem is only isolated to my own threads, but I'd be surprised if that was the case.

Any idea's on how or when this forum is going to operate without the above error?

Tanks, Israeli ones.

[1364 byte] By [ItchyAshcrackistan] at [2007-12-23]
# 1

Hi,

Sorry about the inconvenience caused by the bug. Generally, when there are any patch updates on to the forums web site, you will encounter this kind
of problem. When you encounter such a problem, you just need to refresh the page and mark it as answer again and it works.

Thank you for reporting this to us and your support in MSDN forums.

Regards,
Bhanu.

BhanuPrakashNunna-MSFT at 2007-8-30 > top of Msdn Tech,Feedback for forums and MSDN websites,Bug Reports for Forums website...
# 2

If you continue to get this, please let us know. Also, indicate which thread it occured in. I would like to investigate any ongoing issues like this to see if I can find a cause.

Thanks

Janac

Forums Program Manager [Microsoft]

Jana at 2007-8-30 > top of Msdn Tech,Feedback for forums and MSDN websites,Bug Reports for Forums website...
# 3
This has happened several times over the last few days. Retrying doesn't help -- you just get the error over & over. Sometimes you end up posting multiple replies; sometimes nothing is committed. The only thing that works is waiting an hour and trying again.
RichardBergMSFT at 2007-8-30 > top of Msdn Tech,Feedback for forums and MSDN websites,Bug Reports for Forums website...