Win 2k8 R2 SP1

Forefront TMG 2010 SP2. Stand alone node.

Scenario:

V2V migration from Hyper-V to vmWare. Old NICs were removed and new ones added.

Error:

Microsoft Forefront TMG Control failed to start.

The failure occurred during Security Watchdog notification processing because the system call ApplyAccessControlSettings failed.

Use the source location 122.86.7.0.9193.540 to report the failure.

The error description is: An attempt was made to reference a token that does not exist.

Any advice would be appreciated!

• Edited by merrowind Thursday, October 17, 2013 4:00 AM

Hi,

The issue you encountered may mainly result from two reasons. One is installing order between TMG and some other applications. The other is that TMG works with NLB.

Please refer to the links below to try to solve the problem:

http://social.technet.microsoft.com/Forums/forefront/en-US/c53e6da7-3b09-4fd5-9b67-35f2bfb87e65/forefront-tmg-2010-failed-to-start-automatically-on-windows-2008r2-at-server-startup?forum=Forefrontedgesetup

http://www.isaserver.org/blogs/shinder/news/tmg-control-fails-to-start-on-nlb-array-1524.html

Best Regards

Quan Gu   

Thanks for tips. I`ve already looked into them, and the scenarios are different.

In my case, I hade a working TMG on Hyper-V, which I then migrated to vmWare ESXi (Intel-Intel), with reconfiguration of the machine in regards to NICs. Resulted in the mentioned error.

Hi,

Is the OS of VM same with before? Or is there any other error information during v2v migration?

 

For my research, most solutions for this issue are uninstall and reinstall TMG in correct order. However, the issue may result from many reasons.

 

In general, TMG control service is easily impacted by other applications. So, you should confirm if there is any possibility for this in your environment.

 

If there is no more error information about this, I think you only try to uninstall/reinstall TMG.

 

 

Best Regards

Quan Gu