New issue
Advanced search Search tips

Issue 729484 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jun 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

error on .net frame work websites

Reported by sdm.dho....@gmail.com, Jun 5 2017

Issue description

Server Error in '/' Application.

The string was not recognized as a valid DateTime. There is an unknown word starting at index 3.

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: The string was not recognized as a valid DateTime. There is an unknown word starting at index 3.

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:

<configuration>
   <system.web>
       <compilation debug="true"/>
   </system.web>
</configuration>

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: 


[FormatException: The string was not recognized as a valid DateTime. There is an unknown word starting at index 3.]
   Admin_Dashboard_dashboard.Page_Load(Object sender, EventArgs e) +7805
   System.Web.UI.Control.LoadRecursive() +71
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +3178
 

Comment 1 by peter@chromium.org, Jun 5 2017

Status: WontFix (was: Unconfirmed)
This is a configuration issue with the application server unrelated to Chrome and/or another browser, sorry.

Sign in to add a comment