The page already has the 'SqlDependency="CommandNotification"' attribute specified in the OutputCache directive. On such a page, it is an error to create a SqlCacheDependency object using a SqlCommand object. There are two ways to solve this problem: 1.Do not use the 'SqlDependency="CommandNotification"' attribute in the OutputCache directive. 2.On the SqlCommand object set SqlCommand.NotificationAutoEnlist to false. The side effect is that that SqlCommand object will not affect the output caching of the page.
The OS handle's position is not what FileStream expected. Do not use a handle simultaneously in one FileStream and in Win32 ...
The outgoing message with action '{0}' contains a callback context message property. Callback context cannot be transmitted ...
The output writer for code generation and the writer supplied don't match and cannot be used. This is generally caused by ...
The page '{0}' cannot use the user control '{1}', because it is registered in web.config and lives in the same directory ...
The page already has the 'SqlDependency="CommandNotification"' attribute specified in the OutputCache directive. On such ...
The page already has the 'SqlDependency="CommandNotification"' attribute specified in the OutputCache directive. On such ...
The page is performing an async postback but the ScriptManager.SupportsPartialRendering property is set to false. Ensure ...
The page needs to save viewstate, but session state is disabled or readonly. Enable session state, or disable viewstate for ...
The page requires session state that is no longer available. Either the session has expired, the client did not send a valid ...