SMS - Microsoft Updates Tool Sync Issue

I'm getting errors in this advertisement. i also noticed it's not updating.

Error:
The program for advertisement "PSI20020" failed ("PSI0001D" - "Microsoft Updates Tool Sync"). The failure description was "11459".
 User context: NT AUTHORITY\SYSTEM

Possible cause: The program generated an installation status Management Information Format (MIF) file with a status value of Failed.
Solution: For more information about the failure, refer to the documentation for the program you are distributing.



When I run this command in the command line, it returns with no errors and I noticed it updated.

syncxml.exe /s /unattend /site SMSSERVER /code PSI /package PSI0001D /target \\SMSSERVER\PackageSrc

This is the command in the Microsoft Updates Tool Sync Package.


Devon21Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

stirrinCommented:
Can you check on the wsussyncxml.log on the machine your are trying to sync and see if any errors are there?

Also, check on the version of ITMU you are using. Is it ITMUv3? I have seen problems with previous versions of ITMU unable to process the wsussn2.cab.

One more area to check might be the %systemroot%\windows\WindowsUpdate.log on the server.
0
schristeCommented:
This error may be with the .exe you are pushing from the SMS server. Is this an attended or unattended install?

If attended - Make sure the program is set to run in Normal mode

If unattended - Make sure the program is set to run in Hidden mode

Both options and more are available in the programs properties, then clicking the down arrow next to the box named Run:

0
Devon21Author Commented:
Schriste,

This is the Windows Update package (ITMU) and the program is set to run in hidden mode.

Stirrin,

This is on the SMS server and I could not find the wsussyncxml.log. How do you find out what version of ITMU you are using?

The WindowsUpdate.log reported:

2008-02-14      05:34:14:876       864      13e4      Misc       Microsoft signed: Yes
2008-02-14      05:34:17:814       864      13e4      Misc      WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80190191
2008-02-14      05:34:17:814       864      13e4      Misc      WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80190191
2008-02-14      05:34:18:345       864      13e4      Misc      WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80190191
2008-02-14      05:34:18:345       864      13e4      Misc      WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80190191
2008-02-14      05:34:18:907       864      13e4      Misc      WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80190191
2008-02-14      05:34:18:907       864      13e4      Misc      WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80190191
2008-02-14      05:34:19:485       864      13e4      Misc      WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80190191
2008-02-14      05:34:19:485       864      13e4      Misc      WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80190191
2008-02-14      05:34:19:485       864      13e4      Misc      WARNING: DownloadFileInternal failed for http://download.windowsupdate.com/v7/windowsupdate/redir/wuredir.cab: error 0x80190191
2008-02-14      05:34:19:485       864      13e4      Misc      Validating signature for C:\WINDOWS\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\wuredir.cab:
2008-02-14      05:34:19:501       864      13e4      Misc       Microsoft signed: Yes
2008-02-14      05:34:22:392       864      13e4      Misc      WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80190191
2008-02-14      05:34:22:392       864      13e4      Misc      WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80190191
2008-02-14      05:34:23:157       864      13e4      Misc      WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80190191
2008-02-14      05:34:23:157       864      13e4      Misc      WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80190191
2008-02-14      05:34:23:767       864      13e4      Misc      WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80190191
2008-02-14      05:34:23:767       864      13e4      Misc      WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80190191
2008-02-14      05:34:24:251       864      13e4      Misc      WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80190191
2008-02-14      05:34:24:251       864      13e4      Misc      WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80190191
2008-02-14      05:34:24:251       864      13e4      Misc      WARNING: DownloadFileInternal failed for http://download.microsoft.com/v7/windowsupdate/redir/wuredir.cab: error 0x80190191
2008-02-14      05:34:24:251       864      13e4      Misc      Validating signature for C:\WINDOWS\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\wuredir.cab:
2008-02-14      05:34:24:251       864      13e4      Misc       Microsoft signed: Yes
2008-02-14      05:34:26:892       864      13e4      Misc      WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80190191
2008-02-14      05:34:26:892       864      13e4      Misc      WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80190191
2008-02-14      05:34:27:298       864      13e4      Misc      WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80190191
2008-02-14      05:34:27:298       864      13e4      Misc      WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80190191
2008-02-14      05:34:27:985       864      13e4      Misc      WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80190191
2008-02-14      05:34:27:985       864      13e4      Misc      WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80190191
2008-02-14      05:34:28:517       864      13e4      Misc      WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80190191
2008-02-14      05:34:28:517       864      13e4      Misc      WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80190191
2008-02-14      05:34:28:517       864      13e4      Misc      WARNING: DownloadFileInternal failed for http://www.update.microsoft.com/v7/windowsupdate/redir/wuredir.cab: error 0x80190191
2008-02-14      05:34:28:517       864      13e4      Setup      FATAL: IsUpdateRequired failed with error 0x80244017
2008-02-14      05:34:28:517       864      13e4      Setup      WARNING: SelfUpdate: Default Service: IsUpdateRequired failed: 0x80244017
2008-02-14      05:34:28:517       864      13e4      Setup      WARNING: SelfUpdate: Default Service: IsUpdateRequired failed, error = 0x80244017
2008-02-14      05:34:28:517       864      13e4      Agent        * WARNING: Skipping scan, self-update check returned 0x80244017
2008-02-14      05:34:28:907       864      13e4      Agent        * WARNING: Exit code = 0x80244017
2008-02-14      05:34:28:907       864      13e4      Agent      *********
2008-02-14      05:34:28:907       864      13e4      Agent      **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
2008-02-14      05:34:28:907       864      13e4      Agent      *************
2008-02-14      05:34:28:907       864      13e4      Agent      WARNING: WU client failed Searching for update with error 0x80244017
2008-02-14      05:34:28:907       864      c1c      AU      >>##  RESUMED  ## AU: Search for updates [CallId = {391CDDE1-DFEF-430A-BFA2-F1DE673C8C83}]
2008-02-14      05:34:28:907       864      c1c      AU        # WARNING: Search callback failed, result = 0x80244017
2008-02-14      05:34:28:907       864      c1c      AU        # WARNING: Failed to find updates with error code 80244017
2008-02-14      05:34:28:907       864      c1c      AU      #########
2008-02-14      05:34:28:907       864      c1c      AU      ##  END  ##  AU: Search for updates [CallId = {391CDDE1-DFEF-430A-BFA2-F1DE673C8C83}]
2008-02-14      05:34:28:907       864      c1c      AU      #############
2008-02-14      05:34:28:907       864      c1c      AU      AU setting next detection timeout to 2008-02-14 18:34:28
2008-02-14      05:34:33:517       864      13e4      Report      REPORT EVENT: {3BC4F82C-CC0C-4EEB-898E-874A12F734DD}      2008-02-14 05:34:28:517-0800      1      148      101      {D67661EB-2423-451D-BF5D-13199E37DF28}      0      80244017      SelfUpdate      Failure      Software Synchronization      Windows Update Client failed to detect with error 0x80244017.
0
Cloud Class® Course: CompTIA Healthcare IT Tech

This course will help prep you to earn the CompTIA Healthcare IT Technician certification showing that you have the knowledge and skills needed to succeed in installing, managing, and troubleshooting IT systems in medical and clinical settings.

schristeCommented:
Sounds like a package issue and not a windows update one.

You may need to add security rights to the packages folder. I would start there and make sure the accounts that need it have the rights.

Have you been deploying packages in the past without any issue?
0
Devon21Author Commented:
Any other ideas...

i know it's not the package, it's a built-in package from Microsoft. All I'm trying to do, is to make sure SMS does the Microsoft Updates on a regular basis. For some reason it keeps failing, but it will update if I execute manually.
0
schristeCommented:
Ok, what about your advertisement. Do you have that all set up? I don't use SMS for normal windows updates, I use a seperate WSUS server but I assume the security and MS updates through SMS make you create a package, using a wizard and that package will need an advertisement.

Let me know how you are setting up your packages and your advertisements and we can look there.

Do you have any errors in your Componet Status?
0
Devon21Author Commented:
Schriste,

Using a WSUS instead of SMS seems to be a common event. Why are you using WSUS instead of SMS?

Back to the question...

i have a package and a advertisement for Windows Updates (SMS generated), this is what's confusing me. I might just have to re-create them. Now if i re-create them, will it mess up anything else?
0
schristeCommented:
I prefer to use WSUS for site patching and reporting. It's a preference thing, nothing more. Other sites prefer to use and do use SMS for patching. I like to keep them seperated, that's all.

It should not hurt anything by deleting and starting over. I assume you have been able to push patches before without issue? Did you have any errors in the Componets Status area? Any other errors or warnings showing that I'm not aware of?
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Devon21Author Commented:
I'm just going to create a new one, I think something is wrong with the software. I'm noticing other issues.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.