Thử thêm cái coi lào

Làm gì khi website báo lỗi Server Error in '/' Application

Để khắc phục lỗi này bạn hãy vào trang quản lý hosting (HELM Control Hosting) vào mục Domains > Click vào Domains đó tiếp theo vào mục Web Site Settings > xem ở dòng Website Extensions có ASP.Net: trong phần này có 2 version: bạn hãy move sang version khác rồi nhấn Save sau đó lại move về như cũ Click Save là được.

Server Error in '/' Application.
Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>


Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.

<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>


Có nhiều lỗi đều dẫn đến thông báo lỗi như bên trên,vì vậy để thấy được sự mô tả đầy đủ,chính xác nguồn gốc của những lỗi ấy,hãy thử làm theo sau đây:
Mặc định, những ứng dụng ASP.NET được thiết lập với custom error messages ở chế độ Off.Tuy nhiên một vài công cụ phát triển web,như Visual Studio.NET tạo web.config file với customErrors mode ở chế độ RemoteOnly.Vì vậy để xem chi tiết thông báo lỗi,bạn cần đặt thuộc tính trong customErrors ở chế độ Off trong tập tin cấu hình web.config nằm trong thư mục gốc của ứng dụng web của bạn.

Đổi  <customErrors mode="RemoteOnly"/>  thành  <customErrors mode="Off"/>.

Sau đó ,có thể bạn sẽ thấy nguồn gốc gây ra thông báo lỗi như trên,nếu những ứng dụng mà bạn đã cài đặt không cùng làm việc với nhau.


Lối này do Visual Studio .NET không phiên dịch đúng Double Byte Character Set (DBCS) characters

Server Error in '/' Application.
Compilation Error Description:
An error occurred during the compilation of a resource required to service this request. Please review the following specific error details and modify your source code appropriately.
Compiler Error Message: CS1026: ) expected




Lỗi này do nâng cấp Microsoft .NET Framework version 1.0 đến version 1.1 và chưa cấp quyền trên thư mục


Server Error in '/ApplicationName' Application.
Unspecified error
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.Data.OleDb.OleDbException: Unspecified error


hoặc


Server Error in '/' Application.
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)
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.Data.SqlClient.SqlException: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)

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:
[SqlException (0x80131904): An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)]
   System.Data.SqlClient.SqlInternalConnection.OnErro  r(SqlException exception, Boolean breakConnection) +739123
   System.Data.SqlClient.TdsParser.ThrowExceptionAndW  arning(TdsParserStateObject stateObj) +188
System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject) +685966
System.Data.SqlClient.SqlInternalConnectionTds.Att emptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject) +109
System.Data.SqlClient.SqlInternalConnectionTds.Log inNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart) +383
System.Data.SqlClient.SqlInternalConnectionTds.Ope nLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) +181
System.Data.SqlClient.SqlInternalConnectionTds..ct or(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) +170
System.Data.SqlClient.SqlConnectionFactory.CreateC onnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) +130
System.Data.ProviderBase.DbConnectionFactory.Creat ePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options) +28
   System.Data.ProviderBase.DbConnectionPool.CreateOb  ject(DbConnection owningObject) +424
   System.Data.ProviderBase.DbConnectionPool.UserCrea  teRequest(DbConnection owningObject) +66
   System.Data.ProviderBase.DbConnectionPool.GetConne  ction(DbConnection owningObject) +496
   System.Data.ProviderBase.DbConnectionFactory.GetCo  nnection(DbConnection owningConnection) +82
System.Data.ProviderBase.DbConnectionClosed.OpenCo nnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +105
   System.Data.SqlClient.SqlConnection.Open() +111
   System.Web.DataAccess.SqlConnectionHolder.Open(Htt  pContext context, Boolean revertImpersonate) +84
   System.Web.DataAccess.SqlConnectionHelper.GetConne  ction(String connectionString, Boolean revertImpersonation) +197
System.Web.Profile.SqlProfileProvider.GetPropertyV aluesFromDatabase(String userName, SettingsPropertyValueCollection svc) +766
   System.Web.Profile.SqlProfileProvider.GetPropertyV  alues(SettingsContext sc, SettingsPropertyCollection properties) +428
   System.Configuration.SettingsBase.GetPropertiesFro  mProvider(SettingsProvider provider) +410
   System.Configuration.SettingsBase.GetPropertyValue  ByName(String propertyName) +117
   System.Configuration.SettingsBase.get_Item(String propertyName) +89
   System.Web.Profile.ProfileBase.GetInternal(String propertyName) +36
   System.Web.Profile.ProfileBase.get_Item(String propertyName) +68
   System.Web.Profile.ProfileBase.GetPropertyValue(St  ring propertyName) +4
   ProfileCommon.get_Theme() +12
   Wrox.Web.GlobalEvents.ThemeModule.app_PreRequestHa  ndlerExecute(Object Sender, EventArgs E) +118
   System.Web.SyncEventExecutionStep.System.Web.HttpA  pplication.IExecutionStep.Execute() +92
   System.Web.HttpApplication.ExecuteStep(IExecutionS  tep step, Boolean& completedSynchronously) +

Khoa
07 September 2008 22:50
An error has occurred while establishing a connection to the server.  When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
em bị lỗi thế này
a có thể chỉ e sữa đc ko?
Khoa Email
07 September 2008 22:52
An error has occurred while establishing a connection to the server.  When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
em bị lỗi thế này
a có thể chỉ e sữa đc ko?
hrockvn Email Homepage
08 September 2008 09:00
Lỗi này hình như xảy ra lúc bạn remote SQL từ client lên server để thao tác với dữ liệu. Bạn chưa có phép remote SQL nên bị lỗi này.
CaCa
20 December 2008 11:48
[SqlException (0x80131904): An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)]

anh có thể giúp em được không ?
khanhkhoikhoa
05 September 2010 16:41
vào HELM Control Hosting ntn?
[emot]:-/[/emot]
hrockvn Email Homepage
05 September 2010 21:58
Mặc định HELM chạy trên cổng 8086.
hoang Email Homepage
07 January 2011 08:53
còn lỗi này bị gì máy bác, minh bị lỗi này mà sữa hoài không đượcServer Error in '/WebSite' Application.--------------------------------------------------------------------------------A potentially dangerous Request.Form value was detected from the client (ctl00$TxtTukhoa="1<p><span style="font..."). Description: Request Validation has detected a potentially dangerous client input value, and processing of the request has been aborted. This value may indicate an attempt to compromise the security of your application, such as a cross-site scripting attack. You can disable request validation by setting validateRequest=false in the Page directive or in the configuration section. However, it is strongly recommended that your application explicitly check all inputs in this case. Exception Details: System.Web.HttpRequestValidationException: A potentially dangerous Request.Form value was detected from the client (ctl00$TxtTukhoa="1<p><span style="font...").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: [HttpRequestValidationException (0x80004005): A potentially dangerous Request.Form value was detected from the client (ctl00$TxtTukhoa="1<p><span style="font...").]   System.Web.HttpRequest.ValidateString(String s, String valueName, String collectionName) +8718538   System.Web.HttpRequest.ValidateNameValueCollection(NameValueCollection nvc, String collectionName) +111   System.Web.HttpRequest.get_Form() +129   System.Web.HttpRequest.get_HasForm() +8718647   System.Web.UI.Page.GetCollectionBasedOnMethod(Boolean dontReturnNull) +97   System.Web.UI.Page.DeterminePostBackMode() +63   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +6785   System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +242   System.Web.UI.Page.ProcessRequest() +80   System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context) +21   System.Web.UI.Page.ProcessRequest(HttpContext context) +49   ASP.admin_default_aspx.ProcessRequest(HttpContext context) +37   System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +181   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +75
Phân trang 1/1 Trang đầu 1 Trang cuối