Share via

Why https://schemas.microsoft.com/sqlserver/2004/sqltypes/sqltypes.xsd are no more accessible ?

Benoit Gastellier 1 Reputation point
2022-04-20T07:57:09.38+00:00

194621-image.png

Developer technologies | ASP.NET Core | Other
0 comments No comments

2 answers

Sort by: Most helpful
  1. Vladimir Moldovanenko 276 Reputation points
    2022-04-27T18:02:17.223+00:00

    I experienced the same thing. Let's run a simple command and get default schema

    SELECT *   
    FROM (VALUES(1), (2))v(ID)  
    FOR XML RAW, ROOT, XMLSCHEMA  
    

    Note that schemaLocation="http://schemas.microsoft.com/sqlserver/2004/sqltypes/sqltypes.xsd" references http.
    If it changed, then I expect SQL Server cumulative update to fix it too.

    If I paste schemaLocation value into MS Edge it fails with an error like above but redirects to https in Chrome and works.

    We also use xsd schema normalization process to resolve 'include' statements and this process errors too.
    It worked flawlessly since 2007. the result is deployed to sql xml schema collections
    See preprocess-a-schema-to-merge-included-schemas

    I am not sure what is going on. Any other insight, anyone?

    Thanks
    Vladimir

    Was this answer helpful?

    0 comments No comments

  2. Yijing Sun-MSFT 7,106 Reputation points
    2022-04-20T09:55:31.043+00:00

    Hi @Benoit Gastellier ,
    Schemas.microsoft.com has down. So, I think you could try to activate the TLS1.2 to make the script working.

     # Activate TLS12  
     $TLS12Protocol = [System.Net.SecurityProtocolType] 'Ssl3 , Tls12'  
     [System.Net.ServicePointManager]::SecurityProtocol = $TLS12Protocol  
    

    Best regards,
    Yijing Sun

    Was this answer helpful?

    0 comments No comments

Your answer

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