English

Error: Credentials are either invalid or unspecified

Error Message

The MapIt Spatial Data Assistant enables points (locations) to be created from addresses in a SQL Server table. In the process, the geocode service used to create a point needs to be defined. Any of the following services can be used: the Bing geocode service, a set of ArcGIS Online geocode services, or a custom ArcGIS Server geocode service. If Bing is used, the developer account credentials must be entered. Currently, Bing services are available in both a staging and production environment. If the Bing developer account does not have production level access, the staging environment must be used.

When using the Bing geocode service in the staging environment to create points from addresses, the Spatial Data Assistant returns the following error:

"Credentials are either invalid or unspecified".

The error is returned when, in fact, the Bing developer account credentials are specified and valid.

Cause

The application configuration file for the Spatial Data Assistant defines a set of http bindings for Bing services. The http binding for the Bing geocode service only references the production environment URL. As a result, geocode requests using a Bing developer account without production level access will fail.

Solution or Workaround

The Spatial Data Assistant application configuration file needs to be modified to enable access to the staging environment for Bing services.

  1. Open the Spatial Data Assistant application configuration file in a text editor. The configuration file is named DataAssistant.exe.config and is located in the MapIt install directory under the DataAssistant folder, for example, C:\Program Files\ESRI MapIt v1.1\DataAssistant.
  2. Remove the <system.serviceModel> tag and everything in between (listed below).

    Code:
    <system.serviceModel>
    <bindings>
    <basicHttpBinding>
    <binding name="BasicHttpBinding_IRouteService" maxBufferSize="2147483647"
    maxReceivedMessageSize="2147483647">
    <security mode="None" />
    </binding>
    <binding name="BasicHttpBinding_IGeocodeService" maxBufferSize="2147483647"
    maxReceivedMessageSize="2147483647">
    <security mode="None" />
    </binding>
    <binding name="BasicHttpBinding_IImageryService" maxBufferSize="2147483647"
    maxReceivedMessageSize="2147483647">
    <security mode="None" />
    </binding>
    </basicHttpBinding>
    </bindings>
    <client>
    <endpoint address="http://dev.virtualearth.net/webservices/v1/imageryservice/imageryservice.svc"
    binding="basicHttpBinding" bindingConfiguration="BasicHttpBinding_IImageryService"
    contract="ImageryService.IImageryService" name="BasicHttpBinding_IImageryService" />
    <endpoint address="http://dev.virtualearth.net/webservices/v1/geocodeservice/GeocodeService.svc"
    binding="basicHttpBinding" bindingConfiguration="BasicHttpBinding_IGeocodeService"
    contract="GeocodeService.IGeocodeService" name="BasicHttpBinding_IGeocodeService" />
    <endpoint address="http://dev.virtualearth.net/webservices/v1/routeservice/routeservice.svc"
    binding="basicHttpBinding" bindingConfiguration="BasicHttpBinding_IRouteService"
    contract="RouteService.IRouteService" name="BasicHttpBinding_IRouteService" />
    </client>
    </system.serviceModel>

  3. Save the file and restart the Spatial Data Assistant.