Error 2714: Invalid value for default folder

I know what the error means but I'm not sure how to fix it. I'm using WPS. The logfile reports this:

MSI (s) (74:08) [11:13:09:733]: Note: 1: 2714 2: LIB_ZI~C|lib/zi/Pacific
DEBUG: Error 2714: Invalid value for default folder name: LIB_ZI~C|lib/zi/Pacific.
MSI (s) (74:08) [11:13:09:733]: Product: Oracle Briefing Book_Reader -- Internal Error 2714. LIB_ZI~C|lib/zi/Pacific

Looking in the Directory table I find:

The actual path it's refering to is C:\Program Files\Oracle Business Intelligence\SABBReader\_jvm\lib\zi\Pacific
and there are files in that directory. There are no merge modules.

0 Comments   [ + ] Show comments

Answers (1)

Posted by: anonymous_9363 12 years ago
Red Belt
Entries in the Directory table must be self-contained and not contain sub-folders i.e. you must have separate rows for 'ib', 'zi' and 'Pacific'.

As you're a WPS user and, from my guess, none too au fait with directly editing the MSI tables (which would be the quickest way), I would first create a back-up of the MSI/MST, so that we have a fast route back to where we are now.

Then I'd go back the Installation Expert/Files view, delete the folder structure beneath 'C:\Program Files\Oracle Business Intelligence\SABBReader\_jvm' and then recreate the folders 'lib\zi\Pacific' from scratch, one by one (actually, WPS will only let you create them one by one.) Then, re-test.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ