Topic
19 replies Latest Post - ‏2014-02-18T13:55:48Z by sergio.tarchi
pgill
pgill
8 Posts
ACCEPTED ANSWER

Pinned topic MDT 3.1 issues

‏2013-05-01T18:22:14Z |

I don't know if anyone has attempted to use the new MDT 3.1 or not yet, I can't find any info on it. When ever I go to build a package using the MDT Bundle Creator v3.1.29, it processes, then it errors out on this:

 

[Wed May  1 14:03:21 2013] Creating Media item at L:\BigFixOSD\MDTBundle
[Wed May  1 14:03:21 2013]
<<<<< L:/MDTBundleCreator-3.1.29\bftemp.ps1 <<<<<
Add-PSSnapIn Microsoft.BDD.PSSnapIn -ErrorAction SilentlyContinue
New-PSDrive -Name "BFOSD" -PSProvider MDTProvider -Root "L:\BigFixOSD\DeploymentShare"
new-item -path "BFOSD:\Media" -enable "True" -Name "MEDIA001" -Comments "" -Root "L:\BigFixOSD\MDTBundle" -SelectionProfile "Everything" -SupportX86 "True" -SupportX64 "True" -GenerateISO "False" -ISOName "LiteTouchMedia.iso" -Verbose
new-PSDrive -Name "MEDIA001" -PSProvider "MDTProvider" -Root "L:\BigFixOSD\MDTBundle\Content\Deploy" -Description "BigFix OSD Media Item" -Force -Verbose
Start-Sleep -s 10
>>>>> L:/MDTBundleCreator-3.1.29\bftemp.ps1 >>>>>

[Wed May  1 14:03:21 2013] start /WAIT /I C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -noninteractive -command "& 'L:/MDTBundleCreator-3.1.29\bftemp.ps1'"
[Wed May  1 14:03:50 2013] Modifying Settings.xml...
[Wed May  1 14:03:50 2013] Updating Media. Please wait...
[Wed May  1 14:03:50 2013]
<<<<< L:/MDTBundleCreator-3.1.29\bftemp.ps1 <<<<<
Add-PSSnapIn Microsoft.BDD.PSSnapIn -ErrorAction SilentlyContinue
New-PSDrive -Name "BFOSD" -PSProvider MDTProvider -Root "L:\BigFixOSD\DeploymentShare"
Update-MDTMedia -Path "BFOSD:\Media\MEDIA001" -Verbose
>>>>> L:/MDTBundleCreator-3.1.29\bftemp.ps1 >>>>>

[Wed May  1 14:03:50 2013] start /WAIT /I C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -noninteractive -command "& 'L:/MDTBundleCreator-3.1.29\bftemp.ps1'"
[Wed May  1 14:10:10 2013] Done!
[Wed May  1 14:10:10 2013] Introspection of PE wim files has commenced
[Wed May  1 14:10:10 2013] Using command: RBAGENT\rbagent64.exe -o rad-temmakewpe exportdir="L:\BigFixOSD\MDTBundle\Content\Deploy\Boot" wpex86path="L:\BigFixOSD\MDTBundle\Content\Deploy\Boot\LiteTouchPE_x86.wim" wpeamd64path="L:\BigFixOSD\MDTBundle\Content\Deploy\Boot\LiteTouchPE_x64.wim" osdtoolsdir="L:/MDTBundleCreator-3.1.29/RBAgent"
[Wed May  1 14:11:17 2013] exportdir: L:\BigFixOSD\MDTBundle\Content\Deploy\Boot
[Wed May  1 14:11:17 2013] ERROR: Error generating PE wim files. check L:/MDTBundleCreator-3.1.29/RBAgent\osdtools.log for more info
[Wed May  1 14:11:17 2013] Introspection of PE wim files has completed successfully
[Wed May  1 14:11:17 2013] Making directory: L:\BigFixOSD\MDTBundle\Content\Deploy\$OEM$\BigFixOSD\Boot\PEX86
[Wed May  1 14:11:17 2013] Making directory: L:\BigFixOSD\MDTBundle\Content\Deploy\$OEM$\BigFixOSD\Boot\PEX64
[Wed May  1 14:11:17 2013] Moving L:\BigFixOSD\MDTBundle\Content\Deploy\Boot\WPE-x86.rad to L:\BigFixOSD\MDTBundle\Content\Deploy\$OEM$\BigFixOSD\Boot\PEX86\WPE-x86.rad
[Wed May  1 14:11:17 2013] ERROR: No such file or directory
[Wed May  1 14:11:17 2013] Error: Unable to cleanup and move Windows PE WIM archives: Died at /<L:\MDTBundleCreator-3.1.29\MDTBundleCreator64.exe>MDT/Introspect.pm line 144.

[Wed May  1 14:11:17 2013] ERROR: Media update failed 5 times. Check for any errors in the generated logfile. Make sure to run with Administrator privileges. Otherwise, try freeing up system resources and try again.
[Wed May  1 14:11:17 2013] ERROR: Bundle Creation encountered fatal error:
Died at CreateBundle.pl line 258.

So any assistance is appreicated.

This log L:/MDTBundleCreator-3.1.29/RBAgent\osdtools.log does not exist btws.

v/r

  • JasonHonda
    JasonHonda
    44 Posts
    ACCEPTED ANSWER

    Re: MDT 3.1 issues

    ‏2013-05-01T20:33:28Z  in response to pgill

    We have seen issues similar to this before. First thing would be to try restarting your computer. If trying to run immediately after WADK and/or MDT 2012, issues like this can occur during the media generation process.

    If that doesn't resolve the issue, I would look into manually generating the media, which is what I believe to be failing. To do that, go in to MDT Deployment Workbench. Expand the BigFix OSD Deployment Share->Advanced Configuration->Media. Then right click on the MEDIA001 item and select "Update Media Content". Depending on the error seen there, it might provide better insight. It could be a permissions or AV issue with using DISM or imagex.

  • pgill
    pgill
    8 Posts
    ACCEPTED ANSWER

    Re: MDT 3.1 issues

    ‏2013-05-02T12:48:22Z  in response to pgill

    So I tried a reboot of the system and got the same error message.

    When I tried it through the workbench, I got: "Unable to mount the WIM, so the update process cannot continue. "

    EDIT:

    Turned off McAfee HBSS and got this message instead with the Update Media Content:


    Copied standard folders.
    Boot images updated.
    Setting up dual x86/x64 boot image.
    Not adding x86 boot entry to UEFI BCD because dual boot UEFI media is not supported.
    Not modifying display order for dual boot UEFI.
    Boot configuration editing completed.
    Reset read-only attributes.
    Skipped ISO generation.
     

    When I try to import what was created into IEM, I get : "There was a problem compressing the file."

    Updated on 2013-05-02T13:51:01Z at 2013-05-02T13:51:01Z by pgill
    • JasonHonda
      JasonHonda
      44 Posts
      ACCEPTED ANSWER

      Re: MDT 3.1 issues

      ‏2013-05-02T18:12:27Z  in response to pgill

      Ok, good to see figuring out McAfee was blocking the use of image mounting tools, and so that got further.

      I'm assuming that after that, you ran the MDTBundleCreator again, and it successfully built this time.

      Now on upload of the MDT Bundle to the dashboard you see that error. We can take a look at a log file in %temp%\OSDeployment\TemporaryZipFile.log on the console computer.

      We are attempting to zip up the folder you specified, but it appears the output file is not existing, which should be %temp%\OSDeployment\TemporaryZipFile.zip. I'd also double check that a file zip.exe can be found in that %temp%\OSDeployment directory.

      • pgill
        pgill
        8 Posts
        ACCEPTED ANSWER

        Re: MDT 3.1 issues

        ‏2013-05-02T18:22:51Z  in response to JasonHonda

        With McAfee off, I got this error with the Bundle Creator:

        [Thu May  2 08:51:15 2013] Creating Media item at L:\BigFixOSD\MDTBundle
        [Thu May  2 08:51:38 2013] Modifying Settings.xml...
        [Thu May  2 08:51:39 2013] Updating Media. Please wait...
        [Thu May  2 08:58:11 2013] Done!
        [Thu May  2 08:58:11 2013] Introspection of PE wim files has commenced
        [Thu May  2 08:58:11 2013] Using command: RBAGENT\rbagent64.exe -o rad-temmakewpe exportdir="L:\BigFixOSD\MDTBundle\Content\Deploy\Boot" wpex86path="L:\BigFixOSD\MDTBundle\Content\Deploy\Boot\LiteTouchPE_x86.wim" wpeamd64path="L:\BigFixOSD\MDTBundle\Content\Deploy\Boot\LiteTouchPE_x64.wim" osdtoolsdir="L:/MDTBundleCreator-3.1.29/RBAgent"
        [Thu May  2 08:59:17 2013] exportdir: L:\BigFixOSD\MDTBundle\Content\Deploy\Boot
        [Thu May  2 08:59:17 2013] ERROR: Error generating PE wim files. check L:/MDTBundleCreator-3.1.29/RBAgent\osdtools.log for more info
        [Thu May  2 08:59:17 2013] Introspection of PE wim files has completed successfully
        [Thu May  2 08:59:17 2013] Making directory: L:\BigFixOSD\MDTBundle\Content\Deploy\$OEM$\BigFixOSD\Boot\PEX86
        [Thu May  2 08:59:17 2013] Making directory: L:\BigFixOSD\MDTBundle\Content\Deploy\$OEM$\BigFixOSD\Boot\PEX64
        [Thu May  2 08:59:17 2013] Moving L:\BigFixOSD\MDTBundle\Content\Deploy\Boot\WPE-x86.rad to L:\BigFixOSD\MDTBundle\Content\Deploy\$OEM$\BigFixOSD\Boot\PEX86\WPE-x86.rad
        [Thu May  2 08:59:17 2013] ERROR: No such file or directory
        [Thu May  2 08:59:17 2013] Error: Unable to cleanup and move Windows PE WIM archives: Died at /<L:\MDTBundleCreator-3.1.29\MDTBundleCreator64.exe>MDT/Introspect.pm line 144.

        [Thu May  2 08:59:17 2013] ERROR: Media update failed 5 times. Check for any errors in the generated logfile. Make sure to run with Administrator privileges. Otherwise, try freeing up system resources and try again.
        [Thu May  2 08:59:17 2013] ERROR: Bundle Creation encountered fatal error:
        Died at CreateBundle.pl line 258.

        With McAfee ON, I get this:

        [Wed May  1 17:03:29 2013] Creating Media item at L:\BigFixOSD\MDTBundle
        [Wed May  1 17:03:51 2013] Modifying Settings.xml...
        [Wed May  1 17:03:51 2013] Updating Media. Please wait...
        [Wed May  1 17:06:54 2013] ERROR: Media update failed (try 5/5)
        [Wed May  1 17:06:54 2013] ERROR: Media update failed 5 times. Check for any errors in the generated logfile. Make sure to run with Administrator privileges. Otherwise, try freeing up system resources and try again.
        [Wed May  1 17:06:54 2013] ERROR: Bundle Creation encountered fatal error:
        Died at CreateBundle.pl line 258.

        ----------------------------------------------------------------------------------------------------------------------------------------------------------------------

        TemporaryZipFile.log

        zip error: Nothing to do! (try: zip -r -S C:\Users\xraygill\AppData\Local\Temp\2\OSDeployment\TemporaryZipFile.zip . -i .)

        uploadmanager.exe, UploadManagerFiles folder, zip.exe and TemporaryZipFiles.log are all in that folder.

         

        • JasonHonda
          JasonHonda
          44 Posts
          ACCEPTED ANSWER

          Re: MDT 3.1 issues

          ‏2013-05-02T18:41:52Z  in response to pgill

          Ok, not sure why that failed to upload, but we'll ignore that for now until we get the bundle created properly.

          For that, look at L:/MDTBundleCreator-3.1.29/RBAgent\rbagent.log The output misidentifies the file to look at. This may provide some insight into why we were unable to process things properly.

          • pgill
            pgill
            8 Posts
            ACCEPTED ANSWER

            Re: MDT 3.1 issues

            ‏2013-05-02T18:46:14Z  in response to JasonHonda

            [2013/05/02 08:58:11] IBM Tivoli Provisioning Manager for Images Web extension 64 bits v.7.1.1.12 (200.39)
            [2013/05/02 08:58:11] Licensed Materials - Property of IBM. - INTERNAL
            [2013/05/02 08:58:11] (C) Copyright IBM Corporation 1998, 2013.
            [2013/05/02 08:58:11] All Rights Reserved. IBM, the IBM logo, and Tivoli are trademarks of IBM Corporation in the United States, other countries or both.
            [2013/05/02 08:58:12]  A <NOT> Loading server extensions if available
            [2013/05/02 08:58:12]  A <NOT> Working in offline, extensions are disabled
            [2013/05/02 08:58:12]  A <NOT> No ServerID has been defined
            [2013/05/02 08:58:12]  A <INF> Creating offline WPE environmet...
            [2013/05/02 08:58:12]  A <NOT> Looking for WinPE toolkit (ver=0)
            [2013/05/02 08:58:12] [Progress] 1% done (Creating WinPE 4 engine for x86)
            [2013/05/02 08:58:12] [Progress] 5% done (Base WinPE copied)
            [2013/05/02 08:58:12] [Progress] 5% done (Mounting base WinPE)
            [2013/05/02 08:58:12]  A <NOT> Running ["L:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\dism.exe" /Mount-Wim /WimFile:"C:\Users\xraygill\AppData\Local\Temp\2\tpm_A323D094BD9BE4E1_1\sources\boot.wim" /index:1 /MountDir:"C:\Users\xraygill\AppData\Local\Temp\2\tpm_ED8656F64E67CB83_1"]
            [2013/05/02 08:58:24]  A <INF> Command ["L:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\dism.exe" /Mount-Wim /WimFile:"C:\Users\xraygill\AppData\Local\Temp\2\tpm_A323D094BD9BE4E1_1\sources\boot.wim" /index:1 /MountDir:"C:\Users\xraygill\AppData\Local\Temp\2\tpm_ED8656F64E67CB83_1"] successfully completed in 11.26 seconds
            [2013/05/02 08:58:39]  A <NOT> Running [reg load HKLM\h_sys C:\Users\xraygill\AppData\Local\Temp\2\tpm_ED8656F64E67CB83_1\windows\system32\config\system]
            [2013/05/02 08:58:39]  A <INF> Command [reg load HKLM\h_sys C:\Users\xraygill\AppData\Local\Temp\2\tpm_ED8656F64E67CB83_1\windows\system32\config\system] successfully completed in 0.24 seconds
            [2013/05/02 08:58:40]  A <NOT> Running [reg unload HKLM\h_sys]
            [2013/05/02 08:58:40]  A <INF> Command [reg unload HKLM\h_sys] successfully completed in 0.28 seconds
            [2013/05/02 08:58:40] [Progress] 10% done (Installing packages)
            [2013/05/02 08:58:40]  A <NOT> Running ["L:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\dism.exe" /Image:"C:\Users\xraygill\AppData\Local\Temp\2\tpm_ED8656F64E67CB83_1" /Add-Package  /PackagePath:"L:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\WinPE_OCs\winpe-setup.cab" /PackagePath:"L:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\WinPE_OCs\winpe-setup-client.cab" /PackagePath:"L:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\WinPE_OCs\winpe-setup-server.cab" /PackagePath:"L:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\WinPE_OCs\winpe-legacysetup.cab" /PackagePath:"L:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\WinPE_OCs\winpe-wmi.cab" /English]
            [2013/05/02 08:59:17]  A <ERR> Command ["L:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\dism.exe" /Image:"C:\Users\xraygill\AppData\Local\Temp\2\tpm_ED8656F64E67CB83_1" /Add-Package  /PackagePath:"L:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\WinPE_OCs\winpe-setup.cab" /PackagePath:"L:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\WinPE_OCs\winpe-setup-client.cab" /PackagePath:"L:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\WinPE_OCs\winpe-setup-server.cab" /PackagePath:"L:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\WinPE_OCs\winpe-legacysetup.cab" /PackagePath:"L:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\WinPE_OCs\winpe-wmi.cab" /English] failed with exit code 5 in 37.13 seconds
            [2013/05/02 08:59:17]  A <ERR> Command error: Unknown error, Error when installing some packages in WinPE: Error code (5)
            [2013/05/02 08:59:17]  A <ERR> Error raised by AddPackages in load.rbc, line 3931 [:0]
            [2013/05/02 08:59:17]  A <ERR> Unknown error (Error when installing some packages in WinPE: Error code (5))
            [2013/05/02 08:59:17]  A <WRN>  (called from MakeWPESoftware (load.rbc:3939))
            [2013/05/02 08:59:17]  A <WRN>  (called from MakeWPE (load.rbc:4261))
            [2013/05/02 08:59:17]  A <WRN>  (called from RAD_temmakewpe (load.rbc:4330))
            [2013/05/02 08:59:17]  A <WRN>  (called from AgentDispatch (rbagent.rbc:4066))
            [2013/05/02 08:59:17]  A <WRN>  (called from --toplevel-- (rbagent.rbc:4297))
            [2013/05/02 08:59:17]  A <ERR> RbAgent command rad-temmakewpe has failed [AGT:4073]
             

            • JasonHonda
              JasonHonda
              44 Posts
              ACCEPTED ANSWER

              Re: MDT 3.1 issues

              ‏2013-05-02T18:53:48Z  in response to pgill

              I'll have to get some more team members involved to try and figure out this issue. Of course opening a support case will get some more traction than on the forum, but we of course try to help here.

              The WinPE wim is likely still mounted. You can try running the command yourself that failed to see what kind of error output might be there.

              "L:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\dism.exe" /Image:"C:\Users\xraygill\AppData\Local\Temp\2\tpm_ED8656F64E67CB83_1" /Add-Package  /PackagePath:"L:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\WinPE_OCs\winpe-setup.cab" /PackagePath:"L:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\WinPE_OCs\winpe-setup-client.cab" /PackagePath:"L:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\WinPE_OCs\winpe-setup-server.cab" /PackagePath:"L:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\WinPE_OCs\winpe-legacysetup.cab" /PackagePath:"L:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\WinPE_OCs\winpe-wmi.cab" /English

              Can you confirm the existence of some/all of the packages listed in that command which are being added to WinPE?

              • pgill
                pgill
                8 Posts
                ACCEPTED ANSWER

                Re: MDT 3.1 issues

                ‏2013-05-02T18:58:26Z  in response to JasonHonda

                The cab files are definately there.

                Last time I tried to open up a support case, they refered me to the forums for more support because they said that the engineers were on here more =D

                ------------------------------------------------------------------------------------------------------------------------------------------------------

                When the command is run from an elevated command prompt I get:

                Error 0xc1420127

                The specified image in the specified wim is already mounted for read/write access.

                The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

                 ----------------------------------------------------------------------------------------------------------------------------------------------

                DISM.LOG

                2013-05-02 15:00:06, Info                  DISM   PID=7724 TID=4784 Scratch directory set to 'C:\Users\xraygill\AppData\Local\Temp\2\'. - CDISMManager::put_ScratchDir
                2013-05-02 15:00:06, Info                  DISM   PID=7724 TID=4784 DismCore.dll version: 6.2.9200.16384 - CDISMManager::FinalConstruct
                2013-05-02 15:00:06, Info                  DISM   PID=7724 TID=4784 Successfully loaded the ImageSession at "L:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\amd64\DISM" - CDISMManager::LoadLocalImageSession
                2013-05-02 15:00:06, Info                  DISM   DISM Provider Store: PID=7724 TID=4784 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
                2013-05-02 15:00:06, Info                  DISM   DISM Provider Store: PID=7724 TID=4784 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
                2013-05-02 15:00:06, Info                  DISM   DISM Provider Store: PID=7724 TID=4784 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
                2013-05-02 15:00:06, Info                  DISM   DISM Provider Store: PID=7724 TID=4784 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
                2013-05-02 15:00:06, Info                  DISM   DISM Provider Store: PID=7724 TID=4784 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
                2013-05-02 15:00:06, Info                  DISM   DISM Provider Store: PID=7724 TID=4784 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
                2013-05-02 15:00:06, Info                  DISM   DISM Provider Store: PID=7724 TID=4784 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
                2013-05-02 15:00:06, Info                  DISM   DISM Manager: PID=7724 TID=4784 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
                2013-05-02 15:00:06, Info                  DISM   DISM Provider Store: PID=7724 TID=4784 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
                2013-05-02 15:00:06, Info                  DISM   DISM Provider Store: PID=7724 TID=4784 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
                2013-05-02 15:00:06, Info                  DISM   DISM.EXE:
                2013-05-02 15:00:06, Info                  DISM   DISM.EXE: <----- Starting Dism.exe session ----->
                2013-05-02 15:00:06, Info                  DISM   DISM.EXE:
                2013-05-02 15:00:06, Info                  DISM   DISM.EXE: Host machine information: OS Version=6.1.7601, Running architecture=amd64, Number of processors=16
                2013-05-02 15:00:06, Info                  DISM   DISM.EXE: Dism.exe version: 6.2.9200.16384
                2013-05-02 15:00:06, Info                  DISM   DISM.EXE: Executing command line: "L:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\dism.exe"  /Mount-Wim /WimFile:"C:\Users\xraygill\AppData\Local\Temp\2\tpm_A323D094BD9BE4E1_1\sources\boot.wim" /index:1 /MountDir:"C:\Users\xraygill\AppData\Local\Temp\2\tpm_ED8656F64E67CB83_1"
                2013-05-02 15:00:06, Info                  DISM   DISM Provider Store: PID=7724 TID=4784 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
                2013-05-02 15:00:06, Info                  DISM   DISM Provider Store: PID=7724 TID=4784 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
                2013-05-02 15:00:06, Info                  DISM   DISM Provider Store: PID=7724 TID=4784 Loading Provider from location L:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\FolderProvider.dll - CDISMProviderStore::Internal_GetProvider
                2013-05-02 15:00:06, Info                  DISM   DISM Provider Store: PID=7724 TID=4784 Connecting to the provider located at L:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider
                2013-05-02 15:00:06, Info                  DISM   DISM Provider Store: PID=7724 TID=4784 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
                2013-05-02 15:00:06, Info                  DISM   DISM Provider Store: PID=7724 TID=4784 Loading Provider from location L:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\WimProvider.dll - CDISMProviderStore::Internal_GetProvider
                2013-05-02 15:00:06, Info                  DISM   DISM Provider Store: PID=7724 TID=4784 Connecting to the provider located at L:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\WimProvider.dll. - CDISMProviderStore::Internal_LoadProvider
                2013-05-02 15:00:06, Info                  DISM   DISM Provider Store: PID=7724 TID=4784 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
                2013-05-02 15:00:06, Info                  DISM   DISM Provider Store: PID=7724 TID=4784 Loading Provider from location L:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\VHDProvider.dll - CDISMProviderStore::Internal_GetProvider
                2013-05-02 15:00:06, Info                  DISM   DISM Provider Store: PID=7724 TID=4784 Connecting to the provider located at L:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\VHDProvider.dll. - CDISMProviderStore::Internal_LoadProvider
                2013-05-02 15:00:06, Info                  DISM   DISM Provider Store: PID=7724 TID=4784 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
                2013-05-02 15:00:06, Info                  DISM   DISM Provider Store: PID=7724 TID=4784 Loading Provider from location L:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\ImagingProvider.dll - CDISMProviderStore::Internal_GetProvider
                2013-05-02 15:00:06, Info                  DISM   DISM Provider Store: PID=7724 TID=4784 Connecting to the provider located at L:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\ImagingProvider.dll. - CDISMProviderStore::Internal_LoadProvider
                2013-05-02 15:00:06, Info                  DISM   DISM Provider Store: PID=7724 TID=4784 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
                2013-05-02 15:00:06, Info                  DISM   DISM Provider Store: PID=7724 TID=4784 Loading Provider from location L:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\CompatProvider.dll - CDISMProviderStore::Internal_GetProvider
                2013-05-02 15:00:06, Info                  DISM   DISM Provider Store: PID=7724 TID=4784 Connecting to the provider located at L:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\CompatProvider.dll. - CDISMProviderStore::Internal_LoadProvider
                2013-05-02 15:00:06, Info                  DISM   DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
                2013-05-02 15:00:06, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
                2013-05-02 15:00:06, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: FolderManager
                2013-05-02 15:00:06, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: WimManager
                2013-05-02 15:00:06, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: WimManager.
                2013-05-02 15:00:06, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: VHDManager
                2013-05-02 15:00:06, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: GenericImagingManager
                2013-05-02 15:00:06, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: GenericImagingManager.
                2013-05-02 15:00:06, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: Compatibility Manager
                2013-05-02 15:00:06, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: Compatibility Manager.
                2013-05-02 15:00:06, Info                  DISM   DISM Provider Store: PID=7724 TID=4784 Getting Provider WimManager - CDISMProviderStore::GetProvider
                2013-05-02 15:00:06, Info                  DISM   DISM Provider Store: PID=7724 TID=4784 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
                [7724] Caller did not request sparse mount
                [7724] [0x80070003] FIOGetFileId:(862): The system cannot find the path specified.
                [7724] [0x80070003] FindOtherMountsForWimCallback:(392): The system cannot find the path specified.
                [7724] [0x80070002] FIOGetFileId:(862): The system cannot find the file specified.
                [7724] [0x80070002] FindOtherMountsForWimCallback:(392): The system cannot find the file specified.
                [7724] [0x80070003] FIOGetFileId:(862): The system cannot find the path specified.
                [7724] [0x80070003] FindOtherMountsForWimCallback:(392): The system cannot find the path specified.
                [7724] [0x80070002] FIOGetFileId:(862): The system cannot find the file specified.
                [7724] [0x80070002] FindOtherMountsForWimCallback:(392): The system cannot find the file specified.
                [7724] [0x80070003] FIOGetFileId:(862): The system cannot find the path specified.
                [7724] [0x80070003] FindOtherMountsForWimCallback:(392): The system cannot find the path specified.
                [7724] [0x80070003] FIOGetFileId:(862): The system cannot find the path specified.
                [7724] [0x80070003] FindOtherMountsForWimCallback:(392): The system cannot find the path specified.
                [7724] [0x80070003] FIOGetFileId:(862): The system cannot find the path specified.
                [7724] [0x80070003] FindOtherMountsForWimCallback:(392): The system cannot find the path specified.
                [7724] [0x80070003] FIOGetFileId:(862): The system cannot find the path specified.
                [7724] [0x80070003] FindOtherMountsForWimCallback:(392): The system cannot find the path specified.
                [7724] [0x80070003] FIOGetFileId:(862): The system cannot find the path specified.
                [7724] [0x80070003] FindOtherMountsForWimCallback:(392): The system cannot find the path specified.
                [7724] ImageUnmarshallHandle: Reconstituting wim at C:\Users\xraygill\AppData\Local\Temp\2\tpm_A323D094BD9BE4E1_1\sources\boot.wim.
                [7724] [0xc1420127] WIMMountImageHandle:(906)
                [7724] [0x80070002] StateStoreRemoveMountedImage:(1041): The system cannot find the file specified.
                [7724] [0x80070002] WIMMountImageHandle:(1116): The system cannot find the file specified.
                2013-05-02 15:00:06, Error                 DISM   DISM WIM Provider: PID=7724 TID=4784 Failed to mount the image. - CWimImageInfo::Mount(hr:0xc1420127)
                2013-05-02 15:00:06, Error                 DISM   DISM WIM Provider: PID=7724 TID=4784 base\ntsetup\opktools\dism\providers\wimprovider\dll\wimmanager.cpp:2411 - CWimManager::InternalOpMount(hr:0xc1420127)
                2013-05-02 15:00:06, Error                 DISM   DISM WIM Provider: PID=7724 TID=4784 base\ntsetup\opktools\dism\providers\wimprovider\dll\wimmanager.cpp:3682 - CWimManager::InternalCmdMount(hr:0xc1420127)
                2013-05-02 15:00:06, Error                 DISM   DISM WIM Provider: PID=7724 TID=4784 Error executing command - CWimManager::InternalExecuteCmd(hr:0xc1420127)
                2013-05-02 15:00:06, Error                 DISM   DISM WIM Provider: PID=7724 TID=4784 base\ntsetup\opktools\dism\providers\wimprovider\dll\wimmanager.cpp:1928 - CWimManager::ExecuteCmdLine(hr:0xc1420127)
                2013-05-02 15:00:06, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.
                2013-05-02 15:00:06, Info                  DISM   DISM.EXE:
                2013-05-02 15:00:06, Info                  DISM   DISM.EXE: <----- Ending Dism.exe session ----->
                2013-05-02 15:00:06, Info                  DISM   DISM.EXE:
                2013-05-02 15:00:06, Info                  DISM   DISM Provider Store: PID=7724 TID=4784 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
                2013-05-02 15:00:06, Info                  DISM   DISM Provider Store: PID=7724 TID=4784 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
                2013-05-02 15:00:06, Info                  DISM   DISM Provider Store: PID=7724 TID=4784 Disconnecting Provider: WimManager - CDISMProviderStore::Internal_DisconnectProvider
                2013-05-02 15:00:06, Info                  DISM   DISM Provider Store: PID=7724 TID=4784 Disconnecting Provider: VHDManager - CDISMProviderStore::Internal_DisconnectProvider
                2013-05-02 15:00:06, Info                  DISM   DISM Provider Store: PID=7724 TID=4784 Disconnecting Provider: GenericImagingManager - CDISMProviderStore::Internal_DisconnectProvider
                2013-05-02 15:00:06, Info                  DISM   DISM Provider Store: PID=7724 TID=4784 Disconnecting Provider: Compatibility Manager - CDISMProviderStore::Internal_DisconnectProvider
                2013-05-02 15:00:06, Info                  DISM   DISM Provider Store: PID=7724 TID=4784 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
                 

                Updated on 2013-05-02T19:03:25Z at 2013-05-02T19:03:25Z by pgill
                • francesco.latino
                  francesco.latino
                  48 Posts
                  ACCEPTED ANSWER

                  Re: MDT 3.1 issues

                  ‏2013-05-03T07:10:21Z  in response to pgill

                  Hi, I experienced the same problem with a colleague running the same scenario at customer site and it was the McAfee antivirus not completely disabled.

                  I would please ask you to retry doublechecking no AntiVirus (AV) process running.

                  This is what he just said to me: probably the McAfee Antivirus is still blocking access in some ways

                  "
                  we ran the the command manually for one package at a time and it came back with access denied.
                  At that point we also thought AV was off but it wasn't - the security team just turned off access protection but write privileges was still not given to that directories.
                  so we asked security team to completely disable AV and stop running service and then we manually ran it again for the 1 package and it succeeded.
                  However when we kicked it off from the TEM console it failed again as the AV came on automatically after a while. I would suggest to doublecheck again that AV is absolutely down
                  "

                  I think this is what is causing the issue: may you please validate no AV running?


                  Running the same command should give access denied until completely stopped (and may be it will automatically restart after a while)

                   

                  Other info on the Web:

                  http://social.technet.microsoft.com/Forums/en-US/mdt/thread/fbbc45f7-9d21-4e29-a154-c85486bef856

                  • pgill
                    pgill
                    8 Posts
                    ACCEPTED ANSWER

                    Re: MDT 3.1 issues

                    ‏2013-05-03T14:19:29Z  in response to francesco.latino

                    I think you might be right:

                    5/2/2013 2:21:12 PM Would be blocked by Access Protection rule  (rule is currently not enforced) ------\xraygill C:\Windows\Explorer.EXE C:\Users\xraygill\AppData\Local\Temp\2\OSDeployment\uploadmanager.exe Common Standard Protection:Prevent common programs from running files from the Temp folder Action blocked : Execute
                    5/2/2013 2:21:12 PM Would be blocked by Access Protection rule  (rule is currently not enforced)  ------\xraygill C:\Windows\Explorer.EXE C:\Users\xraygill\AppData\Local\Temp\2\OSDeployment\zip.exe Common Standard Protection:Prevent common programs from running files from the Temp folder Action blocked : Execute

                    • francesco.latino
                      francesco.latino
                      48 Posts
                      ACCEPTED ANSWER

                      Re: MDT 3.1 issues

                      ‏2013-05-03T15:03:59Z  in response to pgill

                      Good ! Hope this will now fix the flow.

                      Let us know if still getting issues....

                      • pgill
                        pgill
                        8 Posts
                        ACCEPTED ANSWER

                        Re: MDT 3.1 issues

                        ‏2013-05-03T16:25:14Z  in response to francesco.latino

                        Yea, no, not the issue.

                        I spoke with our McAfee guy and he said : Would be blocked by Access Protection rule (rule is currently not enforced) means that it would have been blocked, but it is not.

                        DISM is giving me errors though:

                        2013-05-03 12:21:59, Info                  CBS    Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Users/xraygill/AppData/Local/Temp/2/tpm_C7A9D1B12E8EB957_1/Windows/System32/config/SOFTWARE
                        2013-05-03 12:21:59, Info                  CBS    Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Users/xraygill/AppData/Local/Temp/2/tpm_C7A9D1B12E8EB957_1/Windows/System32/config/SOFTWARE, the client may still need it open. [HRESULT = 0x80070005 - E_ACCESSDENIED]
                        2013-05-03 12:21:59, Info                  CBS    Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Users/xraygill/AppData/Local/Temp/2/tpm_C7A9D1B12E8EB957_1/Windows/System32/config/SYSTEM
                        2013-05-03 12:21:59, Info                  CBS    Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Users/xraygill/AppData/Local/Temp/2/tpm_C7A9D1B12E8EB957_1/Windows/System32/config/SYSTEM, the client may still need it open. [HRESULT = 0x80070005 - E_ACCESSDENIED]
                        2013-05-03 12:21:59, Info                  CBS    Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Users/xraygill/AppData/Local/Temp/2/tpm_C7A9D1B12E8EB957_1/Windows/System32/config/SECURITY
                        2013-05-03 12:21:59, Info                  CBS    Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Users/xraygill/AppData/Local/Temp/2/tpm_C7A9D1B12E8EB957_1/Windows/System32/config/SECURITY, the client may still need it open. [HRESULT = 0x80070005 - E_ACCESSDENIED]
                        2013-05-03 12:21:59, Info                  CBS    Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Users/xraygill/AppData/Local/Temp/2/tpm_C7A9D1B12E8EB957_1/Windows/System32/config/SAM
                        2013-05-03 12:21:59, Info                  CBS    Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Users/xraygill/AppData/Local/Temp/2/tpm_C7A9D1B12E8EB957_1/Windows/System32/config/SAM, the client may still need it open. [HRESULT = 0x80070005 - E_ACCESSDENIED]
                        2013-05-03 12:21:59, Info                  CBS    Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Users/xraygill/AppData/Local/Temp/2/tpm_C7A9D1B12E8EB957_1/Windows/System32/config/COMPONENTS
                        2013-05-03 12:21:59, Info                  CBS    Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Users/xraygill/AppData/Local/Temp/2/tpm_C7A9D1B12E8EB957_1/Windows/System32/config/COMPONENTS, the client may still need it open. [HRESULT = 0x80070005 - E_ACCESSDENIED]
                        2013-05-03 12:21:59, Info                  CBS    Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Users/xraygill/AppData/Local/Temp/2/tpm_C7A9D1B12E8EB957_1/Windows/System32/config/DEFAULT
                        2013-05-03 12:21:59, Info                  CBS    Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Users/xraygill/AppData/Local/Temp/2/tpm_C7A9D1B12E8EB957_1/Windows/System32/config/DEFAULT, the client may still need it open. [HRESULT = 0x80070005 - E_ACCESSDENIED]
                        2013-05-03 12:21:59, Info                  CBS    Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Users/xraygill/AppData/Local/Temp/2/tpm_C7A9D1B12E8EB957_1/Users/default/ntuser.dat
                        2013-05-03 12:21:59, Info                  CBS    Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Users/xraygill/AppData/Local/Temp/2/tpm_C7A9D1B12E8EB957_1/Users/default/ntuser.dat, the client may still need it open. [HRESULT = 0x80070005 - E_ACCESSDENIED]
                        2013-05-03 12:21:59, Info                  CBS    Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Users/xraygill/AppData/Local/Temp/2/tpm_C7A9D1B12E8EB957_1/Windows/system32/smi/store/Machine/schema.dat

                        • JasonHonda
                          JasonHonda
                          44 Posts
                          ACCEPTED ANSWER

                          Re: MDT 3.1 issues

                          ‏2013-05-03T16:35:02Z  in response to pgill

                          I still might question whether or not McAfee is still causing issues. Even if it says it's not causing issues, or that it's turned off, we commonly see it still having an impact, so I would very strongly recommend fully circumventing those security tools at least for this test. That is what most searches for the latest errors still point to.

                          At this point due to failed attempts, I might also recommend cleaning up past mounted WIMs.

                          dism /Get-MountedWimInfo

                          dism /Unmount-Wim /MountDir:c:\whateveryousawfromlastcommand /discard

                        • francesco.latino
                          francesco.latino
                          48 Posts
                          ACCEPTED ANSWER

                          Re: MDT 3.1 issues

                          ‏2013-05-06T06:41:41Z  in response to pgill

                          The best is to clean as Jason said

                          dism /Get-MountedWimInfo

                          dism /Unmount-Wim /MountDir:c:\whateveryousawfromlastcommand /discard

                           

                          And manually retry dism command: I expect it to fail independetly from our code

                          If you manually play with Dism, did you get similar failure ?

                          • pgill
                            pgill
                            8 Posts
                            ACCEPTED ANSWER

                            Re: MDT 3.1 issues

                            ‏2013-05-06T13:41:54Z  in response to francesco.latino

                            When I run even the "dism /Get-MountedWimInfo" command all I get is:

                            Deployment Image Servicing and Mangement tool
                            Version: 6.1.7600.16385

                            _

                            And that is it.

                            EDIT:

                            After a while it times out with: This application has requested the Runtime to terminate it in an unusal way.

                            With a pop up box for ServerAgentManager.exe : Application has generated an exception that could not be handled.

                            Updated on 2013-05-06T14:58:09Z at 2013-05-06T14:58:09Z by pgill
                            • IanRobertson
                              IanRobertson
                              2 Posts
                              ACCEPTED ANSWER

                              Re: MDT 3.1 issues

                              ‏2013-12-18T14:08:10Z  in response to pgill

                              I ran into this problem yesterday and found some compound problems.  One is a Tivoli bug, the other is an AV/Microsoft issue (McAfee in my case).  Both are independent but can contribute to the problem.

                              The most easily observed symptom is that the use of mdtbundlecreator fails. Depending upon how much deeper you dig into the various logs, you'll find lots of other errors.  Let me simplify this all and say if you encounter any errors running this tool, check and fix the items below.

                              The first problem I found was with the RBAgent utility and how it uses an environment variable.  The RBAgent utility, which is called by one of the scripts that is part of mdtbundlecreator, is passed a command line which includes the environment variable %temp%.  This variable points to the current user's temporary directory.  Normally this is something like "c:\users\<username>\AppData\Local\Temp".  The problem comes in when the username exceeds 8 characters, because then Windows has that named "c:\users\userna~1\AppData\Local\Temp".  When it's processed by the command line into RBAgent, it replaces the tilde character with a space, so it actually looks like "c:\users\userna 1\AppData\Local\Temp".  That directory is invalid, and it fails.

                              To check for this condition, type "echo %temp%" at the command line and see if it includes the tilde character. If it does, then before you run the utility, reset this variable by typing "set temp=c:\users\<full username>\AppData\Local\Temp".  After you do this you will need to run mdtbundlecreator from the same command-line window.

                              The second issue I found was with McAfee's access protection.  There are reports above here that talk about logs saying "would be blocked, but it isn't", but this issue has nothing to do with that, it's a separate McAfee/AV issue.  Essentially it boils down to a check that McAfee does to a really broken Windows API call that Microsoft can't fix (or it will break a bunch of stuff).  The solution is to temporarily disable Access Protection in McAfee (or any other AV product that does a similar check) when you run mdtbundlecreator.  And as another commenter reported, this will re-enable itself, so make sure it is disabled for the entire time that you are running the utility.  More information can be found at these two URLs:

                              https://kc.mcafee.com/corporate/index?page=content&id=KB76867&actp=LIST

                              https://kc.mcafee.com/corporate/index?page=content&id=KB52204

                              I hope this is helpful for those who are trying to use this feature and are pulling out their hair!

                              • sergio.tarchi
                                sergio.tarchi
                                20 Posts
                                ACCEPTED ANSWER

                                Re: MDT 3.1 issues

                                ‏2014-02-18T13:20:36Z  in response to IanRobertson

                                Hi,

                                in my environment I use the Administrator user to create the MDT bundle and the temp directory is the following:

                                C:\Users\Administrator\Desktop\MDTBundleCreator-3.2.20>echo %temp%
                                C:\Users\ADMINI~1\AppData\Local\Temp

                                I launched the creation from the desktop

                                C:\Users\Administrator\Desktop\MDTBundleCreator-3.2.20>MDTBundleCreator.exe

                                and in parameters.ini I have

                                target=C:\Users\Administrator\Desktop\BigFixOSD

                                but I'm able to successfully build an MDT bundle 3.2.20

                                Do you see any difference from your environment? Could you please attach logs (setup.log file in the MDT bundle creatore folder)?

                                Thanks.

                                • IanRobertson
                                  IanRobertson
                                  2 Posts
                                  ACCEPTED ANSWER

                                  Re: MDT 3.1 issues

                                  ‏2014-02-18T13:41:42Z  in response to sergio.tarchi

                                  Sergio,

                                  I can save you some time and tell you that what I observed is the output from the RBAgent utility shows a space in the filepath where the tilde character is.  When it tries to read the file in that directory, the path is wrong and it fails.  Review the code for the RBAgent utility and I believe you'll find a bug there.

                                  Ian

                                   

                                  • sergio.tarchi
                                    sergio.tarchi
                                    20 Posts
                                    ACCEPTED ANSWER

                                    Re: MDT 3.1 issues

                                    ‏2014-02-18T13:55:48Z  in response to IanRobertson

                                    Hi. Thanks. It would be useful to be able to reproduce the error condition to know which is the code part to review and where that output has been originated from. Would it be possible for you to collect the log file and compare the conditions where the error occurred?

                                    Thanks.