AltaSens
asked on
Windows System Image Manager : Unknown Error 0xC1420127 when attempting to create WIM catalog
I am using the Windows Automated Installation Kit (WAIK) for Windows 7 running on Windows Server 2008R2 SP1.
I have two Windows 7 SP1 x64 images which I exported from the WDS server in my lab; both images were created from the same reference image. On my new production WDS server, when I open the first of the WIM files WSIM tells me there is no catalog and asks if I want to create one. I choose YES, WSIM works as expected and creates the new catalog file.
When I open the second WIM file, WSM again asks me if I want to create a new catalog file. I choose YES and this time WSIM generates an error: "Windows SIM was unable to generate a catalog. Unknown Error (0xC1420127)"
I am using WSIM x64 version 6.1.7600.16385 – can’t recall now if I installed the WAIK supplement for Win7S SP1
Here is the log file:
1:53 PM :
1:53 PM : Windows SIM was unable to generate a catalog. For troubleshooting assistance, see the topic: 'Windows System Image Manager Technical Reference' in the Windows OPK or Windows AIK User's Guide.
1:53 PM :
1:53 PM : System.ComponentModel.Win3 2Exception : Unknown error (0xc1420127)
Server stack trace:
at Microsoft.ComponentStudio. ComponentP latformInt erface.Wim ImageInfo. PreCreateC atalog()
at Microsoft.ComponentStudio. ComponentP latformInt erface.Off lineImageI nfo.Create Catalog()
at Microsoft.ComponentStudio. ComponentP latformInt erface.Cat alogCreato rImpl.Crea teCatalog( OfflineIma geInfo offlineImageInfo)
at System.Runtime.Remoting.Me ssaging.St ackBuilder Sink._Priv ateProcess Message(In tPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
at System.Runtime.Remoting.Me ssaging.St ackBuilder Sink.SyncP rocessMess age(IMessa ge msg, Int32 methodPtr, Boolean fExecuteInContext)
Exception rethrown at [0]:
at System.Runtime.Remoting.Pr oxies.Real Proxy.Hand leReturnMe ssage(IMes sage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Pr oxies.Real Proxy.Priv ateInvoke( MessageDat a& msgData, Int32 type)
at Microsoft.ComponentStudio. ComponentP latformInt erface.ICa talogCreat or.CreateC atalog(Off lineImageI nfo offlineImageInfo)
at Microsoft.ComponentStudio. CatalogGen erator.Cre ateCat(Pro gressDialo g pd, Object o)
I have seen references to this same WSIM error and some solutions suggested placing the WIM file on the same volume as the OS, which I have done. I have also verified these two WIM files have the same exact file permissions.
This did work in the past on my lab WDS server, a while back I created an unattend.xml file for this WIM and successfully used the lab WDS server to deploy this image.
Any ideas here?
Thanks in advance for the help!
I have two Windows 7 SP1 x64 images which I exported from the WDS server in my lab; both images were created from the same reference image. On my new production WDS server, when I open the first of the WIM files WSIM tells me there is no catalog and asks if I want to create one. I choose YES, WSIM works as expected and creates the new catalog file.
When I open the second WIM file, WSM again asks me if I want to create a new catalog file. I choose YES and this time WSIM generates an error: "Windows SIM was unable to generate a catalog. Unknown Error (0xC1420127)"
I am using WSIM x64 version 6.1.7600.16385 – can’t recall now if I installed the WAIK supplement for Win7S SP1
Here is the log file:
1:53 PM :
1:53 PM : Windows SIM was unable to generate a catalog. For troubleshooting assistance, see the topic: 'Windows System Image Manager Technical Reference' in the Windows OPK or Windows AIK User's Guide.
1:53 PM :
1:53 PM : System.ComponentModel.Win3
Server stack trace:
at Microsoft.ComponentStudio.
at Microsoft.ComponentStudio.
at Microsoft.ComponentStudio.
at System.Runtime.Remoting.Me
at System.Runtime.Remoting.Me
Exception rethrown at [0]:
at System.Runtime.Remoting.Pr
at System.Runtime.Remoting.Pr
at Microsoft.ComponentStudio.
at Microsoft.ComponentStudio.
I have seen references to this same WSIM error and some solutions suggested placing the WIM file on the same volume as the OS, which I have done. I have also verified these two WIM files have the same exact file permissions.
This did work in the past on my lab WDS server, a while back I created an unattend.xml file for this WIM and successfully used the lab WDS server to deploy this image.
Any ideas here?
Thanks in advance for the help!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
AltaSens--You are welcome!
ASKER