When any nVision report is run via the web, it result in errors such as:

‘Excel interface exception E:\pt84918b-retail\peopletools\src\psnxl\gridapp.cpp:2048 Microsoft Office Excel cannot access the file ‘pshome\nvision\LAYOUT\F_allocations_2.xnv’.

But  the same report can be run in 2 or 3 tier client workstation.

Upgrading from Windows 2003 to Windows 2008 caused this issue to appear.

PeopleSoft Development has provided a workaround to be implemented on the affected process scheduler machine:

1) Take a backup of the registry before proceeding

2) Associate AppID of “Microsoft Office Excel Application” to its Class ID under the Wow6432Node registry node.

2.1) Create a new String Value by name “AppID” under the following registry key.
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\CLSID\{00024500-0000-0000-C000-000000000046}

The Environment variable PS_CFG_HOME new in this version,  has been created to hold the configuration files for the application server, batch server and search server domains.

This posts is a part of the PeopleTools 8.50 Hints & Tips series on BAOA regarding PeopleSoft 8.50 tools upgrade.

If you have more PS_HOMEs on the same machine, you can create a separate Windows Service for each environment with the next steps:

Step1 – Setting PS_CFG_HOME

Create a  .bat file in each PS_HOME/appserv folder, for example psadmin.bat. This file would contain the following:

In Tools 8.50 the ‘secureFileKeystorePasswd’ parameter of the integrationgateway.properties file must now be encrypted.

This posts is a part of the PeopleTools 8.50 Hints & Tips series on BAOA regarding PeopleSoft 8.50 tools upgrade.

That can be done  through the application so that you do not need to restart the web server.
1. Navigate to PeopleTools -> Integration Gateway -> Configuration – Gateways.

PeopleCode compile error after a Tools-only upgrade to PeopleTools 8.50

This posts is a part of the PeopleTools 8.50 Hints & Tips series on BAOA regarding PeopleSoft 8.50 tools upgrade.

Five new keywords have been introduced in PeopleTools 8.50:

• Primitive
• Compound
• Collection
• Document
• DocumentKey

Some applications released before 9.1 use the word “collection” as class name what result in a PeopleCode compiler error such as:

PeopleCode compiler error.(The create operator can only be used for application classes(2,96)) for program xxxx.yyyy.OnExecute(2,405).

My previous post was about the integration between Siebel and BI Publisher that was available since Siebel 8.1. As I mentioned back then, the integration is promising, but presented  some serious limitations to BI as a report generation tool for Siebel, and I promised to touch this issue again in a new post. Well, here we go.

With the patch to Siebel 8.1.1.1, some of the isssues have been resolved, while some serious new ones have been created. Our main reason to upgrade (Siebel to 8.1.1.1 and BI Publisher to  10.1.3.4.1) were issues with Active Directory. The Siebel Security Model provided by BI was not documented nor functioning properly in the earlier version. This has been resolved in the new version. The Siebel Security Model basically works like this: a user requests a report, BI then checks in Siebel whether the user has the right responsibility (yes, you need to add the XMLP_DEVELOPER responsibility to each user that needs to create reports) and then BI creates the report and sends it back to Siebel. Works a like charm!