Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

vRealize Suite Life Cycle Manager does not catch all vRealize Automation prerequisites   (55679)

Last Updated: 4/5/2019Categories: InformationalTotal Views: 3100Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

vRealize Suite Life Cycle Manager does not catch all vRealize Automation IAAS prerequisites

vRA install succeeds but you see errors similar to the following on Infrastructure/Monitoring/Log tab in vRA, or in the Manager Service logs located at C:\Program Files (x86)\VMware\vCAC\Server\Logs\All.log

System.ApplicationException: Error executing query usp_SelectAgent  —> System.ApplicationException: Error executing query usp_SelectAgentCapabilities  —> System.Transactions.TransactionManagerCommunicationException: Communication with the underlying transaction manager has failed. —> System.Runtime.InteropServices.COMException: The MSDTC transaction manager was unable to pull the transaction from the source transaction manager due to communication problems. Possible causes are: a firewall is present and it doesn’t have an exception for the MSDTC process, the two machines cannot find each other by their NetBIOS names, or the support for network transactions is not enabled for one of the two transaction managers. (Exception from HRESULT: 0x8004D02B)

Prerequisite checker fails with .NET components missing message.

Cause

The vRealize Suite Life Cycle Manager Prerequisite Checker does not catch the following IAAS prerequisites:

MSDTC is not configured on the IAAS database Server

The machines used for IAAS were created from a cloned Windows server, and the MSDTC ID in the windows registry is the same for all servers so MSDTC does not work.

The prerequisite checker warns of missing .NET components.

Resolution

To resolve this issue when:

(a) MSDTC is not installed on the IAAS SQL database server:

1. Open a remote desktop session to the IAAS SQL database server(s)
2. Open the Component Services Console
3. Expand Component Services/Computers/My Computer/Distributed Transaction Coordinator
4. Right Click on LocalDTC and choose properties
5. Select the "Security Tab"
6. Make sure the following is selected (these should match what you have selected on your IAAS servers)
Network DTC Access
Allow Remote Clients
Allow Remote Administration
Allow Inbound
Allow Outbound
Mutual Authentication
Enable SNA LU 6.2 Transactions
DTC Logon Account should be "NT AUTHORITY\NetworkService"
7. Click "OK"
8. Click affirmative to the message about restarting the DTC service.

(b) MSDTC has issue with Cloned Machines:

1. Open a remote desktop session to each of the IAAS Manager Server(s)
2. open a command prompt as Administrator.
3. Run the following command.
msdtc -uninstall
4. Restart the clone.
5. Open another command prompt, and run the following command.
msdtc -install manager-service-host-FQDN
6. Open the Services Console
7. Find Distributed Transaction Coordinator
8. Right click and choose Properties
9. Set the Startup type: to Automatic (start the service if necessary)

(c) IAAS prerequisites are missing:

Web Server:

The requirements are the same, whether or not the Web component hosts the Model Manager.
Configure Java.
Install 64-bit Java 1.8 update 161 or later. Do not use 32-bit.
The JRE is enough. You do not need the full JDK.
Set the JAVA_HOME environment variable to the Java installation folder.
Verify that %JAVA_HOME%\bin\java.exe is available.
Configure Internet Information Services (IIS) according to the following table.
You need IIS 7.5 for Windows 2008 variants, IIS 8 for Windows 2012, IIS 8.5 for Windows 2012 R2, and IIS 10 for Windows 2016.
In addition to the configuration settings, avoid hosting additional Web sites in IIS. vRealize Automation sets the binding on its communication port to all unassigned IP addresses, making no additional bindings possible. The default vRealize Automation communication port is 443.
IaaS Manager Service Host Internet Information Services
IIS Component
Setting
Internet Information Services (IIS) roles
Windows Authentication
Static Content
Default Document
ASPNET 3.5 and ASPNET 4.5
ISAPI Extensions
ISAPI Filter
IIS Windows Process Activation Service roles
Configuration API
Net Environment
Process Model
WCF Activation (Windows 2008 variants only)
HTTP Activation
Non-HTTP Activation (Windows 2008 variants only)
(Windows 2012 variants: Go to Features > .Net Framework 3.5 Features > Non-HTTP Activation)
IIS Authentication settings
Set the following non-defaults.
Windows Authentication enabled
Anonymous Authentication disabled
Do not change the following defaults.
Negotiate Provider enabled
NTLM Provider enabled
Windows Authentication Kernel Mode enabled
Windows Authentication Extended Protection disabled
For certificates using SHA512, TLS1.2 must be disabled on Windows 2012 variants

Manager Server:

The requirements are the same, whether the Manager Service host is a primary or backup.
No firewalls can exist between a Manager Service host and DEM host. For port information, see IaaS Windows Server Ports.
The Manager Service host must be able to resolve the NETBIOS name of the SQL Server database host. If it cannot resolve the NETBIOS name, add the SQL Server NETBIOS name to the Manager Service machine /etc/hosts file.
Configure Internet Information Services (IIS) according to the following table.
You need IIS 7.5 for Windows 2008 variants, IIS 8 for Windows 2012, IIS 8.5 for Windows 2012 R2, and IIS 10 for Windows 2016.
In addition to the configuration settings, avoid hosting additional Web sites in IIS. vRealize Automation sets the binding on its communication port to all unassigned IP addresses, making no additional bindings possible. The default vRealize Automation communication port is 443.
IaaS Manager Service Host Internet Information Services
IIS Component
Setting
Internet Information Services (IIS) roles
Windows Authentication
Static Content
Default Document
ASPNET 3.5 and ASPNET 4.5
ISAPI Extensions
ISAPI Filter
IIS Windows Process Activation Service roles
Configuration API
Net Environment
Process Model
WCF Activation (Windows 2008 variants only)
HTTP Activation
Non-HTTP Activation (Windows 2008 variants only)
(Windows 2012 variants: Go to Features > .Net Framework 3.5 Features > Non-HTTP Activation)
IIS Authentication settings
Set the following non-defaults.
Windows Authentication enabled
Anonymous Authentication disabled
Do not change the following defaults.
Negotiate Provider enabled
NTLM Provider enabled
Windows Authentication Kernel Mode enabled
Windows Authentication Extended Protection disabled
For certificates using SHA512, TLS1.2 must be disabled on Windows 2012 variants

Microsoft SQL Server:

Your SQL Server can reside on one of your IaaS Windows servers, or on a separate host. When hosted together with IaaS components, these requirements are in addition to those for all IaaS Windows servers.
This release of vRealize Automation does not support the default SQL Server 2016 130 compatibility mode. If you separately create an empty SQL Server 2016 database for use with IaaS, use 100 or 120 compatibility mode.
If you create the database through the vRealize Automation installer, compatibility is already configured.
AlwaysOn Availability Group (AAG) is only supported with SQL Server 2016 Enterprise. When you use AAG, you specify the AAG listener FQDN as the SQL Server host.
When hosted together with IaaS components, configure Java.
Install 64-bit Java 1.8 update 161 or later. Do not use 32-bit.
The JRE is enough. You do not need the full JDK.
Set the JAVA_HOME environment variable to the Java installation folder.
Verify that %JAVA_HOME%\bin\java.exe is available.
Use a supported SQL Server version from the vRealize Automation Support Matrix.
Enable TCP/IP protocol for SQL Server.
SQL Server includes a model database that is the template for all databases created on the SQL instance. For IaaS to install correctly, do not change the model database size.
Usually, the server needs more hardware than the minimums described in IaaS Windows Servers.
Before running the vRealize Automation installer, you need to identify accounts and add permissions in SQL. See Accounts and Passwords.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Aria Suite Lifecycle

VMware Aria Automation

Related Versions:

VMware vRealize Suite Lifecycle Manager 2.x

VMware vRealize Suite Lifecycle Manager 1.x

VMware vRealize Automation 7.x

VMware vRealize Automation 7.6.x

Take Our Survey

Support Assistant