none
Warning Reported: Unable to create WebService class RRS feed

  • Question

  • Has anyone run into this warning before? I have Google'd it and nothing to be found. There must have been someone in the world with the same warning.

    I have a stock standard Windows 7 Enterprise LiteTouch deployment. Nothing fancy, just some applications being installed via the MDT database.

    Any comments would be greatly received.

    Tuesday, April 3, 2012 9:50 PM

All replies

  • Nope, not without actually calling any web services...  What version of MDT are you using?

    Please zip together your logs and rules (boostrap.ini and customsettings.ini) and mail them to me... my email address is my last name, and I'm using Google mail :)

    / Johan


    Regards / Johan Arwidmark Twitter: @jarwidmark Blog: http://www.deploymentresearch.com FB: www.facebook.com/deploymentresearch

    Saturday, April 7, 2012 8:21 PM
    Moderator
  • I ran into the exact same warning today while launching a script which deletes desktop icons.

    My Blog: DeployXP [Under Construction]| Viadeo: Mathieu Ait Azzouzene | Linkedin: Mathieu Ait Azzouzene

    Wednesday, May 2, 2012 12:54 PM
  • I just ran into the "Unable to create WebService class" warning today. I think it's related to the LiteTouch client attempting to post to the MDT 2012 Monitoring service. Here's the relevent log entries from my build:

    Property InstalledUpdates070 is now = c33e437b-ebf2-41fa-8c0f-e8b068f7f5ac ZTIWindowsUpdate 5/18/2012 8:28:03 AM 0 (0x0000)
    More to install, Please reboot and run again! ZTIWindowsUpdate 5/18/2012 8:28:04 AM 0 (0x0000)
    Property SMSTSRetryRequested is now = true ZTIWindowsUpdate 5/18/2012 8:28:04 AM 0 (0x0000)
    Property SMSTSRebootRequested is now = true ZTIWindowsUpdate 5/18/2012 8:28:04 AM 0 (0x0000)
    ZTIWindowsUpdate processing completed successfully. ZTIWindowsUpdate 5/18/2012 8:28:05 AM 0 (0x0000)
    Unable to create WebService class ZTIWindowsUpdate 5/18/2012 8:28:14 AM 0 (0x0000)
    Command completed, return code = -2147021886 LiteTouch 5/18/2012 8:28:36 AM 0 (0x0000)
    Property LTIDirty is now = FALSE LiteTouch 5/18/2012 8:28:36 AM 0 (0x0000)
    If there is a drive letter defined, make sure we clear it now so we can *force* recalcutation. LiteTouch 5/18/2012 8:28:36 AM 0 (0x0000)
    Property OSDTargetDriveCache is now = DIRTY LiteTouch 5/18/2012 8:28:36 AM 0 (0x0000)
    LTI initiating task sequence-requested reboot. LiteTouch 5/18/2012 8:28:36 AM 0 (0x0000)
    Error executing web service http://M-2UA125051Y:9800/MDTMonitorEvent/PostEvent?uniqueID=c4da116a-157b-44b5-a844-9026ebf93e3d&computerName=M-REF002&messageID=41017&severity=1&stepName=&currentStep=0&totalSteps=0&id=F5D44D56-EB57-9D85-3880-5E18CB8DA81F,00:0C:29:8D:A8:1F&message=LTI initiating task sequence-requested reboot.&dartIP=&dartPort=&dartTicket=&vmHost=&vmName=: The server name or address could not be resolved
     (-2147012889) LiteTouch 5/18/2012 8:28:40 AM 0 (0x0000)
    Event 41017 sent: LTI initiating task sequence-requested reboot. LiteTouch 5/18/2012 8:28:40 AM 0 (0x0000)
    Shortcut "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup\LiteTouch.lnk" already exists. LiteTouch 5/18/2012 8:28:40 AM 0 (0x0000)
    Property BootPE is now =  LiteTouch 5/18/2012 8:28:40 AM 0 (0x0000)

    --Terry

    Friday, May 18, 2012 8:23 PM
  • Can you access that server?

    Here is a good link for more info:

    Troubleshooting MDT 2012 Monitoring
    http://blogs.technet.com/b/mniehaus/archive/2012/05/10/troubleshooting-mdt-2012-monitoring.aspx

    / Johan


    Regards / Johan Arwidmark Twitter: @jarwidmark Blog: http://www.deploymentresearch.com FB: www.facebook.com/deploymentresearch

    Monday, May 21, 2012 6:34 AM
    Moderator
  • Can you access that server?

    Here is a good link for more info:

    Troubleshooting MDT 2012 Monitoring
    http://blogs.technet.com/b/mniehaus/archive/2012/05/10/troubleshooting-mdt-2012-monitoring.aspx

    / Johan


    Regards / Johan Arwidmark Twitter: @jarwidmark Blog: http://www.deploymentresearch.com FB: www.facebook.com/deploymentresearch

    Johan,

    Thanks for the link. In the case of my deployment, the error was transient. The deployment was able to post to the monitoring service during all of the deployment except for the one instance referenced in the log.

    I think one take away from this is, check the logs. If the error is related to MDTMonitorEvent, then there's not a problem for the integrity of your OS deployment, capture, etc....

    --Terry

    Monday, May 21, 2012 12:48 PM