I have just set up my WDS server and Deployment workbench on a 2012 R2 x64 server. Everything seems to be working but when I go to edit the Unattend.xml file I get the following error. I can open the task sequence and go through everything just fine but when I try to access the Unattend it is a no go.
Performing the operation "generate" on target "Catalog".
Starting: "C:\Program Files\Microsoft Deployment Toolkit\Bin\Microsoft.BDD.Catalog40.exe" "C:\Deployment Shares\Deployment Share 2\Operating Systems\Win 7 Pro UWO Install 020314\install020314.wim" 1 > "C:\Users\user\AppData\Local\Temp\Microsoft.BDD.Catalog.log" 2>&1
No existing catalog file found.
PROGRESS: 0: Starting.
PROGRESS: 0: Creating mount folder: C:\Users\user\AppData\Local\Temp\IMGMGR_install020314_Win 7 Pro_gaccmvfb.pvc.
PROGRESS: 5: Creating temp folder: C:\Users\user\AppData\Local\Temp\IMGMGR_install020314_temp_szufyizb.tyg.
PROGRESS: 10: Mounting Windows image: C:\Deployment Shares\Deployment Share 2\Operating Systems\Win 7 Pro UWO Install 020314\install020314.wim. This might take a few minutes.
ERROR: Unable to generate catalog on C:\Deployment Shares\Deployment Share 2\Operating Systems\Win 7 Pro UWO Install 020314\install020314.wim: System.ComponentModel.Win32Exception (0x80004005): The process cannot access the file because it is being used by another process
Non-zero return code from catalog utility, rc = 2002
I have read stuff about not being able to use a 32bit on a 64bit system, but the image is only for 64bit machines as we don't have any 32bit machines. I am not sure if maybe I did something wrong along the way. I did notice that it says that file is being used by another process but I have no idea what it could be.
If anyone has any insight to this error help would be appreciated.
Thanks in advance,