Submit a ticketCall us

Quickly Address Software Vulnerabilities
Patch Manager is an intuitive patch management software which extends the capabilities of WSUS and SCCM to not only patch Windows® servers and workstations, and Microsoft® applications, but also other 3rd-party applications which are commonly exploited by hackers. Learn more about our patch management solution.

 

Home > Success Center > Network Performance Monitor (NPM) > Scheduled report job Save to disk failed with error: The given path's format is not supported

Scheduled report job Save to disk failed with error: The given path's format is not supported

Created by Adrian Cook, last modified by MindTouch on Jun 23, 2016

Views: 54 Votes: 1 Revisions: 4

Overview

Reports are not saved after performing Save to Disk report job and the following error is found in the Core.Businesslayer.log file:

[71] ERROR ReportingLogger - Saving report to \\servername\ReportsNew failed. The given path's format is not supported.
System.NotSupportedException: The given path's format is not supported.
at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
at System.IO.File.InternalWriteAllBytes(String path, Byte[] bytes, Boolean checkHost)
at System.IO.File.WriteAllBytes(String path, Byte[] bytes)
at SolarWinds.Orion.Core.Actions.Impl.SaveToDiskURL.SaveToDiskURLExecutor.SaveFile(ActiveDirectoryCredential creds, String folderName, String fileName, Byte[] bytes)
at SolarWinds.Orion.Core.Actions.Impl.SaveToDiskURL.SaveToDiskURLExecutor.BuildAndSaveFile(ReportingActionContext reportingContext, SaveToDiskURLConfiguration config)

Environment

All Orion Core versions

Cause 

This occurs when the report name includes special characters. Examples of this are colons, commas, semi-colons, etc.

Resolution

  1. Rename the report to remove any special characters.
  2. Rerun the job.

 

Last modified
23:31, 22 Jun 2016

Tags

Classifications

Public