Re: Error message in SecuritySyncXML.log

From: Adam Welker [MSFT] (adamwel_at_online.microsoft.com)
Date: 12/14/04 

Date: Tue, 14 Dec 2004 09:37:06 -0800

This is new functionality in SMS 2003 SP1 which is why you probably don't
notice anything working any differently than before.

The design of this feature is to pre-populate the database with new updates
which allows faster patch approvals since you don't have to scan and wait
for inventory to return before you can approve updates. You still need to
scan client systems with the new catalog before you can apply the new
updates however.

The error is probably occuring because the user context under which sync is
running does not have rights to the new Software_Updates class. If you
grant the user the right to create and modify on the Software_Updates class
it should work. 

-- 
Adam Welker
This posting is provided "AS IS" with no warranties, and confers no rights.
"Luke Packard [MSFT]" <lukep@online.microsoft.com> wrote in message 
news:uYNNQ6X4EHA.2624@TK2MSFTNGP11.phx.gbl...
> Cross posting to software_updates newsgroup
>
> -- 
> Luke Packard [MSFT]
>
> SMS 2003 Technical FAQ:
> http://www.microsoft.com/technet/prodtechnol/sms/sms2003/techfaq/default.mspx
>
> This posting is provided "AS IS" with no warranties, and confers no 
> rights.
>
> "Jaap Schram" <Jaap Schram@discussions.microsoft.com> wrote in message 
> news:DF6950AC-F3AF-40A8-AE8B-9F2037563DB6@microsoft.com...
>> Hello,
>>
>>
>> We are having the following problem. In the SecuritySyncXML.LOG file the
>> following error message is displayed after new updates are being 
>> processed:
>>
>> UpdateCatalog: Processing security catalog D:\PROGRAM
>> FILES\SECURITYPATCH\PKGSOURCE\1033\mssecure.cab ...
>> UpdateCatalog: 404 bulletins processed, 2 bulletins matched age 
>> requirements
>> UpdateCatalog: 5 patches processed, 1 patches matched product 
>> requirements
>> UpdateCatalog: 1 writes requested, 0 records inserted, 0 records updated
>> UpdateCatalog: error 0x80041001, Generic failure, SQL command failed: ,
>> returned from SMS_UpdatePrograms::PutInstance(UpdateID=729)
>>
>> I cannot find a solution to this problem. The scanner tool runs fine we
>> believe and systems are being updated so why this message?
>>
>> Regards,
>>
>> Jaap
>>
>>
>
>

Relevant Pages

  • Re: Failed to load AuthorizationList?
    ... This posting is provided "AS IS" with no warranties, and confers no rights. ... > Failed to get updates list. ... hRes = ox80004005 ...
    (microsoft.public.sms.admin)
  • Re: SMS SUS and Update Rollup 1 for XP (826939)
    ... An SRP like this is handled outside of the SMS SUSFP. ... SUSFP by using the DSUW (Distribute Software Updates Wizard). ...
    (NT-Bugtraq)
  • Re: Office 2007 Deployment
    ... Other than the SMS restarts it's identical I ... and also in the Updates directory. ... It could be it has problems uninstalling Office 2003.. ... then rerun advertisement for office 2007 install does ...
    (microsoft.public.sms.admin)
  • RE: SMS Admin Issues
    ... SMS do NOT use GPO's to deploy the updates to the client computers. ... By default it will check update for every day but it will only install the ... "Active Directory System Group Discovery" this discovery can detect the OU ...
    (microsoft.public.sms.admin)
  • Re: results.xml file in every computer
    ... results.xml file which will list all the updates missing or installed on ... either SMS office scan tool or the SMS security scan tool, ... updates in the software updates nodes in the SMS admin UI and then you can ... This posting is provided "AS IS" with no warranties, ...
    (microsoft.public.sms.swdist)