microsoft / microsoft/CLRInstrumentationEngine
CLRIE dlls fail to load on IIS, hosted on windows server 2008R2, 4.0 application pool
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 102
- Forks
- 52
- Avg merge
- 13h 11m
- Merged PRs (30d)
- 6
Description
Steps:
Install 2008R2 and IIS, apply latest patches, choose the 4.0 application pool in IIS.
Attempt to load the CLRIE dlls through the Environment key under WAS.
Expectation - the profiler proxy and microsoft CLR instrumentation engine load ok just like they do on server 2012, 2016.
Observation - profiler load fails with HRESULT 0x8007007e . See the attached image for details.
What is different about server 2008?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The report names the CLRIE DLLs, IIS, the 4.0 application pool, the Environment key under WAS, and HRESULT 0x8007007e, but no source file or test. Begin by reproducing the load failure on Windows Server 2008R2 and comparing it with Server 2012 or 2016; done means identifying the compatibility cause and verifying the profiler proxy and CLR instrumentation engine load successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100