Missing PDB file for Windows Server 2012R2 schannel.dll (v 6.3.9600.20336)

Maxim Pak 1 Reputation point
2022-04-20T01:25:52.65+00:00

Hi,

We've noticed that PDB files are missing from the Microsoft symbols servers for Windows Server 2012 schannel.dlls. We use the symchk.exe tool to get the PDB files and it works fine for all other versions of Windows.

.\symchk.exe /v $PathToSchannel /s srv*https://msdl.microsoft.com/download/symbols

Is this possible to purchase a special MSDN subscription to gain access to these symbols or is there any other way?

Thank you

Windows for business | Windows Server | User experience | Other
{count} votes

3 answers

Sort by: Most helpful
  1. Limitless Technology 39,926 Reputation points
    2022-04-25T08:35:33.137+00:00

    Hello

    Thank you for your question and reaching out.

    I am afraid as you can not buy Microsoft Symbols server as Microsoft doesn't provide the PDBs for SLC to prevent creating of cracks to activate Windows.

    Run the VS2012 or 2013 , go to Options->Debugging->automatically load symbols for: "all symbols, unless excluded". Click on the blue link and add SLC to the exclude list.

    Alternatively , This can also happen if you don't have Modify permissions on the symbol cache directory configured in Tools, Options, Debugging, Symbols then Clean and Rebuild the project.


    --If the reply is helpful, please Upvote and Accept as answer--

    0 comments No comments

  2. Maxim Pak 1 Reputation point
    2022-05-02T04:33:27.187+00:00

    @Limitless Technology , thank you for your answer. But why other versions of Windows have symbols (i.e. Windows Server 2016 / 2019 / 2022, Windows 7 / 10 / 11)? This problem is specific to the Windows Server 2012 R2 and not other versions of Windows.

    0 comments No comments

  3. Sam Warner 0 Reputation points
    2023-12-29T22:54:49.7+00:00

    .exepath

    I've had this problem too. The dmp files do not contain the executing image from the target system, and WinDBG will default to using the host platform for the debug session to compare to the timestamp from the symbol server. (I'm not exactly certain of the logic in WinDBG, and when it uses the host vs. target image). What I do to resolve this issue is copy the needed executing images into a target-dir, point the exepath to the target-dir, and reload symbols. The symbols that were failing then succeed.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.