This articles provides some help around setting up nVision.

On a new Windows process scheduler install, there are a few steps required to get PeopleSoft nVision working. These include:

  • Install .NET Framework
  • Install OpenXmlSDK from PS_HOME\setup\OpenXmlSDK
  • Run Microsoft Excel and get past any of the initial install screens
  • Run PS_HOME\bin\client\winx86\psnvs.exe -register from the command line
  • Start nVision client (psnvs.exe) and try running a few nVision reports locally on the process scheduler.

If you see this:


Make sure you have run the PS_HOME\bin\client\winx86\psnvs.exe -register command.

In PeopleTools 8.51, running on Windows 2008 R2 and Office 2007, drill downs run from the web were giving the following OpenXml errors:

An OpenXml error occured. File contains corrupted data. (28,244)
An OpenXml error occured. Object reference not set to an instance of an object. (28,244)
DrillDown only works at the intersection of an amount row and column. (28,123)

To fix, set the UseExcelAutomation=1 flag in the psprcs.cfg file, and restart the process scheduler.

If you are trying to run the nVision client (psnvs.exe) and you receive the following message:

PeopleSoft PeopleTools DSN is missing in ODBC Data Sources.
Quit nVision, Use Configuration Manager, Client Setup, check on Install
PeopleSoft ODBC Driver, click Apply and reload nVision

It means that the ODBC configuration is not correct, and typically occurs on 64 bit versions of Windows. The instructions to fix this in the message probably won't be available to you anymore in newer versions of PeopleTools. Also, simply doing an Install Workstation from configuration manager won't work either.

To fix you'll need to run psodbccrinst.exe from PS_HOME\bin\client\winx86\. When you run this, you'll get the following messages (you can ignore the Crystal configuration failed message for nVision setup):

Installing PeopleSoft ODBC Driver
Installing PeopleSoft ODBC Driver - Complete
Crystal Runtime not found, aborting Crystal configuration...
Crystal configuration failed!
Done, press Enter key to exit...
No Comments
Back to top