Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

Home > Success Center > User Device Tracker (UDT) > UDT - Knowledgebase Articles > UDT endpoint information not populating after running through all troubleshooting steps

UDT endpoint information not populating after running through all troubleshooting steps

Table of contents

Overview

This article explains what may be causing endpoint information to not be populated after performing several troubleshooting steps. Also, you cannot find anything wrong from the polling side.

Environment

UDT 3.0 and later

Detail

See this guide: VLAN Endpoint Troubleshooting guide

 

 

In some cases, after verifying high fragmentation of each UDT_PortToEndpoint* Tables in the SWDebugMaintenance.log files in C:\ProgramData\Solarwinds\Logs\Orion, the issue can be resolved by defragmenting the endpoints tables with database maintenance using the following article: Defragmentation of Indexes.

Last modified

Tags

Classifications

Public