Hello nampnx

Is there any way to bypass some failed files (components) to continute export SUU and download failed files?

You would have to create a new bundle that excluded the failed files. If you go to the Components tab it has a check list of all of the files in the selected bundles. You can uncheck the problem files and choose the option +New Bundle. This will create a new bundle from the selected files in the component list.

I'm creating an SUU right now to try to reproduce the problem. Do you have a list of the problem file(s)?

Thanks

Is there bug in this version or in Dell Repository on the internet ?

I just created the bundles without issue. The problem appears to be with the application installed on your system. I would suggest uninstalling Repository Manager and reinstalling it.

Thanks

Hi DELL-DANIEL,

I exported many bundles for m610, m620, m710, r620, r720xd (firmware, bios, driver). I already deleted failed components in bundles but many failed files. When deleted one component, the others failed so i could not delete them all.

Some components failed: SAS-Drive_Firmware_DVKMP_LN_AS09_A07.BIN, Lifecycle-Controller_Application_GFFFC_LN_1.6.0.73_A00.BIN, Network_Firmware_KTT4W_LN_14.5.8_A00.BIN, SAS-RAID_Firmware_F96NR_LN_6.3.3-0002_X00.BIN, SAS-Drive_Firmware_5CX8G_LN_DE09_A04.BIN.

Is there bug in this version or in Dell Repository on the internet ?

Windows bundles i exported OK but Linux did not work well. Would you help me?

Thanks,

nampnx

Hi DELL-DANIEL,

I already uninstalled and reinstalled this software many times. Did you export bundles OK? How many bundles did you export?

And Is there any way to export SUU not using Dell Repository Manager?

Thanks,

nampnx

I'm having the same issues as NAMPNX

SUU creation failing because of missing files with RM 1.8

Job Result:
Processing failed: Error downloading some files:
SAS-Non-RAID_Firmware_FCR14_WN32_00.10.51.00.06.12.05.00_A05.EXE

I've also checked the logs from exporting the repository and here's the list of the files that fails download.

Files failed to download:
SAS-NON-RAID_FIRMWARE_FCR14_WN32_00.10.51.00.06.12.05.00_A05.EXE
SAS-RAID_DRIVER_37P90_WN32_2.0.35.10_A01.EXE
SAS-RAID_DRIVER_R1K3J_WN32_4.31.1.64_A02.EXE
SAS-NON-RAID_DRIVER_D2P2F_WN32_2.0.35.10_A03.EXE
VIDEO_DRIVER_08MVF_WN32_4.00.01.004_1.0.EXE
POWER_FIRMWARE_JKR9J_WN32_07.09.40_X00.EXE
POWER_FIRMWARE_RD4NT_WN32_07.2B.7D_A00-01.EXE
SERIAL-ATA_FIRMWARE_WM0W0_WN32_MA10_A05.EXE
TAPE-DRIVES_FIRMWARE_PNNJF_WN32_BBNB_A03.EXE
ESM_FIRMWARE_FMWT1_WN32_1.01_A01.EXE
SAS-RAID_DRIVER_CN08G_WN32_2.24.0.64_A07.EXE
SAS-NON-RAID_DRIVER_KPWH9_WN32_1.28.03.01_A07.EXE
SAS-RAID_FIRMWARE_G5TG7_WN32_00.25.47.00.06.22.03.00_A04.EXE
SAS-RAID_DRIVER_8VMD9_WN32_1.28.03.01_A06.EXE
SAS-RAID_FIRMWARE_RPCKX_WN32_2.0.0-016600193000_A06.EXE
SAS-RAID_DRIVER_4JY9T_WN32_2.0.0.0162_A05.EXE
SAS-RAID_DRIVER_68C7G_WN32_1.28.03.01_A02.EXE
SAS-RAID_FIRMWARE_8VM7T_WN32_5.2.2-0076_A11.EXE
SAS-RAID_DRIVER_5F0HG_WN32_2.14.0.32_A06.EXE
SAS-RAID_FIRMWARE_C1NFP_WN32_00.25.47.00.06.22.03.00_A04.EXE
TAPE-DRIVES_FIRMWARE_6M7KV_WN32_BBNBBBH5_A09.EXE
TAPE-DRIVES_FIRMWARE_H2PMX_WN32_BBH4_A13.EXE
TAPE-DRIVES_FIRMWARE_GWRJX_WN32_BBNB_A04.EXE
ESM_FIRMWARE_V8Y6N_WN32_1.10_A00.EXE
VIDEO_DRIVER_DF4D9_WN32_276.14_X04.EXE
SAS-RAID_FIRMWARE_2RPK0_WN32_5.2.2-0072_A09.EXE
SAS-NON-RAID_FIRMWARE_FM3PW_WN32_00.10.51.00.06.12.05.00_A04.EXE

I've even tried to download the files manually and place them in the correct folders, but RM just ignores this.

Repository contains the following System bundles for x32, x64 and Linux:

PE2950, PER410, PER510, PER710, PER720XD, PER820

-VegardH

 

I just created the SUU ISOs again without issue. I created 32 and 64 bit Linux SUU ISOs for the M610, M620, M710, R620, and R720XD. I encountered no issues. If you are still having problems then please delete your local repository manager folder and restart repoman. You can find the local files by going to Application>Settings>File Store.

VergardH, you state that you are creating a linux repository, but all of the files it is failing to download are Windows files. I'm not sure what you are doing.

Thanks

Canada

Here's the svlog file content maybe it could help

0 3 0 2 W7 DownloadBase.CheckSecurity: Digital signature verification error for 'ftp://ftp.dell.com/FOLDER00416461M/1/SAS-Non-RAID_Firmware_FCR14_WN32_00.10.51.00.06.12.05.00_A05.EXE' 0 3 0 2 W7 Downloader.Download: [WebException][Downloader] -> [Download File] -> The remote server returned an error: (550) File unavailable (e.g., file not found, no access).: ftp.dell.com\FOLDER01685163M\1\SAS-Drive_Firmware_5CX8G_WN32_DE09_A04.EXE   at System.Net.FtpWebRequest.SyncRequestCallback(Object obj)   at System.Net.FtpWebRequest.RequestCallback(Object obj)   at System.Net.CommandStream.Dispose(Boolean disposing)   at System.IO.Stream.Close()   at System.IO.Stream.Dispose()   at System.Net.ConnectionPool.Destroy(PooledStream pooledStream)   at System.Net.ConnectionPool.PutConnection(PooledStream pooledStream, Object owningObject, Int32 creationTimeout, Boolean canReuse)   at System.Net.FtpWebRequest.FinishRequestStage(RequestStage stage)   at System.Net.FtpWebRequest.SyncRequestCallback(Object obj)   at System.Net.FtpWebRequest.RequestCallback(Object obj)   at System.Net.CommandStream.Abort(Exception e)   at System.Net.CommandStream.CheckContinuePipeline()   at System.Net.FtpWebRequest.DataStreamClosed(CloseExState closeState)   at System.Net.FtpDataStream.System.Net.ICloseEx.CloseEx(CloseExState closeState)   at System.Net.FtpDataStream.Dispose(Boolean disposing)   at System.IO.Stream.Close()   at DownloadManager.DownloadBase.CopyStreamToStream(Stream readStream, Stream writeStream, String strDownloadTotalKey, Int32 iChunkSize, String& strError) in d:\Jenkins_RepoMgr\workspace\RepositoryManager180\src\Libraries\DownloadManager\DownloadBase.cs:line 445   at DownloadManager.DownloadBase.DownloadFile(String strSourceFile, String strDestFile, Boolean bWebFile, WebClient& downloadClient, String& strError) in d:\Jenkins_RepoMgr\workspace\RepositoryManager180\src\Libraries\DownloadManager\DownloadBase.cs:line 313   at DownloadManager.DownloadBase.ProcessTempFile(Boolean bWebFile, Token token, String strSourceFile) in d:\Jenkins_RepoMgr\workspace\RepositoryManager180\src\Libraries\DownloadManager\DownloadBase.cs:line 477   at DownloadManager.FtpCopy.CopyHelper(Token token, Boolean bAsync) in d:\Jenkins_RepoMgr\workspace\RepositoryManager180\src\Libraries\DownloadManager\FtpCopy.cs:line 33   at DownloadManager.FtpCopy.CopyAsync(Token token) in d:\Jenkins_RepoMgr\workspace\RepositoryManager180\src\Libraries\DownloadManager\FtpCopy.cs:line 51   at DownloadManager.Downloader.Download(Token token, Protocol protocol, Boolean bAsync) in d:\Jenkins_RepoMgr\workspace\RepositoryManager180\src\Libraries\DownloadManager\Downloader.cs:line 400

I'm going to have to test this on an external network. We may be having issues with site replication on the data. We have servers all over the world.

Please keep the reports coming in and if you wouldn't mind please let me now the country you are located in.

Thanks

I think I have the same problem with brand new install of Dell Repository Manager 1.8.0.89

I'm trying to export T610 Windows Bundle x86 4.90 to SUU Directory or ISO to use with Lifecycle Controller

Here's the Job Details

1. 1/23/2014 2:26:57 PM Export to SUU32 : Started Processing...
2. 1/23/2014 2:27:13 PM Export to SUU32 : Preparing for SUU export...
3. 1/23/2014 2:27:25 PM Export to SUU32 : Extracting SUU plugin
4. 1/23/2014 2:27:37 PM Export to SUU32 : Downloading files...
5. 1/23/2014 2:29:39 PM Export to SUU32 : Downloading 3/109: network_firmware_t3tvn_wn32_7.8.16.exe
6. 1/23/2014 2:29:57 PM Export to SUU32 : Downloading 4/109: esm_firmware_63kcr_wn32_1.96_a00.exe
7. 1/23/2014 2:31:09 PM Export to SUU32 : Downloading 5/109: sas-raid_firmware_c3x7d_wn32_12.10.6-0001_a12.exe
8. 1/23/2014 2:31:23 PM Export to SUU32 : Downloading 6/109: network_firmware_ktt4w_wn32_14.5.8_a00.exe
9. 1/23/2014 2:31:56 PM Export to SUU32 : Downloading 8/109: sas-non-raid_firmware_yj78t_wn32_07.03.06.00_a10.exe
10. 1/23/2014 2:32:08 PM Export to SUU32 : Downloading 9/109: diagnostics_application_92pn7_wn32_5158a3_5158.2.exe
11. 1/23/2014 2:32:22 PM Export to SUU32 : Downloading 10/109: frmw_win_r283321.exe
12. 1/23/2014 2:32:30 PM Export to SUU32 : Downloading 11/109: sas-non-raid_firmware_fcr14_wn32_00.10.51.00.06.12.05.00_a05.exe
13. 1/23/2014 2:32:38 PM Export to SUU32 : Failed exporting to SUU format.

vgeek.me

I was able to reproduce issues with that bundle. There are two files in that bundle with expired certificates. Repository Manager will not download files with expired certificates, so that is why they are failing. I could not find any issues with the other files you are receiving errors on. I would like for you to create a custom bundle that excludes the problem files and see if it works for you. It does work for me:

• Go to Dell Online tab where you are searching for the bundles
• Go to the bundle tab where you have the search options
• Select the bundle you want using the search fields by putting a check in the box next to it
• Go to the Components tab
• Select everything in the Components tab except these two files
  • Video_Driver_08MVF_WN32_4.00.01.004_1.0.EXE
  • SAS-Non-RAID_Driver_KPWH9_WN32_1.28.03.01_A07.EXE
• Choose the Copy option at the top
• Choose the second option: Create a NEW Repository and copy component(s) into it
• The rest of the options don't really matter. They are mainly for description and convenience
• Once that finishes go to the My Repositories at the very top. The repository you just created should be there
• Select the repository you just created with a check mark and then select open
• The list will be empty. Select the + Add option at the top left
• Choose to Manually create a bundle
• The rest of the options are self explanatory, but you can just leave everything on All or don't specify. It will then use every file in the repository we just created.
• Select the bundle in the list with a check mark and go through the procedures to export

Let me know if it works. We are still in the process of tracking down problem files and other issues in all of the bundles listed in this thread. So far these are the only two issues we have found. We are letting a debugger run over night to locate any other problem files. We will submit a work order to correct these issues tomorrow after we finish debugging.

Thanks