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

UNKNOWN_FAULT_FATAL - After waiting for 300 seconds internal template VM Instant Clone Creation Error (76469)

Last Updated: 1/6/2023Categories: TroubleshootingTotal Views: 19238Language:
English

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Symptoms

Instant clone push operation fails with an error :

Fault type is UNKNOWN_FAULT_FATAL - After waiting for 300 seconds internal template VM.

Upon reviewing the Debug logs from Connection Server - The Image waits for 300 seconds and then fails with an exception:-

2023-09-30T09:17:57.495-05:00 WARN  (0ED8-18E8) <WFE-14> [Action] The VC Operation failed with error: com.vmware.daas.cloneprep.common.CPException: After waiting for 300 seconds internal template VM: vm-xxxxx is still not powered off. Giving up!

2023-09-30T09:17:57.496-05:00 ERROR (0ED8-0E9C) <WFE-19> [Task] WaitForInternalTemplateAction of Task=[PrepareInternalTemplateTask:c10f26b8-1def-4db1-9814-d4664cfcdc1c:1672355], requestId=ee86de5d-491d-463e-87f9-06ea77a3a365 failed at index=5 with com.vmware.daas.cloneprep.common.CPException: After waiting for 300 seconds internal template VM: vm-xxxxx is still not powered off. Giving up!

Purpose

Instant clone push operation fails with an error Fault type is UNKNOWN_FAULT_FATAL - After waiting for 300 seconds internal template VM.

Cause

The internal template has a default of 5 minutes (300 seconds) to complete customization before it will time out.

Note: The internal template 300 seconds cannot be configured or modified as it's hard coded.

Example:
Domain join usually takes more than a minute. So for instance , if a gpupdate takes more than 4 minutes, it's going to timeout.

Impact / Risks

Unable to create Instant Clone VMs.

Resolution

This issue may occur if Group Policy updates takes too long on the CP-Template and this requires internal assessment within your organization to improve the performance / duration of the updates.

Workaround

To isolate the issue if the group policy update is contributing to the time out ,  you can set the following registry on the parent image

HKLM\Software\VMware, Inc.\ViewComposer\ga\GPUpdateEnabledOnIT
DWORD 0

If this works then to address the issue GPO related issues needs to be fixed.
This key is to assist with isolating the issue and it is not recommended as a solution.

You can block inheritance and iteratively test policies to isolate the problematic policy.

You can follow industry best practices in terms of troubleshooting GP performance.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
vCloud Director 设备安装最佳实践 (76559)

KB
•
在 Linux 虚拟机上跳过 SRM IP 子网规则自定义。未报告已断开连接网卡的 IP 配置 (76492)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Horizon

Related Versions:

VMware Horizon 7.x

VMware Horizon 7

Take Our Survey

Support Assistant