Important:
This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.
A version of this page is also available for
4/8/2010

The NavigateErrorevent method fires when a binding error occurs, with a window or frameset element.

Syntax

void NavigateError(
  IDispatch* 
pDisp,
  VARIANT* 
pvtURL,
  VARIANT* 
pvtFrame,
  VARIANT* 
pvtStatusCode,
  VARIANT_BOOL* 
pvbCancel
);

Parameters

pDisp

[in] Pointer to an IDispatchinterface for the WebBrowserobject that represents the window or frame in which the navigation error occurred.

pvtURL

[in] Pointer to a VARIANTstructure of type VT_BSTRthat contains the URL for which navigation failed.

pvtFrame

[in] Pointer to a VARIANTstructure of type VT_BSTRthat contains the name of the frame in which the resource is to be displayed, or NULL if no named frame was targeted for the resource.

pvtStatusCode

[in] Pointer to a VARIANTstructure of type VT_I4containing an error status code, if available.

pvbCancel

[in,out] Pointer to a VARIANT_BOOLvalue that specifies VARIANT_TRUE to cancel the navigation.

Return Value

None.

Event DISPID

Copy Code
DISPID_NAVIGATEERROR

The DISPIDfor this event is defined in piedocvw.h. Use this value to identify the event handler when implementing IDispatch::Invoke.

Requirements

Header piedocvw.h
Library piedocvw.lib
Windows Mobile Pocket PC for Windows Mobile Version 5.0 and later, Smartphone for Windows Mobile Version 5.0 and later

See Also

500 Internal Server Error

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.