# Dell Repository Manager - ISO Creation Failed

## Servers

Information and ideas on Dell PowerEdge rack, tower and blade server solutions.

#### Dell Repository Manager - ISO Creation Failed

I'm trying to use the Dell Repository Manger (v1.4.104) to create a bootable ISO.  My client machine is Windows 7 64bit.  When I select the bundles I wish to export and click Finish, the progress window pops up and displays "Extracting Dell Deployment Media plug-in ..."

An error then pops up and says:

Bootable ISO creation failed with error:
Unknown
For more details refer to the runtime log at C:\Users\<username>\AppData\Local\RepositoryManager\Log

Looking at the log file provides no extra information about the error.  I've even tried using procmon.exe to see if there are missing files or permissions problems and haven't found anything useful.

Any help is appreciated.

Thanks,
Sean

 Like 0
All Replies
• Hi, We're also having this problem.

Bootable ISO creation failed with error:

The remote name could not be resolved: 't'

For more details refer to the runtime log at C:\Users\<username>\AppData\Local\RepositoryManager\Log

Thanks,

 Like 0
• thats an odd message,, seems more like a connection issue getting out through the network, but it still would not work anyway at this time. I'll have a solid update next week once some internal dates are solidified.

 Like 0
• I am getting the same error, using DRM 1.4.104 on Win 7 64-bit (and also tried on Win XP).  I am exporting latest system bundle for M610.

If you save the repository before the export, then the error in the log file has more information:

"LoadSaveReceiver.SaveRepositoryRefreshInfo: Error saving repository refresh information to file: Object reference not set to an instance of an object."

 Like 0
• Actually, it looks like the error about saving the repository is unconnected to the export to bundle problem - the timestamp on that error is earlier than the timestamp of the export bundle error, so perhaps this is a seperate issue that happened silently when I saved the repo?

 Like 0
• I succeeded exporting to iso using a windows xp client, seems like repository manager is bugged on Windows seven.

 Like 0
• Hi all,

I to am having this very same issue on my x64 Win 7 laptop. The Log file reports:

xmlns="http://schemas.microsoft.com/2004/06/E2ETraceEvent"><System xmlns="http://schemas.microsoft.com/2004/06/windows/eventlog/system"><EventID>0</EventID><Type>3</Type><SubType Name="Error">0</SubType><Level>2</Level><TimeCreated SystemTime="2012-02-20T15:32:24.2192732Z" /><Source Name="RepositoryManager.exe" /><Correlation ActivityID="{00000000-0000-0000-0000-000000000000}" /><Execution ProcessName="RepositoryManager" ProcessID="5560" ThreadID="1" /><Channel/><Computer>XXXXXXXXXX</Computer></System><ApplicationData>AdvancedExportBundleToISO.GetProgress: Error creating ISO image: </ApplicationData></E2ETraceEvent>

Has anyone found a solution that doesn't involve Windows XP?

 Like 0
• we are working this from 2 angles, we are going to be updating the catalog on the ftp site and we are investigating why some windows 7 users systems work and some do not. I am one of the users that has a problem with windows 7.

 Like 0
• Excellent, As another affected Win7 user please let me know if I can help

 Like 0
• OK, just downloaded and installed on a WinXP client and tried again. Gets as far as 'exporting selected bundles to a bootable ISO. Downloaded 1 / 64 and then bombs out (this is a little further than Win7 gets) with:

Bootable ISO creation failed with error:

The remote name could not be resolved: 'c'

For more details refer to the runtime log at C:\Documents and Settings\xxxxxxxx\Local Settings\Application Data\RepositoryManager\Log

And the Log file says (long one this):

 Like 0
• TisorkA, our RM developer looked at your logs, and there is a problem  in the version of RM that you are using AND he says your proxy is not configured correctly. The good news is that they have created a newer version of RM 1.4.113 that will resolve some of the problems that are being seen. The new version of Repository Manager can be downloaded at this location until the files are posted on the support site, which is in process. Also at this location is a folder called Fixed Bios. In this folder are the .bin, .sign and .exe bios files for the R710, R810 and R910. These bios files can be imported into RM so that the bios for these systems can be updated to the latest version that is on the support site. These same bios are NOT in the ftp catalog at this time, but we are working on that as well.

http://dtxdropbox.dell.com

Also, some of  you (like me) were having problems when running RM on Windows 7. The RM guy looked at my system and determined that my .Net 4 files were incomplete and re-installed .Net 4 and all is working properly now. This makes sense to me as our IT pushed out a .Net 4 update (KB2656351) on January 11th and I know my RM was working the week after Xmas and failed some time soon after that. I would be interested to know how this new version of RM works on your systems, and please be careful with the .Net re-install (if you do it) and perhaps even get permission from your IT team before doing so.

 Like 0
• Dell-Rey G - GOOD NEWS. I've downloaded the new RM and installed (having uninstalled the previous version and deleted all repository's) and then re-installed .Net 4 and................. ISO Successfully created on a Win 7 64 bit client.

Big thanks to all that helped with this, my R710's are getting flashed tonight

 Like 0
• I'm getting a similar problem trying to download the v410 release of patches for PER815 and create a Deployment media.

Bootable ISO creation failed with error: Downloader is not able to verify the signature of 'http://ftp.dell.com/FOLDER51863M/1/FRMW_LX_R310829.BIN'For more details refer to the runtime log at C:\Users\MPeters\AppData\Local\RepositoryManager\Log

I've tried from different PC's and I'm running 1.4.113

Any ideas?
 Like 0
• Did you have existing repository's on these PC's?

 Like 0
• I didn't, 2 of the three I tried were clean installs.

 Like 0
• I'm checking on this right now, brb.

 Like 0