Issue
You receive the following error message in Windows Event Viewer:
"Guid should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx)"
The full error message is:
System.FormatException: Guid should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx).
at System.Guid.TryParseGuidWithNoStyle(String guidString, GuidResult& result)
at System.Guid.TryParseGuid(String g, GuidStyles flags, GuidResult& result)
at System.Guid..ctor(String g)
at TAC.DSS.BusinessLogic.TrendLogProcessor.GetLogValues(XmlDocument filterXml, ITrendLogValuesInterface values)
at DssCliLib.TrendLog.GetLogValues2(SByte* pszConnectionString, Char* bstrFilter, ITrendLogValues* pValues)Product Line
TAC Vista
Environment
Vista Workstation
Cause
This error occurs when Trend Log Calculation Objects are misconfigured. Specifically, the "Trend Log Object" field is left blank.
When Vista attempts to execute the trend log calculation, it tries to retrieve data using the GUID of the associated trend log object. If the field is blank, Vista returns a placeholder like "126??"—which does not conform to the required GUID format.
The GUID (Globally Unique Identifier) is essential for linking the trend log calculation to its data source. A missing or malformed GUID causes the system to fail when parsing the identifier.
Resolution
To resolve this issue:
- Review all Trend Log Calculation Objects in your Vista configuration.
- Ensure that each object has a valid reference to a Trend Log Object.
- Update any blank or incorrect fields to include the correct GUID.
Tip: You can use the Vista Workstation to inspect and edit these objects. Look for any entries where the "Trend Log Object" field is empty or contains invalid data.
Additional Notes
- This issue typically appears at regular intervals, depending on how frequently the trend log calculations are triggered.
- Correcting the configuration should eliminate the error from the Event Viewer.
