Submit a ticketCall us

Cloud Workloads: Meet Your New Hybrid IT Reality
Have you found yourself in that evolving, hybrid IT grey area and wondering if cloud workloads are now part of your purview? And if so, will monitoring cloud workloads require a new set of dedicated cloud monitoring tools? Your answers: yes, they should be, and no, they don’t.

Find out how SolarWinds® Server & Application Monitor (SAM) can help you monitor your cloud workloads side by side with your on-premises workloads. Register Now.

Home > Success Center > IP Address Manager (IPAM) > Unable to add supernet or subnet in IPAM

Unable to add supernet or subnet in IPAM

Created by Brian O'Donovan, last modified by MindTouch Content Copy on Nov 13, 2015

Views: 56 Votes: 0 Revisions: 4

Overview

Unable to add supernet or subnet to IPAM. The following error is received on the Web Console:

 

Infrastructure Component is Offline
The Information Service and Orion Module Engine are required components for this website to function, and at least one of them is currently unavailable.

 

In the BusinessLayerHost log file at C:\ProgramData\SolarWinds\Logs\Orion\BusinessLayerHost.log, you see the following message;

 

ERROR SolarWinds.BusinessLayerHost.PluginInstanceAppDomain - Plugin "Core Business Layer" failed to start.
System.Data.SqlClient.SqlException (0x80131904): Could not allocate space for object 'dbo.PartitionErrors' in database 'SolarWindsOrion' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.

 

Environment

All IPAM versions

Cause 

This is caused by the database using the partition/disk on the SQL server at its maximum capacity.

Resolution

Contact your System Administrator to help increase the size of the partition where the SQL database is located.

Last modified

Tags

Classifications

Public