Submit a ticketCall us
Home > Success Center > IP Address Manager (IPAM) > IPAM - Knowledgebase Articles > SWISv3 error: An item with the key 'IPAM.IPInfo' already exists

SWISv3 error: An item with the key 'IPAM.IPInfo' already exists

Created by Brian O'Donovan, last modified by Rodim Suarez_ret on Jul 13, 2017

Views: 206 Votes: 0 Revisions: 10

Updated July 13, 2017

Overview

The Information Service v3 in Windows is flapping after applying IPAM 4.3 hotfix 1 to the IPAM server. The following error message is displayed on the website when loading:

There was no endpoint listening at net.tcp://orion:17777/SolarWinds/InformationService/v3/Orion/certificate that could accept the message. This is often caused by an incorrect address or SOAP action.

The following error is also found in the Orion.InformationService.log file (C:\ProgramData\Solarwinds\InformationService\v3.0\Orion.InformationService.log):

ERROR SolarWinds.InformationService.Core.EndpointInfo - (null)     Error merging schemas files'. Returning empty Schema.
System.ArgumentException: An item with the key 'IPAM.IPInfo' already exists
   at SolarWinds.Data.Entity.SchemaModel.SchemaElementDictionary`1.InsertItem(Int32 index, T item)
   at SolarWinds.Data.Entity.SchemaModel.Schema..ctor(Internal internalElement)
   at SolarWinds.Data.Entity.SchemaModel.SchemaMerger.Merge(Schema schema1, Schema schema2)
   at SolarWinds.Data.Entity.SchemaModel.Schema.SolarWinds.Data.Entity.SchemaModel.ISchema.MergeSchema(ISchema schema)
   at System.Linq.Enumerable.Aggregate[TSource](IEnumerable`1 source, Func`3 func)
   at SolarWinds.Data.Entity.SchemaModel.SchemaFactory.MergeSchemas(IEnumerable`1 schemas)
   at SolarWinds.InformationService.Core.EndpointInfo.LoadSchemas(IEnumerable`1 schemaFiles)

A message similar to the above error is also found in the BusinessLayerHost.log file (C:\ProgramData\Solarwinds\Logs\Orion\BusinessLayerHost.log):

WARN  SolarWinds.Orion.Core.Common.InformationServiceConnectionProvider - Connection via certificate could not be created.
System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at net.tcp://orion:17777/SolarWinds/InformationService/v3/Orion/certificate that could accept the message. This is often caused by an incorrect address or SOAP action.

Environment

IPAM 4.3 with hotfix 1

Cause 

The old IPAM.core.xml file was renamed but the backup file is still found in the C:\Program Files (x86)\SolarWinds\Orion\Information Service\3.0\Schemas\ folder when the hotfix was applied.

Resolution

  1. Stop the services using Orion Service Manager.
  2. Remove the IPAM.core.xml backup file from the C:\Program Files (x86)\SolarWinds\Orion\Information Service\3.0\Schemas\ folder.
  3. Start the services using Orion Service Manager.

 

See the Orion Module Engine service bouncing after applying IPAM 4.3 Hotfix 1 article for a similar issue.

 

 

Last modified

Tags

Classifications

Public