none
Unable to create web service class at end of ztiWindowsUpdate

    Question

  • <![LOG[Success! Please rerun WindowsUpdate to ensure machine is FULLY up to date.]LOG]!><time="12:20:45.000+000" date="02-20-2013" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Begin Windows Update. Reboot=[]  Retry=[]  Count = 1]LOG]!><time="12:20:45.000+000" date="02-20-2013" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Property MSIT_WU_Count is now = 2]LOG]!><time="12:20:45.000+000" date="02-20-2013" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Configuring client to use WSUS server (insert our WSUS server here)]LOG]!><time="12:20:45.000+000" date="02-20-2013" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Configuring Windows Update settings (manual update, use server)]LOG]!><time="12:20:45.000+000" date="02-20-2013" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Windows Update Agent verion 6 found, OK to continue]LOG]!><time="12:20:50.000+000" date="02-20-2013" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Ready to Opt-In to Microsoft Update: WUA Version: 7.6.7600.256]LOG]!><time="12:20:50.000+000" date="02-20-2013" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Microsoft Update Service:  Enabled = False]LOG]!><time="12:20:50.000+000" date="02-20-2013" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Command Line Procesed Query=False Registered=False  UpdateCommand=[IsInstalled = 0 and IsHidden = 0]]LOG]!><time="12:20:50.000+000" date="02-20-2013" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Start Search...]LOG]!><time="12:20:50.000+000" date="02-20-2013" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Scan complete, ready to install updates. Count = 0]LOG]!><time="12:20:57.000+000" date="02-20-2013" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[This computer is up to date (Success)]LOG]!><time="12:20:57.000+000" date="02-20-2013" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Property MSIT_WU_Count is now = ]LOG]!><time="12:20:57.000+000" date="02-20-2013" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Restore NoAutoUpdateKey to 0]LOG]!><time="12:20:57.000+000" date="02-20-2013" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Restore NoAutoUpdateKey to 0]LOG]!><time="12:20:58.000+000" date="02-20-2013" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[ZTIWindowsUpdate processing completed successfully.]LOG]!><time="12:20:58.000+000" date="02-20-2013" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Unable to create WebService class]LOG]!><time="12:20:58.000+000" date="02-20-2013" component="ZTIWindowsUpdate" context="" type="2" thread="" file="ZTIWindowsUpdate">
    <![LOG[Command completed, return code = -2147467259]LOG]!><time="12:20:59.000+000" date="02-20-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Litetouch deployment failed, Return Code = -2147467259  0x80004005]LOG]!><time="12:20:59.000+000" date="02-20-2013" component="LiteTouch" context="" type="3" thread="" file="LiteTouch">
    <![LOG[Event 41014 sent: Litetouch deployment failed, Return Code = -2147467259  0x80004005]LOG]!><time="12:20:59.000+000" date="02-20-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[For more information, consult the task sequencer log ...\SMSTS.LOG.]LOG]!><time="12:20:59.000+000" date="02-20-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Property RetVal is now = -2147467259]LOG]!><time="12:20:59.000+000" date="02-20-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Unable to copy log to the network as no SLShare value was specified.]LOG]!><time="12:20:59.000+000" date="02-20-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    

    Running on a laptop that would image fine in the past, and I get this above error.

    I've verified that the monitoring service started properly. I feel like an update to Windows Update broke this, but have zero proof.

    Wednesday, February 20, 2013 6:49 PM

All replies

  • I think it's most likely related to the monitoring service. This post should help Troubleshooting MDT 2012 Monitoring


    Blog: http://scriptimus.wordpress.com

    Wednesday, February 20, 2013 9:19 PM
  • Unfortunately I've already tried all checks to make sure the correct services were running. I've rebooted the MDT box as well and reinstalled the Monitoring service. No change.
    Wednesday, February 20, 2013 9:52 PM
  • It could be permissions, what account are you running it under? Are you using the run this step as a different user option?


    Blog: http://scriptimus.wordpress.com

    Thursday, February 21, 2013 11:43 AM
  • I'm using the same domain admin account that I've been using for MDT imaging for the last year. These problems just cropped up within the last 2 weeks, on which I've done zero changes to MDT itself other than upgrading an Office addon that gets installed (Cisco ViewMail). Disabling that made no difference.

    The only other thing that might affect this would be a windows update, in my mind. I am not in control of the update server. I have it running windows updates before and after installing all apps.

    I'm considering stopping the update service to see if that breaks it, because it means that updates from this month caused it.

    Thursday, February 21, 2013 12:46 PM
  • That sounds like a good plan. You should always follow your instincts first.

    If it turns out to be an update interfering, you can filter it out from your deployments using WUMU_Exclude. I've done a post to show that here.

    Let me know how you get on please.

    /Andrew


    Blog: http://scriptimus.wordpress.com

    Thursday, February 21, 2013 1:42 PM
  • I haven't tried anything yet, but within the last 2 weeks they've added in the update to windows update...."Windows Update Agent 7.6.7600.256" so I'm gonna follow your instructions on disabling that to see if it fixes it.

    I really don't feel like rebuilding the image just yet to make that work....I'll rebuild in a few months and then get rid of that step, assuming this works.

    Maybe there's some bug with that update and MDT in general? Some changed code acting differently?
    • Edited by VulturEMaN Thursday, February 21, 2013 2:07 PM
    Thursday, February 21, 2013 2:05 PM
  • Is there an easy way to find the GUID for that Windows Update Agent 7.6.7600.256? The KB# isn't listed in the update history, so I'm guessing trying to block by KB would be useless....but I have no idea how to find the GUID of that update.
    • Edited by VulturEMaN Thursday, February 21, 2013 2:20 PM
    Thursday, February 21, 2013 2:18 PM
  • I believe the Windows Update Agent is mandatory. It's the first thing that is tested. It will pull down the latest version.


    Blog: http://scriptimus.wordpress.com

    Thursday, February 21, 2013 3:17 PM
  • I believe the Windows Update Agent is mandatory. It's the first thing that is tested. It will pull down the latest version.


    Blog: http://scriptimus.wordpress.com

    I just disabled both update steps in the Task Sequence, and now it's throwing a similar error in the ZTIBde:


    Performing ProtectKeyWithTpm Installation	ZTIBde	2/25/2013 10:10:16 AM	0 (0x0000)
    Attempting to enable BitLocker TPM	ZTIBde	2/25/2013 10:10:16 AM	0 (0x0000)
    Recovery P@ssword being saved to \\[redacted]\DeploymentShare32$\Keys\[redacted].txt	ZTIBde	2/25/2013 10:10:20 AM	0 (0x0000)
    Validating connection to \\[redacted]\DeploymentShare32$\Keys	ZTIBde	2/25/2013 10:10:20 AM	0 (0x0000)
    Already connected to server [redacted] as that is where this script is running from.	ZTIBde	2/25/2013 10:10:20 AM	0 (0x0000)
    Attempting to intiate ProtectKeyWithNumericalP@ssword	ZTIBde	2/25/2013 10:10:20 AM	0 (0x0000)
    Success protecting Key with numerical p@ssword	ZTIBde	2/25/2013 10:10:22 AM	0 (0x0000)
    Attempting to retrieve numerical p@ssword	ZTIBde	2/25/2013 10:10:22 AM	0 (0x0000)
    Saving numerical p@ssword to file.	ZTIBde	2/25/2013 10:10:22 AM	0 (0x0000)
    ZTI ERROR - Unhandled error returned by ZTIBde:  (-2147022987  0x80070775)	ZTIBde	2/25/2013 10:10:22 AM	0 (0x0000)
    Unable to create WebService class	ZTIBde	2/25/2013 10:10:22 AM	0 (0x0000)
    Command completed, return code = -2147467259	LiteTouch	2/25/2013 10:10:25 AM	0 (0x0000)
    Litetouch deployment failed, Return Code = -2147467259  0x80004005	LiteTouch	2/25/2013 10:10:25 AM	0 (0x0000)
    Event 41014 sent: Litetouch deployment failed, Return Code = -2147467259  0x80004005	LiteTouch	2/25/2013 10:10:26 AM	0 (0x0000)
    For more information, consult the task sequencer log ...\SMSTS.LOG.	LiteTouch	2/25/2013 10:10:26 AM	0 (0x0000)
    Property RetVal is now = -2147467259	LiteTouch	2/25/2013 10:10:26 AM	0 (0x0000)
    Unable to copy log to the network as no SLShare value was specified.	LiteTouch	2/25/2013 10:10:26 AM	0 (0x0000)

    When I looked up 80070775, it's telling me a locked out account or changed password or bad permissions. The account isn't locked out. It cannot be edited at all, actually, by anyone. So it really can't be that. It's a system account we've used for MDT since the beginning. The account is a full local admin on the deployment box.

    I've disabled and re-enabled the monitoring service on all deployment shares to see what happens. Will report back.




    • Edited by VulturEMaN Monday, February 25, 2013 5:07 PM
    Monday, February 25, 2013 4:07 PM
  • Get this....rebooting the computer didn't fix it before (I tried it a few times), but stopping the Monitoring service on all deployment shares and then restarting it fixed the problem (so far).

    I would then assume that the monitoring service is caching something? Maybe credentials or settings?

    Monday, February 25, 2013 7:53 PM
  • Take a look at the first thing I posted, above. And your reply. :(

    Glad it's sorted now. Well done.

    /Andrew


    Blog: http://scriptimus.wordpress.com

    Thursday, February 28, 2013 4:12 PM
  • Take a look at the first thing I posted, above. And your reply. :(

    Glad it's sorted now. Well done.

    /Andrew


    Blog: http://scriptimus.wordpress.com

    Like I said though...I went through all of that. I tested all of the services and that article was the first thing that came up when I googled the problem (before posting here). I tried just about everything, including restarting the service itself.

    The problem started up again after imaging 2 more PCs.

    The only thing that has fixed this situation so far has been disabling monitoring, or fiddling around with the services/checkmark alot. It has been so inconsistent that we've disabled monitoring until I redo the images to integrate all windows updates....still hoping that this is the problem.

    Friday, March 01, 2013 6:01 PM