Update driver manifests on Bare Metal Server failing with exit code 3

While uploading drivers for OS deployment the actions fails on the last line of the code with exit code 3. This failure is not OS or model specific. We are facing this error for all drivers that are uploaded to the OSD server.

Below is the action script that fails on the last line:-

Completed parameter “AGENTFOLDER” = “{following text of first “%22” of preceding text of first “\rbagent” of (value “ImagePath” of key “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RemboAgent” of registry as string)}“
Completed prefetch “W8X86.ini” sha1:F99B623ACBF3391721DB41C2D8E60AF28E0EBF3C size:64 http://ibmiem.tatatechnologies.com:52311/Uploads/f99b623acbf3391721db41c2d8e60af28e0ebf3c/W8X86.ini.BFOSD sha256:324F8790282B60B9310297F936026ECE364B38D2CA5EDF17BCF4473E7801E1FA
Completed prefetch “W8X64.ini” sha1:28B93073D5D24A87F8CF395C71A973E06CCB7B0C size:67 http://ibmiem.tatatechnologies.com:52311/Uploads/28b93073d5d24a87f8cf395c71a973e06ccb7b0c/W8X64.ini.BFOSD sha256:339521589E9D6911543BEB374D7003CD7B935951F27AF33ECF40C41B9F9CDB46
Completed prefetch “W81X86.ini” sha1:30435418D7A5603CE1D4EB92489A20C5173639BE size:67 http://ibmiem.tatatechnologies.com:52311/Uploads/30435418d7a5603ce1d4eb92489a20c5173639be/W81X86.ini.BFOSD sha256:07A7B7937C21C41AF3B9293BF9CD1BCB90BC972CD5DDA1D033764933741F499E
Completed prefetch “W81X64.ini” sha1:0E63E6DA3B3C93CA51666EB31ADDC26963BF3321 size:70 http://ibmiem.tatatechnologies.com:52311/Uploads/0e63e6da3b3c93ca51666eb31addc26963bf3321/W81X64.ini.BFOSD sha256:08B8D831CAB11F4A9181D4207CA304408083A36AABDAA741564644A5F0C048A5
Completed prefetch “W7X86.ini” sha1:605787CBD14DE5E336B3C8723F277A47507ABA5C size:445638 http://ibmiem.tatatechnologies.com:52311/Uploads/605787cbd14de5e336b3c8723f277a47507aba5c/W7X86.ini.BFOSD sha256:1A69EECC3106F20AFB8DDAB5D14322E390808CF76D2F69D41392BA758D74E8B8
Completed prefetch “W7X64.ini” sha1:B3DCBEB11F0C04C42E6008C38D09172B62177DCA size:501592 http://ibmiem.tatatechnologies.com:52311/Uploads/b3dcbeb11f0c04c42e6008c38d09172b62177dca/W7X64.ini.BFOSD sha256:F950C6BB96CE6C3693627CE18B37B0AB0B214F483372CAB6C8C47E91FAB609BD
Completed prefetch “W10X86.ini” sha1:82233E6742F913AA9BFE0BA4C277995076624BB7 size:15746 http://ibmiem.tatatechnologies.com:52311/Uploads/82233e6742f913aa9bfe0ba4c277995076624bb7/W10X86.ini.BFOSD sha256:98BA1A0BA5D667181DE1474E1D3C633F9B59BAE3B23CED77DEDBAEA26443A447
Completed prefetch “W10X64.ini” sha1:FB62C0C94DCCB6162900C1614EE53B0C8B39894F size:80317 http://ibmiem.tatatechnologies.com:52311/Uploads/fb62c0c94dccb6162900c1614ee53b0c8b39894f/W10X64.ini.BFOSD sha256:005380B238DF3A51FC8BEED1E49C6D0AF64B1F82807CA31AEE94BE6FB7920F4E
Completed prefetch “VISTAX86.ini” sha1:A80ADB204F90F3CAA8538C65C4C776445A688DEC size:60 http://ibmiem.tatatechnologies.com:52311/Uploads/a80adb204f90f3caa8538c65c4c776445a688dec/VISTAX86.ini.BFOSD sha256:208625CA071AE8BD934559D36398285DE29C13AD34D127CAD777A2BB18926C06
Completed prefetch “VISTAX64.ini” sha1:9065CD150220029F3BAD5A3947DB652E8AD53C6C size:63 http://ibmiem.tatatechnologies.com:52311/Uploads/9065cd150220029f3bad5a3947db652e8ad53c6c/VISTAX64.ini.BFOSD sha256:3424E928DA948C5A0F7442CF8663C17261F23B833BB4A62DE6E8A71C460B9382
Completed prefetch “XPX86.ini” sha1:CFDC60E5B6D66DF2B8520054CAFB551E716E5786 size:54 http://ibmiem.tatatechnologies.com:52311/Uploads/cfdc60e5b6d66df2b8520054cafb551e716e5786/XPX86.ini.BFOSD sha256:F93D2EF92ED882F6FF08DD19936BA26664E5F3E6B54DBE7E4840C94DCBFE801B
Completed prefetch “XPX64.ini” sha1:C238CD43437D1FAB79E28D411B29A790D332A887 size:57 http://ibmiem.tatatechnologies.com:52311/Uploads/c238cd43437d1fab79e28d411b29a790d332a887/XPX64.ini.BFOSD sha256:883232FC48D70BA361E803B32B8B7C33C00FAF7F73552DF23E781EA884B7B350
Completed prefetch “W2003X86.ini” sha1:06D906660FA4CAC715CC6F3CE1013A923CCA965A size:59 http://ibmiem.tatatechnologies.com:52311/Uploads/06d906660fa4cac715cc6f3ce1013a923cca965a/W2003X86.ini.BFOSD sha256:EA08E5E73843AAD3089F1F97A55CB45E695379F504B8587605177FD98A662960
Completed prefetch “W2003X64.ini” sha1:89D99D07443248822CB8E82080F9049FB9E15E4A size:62 http://ibmiem.tatatechnologies.com:52311/Uploads/89d99d07443248822cb8e82080f9049fb9e15e4a/W2003X64.ini.BFOSD sha256:9A2DC164F2CADC27958CB61897014B7BEDD387D0790C786109886A1F6E5316BB
Completed prefetch “W2008X86.ini” sha1:C892025DA362DBAAAD6D36014CB8A5303E12CC50 size:59 http://ibmiem.tatatechnologies.com:52311/Uploads/c892025da362dbaaad6d36014cb8a5303e12cc50/W2008X86.ini.BFOSD sha256:5F7F4A99EDF2A9B612822560D857FAADDF3D529CFB09C6F3E063A48D090E656C
Completed prefetch “W2008X64.ini” sha1:9E024F9548780AFA6A1682CA60B2B61CCDF62182 size:62 http://ibmiem.tatatechnologies.com:52311/Uploads/9e024f9548780afa6a1682ca60b2b61ccdf62182/W2008X64.ini.BFOSD sha256:C870E7C4808659176F71F8608F11DC5C21093E2BD827434673DE45325CD3B4F2
Completed prefetch “W2008R2X64.ini” sha1:BB5B22FECA0962FD1CF4184CD0A334DD2CC94607 size:66 http://ibmiem.tatatechnologies.com:52311/Uploads/bb5b22feca0962fd1cf4184cd0a334dd2cc94607/W2008R2X64.ini.BFOSD sha256:CD854337B57BBC9A06B54655573CFCE7DFA0C8B20384A816A46E07E8351FD96F
Completed prefetch “W2012X64.ini” sha1:7F9CB2E57E0890FF4FEEC3AC4653CEC9E1D207B5 size:62 http://ibmiem.tatatechnologies.com:52311/Uploads/7f9cb2e57e0890ff4feec3ac4653cec9e1d207b5/W2012X64.ini.BFOSD sha256:52C053C75D1E9FADC3F35FFF49950732E614133C9EA64B42B724864A45A5DD7A
Completed prefetch “W2012R2X64.ini” sha1:DA7DBF8A229A3E9DAB69468F7AFFFFBA235AC86A size:66 http://ibmiem.tatatechnologies.com:52311/Uploads/da7dbf8a229a3e9dab69468f7affffba235ac86a/W2012R2X64.ini.BFOSD sha256:FB473A6DA2362DCE93C868F640F5BA38D1AF09BC8FDB478A123C4634F7C455E4
Completed parameter “ManifestImportlogpath”=”{(parameter “AGENTFOLDER”)}\ManifestImport.log"
Completed parameter “temimportpelogpath”=”{(parameter “AGENTFOLDER”)}\temimportwpe.log"
Completed waithidden cmd /C “echo Starting Driver Manifest Import > “{parameter “ManifestImportlogpath”}” 2>&1"
Completed if {(value “SyncTimeManifest” of key “HKEY_LOCAL_MACHINE\SOFTWARE\BigFix\EnterpriseClient\OSDControl” of registry as integer)|0 < 1488871783792 OR exists file (parameter “temimportpelogpath”) whose (not exists line whose (it as string contains “[WPE10SKIP]”) of it)}
Completed createfile until EOF
Completed SET RBAGT_HTTP_TIMEOUT=1800
Completed cmd.exe /C “{preceding texts of firsts “%00” of (value “ImagePath” of key “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RemboAgent” of registry as string)} -d -v 4 rad-temdriversimport pex86drivers=”{client folder of site “actionsite” as string & “__Download”}W10X86.ini” peamd64drivers="{client folder of site “actionsite” as string & “__Download”}W10X64.ini" >> “{parameter “ManifestImportlogpath”}” 2>&1"
Completed EOF
Completed delete runrbagent.bat
Completed move __createfile runrbagent.bat
Completed else
Completed createfile until EOF
Completed cmd.exe /C echo Skipping WinPE10 driver manifest import (not overwritten) [AGTRC:0]>> “{parameter “ManifestImportlogpath”}” 2>&1
Completed EOF
Completed delete runrbagent.bat
Completed move __createfile runrbagent.bat
Completed endif
Completed waithidden runrbagent.bat
Completed if {(value “SyncTimeManifest” of key “HKEY_LOCAL_MACHINE\SOFTWARE\BigFix\EnterpriseClient\OSDControl” of registry as integer)|0 < 1488871783792}
Completed createfile until EOF
Completed SET RBAGT_HTTP_TIMEOUT=1800
Completed cmd.exe /C “{preceding texts of firsts “%00” of (value “ImagePath” of key “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RemboAgent” of registry as string)} -d -v 4 rad-temdriversimport profiledriverslist=”{client folder of site “actionsite” as string & “__Download”}W7X86.ini";"{client folder of site “actionsite” as string & “__Download”}W7X64.ini";"{client folder of site “actionsite” as string & “__Download”}W8X86.ini";"{client folder of site “actionsite” as string & “__Download”}W8X64.ini";"{client folder of site “actionsite” as string & “__Download”}W81X86.ini";"{client folder of site “actionsite” as string & “__Download”}W81X64.ini";"{client folder of site “actionsite” as string & “__Download”}W10X86.ini";"{client folder of site “actionsite” as string & “__Download”}W10X64.ini";"{client folder of site “actionsite” as string & “__Download”}VISTAX86.ini";"{client folder of site “actionsite” as string & “__Download”}VISTAX64.ini";"{client folder of site “actionsite” as string & “__Download”}XPX86.ini";"{client folder of site “actionsite” as string & “__Download”}XPX64.ini";"{client folder of site “actionsite” as string & “__Download”}W2003X86.ini";"{client folder of site “actionsite” as string & “__Download”}W2003X64.ini";"{client folder of site “actionsite” as string & “__Download”}W2008X86.ini";"{client folder of site “actionsite” as string & “__Download”}W2008X64.ini";"{client folder of site “actionsite” as string & “__Download”}W2008R2X64.ini";"{client folder of site “actionsite” as string & “__Download”}W2012X64.ini";"{client folder of site “actionsite” as string & “__Download”}W2012R2X64.ini" >> “{parameter “ManifestImportlogpath”}” 2>&1"
Completed EOF
Completed delete runrbagent.bat
Completed move __createfile runrbagent.bat
Completed else
Completed createfile until EOF
Completed cmd.exe /C echo Skipping OS driver manifest import (already at right version) [AGTRC:0]>> “{parameter “ManifestImportlogpath”}” 2>&1
Completed EOF
Completed delete runrbagent.bat
Completed move __createfile runrbagent.bat
Completed endif
Completed waithidden runrbagent.bat
Completed // If the synchronization has not been triggered by an update, we must reset the registry key before updating it to be sure to read the status of the last synchronization
Completed if {(value “SyncTimeManifest” of key “HKEY_LOCAL_MACHINE\SOFTWARE\BigFix\EnterpriseClient\OSDControl” of registry as integer)|0 = 1488871783792}
Completed regset “[HKEY_LOCAL_MACHINE\SOFTWARE\BigFix\EnterpriseClient\OSDControl]” “SyncTimeManifest”="0"
Completed endif
Completed // End action if previous command failed before we store a success key in registry
Completed if {exists file (parameter “ManifestImportlogpath” of action) whose ((number of lines whose (it as string contains “[AGTRC:0]”) of it) equals 2)}
Completed regset “[HKEY_LOCAL_MACHINE\SOFTWARE\BigFix\EnterpriseClient\OSDControl]” “SyncTimeManifest”="1488871783792"
Completed endif
Failed continue if {(value “SyncTimeManifest” of key “HKEY_LOCAL_MACHINE\SOFTWARE\BigFix\EnterpriseClient\OSDControl” of registry as integer)|0 >= 1488871783792}

This has been an issue for us for quite some time, as a result of which we have to perform OSD without the essential drivers.

Hi There. The failure you get is an indication that something went wrong while driver were imported on the BM Server. The failure reason could be seen in C:\ProgramFiles…\common files\IBM Tivoli\manifestimport.log file
and/or c:\tpmfosd files\logs\vm.trc
A Full sync of the BM Server may help in restoring a working state. (Fron BM Server dashboard, click on the small icon with the arrows in the affected server…)

Hi,

We tried syncing the affected server. But the syncing creates an action called SYNC BARE METAL SERVER which fails at the same step i.e. Updating driver manifests on Bare Metal Server.

I have the exact same problem. All servers seem to be out of sync in Server Management and Driver manifest update fails to finish when running Full Sync.

So, it’s been over two months since asecoman posted this suggestion…has anyone checked the manifestimport.log or vm.trc files? Those should show the errors that are being encountered in the rbagent process.

Checked the manifestimport.log as directed by @asecoman.
There were no errors in the logs except for the last three lines.
Which are as:-
Import of driver manifest completed (2 success, 0 updated, 1 error / 6 total - 0 deleted)
Import of driver manifest completed (5 success, 0 updated, 1 error / 13 total - 0 deleted)
RbAgent command rad-temdriversimport has failed [AGT:4403]

We have tried upgrading the server and doing a full sync of the server but the sync is failing at the last line of the action script which states
Failed continue if {(value “SyncTimeManifest” of key “HKEY_LOCAL_MACHINE\SOFTWARE\BigFix\EnterpriseClient\OSDControl” of registry as integer)|0 >= 1488871783792}

We also tried this but it was not of any help:-
http://www-01.ibm.com/support/docview.wss?uid=swg21991429

Were you able to attain any success @Knakerton since you were facing the same problem.??

Hi raumohit_10.
The manifest import log indicates that there is likely a driver causing troubles (in the 32 and 64 bit flavours). As JasonWalker suggests the vm.trc file is also needed to determine the driver in question.

You will find a reference to the driver by it’s SHA1 value in the vm.trc file.Find the driver in the driver library with that SHA1 and delete it to confirm this is the driver causing troubles.

If you get to that point then try re-import the driver in question. If it causes the same problem then it becomes a Support team matter to determine why and provide a fix/workaround.

Tried everything that was suggested, we even tried re-installing the OSD server and updating the driver manifests. Nothing was of much use.

Are you able to find anything useful in the vm.trc log?

Hi,

These were the errors that we are seeing in the vm.trc logs.
The problem is mainly arising with with all drivers except for windows 10 and the SHA1 value is present on the Bigfix server

[2017/07/11 12:01:26] Faulty query (console.rbc:11746): INSERT INTO SoftwareItem (SoftItemID,Description,Type,Comment,SoftSeqID,Pass,Source,Dest,Content,RunEnv,Flags,SoftArch,OSFamily,OSLevel,UniqueKB,SharedKB,Scope,ObjVer,ObjStamp,ObjRboVersion) VALUES (7280523,‘Qualcomm Atheros,Qualcomm Atheros Communications,Broadcom,Broadcom Corporation,Atheros,Broadcom Corp.,Intel,Qualcomm Atheros Corp,Qualcomm Atheros Communications Inc.,Realtek USB,Bluetooth,HIDClass,Net,MEDIA,BluetoothVirtual,System,Modem driver (ver. 01/21/2013 - 12/18/2012)’,‘pkg’,‘969 PCI devices and 7782 variants from Qualcomm Atheros,Qualcomm Atheros Communications,Broadcom,Broadcom Corporation,Atheros,Broadcom Corp.,Intel,Qualcomm Atheros Corp,Qualcomm Atheros Communications Inc.,Realtek
[2017/07/11 12:01:26] ‘,3,0,‘tem://ibmiem.abc.com:52311/Uploads/33c5643ba3e781100976b24dcb36b457f2adc821/33C5643BA3E781100976B24DCB36B457F2ADC821pkg.BFOSD/33C5643BA3E781100976B24DCB36B457F2ADC821|772135|765DF6DFEF0845CC55DCA116FB13313F713038F4AFBD11C25DD8ED5465B73F35/33C5643BA3E781100976B24DCB36B457F2ADC821pkg.BFOSD’,’\drivers\USB-Bluetooth-HIDClass-Net-MEDIA-BluetoothVirtual-System-Modem-ZIKPQE’,‘win-drv’,‘os-win’,0,‘x86-64’,‘Windows’,’[7]’,772135,0,‘HNJIBMBSOD’,0,getDate(),2)
[2017/07/11 12:01:26] Error raised by DbRbcExecEx in dbdb.rbc, line 4424 [VAR:3885]
[2017/07/11 12:01:26] Unknown error (Problem in a SQL query, check logs for details[USRMSG]ERROR 1554 (22001): [Microsoft][ODBC SQL Server Driver][SQL Server]String or binary data would be truncated.[console.rbc:11746][I18NMSG]Problem in a SQL query, check logs for details)
[2017/07/11 12:01:26] (called from DbRbcExec (dbdb.rbc:4247))
[2017/07/11 12:01:26] (called from RADImportFromManifestOnServerWorker (console.rbc:11752))
[2017/07/11 12:01:26] (called from --toplevel-- (Eval:1))
[2017/07/11 12:01:26] Error raised by DbRbcExecEx in dbdb.rbc, line 4424 [VAR:3885]
[2017/07/11 12:01:26] Unknown error (Problem in a SQL query, check logs for details[USRMSG]ERROR 1554 (22001): [Microsoft][ODBC SQL Server Driver][SQL Server]String or binary data would be truncated.[console.rbc:11746][I18NMSG]Problem in a SQL query, check logs for details)
[2017/07/11 12:01:26] (called from DbRbcExec (dbdb.rbc:4247))
[2017/07/11 12:01:26] (called from RADImportFromManifestOnServerWorker (console.rbc:11752))
[2017/07/11 12:01:26] (called from --toplevel-- (Eval:1))
[2017/07/11 12:01:29] Import completed (5 success, 0 updated, 1 error / 13 total - 0 deleted)

[2017/07/11 12:02:15] Driver [3055428] was missing in the imported manifest: updated supported OS on server database ([PE10])
[2017/07/11 12:02:16] Driver [5226425] was missing in the imported manifest: updated supported OS on server database ([PE10])
[2017/07/11 12:02:16] Driver [8907948] was missing in the imported manifest: updated supported OS on server database ([PE10])
[2017/07/11 12:02:16] Driver [1639050] was missing in the imported manifest: updated supported OS on server database ([PE10])
[2017/07/11 12:02:16] Driver [7030891] was missing in the imported manifest: updated supported OS on server database ([PE10])
[2017/07/11 12:02:16] Driver [9689690] was missing in the imported manifest: updated supported OS on server database ([PE10])
[2017/07/11 12:02:16] Driver [9546271] was missing in the imported manifest: updated supported OS on server database ([PE10])
[2017/07/11 12:02:16] Driver [1571397] was missing in the imported manifest: updated supported OS on server database ([PE10])
[2017/07/11 12:02:16] Driver [4817684] was missing in the imported manifest: updated supported OS on server database ([PE10])
[2017/07/11 12:02:16] Driver [4748459] was missing in the imported manifest: updated supported OS on server database ([PE10])
[2017/07/11 12:02:27] Import completed (0 success, 0 updated, 0 error / 0 total - 10 deleted)

Hi. so the problem is the description of the driver with SHA1 33c5643ba3e781100976b24dcb36b457f2adc821
for Qualcomm Atheros device apprently USB-Bluetooth-HIDClass-Net-MEDIA-BluetoothVirtual-System-Modem.

Problem is that at insert time into the OSD Server database the description is longer that 255 chars of the table filed.

The description that you are about to insert is:
"Qualcomm Atheros,Qualcomm Atheros Communications,Broadcom,Broadcom Corporation,Atheros,Broadcom Corp.,Intel,Qualcomm Atheros Corp,Qualcomm Atheros Communications Inc.,Realtek USB,Bluetooth,HIDClass,Net,MEDIA,BluetoothVirtual,System,Modem driver (ver. 01/21/2013 - 12/18/2012)"
that is larger that 255.

This description is built from data in the inf file. Specifically from the Version section the Provider and the Class are taken. Then the key value “driver” is added ad finally the DriverVer is added.

To recover:
Delete this driver from the TEM console.
Edit the .inf file of this driver and make the provider value and the Class value shorter.
Import the driver again.
This should get you going.

For a long term solution i encourage you to provide a copy of the driver (the content of the directory where the .inf file is) to the support team and to open an APAR so they can automatically deal with this situations out of the box.

1 Like

Would editing the .inf break the driver signature?

Ha. A good point indeed. I can not confirm but would be surprised if it does not.

Hi @asecoman, thanks for your help. We deleted the sha1 of the driver that was causing the issue and re-uploaded the driver which turned out to be an Intel HD graphics driver .
Our OSD is working perfectly now.