Resolving VSP Device Discovery Failures in ServiceNow(CIM- indentity error)<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: block; max-width: ; width: auto; height: auto; } } Some Virtual Server Provider (VSP) devices fail to be discovered successfully during the discovery process. cim - identity fails with error: "Access denied" or "Cannot invoke "org.w3c.dom.Document.getDocumentElement()" because "dom" is null" The issue occurs due to compatibility problems between the ServiceNow discovery mechanism and the VSP devices. Specifically, the default CIM (Common Information Model) version used by ServiceNow may not be compatible with certain VSP devices. The solution is to add a probe parameter cim_version with value as modern in CIM - Computer System.