locked
Imaged PCs cant update - useless error message RRS feed

  • Question

  • I've been imaging pcs at a rate of about 6 a week for the last few months.  I made a single change to the deployment.  I changed the version of flash from 15 to 18.  The three computers i'm working with are the first three imaged with flash 18.  I do not know if it's relevant, but it's the only change I made, so anything's possible.

    Three newly imaged PCs are unable to check for updates.  I searched and found this article: https://support.microsoft.com/en-us/kb/954960 however these are windows 7 64bit pc's (with 32bit office and in at least one case, a 64bit Microsoft office product, however they are all office 2013) however ospp.vbs tells me that all Microsoft products are 2013.  In addition, the quoted text from the softwaredistribution.log is very different from mine.

    These three pcs are all throwing the same error when I try to check for updates.  Below is a sample from the windowsupdate.log of one of the clients with the problem. I have compared to a healthy pc's windowsupdate.log and this is where the problem starts:

    + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = <server url>/ClientWebService/client.asmx
    WARNING: Cached cookie has expired or new PID is available
    Initializing simple targeting cookie, clientId = 6bf30021-9d59-4e53-84a3-370627da9e02, target group = , DNS name = <computer name>
    Server URL = 2015-07-16 15:41:13.187 UTC Warning w3wp.278 SoapUtilities.CreateException ThrowException: actor = http://<wsus server>:8530/ClientWebService/client.asmx, ID=80f3d0e7-01d7-461e-8d9c-637c004e0ad8, ErrorCode=InternalServerError, Message=, Client=6bf30021-9d59-4e53-84a3-370627da9e02Server URL = 2015-07-16 15:41:13.187 UTC Warning w3wp.278 SoapUtilities.CreateException ThrowException: actor = http://<wsus server>:8530/ClientWebService/client.asmx, ID=80f3d0e7-01d7-461e-8d9c-637c004e0ad8, ErrorCode=InternalServerError, Message=, Client=6bf30021-9d59-4e53-84a3-370627da9e02

    however at the very same time, give or take 5 milliseconds I see this:

    2015-07-16 15:41:13.183 UTC	Error	w3wp.278	ClientImplementation.SyncUpdates	System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
       at System.String.CompareOrdinalHelper(String strA, String strB)
       at System.Web.Caching.CacheKeyComparer.Compare(Object x, Object y)
       at System.Web.Caching.CacheKeyComparer.System.Collections.IEqualityComparer.Equals(Object x, Object y)
       at System.Collections.Hashtable.KeyEquals(Object item, Object key)
       at System.Collections.Hashtable.get_Item(Object key)
       at System.Web.Caching.CacheSingle.UpdateCache(CacheKey cacheKey, CacheEntry newEntry, Boolean replace, CacheItemRemovedReason removedReason, Object& valueOld)
       at System.Web.Caching.CacheInternal.DoGet(Boolean isPublic, String key, CacheGetOptions getOptions)
       at System.Web.Caching.Cache.get_Item(String key)
       at Microsoft.UpdateServices.Internal.DataCache.get_Item(String key)
       at Microsoft.UpdateServices.Internal.DataAccessCache.GetCoreUpdateXml(Int32[] revisionIds, DataAccess da, Int64 maxXmlPerRequest)
       at Microsoft.UpdateServices.Internal.ClientImplementation.GetSyncInfo(Version clientProtocolVersion, DataAccess dataAccess, Hashtable stateTable, Hashtable deploymentTable, Boolean haveGroupsChanged, Boolean driverSyncNeeded, Boolean doChunking)
       at Microsoft.UpdateServices.Internal.ClientImplementation.SoftwareSync(DataAccess dataAccess, UnencryptedCookieData cookieData, Int32[] installedNonLeafUpdateIds, Int32[] leafUpdateIds, Boolean haveGroupsChanged, Boolean expressQuery, Guid[] filterCategoryIds, Boolean needTwoGroupOutOfScopeUpdates)
       at Microsoft.UpdateServices.Internal.ClientImplementation.SyncUpdates(Cookie cookie, SyncUpdateParameters parameters)
       at Microsoft.UpdateServices.Internal.ClientImplementation.SyncUpdates(Cookie cookie, SyncUpdateParameters parameters)
       at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
       at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
       at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
       at System.Web.Services.Protocols.LogicalMethodInfo.Invoke(Object target, Object[] values)
       at System.Web.Services.Protocols.WebServiceHandler.Invoke()
       at System.Web.Services.Protocols.WebServiceHandler.CoreProcessRequest()
       at System.Web.Services.Protocols.SyncSessionlessHandler.ProcessRequest(HttpContext context)
       at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
       at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
       at System.Web.HttpApplication.PipelineStepManager.ResumeSteps(Exception error)
       at System.Web.HttpApplication.BeginProcessRequestNotification(HttpContext context, AsyncCallback cb)
       at System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context)
       at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
       at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
       at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
       at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)

    Again, this is for all three computers with the problem. 

    So I researched that problem and it came up as a potential ram problem on the server, yet if that was the case, wouldn't more desktops be reporting this same problem?  Chkdsk in read only mode indicated no disk errors and I am currently running a RAM diagnostic, just in case - but it's not adding up for me. 

    I have exhausted my skill with google, TechNet and wsus troubleshooting. Can anybody recommend a course of action to continue troubleshooting the problem?

    I have WSUS 3 SP2 with KB2938066 installed on top of that.  WSUS is running with a SQL Server 2008R2 (standard, not express) back end on a Windows 2008R2 server

    The clients are Windows 7 64bit with a combination of 64 and 32bit software installed as part of the imaging process.  Two of the desktops are currently identical since the imaging just completed.  One has had a number of things installed on top of the base image software.

    the imaging process uses ADK and MDT 2012 (lite touch) with pxe boot, if that is relevant at all.

    Thank you.


    • Edited by mdt109 Thursday, July 16, 2015 9:19 PM
    Thursday, July 16, 2015 4:28 PM

Answers

  • ensure new SIDs are being generated for your images

    if you didn't sysprep the reference image this could be a duplicate SID issue

    delete this regkey on the problematic clients, reboot and try again:

    HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate

    if that doesn't work, try the latest WU agent:

    https://support.microsoft.com/en-us/kb/949104

    if this works then you should include it as part of your MDT task sequence to install it into your images or maybe deploy it on your reference image prior to capture

    also, I suggest you edit your earlier post and remove any IPs, host name and domain names from the logs


    • Edited by armin19 Thursday, July 16, 2015 7:07 PM
    • Marked as answer by mdt109 Thursday, July 16, 2015 9:41 PM
    Thursday, July 16, 2015 7:06 PM

All replies

  • ensure new SIDs are being generated for your images

    if you didn't sysprep the reference image this could be a duplicate SID issue

    delete this regkey on the problematic clients, reboot and try again:

    HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate

    if that doesn't work, try the latest WU agent:

    https://support.microsoft.com/en-us/kb/949104

    if this works then you should include it as part of your MDT task sequence to install it into your images or maybe deploy it on your reference image prior to capture

    also, I suggest you edit your earlier post and remove any IPs, host name and domain names from the logs


    • Edited by armin19 Thursday, July 16, 2015 7:07 PM
    • Marked as answer by mdt109 Thursday, July 16, 2015 9:41 PM
    Thursday, July 16, 2015 7:06 PM
  • clients definitely don't have the same client id, however the latest update agent appears to have done the trick. 

    I'll add that to my imaging process then.

    Thank you.

    Thursday, July 16, 2015 9:41 PM