+ Reply to Thread
Results 1 to 7 of 7

Thread: DISM error

  1. Member
    Join Date
    Jun 2010
    Posts
    49

    Certifications
    A+, Network+, Security+, 70-680, 70-642
    #1

    Default DISM error

    Hi am currently reading through chapter 3 of the official microsoft book for 70-680 and having a bit of a problem getting one of the commands to work.

    i have completed excerise 1 for lesson 1 and results from dism/ get-mountedwiminfo are fine


    I then tried to complete exercise 2, created c:\mypackages, c:\scratch and added the lp_en-us cab file to my packages.

    Then i type in the command dism /image:c:\mountedimages /scratchdir:c:\scratch /add-package /packagepath:c:\mypackages\lp_en-us.cab and get an error 2 message:


    I have tried unmounting and mounting the image several times but keep getting the same error. Also deleted all the folders, and created them again.

    I also have a problem when i type in the command without the add package part. (similar to the one i originally had the problem with on page 120

    dism /image:c:\mountedimages /scratchdir:c\scratch

    error 1639


    Not sure what else to try, have made sure i open the deployment tools command prompt in administrator mode. Also mine will differ slightly from the example as my image is located on c drive not d drive as dont have second hard disk.
    Reply With Quote Quote  

  2. SS -->
  3. Member
    Join Date
    Feb 2010
    Location
    Lithuania-Vilnius
    Posts
    74

    Certifications
    MCTS: 70-680, 70-685, 70-432
    #2
    First - get errata pages for this book. It contains a lot of typos. I remember myself doing dism practice tests. Doing and cursing, because "it's all in the details" .
    At the moment I don't have dism at hand, but for excercise 2 - have you tried to type capital C?
    dism /image:C:\mountedimages /scratchdir:C:\scratch /add-package /packagepath:C:\mypackages\lp_en-us.cab
    For the excercise 3 I would suggest the same capital C after scratch flag.
    dism /image:C:\mountedimages /scratchdir:C:\scratch

    As command line states, something is wrong with a path you are typing. In http://technet.microsoft.com/en-us/l...82(WS.10).aspx
    you'll also find that, path is wrote with capital "C" - "Dism /image:C:\test\offline".
    However, I might be completely wrong.
    p.s. you do have read/write permissions on the folder ..."\mountedimages"?
    Last edited by Matt27[lt]; 08-23-2010 at 01:29 PM.
    Reply With Quote Quote  

  4. Member
    Join Date
    Jun 2010
    Posts
    49

    Certifications
    A+, Network+, Security+, 70-680, 70-642
    #3
    despite the rediculous amount of errors on the errata page i can't seem to find any related to this.

    I have read and write permissions for all the folders i created as well as normal vhd users. When run as admin i have all. Have tried putting C instead of c but get the same result.

    Heres the log report if you can make any sense of it lol.
    2010-08-23 13:59:23, Info DISM PID=1752 Scratch directory set to 'C:\Users\James\AppData\Local\Temp\'. - CDISMManager:ut_ScratchDir
    2010-08-23 13:59:23, Info DISM PID=1752 Scratch directory set to 'C:\scratch'. - CDISMManager:ut_ScratchDir
    2010-08-23 13:59:23, Info DISM PID=1752 Successfully loaded the ImageSession at "C:\Program Files\Windows AIK\Tools\AMD64\Servicing" - CDISMManager::LoadImageSession
    2010-08-23 13:59:23, Info DISM DISM Provider Store: PID=1752 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
    2010-08-23 13:59:23, Info DISM DISM Provider Store: PID=1752 Failed to get and initialize the PE Provider. Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
    2010-08-23 13:59:23, Info DISM DISM Provider Store: PID=1752 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
    2010-08-23 13:59:23, Info DISM DISM Provider Store: PID=1752 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
    2010-08-23 13:59:23, Info DISM DISM Provider Store: PID=1752 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
    2010-08-23 13:59:23, Info DISM DISM Provider Store: PID=1752 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
    2010-08-23 13:59:23, Info DISM DISM Provider Store: PID=1752 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
    2010-08-23 13:59:23, Info DISM DISM Manager: PID=1752 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
    2010-08-23 13:59:23, Info DISM DISM Provider Store: PID=1752 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
    2010-08-23 13:59:23, Info DISM DISM Provider Store: PID=1752 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
    2010-08-23 13:59:23, Info DISM DISM.EXE:
    2010-08-23 13:59:23, Info DISM DISM.EXE: <----- Starting Dism.exe session ----->
    2010-08-23 13:59:23, Info DISM DISM.EXE:
    2010-08-23 13:59:23, Info DISM DISM.EXE: Host machine information: OS Version=6.1.7600, Running architecture=amd64, Number of processors=1
    2010-08-23 13:59:23, Info DISM DISM.EXE: Executing command line: dism /image:C:\mountedimages /scratchdir:C:\scratch /add-package /packagepath:c:\mypackages\lp_en-us.cab
    2010-08-23 13:59:23, Info DISM DISM Provider Store: PID=1752 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
    2010-08-23 13:59:23, Info DISM DISM Provider Store: PID=1752 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
    2010-08-23 13:59:23, Info DISM DISM Provider Store: PID=1752 Loading Provider from location C:\Program Files\Windows AIK\Tools\AMD64\Servicing\WimProvider.dll - CDISMProviderStore::Internal_GetProvider
    2010-08-23 13:59:23, Info DISM DISM Provider Store: PID=1752 Connecting to the provider located at C:\Program Files\Windows AIK\Tools\AMD64\Servicing\WimProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2010-08-23 13:59:23, Info DISM DISM Provider Store: PID=1752 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
    2010-08-23 13:59:23, Info DISM DISM Provider Store: PID=1752 Loading Provider from location C:\Program Files\Windows AIK\Tools\AMD64\Servicing\FolderProvider.dll - CDISMProviderStore::Internal_GetProvider
    2010-08-23 13:59:23, Info DISM DISM Provider Store: PID=1752 Connecting to the provider located at C:\Program Files\Windows AIK\Tools\AMD64\Servicing\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2010-08-23 13:59:23, Info DISM DISM Provider Store: PID=1752 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
    2010-08-23 13:59:23, Info DISM DISM Provider Store: PID=1752 Loading Provider from location C:\Program Files\Windows AIK\Tools\AMD64\Servicing\CompatProvider.dll - CDISMProviderStore::Internal_GetProvider
    2010-08-23 13:59:23, Info DISM DISM Provider Store: PID=1752 Connecting to the provider located at C:\Program Files\Windows AIK\Tools\AMD64\Servicing\CompatProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2010-08-23 13:59:23, Info DISM DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
    2010-08-23 13:59:23, Info DISM DISM.EXE: Attempting to add the commands from provider: WimManager
    2010-08-23 13:59:23, Info DISM DISM.EXE: Succesfully registered commands for the provider: WimManager.
    2010-08-23 13:59:23, Info DISM DISM.EXE: Attempting to add the commands from provider: FolderManager
    2010-08-23 13:59:23, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
    2010-08-23 13:59:23, Info DISM DISM.EXE: Attempting to add the commands from provider: Compatibility Manager
    2010-08-23 13:59:23, Info DISM DISM.EXE: Succesfully registered commands for the provider: Compatibility Manager.
    2010-08-23 13:59:23, Error DISM DISM.EXE: Failed to access the image folder or image's windows folder.
    2010-08-23 13:59:23, Info DISM DISM.EXE: Image session has been closed. Reboot required=no.
    2010-08-23 13:59:23, Info DISM DISM.EXE:
    2010-08-23 13:59:23, Info DISM DISM.EXE: <----- Ending Dism.exe session ----->
    2010-08-23 13:59:23, Info DISM DISM.EXE:
    2010-08-23 13:59:23, Info DISM DISM Image Session: PID=1752 Disconnecting the provider store - CDISMImageSession::Final_OnDisconnect
    2010-08-23 13:59:23, Info DISM DISM Provider Store: PID=1752 Disconnecting Provider: WimManager - CDISMProviderStore::Internal_DisconnectProvider
    2010-08-23 13:59:23, Info DISM DISM Provider Store: PID=1752 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
    2010-08-23 13:59:23, Info DISM DISM Provider Store: PID=1752 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
    2010-08-23 13:59:23, Info DISM DISM Provider Store: PID=1752 Disconnecting Provider: Compatibility Manager - CDISMProviderStore::Internal_DisconnectProvider
    2010-08-23 13:59:23, Info DISM DISM Provider Store: PID=1752 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProvider

    Thanks for help. The first couple of chapters of this book are driving me insane...

    (its putting a smiley instead of : p btw)
    Last edited by xSequentialx; 08-23-2010 at 02:08 PM.
    Reply With Quote Quote  

  5. Member
    Join Date
    Feb 2010
    Location
    Lithuania-Vilnius
    Posts
    74

    Certifications
    MCTS: 70-680, 70-685, 70-432
    #4
    ok. I'm at home and will try to reproduce your problem. First chapters? I did them at the end . Started from familiar features. If it drives you insane, skip it for now. Do something else. Come back later.
    when you mounted image, what rights you gave to it? You can mount with read-only rights. Just guessing
    Last edited by Matt27[lt]; 08-23-2010 at 04:39 PM.
    Reply With Quote Quote  

  6. Member
    Join Date
    Jun 2010
    Posts
    49

    Certifications
    A+, Network+, Security+, 70-680, 70-642
    #5
    Thanks i would really appreciate that.

    I have read the sybex book but found it to be very light on detail compared to the microsoft book which i have just started now. If anything i am finding myself doing a lot of research on the tech sites to add to the microsoft book so the sybex book will probably be pretty useless.

    Just taking chapters 2 and 3 in particular very slow and gathering all the info and putting it into a word document so can study from that, just doesn't help with all the errors, and can be pretty overwhelming at times.

    Regarding the problem its no biggie if i can't find a solution as long as i know that it normally works for most people and what it does.

    Thanks again for the help
    Reply With Quote Quote  

  7. Member
    Join Date
    Feb 2010
    Location
    Lithuania-Vilnius
    Posts
    74

    Certifications
    MCTS: 70-680, 70-685, 70-432
    #6
    I'll be back after 2-3 hours. Image mounting process started. After it's finished. I'll try to do some commands.
    again. when you mounted image, what rights you gave to it?

    Ok. Error 1639 (example 3). You have to put "/add-package /packagepath:c:\mypackages\lp_en-us.cab" or something in the end of command line. I tested with *.cab file and works for me.

    For example 2 found suggestions to disable (temp) antivirus. http://social.technet.microsoft.com/...e-f1c396d25752
    It's your decision, though.

    Example 2. Worked for me too and I haven't to disable antivirus. Right now I'm out of option. I also manually gave ...\mountedimages\ write permissions. Not for admin, but for local user name I'm logging in. (Matt27[lt]).
    So:
    1. Mounted image without "read-only" flags.
    2. Granted "write" permissions to the folder mounted images.
    3. Added packages without a problem.
    Last edited by Matt27[lt]; 08-23-2010 at 05:22 PM.
    Reply With Quote Quote  

  8. Member
    Join Date
    Jun 2010
    Posts
    49

    Certifications
    A+, Network+, Security+, 70-680, 70-642
    #7
    Regarding error 1639 it seems that you do need the extra options. Just seems silly to include it on page 120 as dism /image:c:\mountedimages /scratchdir:c:\workingfiles

    I don't have antivirus installed on this virtual pc yet so can't be that. It has read/write permissions when mounted as shown in the first screenshot and have added write permission to all users that didn't have it even though ran the command prompt with admin.

    As long as it works for you then thats all i need to remember. Just wanted to make sure that it actually worked and wasnt an error in the book.

    Thanks
    Reply With Quote Quote  

+ Reply to Thread

Social Networking & Bookmarks