The WSUS administration console was unable to connect to the WSUS Server via the remote API.

Hi to all

I install WSUS in my system after that i am facing a problem this event id 7032..




The WSUS administration console was unable to connect to the WSUS Server via the remote API.

Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service.

System.Net.WebException -- The request failed with HTTP status 404: Not Found.

Source
Microsoft.UpdateServices.Administration

Stack Trace:
   at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)
   at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer()
   at Microsoft.UpdateServices.UI.AdminApiAccess.AdminApiTools.GetUpdateServer()
   at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ConnectToServer()
   at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ConnectToServerAndPopulateNode(Boolean connectingServerToConsole)
   at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.OnExpand(AsyncStatus status)

After this we need to do chances in the services.msc also.. In their default the system like this



We need to update the allow service to interact with desktop click ok .

 
open cmd prompt and type service.msc in that open  World wide Web Publishing service being configured to allow interaction with the desktop. To solve this problem, take the following steps:

    Right-click the World Wide Web Publishing service and select Properties.

    On the LogOn tab, clear the Allow service to interact with desktop check box.

    Click OK,

   Again  open the command prompt, type iisreset.

  Reset all iis in u r system
  
 At this point you should be able to access the WSUS server from the console again.


Then After Go for client system and windows update again then after i will didn't show any error .................




Comments

Post a Comment

Popular posts from this blog

Zabbix Server is not working: the information dispaly may not be current

Image
  Details  Cannot display item queue. Connection to Zabbix server "localhost:10051" refused. Possible reasons: 1. Incorrect "NodeAddress" or "ListenPort" in the "zabbix_server.conf" or server IP/DNS override in the "zabbix.conf.php"; 2. Security environment (for example, SELinux) is blocking the connection; 3. Zabbix server daemon not running; 4. Firewall is blocking TCP connection. Connection refused Observation:- In Centos 9 [root@nmtool ~]# systemctl status zabbix-server.service ● zabbix-server.service - Zabbix Server      Loaded: loaded (/usr/lib/systemd/system/zabbix-server.service; enabled; vendor preset: d>     Active: activating (auto-restart) (Result: exit-code) since Fri 2023-02-03 10:36:52 IST;>    Process: 57289 ExecStart=/usr/sbin/zabbix_server -c $CONFFILE (code=exited, status=0/SUCC>    Process: 57295 ExecStop=/bin/kill -SIGTERM $MAINPID (code=exited, status=1/FAILURE)    Main PID: 57291 (code=exited, status=0/
Read more

How to install VNX Launcher that has embedded java and Firefox

Image
  Alternative for Adobe Flash Player to access Unisphere. Symptoms VNXe Unisphere in older OE revisions is not accessible after December 31, 2020. The Adobe Flash Player plug-in is no longer supported in browsers. VNXe Unisphere used to require a browser with the Flash Player plug-in. Cause When VNXe is running an older OE revision, Adobe Flash Player is required by Unisphere. Refer: https://elabnavigator.emc.com/vault/pdf/EMC_VNXe_ESSM.pdf?key=1588743011568 Adobe has expired Flash Player as of December 31, 2020.   Details: https://www.adobe.com/products/flashplayer/end-of-life.html Resolution Newer VNXe OE revisions support HTML5. Once the VNXe is upgraded, Unisphere will work. Since December 31, 2020 browsers do not support Adobe Flash Player. Most browsers support HTML5. VNXe Unisphere must also support HTML5 in order to use VNXe Unisphere. HTML5 support is delivered in these VNXe revisions:       VNXe3200: VNXe Operating Env
Read more

DHCP FAILED APIPA IS USED

Image
Hi to all, In a Cisco packet tracer while i am trying to connect the dhcp server to pc it will getting the error like dhcp failed. APIPA is being used. For this issues this is also one reason.dhcp is not configured correctly. If we create a  vlan's in the switch's and we configured dhcp server in the layer 3 switch or layer 2 switch or in router. VLAN 10 NAME SALES VLAN 20 NAME DATA We created two vlan's now creating dhcp server for that  Switch(config)#ip dhcp pool name sales (should be the vlan name. not any other name.) Switch(Dhcp-config)#network 192.168.10.0 255.255.255.0  Switch(dhcp-config)#default-router 192.168.10.1 Switch(dhcp-config)#exit Swithc(config)#ip dhcp pool name data Switch(dhcp-config)#network 192.168.20.0 255.255.255.0 Switch(dhcp-config)#default-router 192.168.20.1 Switch(dhcp-config)#exit
Read more