Submit a ticketCall us
Home > Success Center > Enterprise Operations Console (EOC) > EOC Documentation > Previous Versions > Enterprise Operations Console 1.3 Release Notes

Enterprise Operations Console 1.3 Release Notes

Created by Beatrix.Turan, last modified by MindTouch on Jun 23, 2016

Views: 645 Votes: 0 Revisions: 3

Updated: 6/1/2012

These release notes provide additional guidance for SolarWinds Orion Enterprise Operations Console v1.3.

Why Install this Version

This version of Orion Enterprise Operations Console (EOC) provides the following improvements:

  • Faster page loads and less bandwidth use.
  • Orion EOC users can be added by Active Directory group.
  • Orion servers can now be polled using Active Directory credentials that have passwords.
  • Orion EOC users can each have a customized home view. (192511)
  • Global Search resource lets you find nodes more quickly.
  • SolarWinds Orion APM v4.0 added as a supported server type.


  • To integrate EOC with the Orion APM 4.2 or later, upgrade to EOC v1.3 SP1.
  • To integrate EOC with the latest versions of Orion NPM and Orion Core (10.3 and 2012.1, respectively), upgrade to EOC v1.3 SP2.
  • Upgrading removes any "buddy drop" type patches you may have already applied. If you have questions or concerns about reapplying these patches after upgrading, contact SolarWinds technical support.

For information about the features and fixes in Orion NPM 10.3 and Orion Core 2012.1, see the Orion Network Performance Monitor Version 10.3 Release Notes.

For information about the features and fixes in EOC v1.3 SP2, see the SolarWinds knowledge base.

Fixed Issues in this Release

This release of Orion EOC includes several fixes:

  • Fixed an issue preventing Orion EOC from monitoring Orion NPM 10.1.
  • Fixed an issue preventing Orion EOC from displaying maps if Orion NPM 10.1 was installed on the same server as Orion EOC.
  • It is now possible to change the subtitle of the Global Application Status resource. (157062)
  • The EOC Global Active Alerts page now correctly shows wireless AP alerts. (136538)
  • Custom property data type mismatches are now handled and reported correctly. (144498,147372)
  • Adding a resource to a view no longer requires a reset of all resource settings. (157066)
  • Fixed an issue that could prevent Orion EOC from seeing IPSLA data. (144436)
  • Account manager page can now be sorted by Role. (143382)
  • Fixed an issue that would cause the JobEngine.sdf file to grow in size and kill the JobEngine and JobScheduler. (99285)
  • The Orion EOC users list no longer displays Active Directory users who cannot be added as Orion EOC users. (138732)
  • Orion EOC can now determine between Orion servers with invalid credentials and those with out-of-sync system clocks. (192020)
  • The Copy View command now works for views that contain an asterisk or a slash in the name.
  • Orion Network Atlas now supports Active Directory accounts.
  • There is now a specific error message if the remote server time is out of sync with the Orion EOC Server.
  • Orion APM unmanaged status no longer appears as down status.
  • Nested maps no longer generate out of memory errors due to permission errors. (225176)
  • Changes made to a resource on a copy of a view no longer also changes the original. (191492, 191076)
  • Users not assigned to the administrator role can now correctly see nested maps. (224502)
  • Deleting users accounts from the Manage User page no longer deletes non-selected accounts. (195414)
  • The configuration wizard no longer sets the Recovery Model to simple if you set it to full. (208448)
  • Orion servers no longer send Orion EOC far more data than is necessary. (200133)
  • Fixed a bug that sometimes would prevent maps being displayed in Orion EOC. (188620)
  • Applications in an unmanaged state are now displayed correctly. (201762)
  • Global Status of Nodes by Site and Global Active Alerts resources no longer time out.

Open Issues in this Release

This release of Orion EOC has the following open issues:

  • Microsoft Internet Explorer 9 is not a supported browser.
  • Incremental polling does not work properly with regional settings that use a comma as a decimal separator.
  • Groups are not supported.
  • Most references to "Orion NPM servers" should be changed to "Orion servers" to accomodate other Orion products.
  • Nodes that are monitored by more than one Orion server create duplicate Alerts.
  • Alerts views do not list all IPSLA operation alerts
  • Accounts limited by System Name Pattern cannot see any Orion server data.
  • Internet Explorer 7 and 8 will not display embedded objects within Custom HTML resources.
  • If the data for a call path has not been collected, the corresponding call path entry in the Global VoIP Call Path resource appears empty. Please wait a few minutes for data to be collected.
  • VoIP call paths display invalid Quality of Service values if the source site or the destination site are down.
  • You cannot remove a user from Orion EOC if the Windows account for that user has been deleted.
  • Duplicate custom properties appear if custom properties from different Orion NPM servers have identical names but different value types.
  • The Global VoIP Call Managers resource does not display hosts that do not have any collected data.

Open Issues Related to Network Atlas

  • Do not uninstall Orion Network Atlas from the Orion EOC server. If you uninstall Orion Network Atlas from the Orion EOC server, the Orion web console map resources stop working.
  • Performing more than ten Undo actions in a row in Orion Network Atlas marks the map as having been saved.

Fixes in Previous Versions

Previous versions of Orion EOC have included the following additions and fixes:

Orion EOC v1.2.2


  • Added support for Orion NPM v10.1


  • Fixed an issue preventing Orion EOC from monitoring Orion NPM 10.1.
  • Fixed an issue preventing Orion EOC from displaying maps if Orion NPM 10.1 was installed on the same server as Orion EOC.

Orion EOC v1.2.1


  • Added support for:
    • Orion NPM v9.5 sp5, v10.0
    • Orion APM v3.1, v3.5
    • Orion IP SLA v3.1
    • Orion NCM v5.5.2, v6.0
    • Orion NTA v3.6
    • Orion VoIP v2.1
  • Added IPSLA Global Operations Overview resource.
  • Added confirmation for Reset View for All Users.
  • Added a confirmation dialog box to prevent accidental resets of custom views.
  • Expanded width of Group Nodes list box.
  • Propety names now display more than the first eight characters.


  • Fixed an issue that could rapidly fill up the hard drive with log files.
  • Fixed an issue where modifying a copy of a view would also affect the original.
  • Fixed an issue where external nodes caused parent objects to go into warning status.
  • Fixed an issue where APM alerts did not appear in the EOC Alerts resource.
  • Fixed an issue where timestamps in the EOC Global Active Alerts were displayed in the wrong time zone.
  • Fixed an issue where data from Orion IP SLA 3.1 were not polled correctly.
  • Fixed an issue where data from Orion NCM 5.5.2 were not polled correctly.
  • Fixed an issue where Orion APM statistics were not polled correctly.
  • Fixed an issue where IP SLA resources were missing hyperlinks to the Orion Web Console.
  • Fixed an issue where Orion Auto-Login did not work if the Orion NPM password contained ampersand (&) characters.
  • Fixed an issue where VoIP resources failed to show data after installing Orion IP SLA.

Orion EOC v1.2


  • Monitor Orion NCM 5.5.2 and later
  • Adding Orion NPM servers made easier
  • New resource: User-defined links
  • Select all events or Syslog items for acknowledgement
  • Administrators can personalize EOC views by default
  • Performance improvements
  • Orion EOC and Orion NPM can be installed together on either 32-bit or 64-bit Windows servers


  • Fixes an issue where Syslog message counts incorrectly included cleared messages.
  • Fixes an issue that made it possible to enter invalid SQL statements into a resource filter.
  • Fixes an issue where the Last XX Events resource was not added to the web console after upgrading to the latest version of Orion EOC.
  • Fixes an issue where the Wireless view generated invalid Orion NPM web page links if the Orion Auto-Login option was checked.
  • Fixes an issue where maps could time out before loading.
  • Fixes an issue where auto-refreshing maps caused a memory leak in Internet Explorer.
  • Fixes an issue where the view editing page displayed multiple copies of the same resource incorrectly.
  • Fixes an issue where the same custom property could appear erroneously multiple times in list menus.
  • Fixes an issue that could prevent editing user-created views.

Orion EOC v1.1


  • Updated for the latest versions of SolarWinds Orion products
  • Expanded platform and infrastructure Support
  • Enabled auto-login to Orion NPM Servers
  • Replaced Orion MapMaker with Orion Network Atlas
  • Introduced new licensing method


  • Fixes an issue where the Error and Warnings threshold page rejected decimal values entered in the regional number format of the Orion EOC server.
  • Fixes an issue where the Configuration Wizard failed if creating a virtual directory for the Orion EOC web site.
  • Fixes an issue where domain users and local users who had the same user names could not see Orion EOC data in the web console.
  • Fixes an issue where changes to column layouts were not propagated to all user views even if the Reset view for all users option was checked.
  • Users who have not been given access to any Orion NPM servers by the Orion EOC administrator are now given a notification message to contact the administrator.
  • Fixes an issue where the Applications in the Global Top XX resources could not be grouped by node.
  • Fixes an issue where events triggered by devices not in the Orion NPM database were given invalid, clickable hyperlinks.
  • Fixes an issue where the map links to Orion NPM servers were invalid unless the Orion NPM web site URL setting was prefixed with http:// when adding Orion NPM servers to Orion EOC.
  • Fixes an issue where acknowledging an alert provided the wrong acknowledgement time until the next polling cycle.
  • Fixes an issue where deleting a menu bar containing an apostrophe symbol in the name crashed the web console.
  • Fixes an issue where if the MOS value of a VoIP call path was a null value, all of the resource nodes appeared in a down state.
  • Fixes an issue where menu bars with the "Open in new window" option enabled were instead opened in the same window.

Active Directory Accounts Require Passwords

Because of a limitation in Windows account impersonation, certain actions will require you to edit your Orion EOC user account and to enter and save your Active Directory password in the password field. These actions include clearing events, acknowledging alerts and syslog messages, and listing reports.

Reading NCM data

The instructions for configuring Orion EOC to gather Orion NCM data have changed. For more information see Setting up Orion NCM accounts in the SolarWinds knowledge base.

Using the New Licensing System

After installing the software through the setup wizard, you are prompted to enter the licensing information for your product.

To evaluate the software without a license:

Click Continue Evaluation.

To license the software on a server with Internet access:

  1. Click Enter Licensing Information.
  2. Select I have internet access and an activation key.
  3. Click the link to access the customer portal on the SolarWinds web site.
  4. Log on to the portal using your SolarWinds customer ID and password.
  5. Click License Management on the left navigation bar.
  6. Navigate to your product, choose an activation key from the Unregistered Licenses section, and then copy the activation key.
  7. If you cannot find an activation key in the Unregistered Licenses section, contact SolarWinds customer support.
  8. Return to the Activate EOC window, and then enter the activation key in the Activation Key field.
  9. If you access Internet web sites through a proxy server, click I access the internet through a proxy server, and enter its proxy address and port.
  10. Click Next.
  11. Enter your email address and other registration information, and then click Next.


To license the software on a server without Internet access:

  1. Click Enter Licensing Information
  2. Select This server does not have internet access, and then click Next.
  3. Click Copy Unique Machine ID.
  4. Paste the copied data into a text editor document.
  5. Transfer the document to a computer with Internet access.
  6. On the computer with Internet access, complete the following steps:
    1. Browse to and then log on to the portal with your SolarWinds customer ID and password.
    2. Navigate to your product, and then click Manually Register License.
    3. If the Manually Register License option is not available for your product, contact SolarWinds customer support.
    4. Provide the Machine ID from Step 5, and then download your license key file.
  7. Transfer the license key file to the server.
  8. Return to the Activate EOC window, browse to the license key file, and then click Next.

Managing your Open Issues in Licensing

For information about managing your licenses for SolarWinds products, including how to deactivate or reuse a license, see SolarWinds License Manager.

Open Issues in Licensing

  • Applying Federal Information Processing Standards (FIPS) to a licensed Orion EOC server invalidates the existing license. To reactivate your license, contact SolarWinds customer support.
  • If you enter the activation key from another SolarWinds product by mistake, the activation key for the other product is considered registered even though your actual product remains unlicensed. To return the activation key to your pool of unregistered licenses, contact SolarWinds customer support.

Configuring Virtual Directories

The Configuration Wizard lets you set up the Orion EOC web console as a virtual directory of an existing web site, but does not check to see if the web site is running. If you set up the web console as a virtual directory of a stopped web site, the Configuration Wizard fails with an error. To avoid this problem, make sure the web site you choose for your virtual directory is running.

UTC Server Time Synchronization

The coordinated universal time (UTC) of the Orion NPM server must be within five minutes of the UTC of the Orion EOC server. If there is a time discrepancy greater than five minutes, a secure connection to the Orion NPM server cannot be established. If you receive an invalid credential error even though you are sure the credentials are correct, check the UTC of both servers.

The coordinated universal time (UTC) of any computers running Orion Network Atlas must be within five minutes of the Orion NPM or Orion EOC server to which you are connecting. If the time discrepancy is greater than five minutes, it is not possible to connect to the Orion NPM or Orion EOC server.

Configuring HTTPS in Windows Server 2008

The process for configuring Internet Information Service to accept HTTPS/SSL connections differs between Windows Server 2003 and Windows Server 2008. Use the following procedure to enable SSL connections to the Orion EOC web site in Windows Server 2008.

To enable SSL Connections to the SolarWinds EOC web site in Windows Server 2008:

  1. Log on as an administrator to your SolarWinds EOC server.
  2. Click Start > Administrative Tools > Internet Information Services (IIS) Manager.
  3. In the Connections pane, expand the name of your SolarWinds EOC server, and then expand Sites.
  4. Select your SolarWinds EOC web site, and then click Bindings in the Actions pane on the right.
  5. Click Add in the Site Bindings window.
  6. In the Type field, select https, and then confirm that the Port value is 443.
  7. In the SSL Certificate field, select a certificate, and then click OK.
  8. Click Close on the Site Bindings window.
  9. In the center pane, double-click SSL Settings in the IIS group.
  10. Select Require SSL, and then click Apply in the Actions pane on the right.
  11. In the Connections pane, select your SolarWinds EOC web site.
  12. Click Restart in the Manage Web Site group on the right.


Adding an Orion NCM server fails.

Are you trying to add an Orion NCM server directly to Orion EOC? You cannot directly add Orion NCM servers to Orion EOC. Instead, you install and configure the Orion NCM integration module on an Orion NPM server and then add that Orion NPM server to Orion EOC.

Software Requirements

  • Orion NCM and integration module version 5.5.2 or later
  • Orion NPM version 9.5.1 or later

Credential Requirements

You must have correctly configured the Orion NCM Integration module with a valid Orion NCM server and a valid Orion NCM credential.

The Orion NPM credential you specify in Orion EOC must not have any account limitations that would prevent access to the Orion NCM integration module.

A database initialization string error occurs while running the Configuration Wizard.

Passwords containing special characters can sometimes cause an error during completion of the Orion EOC Configuration Wizard. If you receive the following error, check that there are no special characters in the database password: Format of the initialization string does not conform to specification starting at index 86.

The database section of the Configuration Wizard does not list your database.

During the database section of the Configuration Wizard, the browse function of the wizard may fail to locate your database. If you experience difficulty browsing to your SQL Express instance, type ServerName\sqlexpress in the SQL Server field on the Login to SQL Server dialog, where ServerName is the pre-Windows 2000 name of your SQL Server.

Adding an Orion NPM server fails.

While adding an Orion NPM server to Orion EOC, if you receive the error "Failed test. Cannot connect to a SolarWinds Orion Information Service. You may have mistyped the Orion NPM server address or the SOIS may not be running", the following steps can help you troubleshoot and fix the problem:

  1. Verify that the SolarWinds Orion Information Services is running on the Orion NPM server.
  2. Verify that a firewall on the NPM Windows machine is not blocking incoming data on port 17777.
  3. Verify that a firewall on the EOC Windows machine is not preventing EOC from opening port 17777 for communication.
  4. Check the Application log on the Orion NPM server (use Windows Event Viewer) for any .Net-related errors. The following third-party security applications are known to interfere with Orion products:
    • Wave Systems EMBASSY Trust Suite. On DELL machines the EMBASSY suite is installed and is known to cause the .Net TCP Port Sharing service to crash. If this is the problem, try installing the .NET hotfix from If this does not resolve this issue, uninstall the Wave Systems EMBASSY Trust Suite software.


Last modified