locked
The server cannot find the requested URI (Uniform Resource Identifier) RRS feed

  • Question

  • Hi

    We are working on a new WSUS server with more power to replace our old WSUS server. I thought it would be an easy task to do, because I could just look on the old one that is still running and working fine.

    Both servers are Running Windows Server 2012 R2 and nothing else. Just like my old server I want it to run on port 443 with SSL certificate. I have stopped the Default Web Site leaving me with only the WSUS Administration website with bindings on port 80 and 443. My users are not domain joined and many of the are connecting from external locations. Because if that WSUS configuration is made in registry and not with GPO, but again this setup work fine with my old WSUS server.

    I get this error:

    Result CODE: 0x0 0x80244019 - Same as HTTP status 404  The server cannot find the requested URI (Uniform Resource Identifier).

    My test computers does not register in WSUS, unless I use plan http (80). I guess I have some kind of issue on my IIS, but how do I troubleshoot this issue?

    I have no problem connecting to https://wsus2.domain.com/ClientWebService/client.asmx from my test client.


    Thomas | MCP | http://www.techwork.dk


    Monday, May 23, 2016 11:48 AM

Answers

  • I finally found the cause of this issue. Before I configured the WSUS role I installed all updates available from Windows Update including KB3159706. This update requires manual configuration if you are using SSL on our WSUS server. More information about that here: https://support.microsoft.com/en-us/kb/3159706

    The thing is that you can't just uninstall KB3159706 to get back the normal state of your WSUS server. The updates make changes to both database and webservices (/ClientWebService/web.config). It is kind of a no way back update.

    I decided to uninstall WSUS, IIS and WID database service and start all over with my installation again, but this time, without the KB3159706 installed. Now everything works with my 3th party wildcard certificate and https.

    Next step is to install KB3159706 and make it work with SSL. It requires manual steps: https://p0w3rsh3ll.wordpress.com/2016/05/11/wsus-2012-r2-kb3159706-manual-steps/ 


    Thomas | MCP | http://www.techwork.dk


    Monday, May 30, 2016 2:10 PM

All replies

  • I have the same exact issue.  WSUS is configured on port 8530/8531.  Without SSL everything works great.  Once I switch to SSL I get the URI error.
    Monday, May 23, 2016 8:16 PM
  • I am not sure if it is an issue with my certificate. Are using an AlphaSSL wildcard certificate.

    Thomas | MCP | http://www.techwork.dk

    Tuesday, May 24, 2016 8:03 AM
  • Hi Thomas Nielsen,

    Please check if the configuration steps are all correct:

    https://technet.microsoft.com/en-us/library/hh852346%28v=ws.11%29.aspx?f=255&MSPPError=-2147217396

    http://jackstromberg.com/2013/11/enabling-ssl-on-windows-server-update-services-wsus/

    (This is a third-party article, so it will change the content without notification, if you have any questions, feel free to point out.)

    Check if you have appended the port 443 to the URL.

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.


    Tuesday, May 24, 2016 8:09 AM
  • Hi Thomas Nielsen,

    Please check if the configuration steps are all correct:

    https://technet.microsoft.com/en-us/library/hh852346%28v=ws.11%29.aspx?f=255&MSPPError=-2147217396

    http://jackstromberg.com/2013/11/enabling-ssl-on-windows-server-update-services-wsus/

    (This is a third-party article, so it will change the content without notification, if you have any questions, feel free to point out.)

    Check if you have appended the port 443 to the URL.

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.


    Hi Anne

    I really believe I have followed all the steps in the guide from Technet. My clients are external end connect using and Internet facing URL. I can't really figures out if my issue is with my certificate missing the local name of the server. My clients has no issue connecting to the /ClientWebService/Client.asmx on the Internet URL.


    Thomas | MCP | http://www.techwork.dk


    Wednesday, May 25, 2016 6:31 AM
  • Hi

    What are the requirements for a 3th party SSL certificate for a WSUS server on Windows Server 2012 R2?

    I have a wildcard certificate that match my internet facing FQDN, but is that usable or do I need a special certificate for WSUS? I am not able to use self signed certificates for my installation.


    Thomas | MCP | http://www.techwork.dk


    Thursday, May 26, 2016 12:49 PM
  • Hi Thomas Nielsen,

    >I can't really figures out if my issue is with my certificate missing the local name of the server.

    I usually use a certificate duplicated from web server certificate issued by CA server.

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.


    Friday, May 27, 2016 3:00 AM
  • Hi Thomas Nielsen,

    Sorry for the later reply in another post created by you with the similar issue.

    I haven't tested third-party certificates to deploy WSUS SSL. I generally created a CA server in my domain, then duplicate the template of web server certificate for SSL.

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Friday, May 27, 2016 3:12 AM
  • Hi Anne

    I know that is the normal way to do it, but my setup is a bit different than that. My client computer are not in my domain, they are external. That is why I want to use a 3th party trusted SSL certificate. I am just not sure about what the requirements are for that.


    Thomas | MCP | http://www.techwork.dk

    Friday, May 27, 2016 6:18 AM
  • Hi Thomas Nielsen,

    Ensure the root certificate of the 3 party certificate is stored in "Trusted root certificate" on WSUS server and WSUS clients, and check if the common name of the certificate is configured with the FQDN of the WSUS server.

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Monday, May 30, 2016 9:26 AM
  • I finally found the cause of this issue. Before I configured the WSUS role I installed all updates available from Windows Update including KB3159706. This update requires manual configuration if you are using SSL on our WSUS server. More information about that here: https://support.microsoft.com/en-us/kb/3159706

    The thing is that you can't just uninstall KB3159706 to get back the normal state of your WSUS server. The updates make changes to both database and webservices (/ClientWebService/web.config). It is kind of a no way back update.

    I decided to uninstall WSUS, IIS and WID database service and start all over with my installation again, but this time, without the KB3159706 installed. Now everything works with my 3th party wildcard certificate and https.

    Next step is to install KB3159706 and make it work with SSL. It requires manual steps: https://p0w3rsh3ll.wordpress.com/2016/05/11/wsus-2012-r2-kb3159706-manual-steps/ 


    Thomas | MCP | http://www.techwork.dk


    Monday, May 30, 2016 2:10 PM
  • Hi Thomas Nielsen,

    Glad to hear you have made it work and thanks for your feeding back.

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Tuesday, May 31, 2016 1:31 AM
  • Hi Thomas Nielsen,

    I notice you have solved the issue which mentions in another post, I will merge this post to that one, thanks for your understanding.

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Tuesday, May 31, 2016 1:50 AM