Updated April 17, 2017
Reports with custom fields cannot be viewed on the additional web server but can be viewed on the primary web server. The following errors are displayed:
System.ApplicationException: Field not specified or invalid at SolarWinds.Orion.Web.Reporting.C1QueryWrapper.BuildSQL() at SolarWinds.Orion.Web.Reporting.OrionReport.BuildQuery(String orderBy, Streing grouping, String filter) at SolarWinds.Orion.Web.Reporting.ReportRunner.WorkerProc(Object state)
SolarWinds.Orion.Web.InformationService.InformationServiceProxy - Entity IPAM.GroupNodeAttr does not contain requested property <Custom Field Name>
SolarWinds.Orion.Web.Reporting.ReportCellPreviewControl+<>c__DisplayClassb - Error setting up report cell during rendering '.'
SolarWinds.Orion.Core.Reporting.Exceptions.ExecutionFailedException: Entity IPAM.GroupNodeAttr does not contain requested property <Custom Field Name>
IPAM 4.3.2 and earlier
When adding custom fields to IPAM, the
C:\Program Files (x86)\SolarWinds\Orion\Information Service\3.0\Schemas\IPAM.Attributes.xml file in the primary web server is not synchronized with the file in the additional web server.
Note: The following instructions assume that IPAM is installed in the default location. Change the paths if you installed IPAM in another location.
C:\Program Files (x86)\SolarWinds\Orion\Information Service\3.0\Schemas\IPAM.Attributes.xml. Verify that the backup is saved in a location outside the Orion installation folder
C:\Program Files (x86)\SolarWinds\.
C:\Program Files (x86)\SolarWinds\Orion\Information Service\3.0\Schemas\in the main polling engine.
IPAM.Attributes.xmlfile and replace the file in
C:\Program Files (x86)\SolarWinds\Orion\Information Service\3.0\Schemas\ of the additional polling engine.
Repeat this procedure whenever a new custom field is added.