Submit a ticketCall us

WebinarUpcoming Webinar: Should I Move My Database to the Cloud?

So you’ve been running an on-premises SQL Server® for a while now. Maybe you’ve moved it from bare metal to a VM, and have seen some positive benefits. But, do you want to see more? If you said “YES!”, then this session is for you, as James Serra will review the many benefits that can be gained by moving your on-prem SQL Server to an Azure® VM (IaaS). He’ll also talk about the many hybrid approaches, so you can gradually move to the cloud. If you are interested in cost savings, additional features, ease of use, quick scaling, improved reliability, and ending the days of upgrading hardware, this is the session for you.

Register now.

Home > Success Center > Patch Manager > Patch Manager - Knowledgebase Articles > Patch Manager fails to start and generates an Xceed.FileSystem.DiskFile error

Patch Manager fails to start and generates an Xceed.FileSystem.DiskFile error

Overview

Patch Manager fails to start and displays the following error:

Failed to connect to the Application Server

Sorry, we are unable to connect to the Patch Manager Server.
Verify that the connection information for the Patch Manager
Server is correct and the Data Grid Service is started.

Details: An unexpected internal failure occurred in the FileSystem
component, or one of its descendants.
Type: Xceed.FileSystem.DiskFile

 

Environment

All Patch Manager versions

Cause 

An antivirus application is preventing Patch Manager from starting. 

Resolution

Disable the antivirus application. See How do I uninstall antivirus or antispyware programs? for details.

If the antivirus application is required, verify that the files and directories in Patch Manager Anti Virus Exclusions are excluded.

 

Last modified

Tags

Classifications

Public