Posted by: DPSI - Thursday, 31 March 2011 18:28:05
After we upgraded to YAF 1.9.5.5 we started to reveive an error message when trying to create a new Topic. This worked fine before we upgraded. I did read somewhere about changing you default language back to English (US) but ours is already there.
Is this a known issue? If so is there a fix?
The error is listed below
Thanks,
DPSI
_______________________________________________________________________________________
Server Error in '/' Application.
--------------------------------------------------------------------------------
Sequence contains no elements
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.InvalidOperationException: Sequence contains no elements
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[InvalidOperationException: Sequence contains no elements]
System.Linq.Enumerable.First(IEnumerable`1 source) +730976
YAF.Pages.posts.BindData() +1528
YAF.Pages.posts.Page_Load(Object sender, EventArgs e) +3817
System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e) +14
System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) +35
System.EventHandler.Invoke(Object sender, EventArgs e) +0
System.Web.UI.Control.OnLoad(EventArgs e) +99
System.Web.UI.Control.LoadRecursive() +50
System.Web.UI.Control.LoadRecursive() +141
System.Web.UI.Control.LoadRecursive() +141
System.Web.UI.Control.LoadRecursive() +141
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +627
--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:2.0.50727.3082; ASP.NET Version:2.0.50727.3082
Posted by: goyankees69 - Wednesday, 6 April 2011 22:43:06
Upgraded to YAF 1.9.5.5 yesterday and we are getting the same error. Was working fine before as well. We are and have been using English(US) as well.
Please help!
Posted by: Jaben - Thursday, 7 April 2011 05:39:05
Can either one of you provide a way to view this behavior on your site? e.g. the urls of your forum?
Posted by: DPSI - Thursday, 7 April 2011 12:34:39
Actually we did figure out our problem. The time on our Server was incorrect. We did apply a Daylights savings hotfix to correct the server time but that caused the error to appear even when the time on the server was correct. We had to remove the hotfix and manually set the time, the error then went away.
Hope this helps
Posted by: DPSI - Thursday, 7 April 2011 21:12:36
My mistake, I spoke too soon. If our server has the Daylights Savings Time hotfix applied then this issues re-appears. It only works without the hotfix. Problem is if we take off the hotfix then our server time keeps changing.
Any suggestions?
DPSI
Posted by: DPSI - Thursday, 7 April 2011 21:14:48
Test after changing my Daylight Savings time in THIS forum
Posted by: DPSI - Thursday, 7 April 2011 21:15:24
And it works.
Posted by: Reidy - Thursday, 7 April 2011 23:42:13
Hey
I wonder if you could help me with this issue. I am having the same problems, but am very new to YAF so not getting anywhere with a resolution.
What is "Daylights Savings Time hotfix" - is this a hotfix on the webserver itself? Or something to be applied to YAF? I don't have access to the operating system on the server therefore is there a way around this?
Can you give me more information about "Daylight Savings time in THIS forum"?
Any help would be greatly appreciated!
Thanks
David
Posted by: DPSI - Friday, 8 April 2011 12:42:02
I am refering to a MS hotfix (KB931836) that was applied to our server. It is not a YAF fix or anything like that, but it does affect my ability to create new topics inside YAF. If we remove this hotfix, everything seems to work fine, but we really need to keep this fix on our server.
Posted by: rking - Monday, 11 April 2011 22:18:32
Hi, I'm working with DPSI on this issue. We have narrowed it down to a 3 second time difference between our database server on SQL 2008R2 and our web server running on a different box. If we fudge the time on the web server by setting it ahead or behind the database server by 1 minute, we can make the issue appear and disappear.
Does YAF.NET use the sql server time for writing timestamps but use the web server time to determine what get's 'returned' by the query/view? Or is it somehow an issue of SQL or the websever treating the write of the new topic to the database and the read to refresh the page asynchronously, and the read is somehow executing before the write completes?
Posted by: bbobb - Monday, 11 April 2011 23:26:16
Just a notion - the error occurs when you retrieve post list. The list uses .NET framework UTC time to get posts. It related toa logic.
Yes, YAF uses database utc time extensively and to write the timestamps.
I guess you can try to workaround the issue by passing Framework time to a respective sp which stores a post data. I don't have time to look into it just educated guessing:-d