Skip to main content

 none
HLK-1809: Static Tools Logo Test fails with "Could not load... RoMetadata.dll could not be found" RRS feed

  • Question

  • Attempting to certify several drivers with Server 2019 (build 17763, datacenter without desktop) on HLK 1809 (build 17763), and the Static Tools Logo Test fails with

    [HRESULT 0x8007007E] Failed to load 'C:\hlk\JobsWorkingDir\Tasks\WTTJobRun083EB4D8-A7CB-E811-80B7-C616C55925F2\Devfund_DvlTest.dll'. (Could not load managed test module because RoMetadata.dll could not be found. Make sure the TAEF package is deployed or RoMetadata.dll is deployed to a location in your PATH environment variable.)

    No test cases were executed.

    What am I missing? Should this file be installed by the HLK client setup (which reports that all components are installed)

    Thanks

    Owen

    Tuesday, October 9, 2018 10:05 AM

Answers

  • This is a known issue with ServerCore on WS 2019.  The workaround is to run the Static Tools Logo test on Server GUI and then merge that package with the package containing the other results from ServerCore.
    • Marked as answer by Owen-Smith Monday, November 5, 2018 3:55 PM
    Thursday, October 25, 2018 6:30 PM

All replies

  • Me too.

    For Windows Server 2019 ServerCore, an error occurs but no error occurs on Windows Server 2019 Full Server.

    RoMetadata.dll seems to be a dll that does not exist in ServerCore.

    • Proposed as answer by Luis Salmeron Friday, October 19, 2018 4:03 PM
    • Unproposed as answer by Luis Salmeron Friday, October 19, 2018 4:04 PM
    Wednesday, October 10, 2018 3:23 AM
  • I was able to get this to work by manually copying the RoMetadata.dll file to the host.

    On your HLK host, search for RoMetadata.dll. In my system, it was found in C:\Windows\WinSxS\amd64_microsoft-windows-winrt-metadata_31bf3856ad364e35_6.3.9600.16384_none_2f9df483133c48b0. On your test host, enter the command "path" to show the environmental variable paths and then copy the dll to one of these locations.

    Friday, October 19, 2018 7:07 PM
  • This is a known issue with ServerCore on WS 2019.  The workaround is to run the Static Tools Logo test on Server GUI and then merge that package with the package containing the other results from ServerCore.
    • Marked as answer by Owen-Smith Monday, November 5, 2018 3:55 PM
    Thursday, October 25, 2018 6:30 PM
  • >The workaround is to run the Static Tools Logo test on Server GUI and then merge that package with the package containing the other results from ServerCore.

    It seems not to merge if GUI / Core is not in the same Machine Pool.

    >This is a known issue with ServerCore on WS 2019.
    By the way, is the document published somewhere?
    It is troubled if there is no way to know on the user side.

    Also, when will this issue be fixed?
    Is it fixed at the timing of republishing Windows Server 2019?
    (Originally, what time Windows Server 2019 can be downloaded from My Visual Studio ...)

    Monday, October 29, 2018 8:16 AM
  • I do have 1 question.

    I have a 2019c machine and 2019g machine.  My gui machine doesn't get the Static Tools test chosen for it.  I then tried placing them both in a group to see if perhaps it would run on the machine it'd test with, but that test is 100% bound to that 2019c on my system.

    Any thoughts? I'm just popping on here because i'm having this issue and if it's found to be "worked around" i'm trying to sort out why it's not even an optional work around for me.

    Thanks for your time!

    Ren

    Monday, March 11, 2019 3:10 PM