WSUS not enough space

Hi there,
I have a strange problem:
I run WSUS3 on W2k3 Server SP2 and sync from another sync-Server. I once
ran WSUS1 on that machine, but uninstalled all WSUS1 components (I dont
know wether this is important or not).
Somehow I am getting Error 10042 (less than 200MB Space left on device)
although I have 43GB free.
I ran the cleaner assistant, deleted english (and left only the local
language) and made WSUS download instead of only 3GB now 20GB of Data,
but there are still 20GB data do download (and if those 20GB are
downloaded there are still 23GB more left on device)

I also tried WSUS-Server-Diagnostic-Tool but it seems to fail:
Z:\>z:\wsus-server-diag\WsusDebugTool.exe /Tool:GetConfiguration

Unbehandelte Ausnahme: System.Security.SecurityException: Sicherheitsfehler.
at Microsoft.SoftwareDistribution.Tools.SusServerTool .Main(String[]
args)

Gewährter Berechtigungssatz der fehlgeschlagenen Assembly war:
<PermissionSet class="System.Security.PermissionSet"
version="1">
<IPermission
class="System.Security.Permissions.FileDialogPermi ssion, mscorli
b, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"
version="1"
Access="Open"/>
<IPermission
class="System.Security.Permissions.IsolatedStorage FilePermission
, mscorlib, Version=1.0.5000.0, Culture=neutral,
PublicKeyToken=b77a5c561934e089
"
version="1"
Allowed="DomainIsolationByUser"
UserQuota="10240"/>
<IPermission class="System.Security.Permissions.SecurityPermiss ion,
mscorlib,
Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"
version="1"
Flags="Execution"/>
<IPermission class="System.Security.Permissions.UIPermission,
mscorlib, Versi
on=1.0.5000.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"
version="1"
Window="SafeTopLevelWindows"
Clipboard="OwnClipboard"/>
<IPermission class="System.Drawing.Printing.PrintingPermission,
System.Drawin
g, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"
version="1"
Level="SafePrinting"/>
<IPermission
class="System.Security.Permissions.PublisherIdenti tyPermission,
mscorlib, Version=1.0.5000.0, Culture=neutral,
PublicKeyToken=b77a5c561934e089"
version="1"

X509v3Certificate="308204E1308203C9A003020102020A6 10587580003000
0005A300D06092A864886F70D01010505003081A6310B30090 603550406130255533113301106035
50408130A57617368696E67746F6E3110300E0603550407130 75265646D6F6E64311E301C0603550
40A13154D6963726F736F667420436F72706F726174696F6E3 12B3029060355040B1322436F70797
269676874202863292032303030204D6963726F736F6674204 36F72702E312330210603550403131
A4D6963726F736F667420436F6465205369676E696E6720504 341301E170D3035303130353233323
031395A170D3036303430353233333031395A3074310B30090 603550406130255533113301106035
50408130A57617368696E67746F6E3110300E0603550407130 75265646D6F6E64311E301C0603550
40A13154D6963726F736F667420436F72706F726174696F6E3 11E301C060355040313154D6963726
F736F667420436F72706F726174696F6E30820122300D06092 A864886F70D01010105000382010F0
03082010A0282010100CF38F7E1A4275EF8F0CCAACEFB3ADE3 B6231460546BBF5B6051AD3B3ACC29
F0F4C670828C44310F53B75797F6A91F4D633C861BFFA91900 07AF0791D5D6870F690B29877B5031
D2F9B9D9B75892F4A01417C9E7CCB87439BF49674999E98C1C F40575816F6C0D59216E52485718F9
949ED557C65C91F380023C53EAB11D6296CC69EA0705B7DD53 7D4677720C306CE85F84E3480A035C
41C53320157EFB128BD6C01E3AD40BC80A90949DB36E337F41 D49AA2AA76BD019D3CC8E9DD686467
A134AD64519A553B3E2782F2E35976B4CC6E81AB0D3D124906 9ABCEFC696E3E4CFB024162DC07985
D7E5CA74C27316B564CE198D8E0D11D718D3D2AC07F714DFFC F0203010001A38201403082013C300
E0603551D0F0101FF0404030206C0301D0603551D0E0416041 4921112143477B18F6834E20EF1323
4C0E9F3633130130603551D25040C300A06082B06010505070 3033081A90603551D230481A130819
E801425F82B4B5DC87254ADE5F6A02A1716FBC1F95381A174A 4723070312B3029060355040B13224
36F70797269676874202863292031393937204D6963726F736 F667420436F72702E311E301C06035
5040B13154D6963726F736F667420436F72706F726174696F6 E3121301F060355040313184D69637
26F736F667420526F6F7420417574686F7269747982106A0B9 94FC0000CAB11D822EF7D6C797E304
A0603551D1F04433041303FA03DA03B8639687474703A2F2F6 3726C2E6D6963726F736F66742E636
F6D2F706B692F63726C2F70726F64756374732F436F6465536 9676E5043412E63726C300D06092A8
64886F70D010105050003820101000C010A0DEE261EC311BCC 4743CA71DEEF54ADE2799A2F7AB8C8
E4772A051BFA8B14BD87F42D51C8FA3E6B812BD5123AFB13BD 365F12D8C03E94C50ED38F6575E3A7
34F33AC132DB525C33BE59159DFD01BB8D0AE110709CC05D35 21CE20A647705181977127510931A3
6168CD5201F6C33EF602F6DAFE6F1D4DA29BE8ADBB50F6B952 240F22B973250FFFAEA8AC6B6E3EC3
68AB27729543E7E1695FE71598DA7CA840FE1FF8211812F198 7DDE7449F8DEF22F2FEB68CCFC8DB2
186B59798480DABD8E16372DD6FE72C932B9FEEB612D63A594 A21E59FA962509315751D765FD8A0C
2FAF9A4AC7E11CAF957BFFDD289E97DEE8CA4DA07BBBA14DD1 343D5EA9DE6"/>
<IPermission
class="System.Security.Permissions.UrlIdentityPerm ission, mscorl
ib, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"
version="1"
Url="file://Z:/wsus-server-diag/WsusDebugTool.exe"/>
<IPermission
class="System.Security.Permissions.ZoneIdentityPer mission, mscor
lib, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"
version="1"
Zone="Internet"/>
</PermissionSet>


Z:\>


Any Ideas?

Thanks in Advance

Erik

"Pimperator" <> wrote in message
news:uwR5L3%...

> Hi there,
> I have a strange problem:

This post actually creates more questions than I'm able to provide answers..
so let me ask my questions first, and then hopefully I can provide you an
intelligent answer.

> I run WSUS3 on W2k3 Server SP2 and sync from another sync-Server.

What do you mean by "sync from another sync-Server". What is a
"sync-Server". Do you mean that this WSUS3 server is a *downstream* server
and is synchronizing from an *upstream* WSUS3 server?

> I once ran WSUS1 on that machine, but uninstalled all WSUS1 components (I
> dont know wether this is important or not).

Well it might be important. Did you subsequently install WSUS3 on that
machine? Is that machine a WSUS Server at all? If it has WSUS 3 running on
it, then that's prima facie evidence that WSUS1 (sic) (version 1 was
actually called =SUS=: Software Update Services) was successfully
uninstalled, since WSUS3 cannot be installed to a machine with any remnants
of SUS1 present.

> Somehow I am getting Error 10042 (less than 200MB Space left on device)
> although I have 43GB free.

And are we certain that the error being reported is the same logical volume
that you claim to have 43GB free on? Have you inspected the Recycle Bin and
other resources that are normally not included in the User Interface when
free space is reported?

> I ran the cleaner assistant, deleted english (and left only the local
> language) and made WSUS download instead of only 3GB now 20GB of Data, but
> there are still 20GB data do download (and if those 20GB are downloaded
> there are still 23GB more left on device)

All of which is pointless if the system thinks there's only 200MB of free
space on the volume.

> I also tried WSUS-Server-Diagnostic-Tool but it seems to fail:
> Z:\>z:\wsus-server-diag\WsusDebugTool.exe /Tool:GetConfiguration

Uhhh.. you're on the Z: drive, and you're executing a resource ostensibly
located on the Z: drive, so first, I'd ask, why not do this:

Z:\> CD \WSUS-SERVER-DIAG
Z:\WSUS-SERVER-DIAG> WSUSDEBUGTOOL.exe /Tool:GetConfiguration

Or, even more appropriately, rather than trying to run the tool across the
network (or from removable media if that's what drive Z: actually is)...

COPY the tool to the LOCAL drive...

Z:\> COPY \WSUS-SERVER-DIAG\WSUSDebugTool.exe C:\TEMP
Z:\> C:
C:\> CD \TEMP
C:\TEMP> WSUSDebugTool /Tool:GetConfiguration

In any event, the server debug tool throws an exception...

Is the machine you ran this tool from actually a WSUS 3 server?
Or is this the machine that used to be a SUS1 server?
What "configuration" are you expecting to retrieve from this tool?
Why are we interested in retrieving the server configuration?



--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

Hi there,
I'm trying to answer your questions below.

First of all let's define two computers:
Server1 = the one which runs WSUS3 now and has the problems (It is also
the machine with the formerly installed SUS1)
Server2 = the one which ran WSUS2

Lawrence Garvin [MVP] schrieb:
> "Pimperator" <> wrote in message
news:uwR5L3%...
>
>> Hi there,
>> I have a strange problem:
>
> This post actually creates more questions than I'm able to provide
answers.. so let me ask my questions first, and then hopefully I can
provide you an intelligent answer.
>
>> I run WSUS3 on W2k3 Server SP2 and sync from another sync-Server.
>
> What do you mean by "sync from another sync-Server". What is a
"sync-Server". Do you mean that this WSUS3 server is a *downstream*
server and is synchronizing from an *upstream* WSUS3 server?
I hope by pasting my configs below this question has an answer

>
>> I once ran WSUS1 on that machine, but uninstalled all WSUS1
components (I dont know wether this is important or not).
>
> Well it might be important. Did you subsequently install WSUS3 on
that machine?
As far as I know (it is too long ago) I uninstalled (I dont know how
successful it was, because some data were left) SUS1 to install WSUS2,
which failed(I dont know why) on Server1, installed WSUS2 on Server2 and
after a while (about two years) I replaced WSUS2 on Server2 by WSUS3 on
Server1.

> Is that machine a WSUS Server at all? If it has WSUS 3 running on it,
then that's prima facie evidence that WSUS1 (sic) (version 1 was
actually called =SUS=: Software Update Services) was successfully
uninstalled, since WSUS3 cannot be installed to a machine with any
remnants of SUS1 present.
>
okay, so SUS1 (If I write WSUS1 I of course mean SUS1) is uninstalled.
Although I had difficulties with installing WSUS3, because I compressed
the target-Folder containing WSUS-Database and update-Files before
installation. Now only c:\programs\ (which contains IIS-Stuff and
Exefiles a.s.o. is compressed. Just fyi
>> Somehow I am getting Error 10042 (less than 200MB Space left on
device) although I have 43GB free.
>
> And are we certain that the error being reported is the same logical
volume that you claim to have 43GB free on? Have you inspected the
Recycle Bin and other resources that are normally not included in the
User Interface when free space is reported?
Yes, I am sure that there are 43GB free. I have two volumes c: (
2.223.255.552 Bytes free) and f: ( 45.155.770.368 Bytes free)
>
>> I ran the cleaner assistant, deleted english (and left only the
local language) and made WSUS download instead of only 3GB now 20GB of
Data, but there are still 20GB data do download (and if those 20GB are
downloaded there are still 23GB more left on device)
>
> All of which is pointless if the system thinks there's only 200MB of
free space on the volume.
Yes, I now ran cleaning for the second time. there are no data in
recycle bin.
>
>> I also tried WSUS-Server-Diagnostic-Tool but it seems to fail:
>> Z:\>z:\wsus-server-diag\WsusDebugTool.exe /Tool:GetConfiguration
>
> Uhhh.. you're on the Z: drive, and you're executing a resource
ostensibly located on the Z: drive, so first, I'd ask, why not do this:
>
>
> In any event, the server debug tool throws an exception...

A sh***y behaiviour in windows not to be able to handle network
ressources. Thanks for the hint. It now works from a local volume as you
can see below.
>
> Is the machine you ran this tool from actually a WSUS 3 server?
YES
> Or is this the machine that used to be a SUS1 server?
YES SUS1==WSUS3==Server1
> What "configuration" are you expecting to retrieve from this tool?
The one I can send you for debugging or better understanding
> Why are we interested in retrieving the server configuration?
see above
>
>
>


This is my config:

F:\>WsusDebugTool.exe /Tool:GetConfiguration
Running... GetConfiguration
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Update Services\Server\Setup
:
Version:3
VersionString:3.1.6001.65
ConfigurationSource:0
ServicePackLevel:1
TargetDir:C:\Programme\Update Services\
InstallType:1
EnableRemoting:1
WsusAdministratorsSid:your-mother
WSUSReportersSid:your-mother2
SqlServerName:MUENCHEN\MICROSOFT##SSEE
SqlAuthenticationMode:WindowsAuthentication
SqlDatabaseName:SUSDB
SqlUserName:
SqlEncryptedPassword:
SqlInstanceIsRemote:0
wYukonInstalled:1
IISInstallRevision:3.1.6001.65
IISPreviousInstallRevision:
IISUninstallConfigFilePath:C:\Programme\Update
Services\setup\UninstallS
ettings.xml
IISTargetWebSiteCreated:True
IISTargetWebSiteIndex:your-mother3
ContentDir:F:\WSUS
SmtpUserPassword:
ProxyPassword:
PortNumber:8530
IIsDynamicCompression:0
EncryptionParam:System.Byte[]
EncryptionKey:System.Byte[]
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Update
Services\Server\Setup\Retai
nData
Location:F:\WSUS\MSSQL$WSUS\Data
Version:231
<NewDataSet>
<Table>
<ConfigurationID>1</ConfigurationID>
<LastConfigChange>2009-06-19T14:00:00.3830000+02:00</LastConfigChange>
<DssAnonymousTargeting>false</DssAnonymousTargeting>
<IsRegistrationRequired>true</IsRegistrationRequired>
<MaxDeltaSyncPeriod>30</MaxDeltaSyncPeriod>

<ReportingServiceUrl>https://stats.update.microsoft.com</ReportingServiceUrl
>
<ServerID>your-mother4</ServerID>
<AnonymousCookieExpirationTime>10080</AnonymousCookieExpirationTime>

<SimpleTargetingCookieExpirationTime>60</SimpleTargetingCookieExpirationTime
>

<MaximumServerCookieExpirationTime>10080</MaximumServerCookieExpirationTime>


<DssTargetingCookieExpirationTime>240</DssTargetingCookieExpirationTime>
<EncryptionKey>your-mother5</EncryptionKey>
<ServerTargeting>true</ServerTargeting>
<SyncToMU>false</SyncToMU>
<UpstreamServerName>sus.lrz-muenchen.de</UpstreamServerName>
<ServerPortNumber>80</ServerPortNumber>
<UpstreamServerUseSSL>false</UpstreamServerUseSSL>
<UseProxy>false</UseProxy>
<ProxyName />
<ProxyServerPort>80</ProxyServerPort>
<AnonymousProxyAccess>true</AnonymousProxyAccess>
<ProxyUserName />
<HostOnMu>false</HostOnMu>

<LocalContentCacheLocation>f:\WSUS\WsusContent\</LocalContentCacheLocation>
<ServerSupportsAllLanguages>false</ServerSupportsAllLanguages>
<LogLevel>0</LogLevel>
<LogPath />

<SubscriptionFailureNumberOfRetries>3</SubscriptionFailureNumberOfRetries>

<SubscriptionFailureWaitBetweenRetriesTime>15</SubscriptionFailureWaitBetwee
nRetriesTime>
<DispatchManagerPollingInterval>5</DispatchManagerPollingInterval>

<StateMachineTransitionLoggingEnabled>false</StateMachineTransitionLoggingEn
abled>

<StateMachineTransitionErrorCaptureLength>600</StateMachineTransitionErrorCa
ptureLength>
<MaxSimultaneousFileDownloads>10</MaxSimultaneousFileDownloads>
<MUUrl>https://www.update.microsoft.com/v6</MUUrl>
<EventLogFloodProtectTime>10</EventLogFloodProtectTime>
<HandshakeAnchor>28481,2009-06-19 14:00:00.480</HandshakeAnchor>
<StatsDotNetWebServiceUri>http://localhost</StatsDotNetWebServiceUri>
<QueueFlushTimeInMS>3000</QueueFlushTimeInMS>
<QueueFlushCount>100</QueueFlushCount>
<QueueRejectCount>500</QueueRejectCount>
<SleepTimeAfterErrorInMS>30000</SleepTimeAfterErrorInMS>
<LogDestinations>0</LogDestinations>
<AutoRefreshDeployments>true</AutoRefreshDeployments>
<RedirectorChangeNumber>0</RedirectorChangeNumber>
<ImportLocalPath />
<UseCookieValidation>true</UseCookieValidation>
<AutoPurgeClientEventAgeThreshold>15</AutoPurgeClientEventAgeThreshold>
<AutoPurgeServerEventAgeThreshold>90</AutoPurgeServerEventAgeThreshold>
<AutoPurgeDetectionPeriod>12</AutoPurgeDetectionPeriod>
<DoReportingDataValidation>true</DoReportingDataValidation>
<DoReportingSummarization>true</DoReportingSummarization>

<MaxNumberOfIdsToRequestDataFromUss>100</MaxNumberOfIdsToRequestDataFromUss>

<MaxCoreUpdatesPerRequest>30</MaxCoreUpdatesPerRequest>
<MaxExtendedUpdatesPerRequest>50</MaxExtendedUpdatesPerRequest>
<DownloadRegulationUrl />

<AllowProxyCredentialsOverNonSsl>false</AllowProxyCredentialsOverNonSsl>
<LazySync>true</LazySync>
<DownloadExpressPackages>false</DownloadExpressPackages>
<DoServerSyncCompression>true</DoServerSyncCompression>
<ProxyUserDomain />
<BitsHealthScanningInterval>3600000</BitsHealthScanningInterval>
<BitsDownloadPriorityForeground>false</BitsDownloadPriorityForeground>
<MaxXmlPerRequest>200000</MaxXmlPerRequest>
<MaxXmlPerRequestInServerSync>2000000</MaxXmlPerRequestInServerSync>
<MaxTargetComputers>30000</MaxTargetComputers>
<MaxEventInstances>2000000</MaxEventInstances>
<LogRolloverFileSizeInBytes>0</LogRolloverFileSizeInBytes>
<WUSInstallType>0</WUSInstallType>
<ReplicaMode>false</ReplicaMode>
<AutoDeployMandatory>true</AutoDeployMandatory>
<DeploymentChangeDeferral>30</DeploymentChangeDeferral>
<RevisionDeletionTimeThreshold>30</RevisionDeletionTimeThreshold>
<RevisionDeletionSizeThreshold>1024</RevisionDeletionSizeThreshold>
<CollectClientInventory>false</CollectClientInventory>
<DoDetailedRollup>true</DoDetailedRollup>
<RollupResetGuid>your-mother7</RollupResetGuid>
<UssSupportsAllLanguages>false</UssSupportsAllLanguages>
<GetContentFromMU>false</GetContentFromMU>
<HmDetectIntervalInSeconds>600</HmDetectIntervalInSeconds>
<HmRefreshIntervalInSeconds>21600</HmRefreshIntervalInSeconds>
<HmCoreDiskSpaceGreenMegabytes>500</HmCoreDiskSpaceGreenMegabytes>
<HmCoreDiskSpaceRedMegabytes>200</HmCoreDiskSpaceRedMegabytes>
<HmCoreCatalogSyncIntervalInDays>1</HmCoreCatalogSyncIntervalInDays>

<HmClientsInstallUpdatesGreenPercent>10</HmClientsInstallUpdatesGreenPercent
>

<HmClientsInstallUpdatesRedPercent>25</HmClientsInstallUpdatesRedPercent>
<HmClientsInventoryGreenPercent>2</HmClientsInventoryGreenPercent>
<HmClientsInventoryRedPercent>5</HmClientsInventoryRedPercent>

<HmClientsInventoryScanDiffInHours>30</HmClientsInventoryScanDiffInHours>
<HmClientsSilentGreenPercent>10</HmClientsSilentGreenPercent>
<HmClientsSilentRedPercent>25</HmClientsSilentRedPercent>
<HmClientsSilentDays>30</HmClientsSilentDays>
<DssRollupChunkSize>5000</DssRollupChunkSize>
<MURollupOptin>True</MURollupOptin>

<AutoRefreshDeploymentsDeclineExpired>true</AutoRefreshDeploymentsDeclineExp
ired>
<ServerString>Default</ServerString>
<HmCoreFlags>-1</HmCoreFlags>
<HmClientsFlags>-1</HmClientsFlags>
<HmDatabaseFlags>-1</HmDatabaseFlags>
<HmWebServicesFlags>-1</HmWebServicesFlags>
<ClientReportingLevel>2</ClientReportingLevel>
<LocalPublishingMaxCabSize>384</LocalPublishingMaxCabSize>
<DownloadRegulationWebServiceUrl />
<LoadOdfLocally>false</LoadOdfLocally>
<OdfFilePath />
<HmClientsTooManyGreenPercent>80</HmClientsTooManyGreenPercent>
<HmClientsTooManyRedPercent>90</HmClientsTooManyRedPercent>
<ComputerDeletionTimeThreshold>30</ComputerDeletionTimeThreshold>
<ConfigurationChangeNumber>138237</ConfigurationChangeNumber>
<UseSeparateProxyForSsl>false</UseSeparateProxyForSsl>
<SslProxyName />
<SslProxyServerPort>443</SslProxyServerPort>
</Table>
</NewDataSet>

F:\>

"Pimperator" <> wrote in message
news:%...

> First of all let's define two computers:
> Server1 = the one which runs WSUS3 now and has the problems (It is also
> the machine with the formerly installed SUS1)

> Server2 = the one which ran WSUS2

> As far as I know (it is too long ago) I uninstalled (I dont know how
> successful it was, because some data were left) SUS1 to install WSUS2,
> which failed(I dont know why) on Server1, installed WSUS2 on Server2 and
> after a while (about two years) I replaced WSUS2 on Server2 by WSUS3 on
> Server1.

Excellent. This definitely helps.

Your WSUS2 installation probably failed due to an incomplete uninstallation
of SUS v1. The paper that was written for SUS-to-WSUS migration was missing
a couple of critical bits of information. Many people had issues with this
migration process.

> > In any event, the server debug tool throws an exception...
>
> A sh***y behaiviour in windows not to be able to handle network
> ressources. Thanks for the hint. It now works from a local volume as you
> can see below.

You should never *assume* a product is fully network aware. In fact most
command-line utilities are not written with that consideration. They're
written with the assumption that the utility will be used on the machine
being analyzed. I don't know that the tool does, or does not, work across a
network connection -- but I would say that you should never run a diagnostic
tool across a network connection unless you *must*. For one, it introduces
additional possible points of failure that could impact the results reported
from the tool. Here we see the tool worked perfectly when run from a local
drive.


>> What do you mean by "sync from another sync-Server". What is a
>> "sync-Server". Do you mean that this WSUS3 server is a *downstream*
>> server and is synchronizing from an *upstream* WSUS3 server?

> I hope by pasting my configs below this question has an answer

Well, from the above paragraph I understand that:
[1] Server1 used to have SUS1, you attempted to install WSUS2 on it, but it
failed, and a couple of years later you were able to install WSUS3 on
Server1. I understand that Server1 is currently running Windows Server 2003
Service Pack 2.
Questions:
[a] Between the time you attemped the install of WSUS2 that failed, and the
two years later that you installed WSUS3, did you also reinstall the
operating system?
[b] What operating system was running on the machine when you had SUS1
installed and attempted the upgrade to WSUS2?

[2] Server2 has been running WSUS2 for the past couple of years.
Question:
[a] What operating system is running on Server2 now with WSUS2?

In your original post you stated "I run WSUS3 on W2k3 Server SP2 and sync
from another sync-Server.", which suggests to me that you are trying to
synchronize Server1 (WSUS3) from Server2 (WSUS2)? Can you please clarify
this?

Now that I have all of that core information clarified, we can proceed with
the issue regarding the Error 10042. Could you please post the full text
contents of the most recent logged Error 10042 from your WSUS server?

> Yes, I am sure that there are 43GB free. I have two volumes c: (
> 2.223.255.552 Bytes free) and f: ( 45.155.770.368 Bytes free)

And, is the 2GB of freespace on the C: drive before, or after, you ran the
Disk Cleanup utility?

> Yes, I now ran cleaning for the second time. there are no data in recycle
> bin.

And, how much was in the Recycle Bin before you cleaned it out?

--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

Lawrence Garvin [MVP] schrieb:
> "Pimperator" <> wrote in message
> news:%...
>
>> First of all let's define two computers:
>> Server1 = the one which runs WSUS3 now and has the problems (It is
>> also the machine with the formerly installed SUS1)
>
>> Server2 = the one which ran WSUS2
>
>> As far as I know (it is too long ago) I uninstalled (I dont know how
>> successful it was, because some data were left) SUS1 to install WSUS2,
>> which failed(I dont know why) on Server1, installed WSUS2 on Server2
>> and after a while (about two years) I replaced WSUS2 on Server2 by
>> WSUS3 on Server1.
>
> Excellent. This definitely helps.
>
> Your WSUS2 installation probably failed due to an incomplete
> uninstallation of SUS v1. The paper that was written for SUS-to-WSUS
> migration was missing a couple of critical bits of information. Many
> people had issues with this migration process.
yes, while it was possible to use compressed folders for database and
update-files in SUS1, it was not in WSUS3 (and maybe WSUS2), that's
maybe installation failed.
>
>> > In any event, the server debug tool throws an exception...
>>
>> A sh***y behaiviour in windows not to be able to handle network
>> ressources. Thanks for the hint. It now works from a local volume as
>> you can see below.
>
> You should never *assume* a product is fully network aware. In fact most
> command-line utilities are not written with that consideration. They're
> written with the assumption that the utility will be used on the machine
> being analyzed. I don't know that the tool does, or does not, work
> across a network connection -- but I would say that you should never run
> a diagnostic tool across a network connection unless you *must*. For
> one, it introduces additional possible points of failure that could
> impact the results reported from the tool. Here we see the tool worked
> perfectly when run from a local drive.

Yes, it goes now off-topic but sometimes I miss something like scp and
ssh in windows. Even more when these tools do not work through network
or network-implementation is buggy. Nevertheless due to your tipp I made
that program running locally and - what is more important- successfully.
>
>
>>> What do you mean by "sync from another sync-Server". What is a
>>> "sync-Server". Do you mean that this WSUS3 server is a *downstream*
>>> server and is synchronizing from an *upstream* WSUS3 server?
>
>> I hope by pasting my configs below this question has an answer
>
> Well, from the above paragraph I understand that:
> [1] Server1 used to have SUS1, you attempted to install WSUS2 on it, but
> it failed,
true
and a couple of years later you were able to install WSUS3 on
> Server1. I understand that Server1 is currently running Windows Server
> 2003 Service Pack 2.
true
> Questions:
> [a] Between the time you attemped the install of WSUS2 that failed, and
> the two years later that you installed WSUS3, did you also reinstall the
> operating system?
it is the same system. I havent done any reinstallation. The only thing
that changed was installing SP2.
This means. Years ago that computer ran without any servicepack and
before we installed WSUS3 we installed SP2.
> [b] What operating system was running on the machine when you had SUS1
> installed and attempted the upgrade to WSUS2?
Win2003 Server without SP
>
> [2] Server2 has been running WSUS2 for the past couple of years.
> Question:
> [a] What operating system is running on Server2 now with WSUS2?
Server2 was a virtual machine, that is now turned off. It ran Win2003
Server. I think without SP.
>
> In your original post you stated "I run WSUS3 on W2k3 Server SP2 and
> sync from another sync-Server.", which suggests to me that you are
> trying to synchronize Server1 (WSUS3) from Server2 (WSUS2)? Can you
> please clarify this?
Yes, I describe you our setup:
We are inbetween a semi-public scientific network (public because about
60000 students, scientists and employees can access this network), with
I think about 30000 users. So it is a network of two universities. The
main network administration is running (to avoid traffic) a wsus-Server
(let's call this server Server3) which is connecting daily to MS
Windowsupdate-Server. We connect to Server3 daily and fetch updates. The
main administration has no access on our servers. they only provide
network access and some other services like a WSUS mirror.
I dont know which version of WSUS they run.
>
> Now that I have all of that core information clarified, we can proceed
> with the issue regarding the Error 10042. Could you please post the full
> text contents of the most recent logged Error 10042 from your WSUS server?
Yes, I had a look on our logs. this one is the latest:
Ereignistyp: Fehler
Ereignisquelle: Windows Server Update Services
Ereigniskategorie: Core
Ereigniskennung: 10042
Datum: 21.06.2009
Zeit: 09:41:57
Benutzer: Nicht zutreffend
Computer: Server1
Beschreibung:
Auf dem Inhaltslaufwerk stehen weniger als 200 MB freier Speicherplatz
zur Verfügung. Geben Sie möglichst bald mehr Speicherplatz frei.

Weitere Informationen über die Hilfe- und Supportdienste erhalten Sie
unter http://go.microsoft.com/fwlink/events.asp.

>
>> Yes, I am sure that there are 43GB free. I have two volumes c: (
>> 2.223.255.552 Bytes free) and f: ( 45.155.770.368 Bytes free)
it is now. I'm runnign cleanup-utility now again while I'm writing this
message. et voila it is now 2.274.611.200 bytes. so nearly nothing has
changed on drive c:
>
> And, is the 2GB of freespace on the C: drive before, or after, you ran
> the Disk Cleanup utility?
both, I have now some megabytes free.
>
>> Yes, I now ran cleaning for the second time. there are no data in
>> recycle bin.
>
> And, how much was in the Recycle Bin before you cleaned it out?
>
nothing, it was empty


The bad thing is: something seems to avoid wsus from seeing those 43GB
of free space. might it be any problems with data system? I am using
NTFS5 (versin 4 was used with WinNT4)

"Pimperator" <> wrote in message
news:...

> Lawrence Garvin [MVP] schrieb:

>> "Pimperator" <> wrote in message
>> news:%...

>> Your WSUS2 installation probably failed due to an incomplete
>> uninstallation of SUS v1. The paper that was written for SUS-to-WSUS
>> migration was missing a couple of critical bits of information. Many
>> people had issues with this migration process.

> yes, while it was possible to use compressed folders for database and
> update-files in SUS1, it was not in WSUS3 (and maybe WSUS2), that's maybe
> installation failed.

The issues about compressed folders is not one of the issues I'm thinking of
above, and, to be honest, compressed folders is not a WSUS issue, it's a
=SQL Server= issue, and NO version of SUS or WSUS has been able to support
compressed folders on the folder(s) that contain the database.

Further, there's no value in compressing the content store, since most of
that content is already shipped in compressed CAB files.

>> In your original post you stated "I run WSUS3 on W2k3 Server SP2 and sync
>> from another sync-Server.", which suggests to me that you are trying to
>> synchronize Server1 (WSUS3) from Server2 (WSUS2)? Can you please clarify
>> this?

> I dont know which version of WSUS they run.

This is a critical issue, as WSUS3 servers *CANNOT* synchronize from WSUS2
servers, so you must know what version the upstream server(s) are running.

> Yes, I had a look on our logs. this one is the latest:

An English translation would be most helpful in understanding the *exact*
message, but it's clear that the WSUS service thinks there is only 200MB of
free space on *something*.

> Ereignistyp: Fehler
> Ereignisquelle: Windows Server Update Services
> Ereigniskategorie: Core
> Ereigniskennung: 10042
> Datum: 21.06.2009
> Zeit: 09:41:57
> Benutzer: Nicht zutreffend
> Computer: Server1
> Beschreibung:
> Auf dem Inhaltslaufwerk stehen weniger als 200 MB freier Speicherplatz zur
> Verfügung. Geben Sie möglichst bald mehr Speicherplatz frei.


> The bad thing is: something seems to avoid wsus from seeing those 43GB of
> free space.

You assume, and I cannot confirm, that the (German language) message is
about your content store, and not your SYSVOL. Either way, yes, it's
definitely a problem that WSUS thinks there is only 200MB free.

> might it be any problems with data system?

Could be.

> I am using NTFS5 (versin 4 was used with WinNT4)

It's not likely the version of NTFS that is at issue, here, but it could be
a corrupted filesystem.

I would suggest:
[a] Make a full system file-level backup of the entire machine.
[b] Reboot.
[c] Run CHKDSK /F on the F: drive.
[d] Reboot.
[e] Run CHKDSK /F on the C: drive.
[f] Reboot.

And see if that doesn't help clear up the problem.


--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

Hi Lawrence,
I have solved the problem.

After having googled a while for the errormessage I found this:
http://forums.techarena.in/server-up...ice/852032.htm
It is the same errorcode and the same message (but in english).

I also verified errormessages as described here with "wsusutil checkhealth":
http://www.microsoft.com/technet/sup...ices&LCID=1033


The main thing was, that the user NT-AUTHORITY\NETWORKSERVICE had a
quota on that drive. After removing the quota (ok, I didnt really remove
the quota but I set the quota to <unlimited>) I ran "wsusutil
checkhealth" again and it worked perfectly.

So now this problem is SOLVED.

Thanks a lot for your help and patience!

Erik


Lawrence Garvin [MVP] schrieb:
> "Pimperator" <> wrote in message
> news:...
>
>> Lawrence Garvin [MVP] schrieb:
>
>>> "Pimperator" <> wrote in message
>>> news:%...
>
>>> Your WSUS2 installation probably failed due to an incomplete
>>> uninstallation of SUS v1. The paper that was written for SUS-to-WSUS
>>> migration was missing a couple of critical bits of information. Many
>>> people had issues with this migration process.
>
>> yes, while it was possible to use compressed folders for database and
>> update-files in SUS1, it was not in WSUS3 (and maybe WSUS2), that's
>> maybe installation failed.
>
> The issues about compressed folders is not one of the issues I'm
> thinking of above, and, to be honest, compressed folders is not a WSUS
> issue, it's a =SQL Server= issue, and NO version of SUS or WSUS has been
> able to support compressed folders on the folder(s) that contain the
> database.
>
> Further, there's no value in compressing the content store, since most
> of that content is already shipped in compressed CAB files.
>
>>> In your original post you stated "I run WSUS3 on W2k3 Server SP2 and
>>> sync from another sync-Server.", which suggests to me that you are
>>> trying to synchronize Server1 (WSUS3) from Server2 (WSUS2)? Can you
>>> please clarify this?
>
>> I dont know which version of WSUS they run.
>
> This is a critical issue, as WSUS3 servers *CANNOT* synchronize from
> WSUS2 servers, so you must know what version the upstream server(s) are
> running.
>
>> Yes, I had a look on our logs. this one is the latest:
>
> An English translation would be most helpful in understanding the
> *exact* message, but it's clear that the WSUS service thinks there is
> only 200MB of free space on *something*.
>
>> Ereignistyp: Fehler
>> Ereignisquelle: Windows Server Update Services
>> Ereigniskategorie: Core
>> Ereigniskennung: 10042
>> Datum: 21.06.2009
>> Zeit: 09:41:57
>> Benutzer: Nicht zutreffend
>> Computer: Server1
>> Beschreibung:
>> Auf dem Inhaltslaufwerk stehen weniger als 200 MB freier Speicherplatz
>> zur Verfügung. Geben Sie möglichst bald mehr Speicherplatz frei.
>
>
>> The bad thing is: something seems to avoid wsus from seeing those 43GB
>> of free space.
>
> You assume, and I cannot confirm, that the (German language) message is
> about your content store, and not your SYSVOL. Either way, yes, it's
> definitely a problem that WSUS thinks there is only 200MB free.
>
>> might it be any problems with data system?
>
> Could be.
>
>> I am using NTFS5 (versin 4 was used with WinNT4)
>
> It's not likely the version of NTFS that is at issue, here, but it could
> be a corrupted filesystem.
>
> I would suggest:
> [a] Make a full system file-level backup of the entire machine.
> [b] Reboot.
> [c] Run CHKDSK /F on the F: drive.
> [d] Reboot.
> [e] Run CHKDSK /F on the C: drive.
> [f] Reboot.
>
> And see if that doesn't help clear up the problem.
>
>

"Pimperator" <> wrote in message
news:%23ZuHG30%...
> Hi Lawrence,
> I have solved the problem.
>
> After having googled a while for the errormessage I found this:
> http://forums.techarena.in/server-up...ice/852032.htm
> It is the same errorcode and the same message (but in english).
>
> I also verified errormessages as described here with "wsusutil
> checkhealth":
> http://www.microsoft.com/technet/sup...ices&LCID=1033
>
>
> The main thing was, that the user NT-AUTHORITY\NETWORKSERVICE had a quota
> on that drive.

Ahhh.yess... QUOTAS!... Gosh, it's been so so long since I encounted an
issue with Quotas being configured, that I totally forgot it was a known
cause for 'not enough space' scenarios.

I'm glad you found the fix, and thanks for reminding me it should still be
on the list!


--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin