Unsolved

This post is more than 5 years old

30472

June 19th, 2008 00:00

String was not recognized as a valid DateTime because the day of week was incorrect.

I am trying to view a webpage and I keep getting the following error:

Server Error in '/MyRes' Application.
String was not recognized as a valid DateTime because the day of week was incorrect. 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.FormatException: String was not recognized as a valid DateTime because the day of week was incorrect.

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:

[FormatException: String was not recognized as a valid DateTime because the day of week was incorrect.]
   System.DateTimeParse.Parse(String s, DateTimeFormatInfo dtfi, DateTimeStyles styles) +2228162
   System.DateTime.Parse(String s) +22
   MyRes.controls.CruiseSummary_DuringCruise.GetFormattedDate(String UnFormattedDate) in C:\wip\eCommerceAppDev\MyRes\MyRes\controls\CruiseSummary_DuringCruise.ascx.cs:225
   MyRes.controls.CruiseSummary_DuringCruise.LoadGrid() in C:\wip\eCommerceAppDev\MyRes\MyRes\controls\CruiseSummary_DuringCruise.ascx.cs:396
   MyRes.controls.CruiseSummary_DuringCruise.Page_Load(Object sender, EventArgs e) in C:\wip\eCommerceAppDev\MyRes\MyRes\controls\CruiseSummary_DuringCruise.ascx.cs:69
   System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e) +15
   System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) +34
   System.Web.UI.Control.OnLoad(EventArgs e) +99
   System.Web.UI.Control.LoadRecursive() +47
   System.Web.UI.Control.LoadRecursive() +131
   System.Web.UI.Control.LoadRecursive() +131
   System.Web.UI.Control.LoadRecursive() +131
   System.Web.UI.Control.LoadRecursive() +131
   System.Web.UI.Control.LoadRecursive() +131
   System.Web.UI.Control.LoadRecursive() +131
   System.Web.UI.Control.LoadRecursive() +131
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1061

 

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

 

 

Any ideas on how I might get this to stop??  I can view the page on another computer, running the same Vista O/S, same IEv7 and I am running IEv7...there seems to be no logical reason for this....both of my laptops were purchased from Dell at the same time, with the same software, same security settings and yet the XPS M1710 can see the page no problem, but the Inspiron 9400 can't.

 

Thanks in advance for any help.

 

Greg.

414 Posts

June 19th, 2008 08:00

This is a bit of a shot in the dark as I've no idea what program is running here - What's "wip"?

 

I suspect that somewhere in the configuration of "wip" there is a day/date/year configuration. In the US you use 6/12/08 to indicate 12th June 2008 but in most of Europe that would indicate 6th December 2008 - thus you would get an error as to the day of the week.

 

To test this, use a date, say, 8/8/2008, which is the same in both, and see if the error repeats.

Message Edited by Delierious on 06-19-2008 04:16 AM

2 Intern

 • 

1.7K Posts

June 19th, 2008 19:00

Is the page yours or just a page you are trying to view?  From the looks of that error, whoever the site admin is needs to fix something with it ...

June 20th, 2008 05:00

It is a webpage on the internet.  I downloaded Firefox and still no luck, so I reset my IE settings and wahla!  I could see the webpage just fine.  I don't know what was preventing me from seeing it but it is fine now.  It seemed this would happen at secure sites like seeing the prices for tickets on disneyland.com...all is well but thanks for the attempts.

Greg

2 Intern

 • 

1.7K Posts

June 20th, 2008 14:00

Honestly, I don't think anything you did fixed it.  I think the site admin fixed his page, and once that fix happened you (and everyone else seeing the error message) were able to view the page properly again. ;)

0 events found

No Events found!

Top