We are running into an issue dat adding an image to the image library takes insanely long, the process is either stuck on " inspecting image information" " inspecting drivers in image"
the iso we are uploading is just a plain Microsoft ISO is there a way to improve the speed of uploading images to the library?
The first thing is to make sure the image is local on your console machine. If you are accessing it over a mapped drive or UNC path, calculating the hash takes an extremely long time because of the way SMB works - it’s thousands of tiny read operations which are slow over SMB.
Other than that, try to have your console close to the root server.
We have the iso mounted on the bigfix server itself , it trows an warning " do you want to stop running scripts" if you dont answer that prompt fast enough the process failes. However what we facing now is that we used the new version of the image librabry without flash and that trows an error that it cant find some file RBAgentCheckingOutputNotFound
Hi,
the same warning was also being displayed during the import image process with the old version of the Image Library dashboard, but it seems that with the new one it’s being displayed more frequently.
That message should refer to an error while inspecting the image: could you please check this log file to have more details on the error?
%userprofile%\OSDeployment\rbagent.trc
Thanks.
rebooted the bigfix server where th eprocess was also running
[2021/01/11 18:28:45:884] Error c1420117 while attempting to unmount image
[2021/01/11 18:28:46:587] A Command error: Archive inconsistency detected, Error c1420117 while attempting to unmount image
[2021/01/11 18:28:46:587] A Error raised by WIMWait in pakutils.rbc, line 423 [@SY:7780]
[2021/01/11 18:28:46:587] A Archive inconsistency detected (Error c1420117 while attempting to unmount image )
[2021/01/11 18:28:46:587] A (called from unmount (pakutils.rbc:688))
[2021/01/11 18:28:46:587] A (called from CheckVistaState (pakutils.rbc:813))
[2021/01/11 18:28:46:587] A (called from WIMGetImageDescriptions (pakutils.rbc:508))
[2021/01/11 18:28:46:587] A (called from generateWinImageInfo (load.rbc:14555))
[2021/01/11 18:28:46:587] A (called from generateWinImageInfoForSetupImage (load.rbc:15920))
[2021/01/11 18:28:46:587] A (called from RAD_temmksetup (load.rbc:16097))
[2021/01/11 18:28:46:587] A (called from AgentDispatch (rbagent.rbc:4398))
[2021/01/11 18:28:46:587] A (called from --toplevel-- (rbagent.rbc:4825))
[2021/01/11 18:28:46:587] A RbAgent command rad-temmksetup has failed [AGT:4405]
uploading from my local machine against the bigfix server
[2021/01/11 19:04:48:967] Error c1420117 while attempting to unmount image
[2021/01/11 19:04:49:440] A Command error: Archive inconsistency detected, Error c1420117 while attempting to unmount image
[2021/01/11 19:04:49:441] A Error raised by WIMWait in pakutils.rbc, line 423 [@SY:7780]
[2021/01/11 19:04:49:443] A Archive inconsistency detected (Error c1420117 while attempting to unmount image )
[2021/01/11 19:04:49:444] A (called from unmount (pakutils.rbc:688))
[2021/01/11 19:04:49:445] A (called from CheckVistaState (pakutils.rbc:813))
[2021/01/11 19:04:49:445] A (called from WIMGetImageDescriptions (pakutils.rbc:508))
[2021/01/11 19:04:49:445] A (called from generateWinImageInfo (load.rbc:14555))
[2021/01/11 19:04:49:445] A (called from generateWinImageInfoForSetupImage (load.rbc:15920))
[2021/01/11 19:04:49:445] A (called from RAD_temmksetup (load.rbc:16097))
[2021/01/11 19:04:49:445] A (called from AgentDispatch (rbagent.rbc:4398))
[2021/01/11 19:04:49:446] A (called from --toplevel-- (rbagent.rbc:4825))
[2021/01/11 19:04:49:447] A RbAgent command rad-temmksetup has failed [AGT:4405]
so no mather where i do it , and i’ve got 2 bigfix environments i tried i’m running into errors
ERROR: Problem detected during inspection of [object Object] info.
[2021/01/11 19:28:50:539] WIMUnMount(“C:\Users\user\AppData\Local\Temp\tpm_466A7F357E41949F_1”,0)
[2021/01/11 19:31:30:31] Error c1420117 while attempting to unmount image
[2021/01/11 19:31:30:506] A Command error: Archive inconsistency detected, Error c1420117 while attempting to unmount image
[2021/01/11 19:31:30:508] A Error raised by WIMWait in pakutils.rbc, line 423 [@SY:7780]
[2021/01/11 19:31:30:511] A Archive inconsistency detected (Error c1420117 while attempting to unmount image )
[2021/01/11 19:31:30:512] A (called from OSDT_ExtractWIMDrivers (load.rbc:2293))
[2021/01/11 19:31:30:513] A (called from AgentDispatch (rbagent.rbc:4398))
[2021/01/11 19:31:30:513] A (called from --toplevel-- (rbagent.rbc:4825))
[2021/01/11 19:31:30:513] A RbAgent command osdtools-extractwimdrivers has failed [AGT:4405]
Could you please try to re-launch the bigfix console with right click on its icon and “Run as administrator”?
The error could be due to the fact that the user that is running the console does not have the needed authorization to mount the image.
To import a setup image, the selection for installation media (.iso) must be used, providing the iso file, and not for Windows for image (.wim) providing the install.wim contained in the .iso. If the install.wim is imported, the import could be successful but the imported image will be unusable since it will be seen as a captured image and it’s not.
Thanks.
i am running as administrator, made that error one to many time before previously i’ve trie duploadeing an install.wim but indeed that is shows as capture image , coworker created a ticket with HCL since this process is very annoying if you have to wait and keep staring at your screen towards the " stop running script " popup if you want to have any change of success. I’ve wasted almost a whole day on this
For the RBAgentCheckingOutputNotFound error, did you check if, starting the console with “Run as administrator” (even if you are already logged as administrator) solves the issue?
Thanks.
ok, sorry for asking but being logged as Administrator and lunching the console normally is not the same that right clicking and “Run as Administrator”.
If also in this way you have in rbagent.trc
Error c1420117 while attempting to unmount image
it’s not an authorization issue.
Thanks.
well this process is buggy as hell now i’ve installed the console on my own private machine which has more resources spare then the bigfix server and my work laptop, now i start the image upload proces and it errors with " windows script host" " there is no file extension in " c:\users\martijn" but my folder name is c:\users\martijn lastname\ guess it doesnt handle spaces in folder names.
I’ve made a symlink to my folder in c:\users\martijn but it doesnt want to run
Yes, the junction does not solve the issue. As workaround at the moment, if feasible, you could try to import, on the computer where the user folder has a space, with the flash image library dashboard.
Starting from today you could find the flash dashboards blocked, there are some steps to unblock them that are documented at this link -> BigFix - Flash announcement
in the section “How to enable Allow List mode for Adobe Flash Player”
Hi,
did you add both rbagent64.exe and rbagent.pak to the user folder of the user with a space in his home directory? It’s %userprofile%\OSDeployment
In the same directory you should also find other files, for example RelayDownloader.exe.
Other alternatives could be:
use a user whose home directory does not have a space
or
use the Flash Image Library dashboard (following the procedure to enable it if disabled)
Thanks.
with a lot of trying and stuff we managed to upload an image, its shown as an " setup " image now but fixlet 202 shows only " image name" “no data retrieved”
Hello.
The Windows 10 setup images should be displayed in this list. More investigation is needed on the data in the datastore to understand the issue.
This is the query to run in presentation debugger as next level of investigation:
(name of it, value of it) of shared variables whose (name of it starts with “OSD_WIM” and value of it does not contain “%22Capture%22”) of wizard whose (dashboard id of it = “OSD_DataStore.ojo”) of bes site whose (name of it = “OS Deployment and Bare Metal Imaging”)
I suggest to continue the investigation with the support team to speed up the resolution.
Thanks.