Jump to content


vikrammidha

Established Members
  • Content Count

    8
  • Joined

  • Last visited

Community Reputation

0 Neutral

About vikrammidha

  • Rank
    Newbie

Recent Profile Visitors

607 profile views
  1. I am getting a message as "Not refreshing update presence state as error CI Info status received" when installing patches using Software Center. below is a snippet from Updatesdeployment.log ................................................................................​................................................................................​................................................................................​................................................. Raising client SDK event for class CCM_SoftwareUpdate, instance CCM_SoftwareUpdate.UpdateID="Site_5C2C7B9A-CCFC-436C-8EAB-8BB1CC0D9CA5/SUM_79270a15-031c-4c07-81a7-b1dcc0eea6d9", actionType 1l, value NULL, user NULL, session 4294967295l, level 0l, verbosity 30l UpdatesDeploymentAgent Not refreshing update presence state as error CI Info status received UpdatesDeploymentAgent Raising client SDK event for class CCM_SoftwareUpdate, instance CCM_SoftwareUpdate.UpdateID="Site_5C2C7B9A-CCFC-436C-8EAB-8BB1CC0D9CA5/SUM_79270a15-031c-4c07-81a7-b1dcc0eea6d9", actionType 11l, value NULL, user NULL, session 4294967295l, level 0l, verbosity 30l UpdatesDeploymentAgent CUpdatesJob({A811BD6B-4CFE-4398-BD2A-8F430649F9EF}): Delete job from WMI UpdatesDeploymentAgent IsRebootSetForScheduledUpdate - Scheduled update Site_5C2C7B9A-CCFC-436C-8EAB-8BB1CC0D9CA5/SUM_040f13b3-dce2-44cb-9673-5f2b00bab0f5 - Job options = 0 RebootImmediately = False UpdatesDeploymentAgent IsRebootSetForScheduledUpdate - Scheduled update Site_5C2C7B9A-CCFC-436C-8EAB-8BB1CC0D9CA5/SUM_e24d2431-1b85-495e-8b75-c339cdfc919b - Job options = 0 RebootImmediately = False UpdatesDeploymentAgent IsRebootSetForScheduledUpdate - Scheduled update Site_5C2C7B9A-CCFC-436C-8EAB-8BB1CC0D9CA5/SUM_6f0b3990-56cc-4bc0-87bb-c54d7fafaac8 - Job options = 0 RebootImmediately = False UpdatesDeploymentAgent IsRebootSetForScheduledUpdate - Scheduled update Site_5C2C7B9A-CCFC-436C-8EAB-8BB1CC0D9CA5/SUM_bbb2c1d5-4809-48ad-b569-bd9ea6617fa4 - Job options = 0 RebootImmediately = False UpdatesDeploymentAgent No installations in pipeline, notify reboot. UpdatesDeploymentAgent 9/15/2014 3:42:48 PM 6248 (0x1868) Notify reboot UpdatesDeploymentAgent EnumerateUpdates for action (UpdateActionInstall) - Total actionable updates = 79 UpdatesDeploymentAgent ................................................................................​................................................................................​................................................................................​................................................. Below are the error messages in WindowsUpdate.log ...............................................................................​................................................................................​................................................................................​................................................. 2014-09-17 12:32:45:154 6372 ce0 Handler CBS package identity: Package_for_KB2966825~31bf3856ad364e35~amd64~~6.2.1.4 2014-09-17 12:32:45:163 6372 ce0 Handler Installing self-contained with source=C:\Windows\SoftwareDistribution\Download\be5ae942269a9467c89b7ef1fa4ed938\windows8-rt-kb2966825-x64.cab, workingdir=C: \Windows\SoftwareDistribution\Download\be5ae942269a9467c89b7ef1fa4ed938\inst 2014-09-17 12:42:44:413 6372 20d0 Handler CUHCbsHandler::Cancel called with fReleaseThreadNow=0 2014-09-17 12:43:20:571 6372 17b4 Handler FATAL: CBS called Error with 0x800f0821, 2014-09-17 12:43:36:642 6372 ce0 Handler FATAL: Completed install of CBS update with type=2, requiresReboot=0, installerError=0, hr=0x80242008 2014-09-17 12:43:37:686 6372 ce0 Handler ::::::::: 2014-09-17 12:43:37:686 6372 ce0 Handler :: END :: Handler: CBS Install 2014-09-17 12:43:37:686 6372 ce0 Handler ::::::::::::: 2014-09-17 12:43:37:746 872 df0 Agent * WARNING: Exit code = 0x8024000B 2014-09-17 12:43:37:747 872 df0 Agent ********* 2014-09-17 12:43:37:747 872 df0 Agent ** END ** Agent: Installing updates [CallerId = CcmExec] 2014-09-17 12:43:37:747 872 df0 Agent ************* 2014-09-17 12:43:37:747 872 df0 Agent WARNING: WU client failed installing updates with error 0x8024000b 2014-09-17 12:43:37:747 3164 dd4 COMAPI >>-- RESUMED -- COMAPI: Install [ClientId = CcmExec] 2014-09-17 12:43:37:747 3164 dd4 COMAPI - Install call aborted 2014-09-17 12:43:37:748 3164 dd4 COMAPI - Reboot required = No 2014-09-17 12:43:37:748 3164 dd4 COMAPI - WARNING: Exit code = 0x80240FFF; Call error code = 0x8024000B 2014-09-17 12:43:37:748 3164 dd4 COMAPI --------- 2014-09-17 12:43:37:748 3164 dd4 COMAPI -- END -- COMAPI: Install [ClientId = CcmExec] ................................................................................​................................................................................​................................................................................​................................................. When I try to install the patch manually directly on the machine, it works but not via SCCM, the issue is on Windows 2012 Server Standard. There are 3+ servers they fail 2-3 patches but install rest of them. Few patches are common but few are not.
  2. Hey Garth, Yes, saw it today, i could relate the error message to the link you provided. Followed the methods described in the link but that didnt help. Moreover, this is happening with quite a few number of machines, This is not feasible to be done on multiple machines. What i am not able to understand is how come it work on one of the machines.
  3. I tried again and surprisingly this time, it worked on one of the windows 7 machine and the patch was removed. However it did fail on 2 other machines (windows 7 and 8) with the below different errors : ............................................................................................................................................ Environment scope "Global\{51A016B6-F0DE-4752-B97C-54E6F386A912}" has already been created TSAgent 7/23/2014 5:46:55 PM 4884 (0x1314) Error creating TS environment. Code 0x800700b7 TSAgent 7/23/2014 5:46:55 PM 4884 (0x1314) Task sequence launcher advertisement failed!. Code 0x800700b7 TSAgent 7/23/2014 5:46:55 PM 4884 (0x1314) Failed to delete registry value HKLM\Software\Microsoft\SMS\Task Sequence\Package. Error code 0x80070002 TSAgent 7/23/2014 5:46:55 PM 4884 (0x1314) CTSAgent::Execute - Failed to launch Task Sequence manager. TSAgent 7/23/2014 5:46:55 PM 4884 (0x1314) ............................................................................................................................................ Please assist !!!
  4. I tried deploying this task sequence on a physical machine and it came up with the below error in TSAGENT.log : ------------------------------------------------------------------------------------------------------------------------------------ Error initializing policy environment variables. Code 0x8007000e TSAgent 7/18/2014 1:47:43 PM 6132 (0x17F4) Error initializing TS environment. Code 0x8007000e TSAgent 7/18/2014 1:47:44 PM 6132 (0x17F4) Task sequence launcher advertisement failed!. Code 0x8007000e TSAgent 7/18/2014 1:47:44 PM 6132 (0x17F4) CTSAgent::Execute - Failed to launch Task Sequence manager. TSAgent 7/18/2014 1:47:44 PM 6132 (0x17F4) ------------------------------------------------------------------------------------------------------------------------------------ Code 0x8007000e says "Not enough storage is available to complete this operation". But i believe there is no space requirement to delete an already installed patch.
  5. I was checking for the method to uninstall any software update patch in case need be. I came across one of the switch to use with the task sequence as below to uninstall any specific patch from systems : C:\Windows\System32\wusa.exe /uninstall /kb:2781197 /quiet /norestart where KB number is any patch which we would like to remove. The task sequence gave up the below error in TSAGENT.log but execmgr.log is clean without any errors : ------------------------------------------------------------------------------------------------------------------------ Task sequence launcher advertisement failed!. Code 0x80070480 TSAgent 6/26/2014 3:08:12 PM 2448 (0x0990) Failed to delete registry value HKLM\Software\Microsoft\SMS\Task Sequence\Active Request Handle. Error code 0x80070002 TSAgent 6/26/2014 3:08:12 PM 2448 (0x0990) Failed to delete registry value HKLM\Software\Microsoft\SMS\Task Sequence\Package. Error code 0x80070002 TSAgent 6/26/2014 3:08:12 PM 2448 (0x0990) CTSAgent::Execute - Failed to launch Task Sequence manager. TSAgent 6/26/2014 3:08:12 PM 2448 (0x0990) ------------------------------------------------------------------------------------------------------------------------ I tried creating a package just to check if that works, however several users have reported that task sequence is the only method that works but as that was not working in my case, so tried the package with a batch file using the same script as mentioned above but that came up with the below error : ------------------------------------------------------------------------------------------------------------------------ EnterRsRuningState failed to run script PatchRemoval.bat 0x87d01106 ------------------------------------------------------------------------------------------------------------------------ If i try to run the same script using the CMD prompt manually on client machine, it successfully removes the patch silently. Not sure why this is not working as a task sequence.
  6. Hi, I am facing winpe error in OSD. It gets to the point where user presses the F12 key and it starts loading the file, finally it goes to the screen showing WINPE is initializing and windows is starting but goes blank after that. I thought this would be a driver issue and imported some network drivers but when trying to create a driver package, it says "some drivers cannot be imported". Please assist.
×
×
  • Create New...