Error 0x80070003 in Software Update Services (SUS) Synchronization Log

You see the following error in SUS synchronization log;
--------------------------------------------------------------------------------
Manual Sync Started- Tuesday, April 19, 2005 10:53:55 AM Failed
Updates Added:
�None
Updates Removed:
�None
Reissued Update(s):
�None
Errors:
Error writing to the content folder. (Error 0x80070003: The system cannot find the path specified.)
Sync Finished-Tuesday, April 19, 2005 10:53:55 AM

This is due to a missing entry in 'C:\inetpub\wwwroot\autoupdate�\dictionaries\settings.txt' for CabPoolPath, which should be followed by location to the contents cab folder.

The CabPoolPath section should contain the path to the downloaded patches (i.e. <Installation Drive>:\SUS\content\cabs)
�
For Instance;
CabPoolPath, C:\SUS\content\cab�s
CabPoolURL, http://Your-SUSSERVER-Name/con�tent
�
Make sure you save the changes and try to synchronize again and to see if synchronization works.

�

Issue with Settings.txt not saving the CabPoolPath location in Software Update Services, SUS
http://support.microsoft.com/kb/555338

Microsoft corporation and/or its respective suppliers make no representations about the suitability, reliability, or accuracy of the information and related graphics contained herein. All such information and related graphics are provided "as is" without warranty of any kind. Microsoft and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information and related graphics, including all implied warranties and conditions of merchantability, fitness for a particular purpose, workmanlike effort, title and non-infringement. You specifically agree that in no event shall Microsoft and/or its suppliers be liable for any direct, indirect, punitive, incidental, special, consequential damages or any damages whatsoever including, without limitation, damages for loss of use, data or profits, arising out of or in any way connected with the use of or inability to use the information and related graphics contained herein, whether based on contract, tort, negligence, strict liability or otherwise, even if Microsoft or any of its suppliers has been advised of the possibility of damages.