On Windows, certain versions of Snow Inventory Oracle scanners (Java, Middleware, Hardware, and SIOS) may not complete their scans. Instead, the log repeatedly reports:
ERROR; Initializing;;; Invalid jar entry
This issue affects older versions of the four Snow Inventory scanner modules. The problem occurs if the scanner version is earlier than the following release numbers:
-
Snow Inventory Java Scanner 3.2.3
-
Snow Inventory Oracle Middleware Scanner 3.2.2
-
Snow Inventory Oracle Hardware Scanner 2.1.2
-
Snow Inventory Oracle Scanner 8.2.3
Cause
Recent releases introduced a security enhancement that validates jar file contents to prevent path‑traversal attacks. As a result, the scanner must unpack jar files to a temporary directory whose path exactly matches the path reported by Windows. If the paths differ (for example, because Windows shortened the username or changed the case of a folder), the scanner will reject the path and report “Invalid jar entry”.
For example, Windows might return a short path like C:\Users\ROBERT~1.URQ\AppData\Local\Temp.
But the actual folder is C:\Users\robert.urquhart\AppData\Local\Temp.
Because these do not match exactly, the scanner cannot verify the temporary directory and fails.
Configure a fixed temporary directory that always matches the file system path exactly by setting the env.temp_dir key in the snowagent.config file:
<Setting key="env.temp_dir" value="C:\Windows\Temp"/>
Choose a folder that already exists and is writable. We recommend using C:\Windows\Temp. The agent will not create this path, so it must exist beforehand. This configuration overrides the default temporary directory and allows the scanners to unpack jar files successfully.
For more details, see the Snow Inventory Agents and Oracle Scanners configuration reference.
Steps to implement
- On the machine where the scanner is installed, open
snowagent.configin a text editor with administrative privileges. - Locate the
<Configuration>section and add or update the <Setting key="env.temp_dir" value="C:\Windows\Temp"/>entry. - Save the file.
- Re-run the Oracle scanner. It should now complete without the “Invalid jar entry” error.
For more information on these enhancements, see:
Related Articles
How to enable debugging mode in Snow Inventory Oracle Scanner 48Number of Views Oracle Verified - There was no entry for a estate item within virtualization topology raw data, but the agent and scanners… 11Number of Views How to Write Custom Messages in the DEBUG log using lc_log? 471Number of Views ndtrack.exe process may crash gathering info report for Oracle FMW inventory if an WMI query returns Invalid class (0x8004… 3Number of Views Add custom Snow Oracle Scanner cron in the Snow Agent Package Builder 26Number of Views
Hi, I am Reva - Ask me anything.
No new updates
Thanks for the feedback!
Your feedback has been saved.Rate this response:
Add Additional feedback ( Optional )
Are you sure you want to cancel
the case creation?
Are you sure you want to cancel the case creation?
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
Case id: 00001065
Activity: Status change: 2 hours ago