Field Mapping

Error message when a Web browser sends a request for an active server page to a Web server that is running IIS 6.0: "Response buffer limit exceeded" Response object error 'ASP 0251 : 80004005' Response Buffer Limit Exceeded /PageName.asp, line LineNumber CAUSE This issue occurs because of a change in behavior that was introduced in IIS 6.0 and added to IIS 5.0. These versions of IIS enforce a default ASP response buffer limit of 4 MB. This limit prevents large ASP responses from adversely affecting the IIS process that hosts the Web application. If an ASP request generates a response that is larger than the configured buffer limit, you experience the symptoms that are mentioned in the "Symptoms" section. Method 4: Increase the buffer limit You can increase the buffering limit if one of the following conditions is true: • The client is not a Web browser. • You cannot redesign the application to take advantage of a paging technology, such as the GridView class...

When responding to a request from Google Earth (or any Earth browser), a KML server must follow a certain set of rules so that Google Earth can correctly interpret its responses. Upon success, the server must return a response code of HTTP 200 and set the response's content-type to a suitable MIME type, as described here. Google Earth reads KML and KMZ files. The MIME type for KML files is application/vnd.google-earth.kml+xml The MIME type for KMZ files is application/vnd.google-earth.kmz For Apache, add these lines to the httpd.conf file: AddType application/vnd.google-earth.kml+xml .kml AddType application/vnd.google-earth.kmz .kmz See the Microsoft documentation for details on setting up MIME types on Microsoft's IIS. The body of the response must contain valid KML data, including the XML declaration (<?xml version="1.0" encoding="UTF-8"?>). If the server returns invalid KML, the Network Link will stop, deactivate, and output an error message.