Trying to setup a test environment for E10 and when I am creating the App server I keep getting the error Dism Image Servicing Utility has stopped working. I have all the required roles and features, and even got a different dl file from my live environment, registered it and still getting the error. Anyone else have any ideas?
Problem signature:
Problem Event Name: APPCRASH
Application Name: Dism.exe
Application Version: 6.2.9200.16384
Application Timestamp: 5010a2ae
Fault Module Name: dismprov.dll
Fault Module Version: 6.2.9200.16384
Fault Module Timestamp: 5010a27e
Exception Code: c0000005
Exception Offset: 0000000000012b4a
OS Version: 6.2.9200.2.0.0.272.7
Locale ID: 1033
Additional Information 1: 494b
Additional Information 2: 494bad0aa68bb58c39f44fbf01489817
Additional Information 3: 0f8c
Additional Information 4: 0f8c60a3b0cac05ef0e09211738f43ae
The exception code is referring to not having the rights to either read or write to a file. Any ideas on what this may be?
Hi William! Have you solved this? Curious as I’ve never seen that behaviour when deploying AppServers.
I saw this before when I was working on a Docker Image for ERP and it was due to pending windows updates requiring a restart. DISM is used to setup WCF Try this command manually
DISM.EXE /Online /Add-Package /PackagePath:C:\Microsoft-Windows-NetFx3-OnDemand-Package.cab
You can also utilise SysInternal Tools to see the process that is being spawned to see what environmental issues you may have.
@PatoMtz No I have not.
@Edge Thanks for the reply. I ran what you mentioned ina an elevated CMD prompt and got an error trying to open the CAB file. Error: 0X80070003 So guess I will run this one down and see what is going on.
I could never get .NET 3.x in 2012 R2 and 2016 to Install from Online… I always ended up having to have access to the CD/DVD Sources of the Windows Image and run:
@Will79 Make sure you have the right Path, Stephen was just giving you a boilerplate.
Yeah, noticed that. Too early in the morning for me! LOL!
Fixed! Jsut uninstalled and reinstalled the Net 3.5 (aout 3 times) and it fixed the issue.