Submit a ticketCall us

WebinarVisual Monitoring Tactics: Getting More Log Search Value from SolarWinds Log & Event Manager with nDepth Webcast

Do things seem to make more sense when they are visualized? Are you an IT professional or security expert with a wish for more cybersecurity tools that provide an intuitive visual experience? Join Alexis Horn and Jamie Hynds from SolarWinds as they demonstrate how the nDepth feature in LEM can help make visualizing log search results a reality.

Register now.

Home > Success Center > Network Configuration Manager (NCM) > NCM - Knowledgebase Articles > Value of the ${DateTime} variable is evaluated incorrectly for file names

Value of the ${DateTime} variable is evaluated incorrectly for file names

Updated September 28, 2017

Overview

When the ${DateTime} variable is used as part of a file name, the variable is not evaluated correctly. An error similar to the following can be found in the log file:

 

ERROR SolarWinds.Cirrus.BusinessLayer.Jobs.Notifications.BaseJobNotification - Unable to save results to file "E:\SolarWinds_Reports\VLAN_911_Check\VLAN_911_check-9-24-2017 7:56 PM.txt" due to exception: System.NotSupportedException: The given path's format is not supported.

Environment

  • NCM 7.6 and 7.7

Cause 

The ${DateTime} macro is evaluated to a value such as the following: 9-24-2017 7:56 PM. However, Windows does not support the colon character (:) in file names. 

Resolution

Replace the ${DateTime} variable with other variables that do not contain the colon character (:). For example, use the following variables:

${Date} ${HH}-${Minute}

 

The generated file name won’t contain the colon character (:). Example:

C:\SolarWindsReports\Test-${Date} ${HH}-${Minute}.txt

 

 

Last modified

Tags

Classifications

Public