nVision conversion issues

1 Star2 Stars3 Stars4 Stars5 Stars (No Ratings Yet)


In this post I would like to share the recent issues and workarounds we have gone through while upgrading to PeopleTools 8.53.  We had an issue with nVision client crashing when attempting to run a layout after converting from Office 2003 to Office 2007/2010.

I checked and this layout runs just fine under Tools 8.50 but when trying to do so under Tools 8.53.11 it crashes the nVision with the following error – this is from Windows Event Log:


Faulting application name: psnvs.exe, version:, time stamp: 0x52f2f20e
Faulting module name: ntdll.dll, version: 6.1.7601.22436, time stamp: 0x521eaa80
Exception code: 0xc0000374
Fault offset: 0x000ce723
Faulting process id: 0x1a34
Faulting application start time: 0x01cfc2f867fa73b4
Faulting application path: C:\psft\853\bin\client\winx86\psnvs.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: 21db0ba4-2eec-11e4-b0f0-5c514fbb52eb
Error Codes
Exception code: 0xc0000374

The issue is caused by the unnamed ranges that are used in the nVision layouts. In our case there were some named ranges that were used in formulas by were dynamically defined by the macros called vi nvsInstanceHook.

The only way to currently resolve this issue is to define those ranges in the layout. Here is the example:

For example :

nvision_name_rangeCell Q53 has a formula that references Cell P53 that has a formula that uses undefined Name Ranges highlighted below in red:

  • Go to Formulas Tab > Name Manager and check to see if the name range is define there – if not then that is the issue.
  • You can also confirm if this is the issue by Double-clicking the cell in the layout that should cause the Excel and nVision to crash:


  • If that is the case you have to restart your machine or go to Task Manager and end all nVision and Excel processes



In order to resolve this you need to define the name range in the spreadsheet.


  1. Open nVision and the layout
  2. Go to Formulas Tab > Name Manager
  3. Click new and define the Range to point to some far reaching cell like below that you are sure will not be used by your layout or macros in it:

After you define the name ranges you should see that you do not have invalid names errors shown in Excel:


I hope this helps.

The full details of the references and patches can be found by following the thread that I created on Oracle Community



I really want to know what you think