Quantcast
Channel: WSUS forum
Viewing all articles
Browse latest Browse all 12874

Another unable to connect to Update Services console after movecontent

$
0
0

Sorry to post another thread on this topic, but I've tried to resolve this issue based on suggestions in other threads and it still isn't working, so am a bit lost.

So our C drive on the WSUS server was running out of space and I added a new 1TB drive (E:\) and then proceeded with the command:wsusutil.exe movecontent E:\WSUS\ E:\wsusmove.log

This appeared to work fine and took a couple of hrs to move about 145GB of files to E drive.

2015-10-29T05:00:17 Successfully stopped WsusService.
2015-10-29T05:00:17 Beginning content file location change to E:\WSUS\
2015-10-29T06:45:03 Successfully copied content files.
2015-10-29T06:45:04 Successfully copied application files.
2015-10-29T06:45:08 Successfully changed WUS configuration.
2015-10-29T06:45:10 Successfully changed IIS virtual directory path.
2015-10-29T06:45:11 Successfully removed existing local content network shares.
2015-10-29T06:45:12 Successfully created local content network shares.
2015-10-29T06:45:12 Successfully changed registry value for content store directory.
2015-10-29T06:45:12 Successfully changed content file location.
2015-10-29T06:45:17 Successfully started WsusService.
2015-10-29T06:45:17 Content integrity check and repair...
2015-10-29T06:45:17 Initiated content integrity check and repair.

However, once I restarted the server and attempted to connect to the Update Services console (logged into the server itself), I get the "Error: Connection Error - an error occurred trying to connect to the WSUS Server. This error can happen for a number of reasons" etc.

Event ID's 7032 (The WSUS administration console was unable to connect to the WSUS Server via the remote API. ) and 7053 (The WSUS administration console has encountered an unexpected error. This may be a transient error; try restarting the administration console) are showing in the event log.

I've tried the following to fix with no luck:

- Deleted the 'wsus' file under C:\Users\administrator.INTRANET\AppData\Roaming\Microsoft\MMC

- Set permissions on the new E:\ to ensure SYSTEM and NETWORK SERVICE has Full Control

- Restarted the server several times to ensure any changes are refreshed etc.

This is using WSUS v3.2.7600.274 on a Windows Server 2008 SP2 (32-bit) VM.

The only thing I can think of which might be causing strange behavior is that the E drive where I moved the files to is actually an external USB I have setup on the VM host to be available to the WSUS VM as a fixed drive. Not sure if this should cause any problems? The OS just sees it as a normal drive as far as I can tell. It's running NTFS like C drive is.



Viewing all articles
Browse latest Browse all 12874

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>