What's in 9.2 Service Pack 3
Anne Reuland and Derek Weatherbe contributed these descriptions of issues fixed
in Service Pack 3 of ArcGIS Server for the Microsoft .Net Framework 9.2. You
can
download the service pack from the ESRI Support Site.
NIM004587 Add support for displaying symbology for ArcIMS ArcMap image services
in the Table of Contents
Layers from ArcIMS ArcMap image services now display symbology swatches in the
Table of Contents. Prior to this change, the TOC was displaying only the layer
names.
NIM007561 Add support for the public services provided from ArcWeb Services
ArcGIS Server 9.2 provided support for Commercial ArcWeb Services. This
enhancement adds support for Public ArcWeb Services. Information on ArcWeb
Services and how to subscribe to the Public services is available from:
http://www2.arcwebservices.com/v2006/account_types.jsp
NIM008269 When using the Identify tool or displaying task results for features
containing curves, display the message ‘Curves are not supported’
Prior to Service Pack 3, performing an Identify on a feature containing a curve
or executing a Search or Query task that returned a set of results which
included curve geometry would cause an unhandled object reference error. With
Service Pack 3, result sets for Identify, Search and Query will display the
text 'Curves are not supported' and it will not be possible to select these
features. Future development work planned for 9.3 is intended to add support
for geometry containing curves. There is a programmatic workaround
available for this known problem, you can get the details from this Knowledge
Base article:
http://support.esri.com/index.cfm?fa=knowledgebase.techarticles.articleShow&d=33331
NIM008691 The Web ADF generates an unnecessary number of callback responses when
updating the Table of Contents
This fix addresses a performance problem with the Table of Contents. The
problem could be detected when the map contained a significant number of
layers, group layers and layers with visible scale ranges defined.
NIM008461 The Search Attributes and Query Attributes Tasks fail to return
results for text searches against ArcIMS ArcMap image services
Executing string searches in Search and Query tasks will now work correctly for
ArcIMS ArcMap image services.
NIM008669 The feature ID property of the CreateFeature and SelectFeature tools
is not set when executing these tools. These tools are part of the Editor task.
NIM009235 Need to expose a utility method for clearing the feature attribute
cache
These two fixes address problems when customizing the Editor Task.
NIM005177 Change the .NET Geoprocessing Tool wrappers to map Boolean parameters
to String values
Developers who were using the pre-built Geoprocessing assemblies prior to
Server Pack 3 would encounter a problem when coding for Geoprocessing tools
which used boolean parameters. Working around this problem required creating an
array of tool parameters and passing it to Geoprocessor.Execute method instead
of the expected coding pattern of being able to set Boolean parameters.
Example of old coding pattern to work around the limitation:
Geoprocessor
gp = new Geoprocessor();
IVariantArray parameters = new VarArrayClass();
parameters.Add(@"C:\cities");
parameters.Add(@"C:\roads");
parameters.Add(@"#");
parameters.Add(@"NO_LOCATION");
parameters.Add(@"NO_ANGLE");
gp.Execute("Near", parameters, null);
New coding pattern for Geoprocessing commands which have Boolean parameters:
Near near =
new Near();
near.in_features = path + @"Analysis\cities";
near.near_features = path + @"Analysis\roads";
near.location = false; //Boolean parameter
near.angle =
false; //Boolean parameter
Geoprocessor
gp = new Geoprocessor();
gp.OverwriteOutput = true;
gp.Execute(near, null);
NIM007060 Web Mapping Applications published from Manager are not enabled as
applications in IIS when the web site Manager has been deployed to run on a
port number other than the default of 80
NIM007061 Web Mapping Applications published from Manager are not enabled as
applications in IIS when Manager has been deployed to a web site other than the
Default Web Site in IIS Manager
Prior to Service Pack 3, customers who were running Manager on a web site other
than the default web site or on a web site using a port other than 80 would be
unable to successfully publish web applications from Manager. The result was
that a new web application published from Manager required manual configuration
in IIS to enable it as a web application.
Manager can now publish web applications on non-default web sites. Running
Manager on a port other than 80 (For example: 1234) requires that the Manager
administrator edit the web.config located under $wwwroot\ArcGIS\Manager to
insert the port number on the following line:
<add key="PublishPort" value="1234" />
When using a port other than 80, the URL to the Manager application will then
need to include the port number:
http://localhost:1234/ArcGIS/Manager/default.aspx
Further, ArcGIS Server web service resources on this web site will need to
include the port number in the URL:
http://localhost:1234/arcgis/services
The same fix applies to the ArcIMS Manager application with the file to be
edited being located under $wwwroot\ArcIMS\Manager .
Please note that Service Pack 3 does not change anything in regards to how
Manager is installed. The installation location of Manager is controlled by the
registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\INetStp\PathWWWRoot and this
cannot be modified through IIS Manager.
Information on manually deploying Manager to a non-default web site is
available in the following KB article:
http://support.esri.com/index.cfm?fa=knowledgebase.techarticles.articleShow&d=32546
Allowing the install of Manager to a non-default location is planned to be
addressed at the next release of the software. Changes to the install cannot be
implemented at Service Packs.
NIM009719 IToolBarItemSetup::Initialize does not work for Toolbar command items
This fix addressed a problem where IToolBarItemSetup::Initialize was working
for Tools, but not executing for Command and Dropdown items on the Toolbar
control.
NIM008163 The TOC for the PageLayout is displaying a checkbox for the highest
data frame node when it did not at 9.2 Final. Toggling it causes an object
reference error
Prior to this fix, an unnecessary checkbox was displayed for Table of Contents
(TOC) controls when buddied to a PageLayout control. Checking this box would
cause an object reference error. The fix removed this unnecessary checkbox.
NIM008846 When blending map services with ArcGIS Online services, the services
may not display correctly at the initial extent
This fix was related to the use case where a cached map service was blended
with an ArcGIS Online service. Displaying this blend scenario in a map control
could have resulted in the cached map service not aligning correctly with the
ArcGIS Online service at the initial extent.
NIM006274 Some publicly available OGC WMS services cannot be used in the
ArcGIS Server for the Microsoft .Net Framework Web Mapping Applications
This problem with displaying OGC WMS services has been resolved.
By default, the Web Mapping Application now only turns on the first 10 layers
in the Table of Contents control for WMS services. This is analogous to
the behavior in Desktop where only the first 20 layers are turned on by
default.
To override this behavior, use the following code in the Default.aspx.cs file
of your Web Mapping Application:
protected void Page_Init(object sender, EventArgs e)
{
IMapResource mapResource =
MapResourceManager1.GetResource("MapResourceItem0");
if (mapResource != null)
{
ESRI.ArcGIS.ADF.Web.DataSources.OGCWMSService.MapResource wmsMapResource =
mapResource as ESRI.ArcGIS.ADF.Web.DataSources.OGCWMSService.MapResource;
if
(wmsMapResource != null)
{
wmsMapResource.MaxInitialSelectedLayers = 25; //Example of turning on the first
25 layers by default
}
}
}