Why might wsusutil export to a .xml.gz file produce a 0 byte output?

Question

We're doing monthly updates to a disconnected network with Server 2012 installed on all servers.

Last month (February), the export created a 60 megabyte .xml.gz. Today, it creates a 0 byte file timestamped at the start of the export and the log's timestamp hits at the end of the process.

Any ideas where to look next? Google just returns results for the .cab 0 byte issue.

score 0 · Answer 1 · answered Jun 20 '14 at 08:22

0

Same happened to me. Yo have to install a patch for WSUS.

http://blogs.technet.com/b/wsus/archive/2013/04/09/problem-solved-the-wsus-export-bug.aspx

answered Jun 20 '14 at 08:22

Angel Sancho

1

I believe this fixes the `.cab 0 byte issue` that the OP emphasized is not his current problem, no? – Felix Frank Jun 20 '14 at 08:50
Does that patch fix the xml coming out as 0 or just let you use the xml format? – Simon Gill Jun 20 '14 at 09:51

Why might wsusutil export to a .xml.gz file produce a 0 byte output?

1 Answers1