Disable experience/compatibility services on win64-rev2 machines to avoid unwanted file locking

RESOLVED FIXED

Status

Infrastructure & Operations
RelOps
RESOLVED FIXED
4 years ago
4 years ago

People

(Reporter: jhopkins, Assigned: markco)

Tracking

Details

(Reporter)

Description

4 years ago
I've run into these frequent conftest.exe "permission denied" failures while doing various Windows builds on the new win64-rev2 (ix-mn-w0864-*) machines:

======
checking whether the C++ compiler (cl  ) works... no
------ config.log ------
rm: cannot lstat `conftest.exe': Permission denied
configure: error: installation or configuration problem: C++ compiler cannot create executables.
======

This has been happening often enough to consider it a blocker to rolling out the new platform.

I've been testing the settings in https://bugzilla.mozilla.org/show_bug.cgi?id=545015#c24 and initial test results indicate it has resolved the file locking problem.  To summarize, the manual changes I made are:

- disable the application experience service
- turn off application compatibility engine
- turn off program compatibility engine

The file indexing service does not appear to be installed so that step of the solution is a no-op.
Assignee: relops → mcornmesser
(Assignee)

Comment 1

4 years ago
This will now be handled by GPO 2008_compatibility_off:

Computer Configuration> Policies> Windows Settings> Security Settings> System Services>
Application Experience Service disabled

Computer Configuration> Policies> Administrative Templates> Windows Components>
Turn off Application Compatibility Engine disabled
Turn off Program Compatibility Assistant disabled
(Reporter)

Comment 2

4 years ago
I left these settings as they were:

Turn off Application Compatibility Engine disabled
Turn off Program Compatibility Assistant disabled

Then manually re-enabled and started the "Application Experience" service.  Following that, I started two new builds and did not hit the conftest.exe locking problem that had been plaguing that build type (WINNT 6.1 x86-64 try build).

Mark: can you please adjust the GPO change you made above to enable the Application Experience service?  I'd like to try with this setting for awhile, since I did see some contention on web forums about whether disabling that service helped or hindered file locking.
Flags: needinfo?(mcornmesser)
(Assignee)

Comment 3

4 years ago
John, the Application Experience service has been re-enable. It should be running on the next reboot.
Flags: needinfo?(mcornmesser)

Comment 4

4 years ago
(In reply to John Hopkins (:jhopkins) from comment #0)
> I've run into these frequent conftest.exe "permission denied" failures while
> doing various Windows builds on the new win64-rev2 (ix-mn-w0864-*) machines:
> 
> ======
> checking whether the C++ compiler (cl  ) works... no
> ------ config.log ------
> rm: cannot lstat `conftest.exe': Permission denied
> configure: error: installation or configuration problem: C++ compiler cannot
> create executables.
> ======
> 
> This has been happening often enough to consider it a blocker to rolling out
> the new platform.
> 
> I've been testing the settings in
> https://bugzilla.mozilla.org/show_bug.cgi?id=545015#c24 and initial test
> results indicate it has resolved the file locking problem.  To summarize,
> the manual changes I made are:
> 
> - disable the application experience service
> - turn off application compatibility engine
> - turn off program compatibility engine
> 
> The file indexing service does not appear to be installed so that step of
> the solution is a no-op.

Works like a charm after doing the 3 steps...
(Reporter)

Comment 5

4 years ago
So far, I have not hit the conftest.exe problem since re-enabling the application experience service (and leaving the compatibility engines set to 'disabled').
(Reporter)

Comment 6

4 years ago
This is looking pretty solid now.  I'll reopen if I run into any other file locking problems.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.