Running a BI Publisher Report from an online page logs user out of PIA

When user runs a BI Publisher Report from an online PIA page by clicking a button and this report is based on a Query, user sees the below message.

An error has occurred. You may attempt to sign in again. If your attempt fails, please contract your System Administrator.
Please make sure Webserver and Appserver are up. null

In the Appserver Log, we see the error

PSPAL: Abort: Unexpected signal received
PSPAL: Abort: Location: /vob/peopletools/src/pspal/exception_sigaction.cpp:494: RecoverableSignalHandler
PSPAL: Abort: Generating process state report to /opt/test/psft/pt/8.53/appserv/prd/LOGS/PSAPPSRV.10742/process_state.txt

Inside the process_state.txt, we see that RuntoFile is actually generating the exception and killing the appserver thread.

#2  0x00007f7012a8f224 in PSPAL::DumpProcessState::GenerateAbortDiagnostics(char const*, PSPAL::ExceptionContext*) () from /opt/test/tools/bin/libpspal64.so    #3  0x00007f7012a8386b in PSPAL::Abort(char const*, char const*, int, char const*, PSPAL::ExceptionContext*) () from /opt/test/tools/bin/libpspal64.so
   #4  0x00007f7012a89191 in PSPAL::SigactionSignalHandler::RecoverableSignalHandler(int, siginfo*, void*) () from /opt/test/tools/bin/libpspal64.so
   #5  0x00007f7012a89a65 in PSPAL::SigactionSignalHandler::SignalHandler(int, siginfo*, void*) () from /opt/test/tools/bin/libpspal64.so
   #6  0x00007f6ff6e15f12 in os::Linux::chained_handler(int, siginfo*, void*) () from /opt/test/tools/jre/lib/amd64/server/libjvm.so
   #7  0x00007f6ff6e1bbf6 in JVM_handle_linux_signal () from /opt/test/tools/jre/lib/amd64/server/libjvm.so
   #8  <signal handler called>
   #9  0x00007f700f03619f in QpmEnd () from /opt/test/tools/bin/libpssys.so
   #10 0x00007f70088b7815 in CPSQuery::CleanupQueryExecution(void*, void*) () from /opt/test/tools/bin/libpsoftapi.so
   #11 0x00007f70088fa777 in CPSQuery::RunToFile(IPSRecBuf*, wchar_t const*, int, int) () from /opt/test/tools/bin/libpsoftapi.so
   #12 0x00007f70088c28fc in _IPSQuery::InvokeMethod(wchar_t const*, IPSApiVariant*, IPSApiVariant**, int) () from /opt/test/tools/bin/libpsoftapi.so

Resolution: Please determine the Records used in PeopleSoft query that is used in BI Publisher Report definition. Please make sure that this record is added to permission list that belongs to the user running this report using Query tab in permission list component and accessing the Access group link. Once the permission list is modified add the permission list to the Role that is assigned to user if not already added. This resolves the issue. Noted this in PT 8.53.12.

Installation directory is corrupt, could not find uninstaller: XMLPReportingTools4WordSetup.msi!

User is getting the following message after the reboot of the PC and trying to install BI Publisher (XML Publisher) on previously installed installation. User has deleted the original folder, and now unable to complete the Installation by running BIPublisherDesktop.exe. The installer first tries to uninstall and it fails because it count not find the original .msi file.

Solution

The uninstall information is located under 2 places.

“ C:\Program Files (x86)\InstallShield Installation Information” .

C:\Program Files (x86)\InstallShield Installation Information\{CF76FCE2-995F-479B-A004-1B67DFC7E80D}.

and under the following registry Key. Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{CF76FCE2-995F-479B-A004-1B67DFC7E80D}

Renaming the registry key to {CF76FCE2-995F-479B-A004-1B67DFC7E80D}.orig and rebooting the machine fixed the issue. Without rebooting, you may get a message Close the Word.

See the registry screenshots

Location of msi file

"C:\Program Files (x86)\Oracle\BI Publisher\BI Publisher Desktop\DotNetInstallFiles\XMLPReportingTools4WordSetup.msi"

This issue was happening on Windows 7 64 bit machine.

On Oracle Support following resolution is listed, but it does not resolved the issue

BI Publisher Errors ActiveX Component Can't Create Object and Installation Directory is Corrupt [ID 1088097.1]

Query 'XXX' has Tree Prompt Option criteria defined. (241,93). Queries with Tree Prompt Option criteria cannot be used in Connected Query, XML Publisher, Query Access Services and some other Applications.

The issue was due to the fact that a new record was added to an existing query and this record was not added to query tree access group assigned to user running this query.

Once the record was added to the appropriate query tree access group, issue is resolved.

This issue was noted in PT 8.50.22. In reality, the following message should be given.

The record (XXX) used by query is not available to the access group assigned to user. Hopefully they may fix this in future release.

This issue can also happen when you modify the query using a userid that has access to query record, but the user running it does not have access to it.

Query to determine all the records available to a userid.

Query to determine which records user can see