Month: January 2025

Easier method to simulate custom ESXi SMBIOS…

Easier method to simulate custom ESXi SMBIOS…

Happy 2025! 🎉 Here is a fun one to kick off the New Year ☺️ Last year, I demonstrated a method for customizing the SMBIOS hardware string using Nested ESXi, but the solution was not perfect and required hacking up a VM ROM file and it was also limited to using the BIOS firmware for […]

Broadcom Social Media Advocacy

vRealize Events Missing After Patch or Version Upgrade

(Authorization Error on vRealize Host)

After applying a patch or performing a version upgrade of vRealize Operations, some customers notice that events stop appearing in ServiceNow, specifically in the em_event table.

At first glance, the integration looks healthy: the MID Server is up, credentials haven’t changed, and the connection test may even pass. Yet no new events are flowing.

This post explains why this happens, how to recognize it quickly, and how to fix it safely.

Symptoms

After upgrading vRealize Operations, you may observe:

  • No new events in ServiceNow (em_event)
  • Existing integrations appear configured correctly
  • No obvious UI errors in vRealize Operations

However, the vRealize MID Server logs reveal the real problem.

How to Identify the Issue

Worker-Interactive:ConnectorProbe-) [MIDSystem:35]
*** Script: vRealize Payload : Response Body of Resource Properties :
<head><title>Not Authorized</title></head>
<body>
We apologize. You are not authorized for the request
</body>

This message is the key indicator that authentication between ServiceNow and vRealize Operations is failing at the API level.

Root Cause

Starting with vRealize Operations 8.1 and later, Basic Authentication is required for API access used by the MID Server.

basicAuthentication.enabled=false

As a result:

  • The MID Server cannot authenticate
  • API calls return Not Authorized
  • Events silently stop flowing to ServiceNow

Resolution: Enable Basic Authentication (vROps 8.1+)

To restore event flow, Basic Authentication must be enabled on all nodes in the vRealize Operations cluster.

Step-by-step fix

  • Log in to the Primary Node of vRealize Operations
    (SSH or console, user: root)
  • Edit the API configuration file
/usr/lib/vmware-vcops/user/conf/api-conf.properties

Set Basic Authentication to enabled

basicAuthentication.enabled=true

Save and close the file

Restart the REST API service

service api restart

Repeat steps on all other nodes
(Replica, Data, and Remote Collector nodes)

Reference

This behavior and resolution are documented by Broadcom/VMware in the official KB:

How to Apply for the 2025 vExpert Program as a…

How to Apply for the 2025 vExpert Program as a…

Are you a VMTN Community Moderator? If so, you have a unique opportunity to join the prestigious vExpert Program for 2025. This program celebrates individuals who make outstanding contributions to VMware communities—and as a moderator, your role already puts you on the fast track to approval. […]

Broadcom Social Media Advocacy