Note: Forums will be making significant UX changes to address key usability improvements surrounding search, discoverability and navigation. To learn more about these changes please visit the announcement which can be found HERE.
MDT 2010 Update 1 w/ SCCM - ADO error: Multiple-step OLE DB operation generated errors.

Unanswered MDT 2010 Update 1 w/ SCCM - ADO error: Multiple-step OLE DB operation generated errors.

  • Friday, June 15, 2012 11:35 PM
     
     

    Hi all,

    We're using the MDT PackageMapping table along with a customized stored procedure to reinstall user applications during Windows 7 migration. It works really well about half the time. The rest of the time, I get no applications and the following error in ZTIGather.log:

    About to issue SQL statement: EXECUTE RetrievePackages '00:0C:29:36:CA:98'

    ERROR - Opening Record Set (Error Number = -2147217887)

    ADO Error: Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.

    Unable to execute database query.

    Running the procedure from within SQL Admin Studio works fine every time. I did notice it sometimes takes over 30 seconds to execute. Is there a timeout somewhere? Any tips on how to troubleshoot this further?

    We're using MDT boot images generated with the WinPE 3.1 supplement, if that has any bearing.

All Replies

  • Wednesday, June 20, 2012 5:06 PM
     
     

    I am also getting the same error message. Where you able to get it resolved?

    Cheers

  • Monday, July 16, 2012 6:36 PM
     
     

    No, we have a premier support case open, but they have not been able to figure it out either. Running ztigather.wsf manually from a Windows 7 machine does the same thing - its not a WinPE issue at least. The issue seems intermittent, but it tends to have lots of failures or successes in a row.

    What's your configuration? Our database is 64-bit SQL 2005.

  • Monday, October 15, 2012 10:42 PM
     
     

    Any update?  I just configured dynamic packages and am getting this same error.

    Thanks,

    Joshua

  • Tuesday, October 16, 2012 8:19 PM
     
     
    I just fixed this issue by granting my Network Access account "Execute" permission on the Stored Procedure 'RetrievePackages'.