7.4

Table Of Contents
Cause
vRealize Automation IaaS is built on Microsoft Windows Communication Foundation (WCF), which does
not support FIPS.
Solution
On the IaaS Windows server, disable the FIPS policy.
1 Go to Start > Control Panel > Administrative tools > Local Security Policy.
2 In the Group Policy dialog, under Local Policies, select Security Options.
3 Find and disable the following entry.
System cryptography: Use FIPS compliant algorithms for encryption, hashing, and
signing.
Adding an XaaS Endpoint Causes an Internal Error
When you attempt to create an XaaS endpoint, an internal error message appears.
Problem
Creation of an endpoint fails with the following internal error message, An internal error has
occurred. If the problem persists, please contact your system administrator. When
contacting your system administrator, use this reference: c0DD0C01. Reference codes are
randomly generated and not linked to a particular error message.
Solution
1 Open the vRealize Automation appliance log file.
/var/log/vcac/catalina.out
2 Locate the reference code in the error message.
For example, c0DD0C01.
3 Search for the reference code in the log file to locate the associated entry.
4 Review the entries that appear above and below the associated entry to troubleshoot the problem.
The associated log entry does not specifically call out the source of the problem.
Uninstalling a Proxy Agent Fails
Removing a proxy agent can fail if Windows Installer Logging is enabled.
Problem
When you try to uninstall a proxy agent from the Windows Control Panel, the uninstall fails and you see
the following error:
Error opening installation log file. Verify that the
specified log file location exists and is writable
Installing vRealize Automation
VMware, Inc. 173