nVision Start-Up and Shut-Down Best Practices

Start Up

Best Practice

Close any current sessions of Excel before launching the nVision signon dialog

Many users of nVision are frequent users of Excel for their job responsibilities and will start nVision when Excel has already been started for other job functions. At startup, nVision initiates its own instance of Excel that is separate from the session that is already running, as can be illustrated in the screen shot from Task Manager:

Consequences of multiple Excel Instances

·         After completing the signon dialog for nVision, nVision fails to start up

·         As the user jumps unknowingly from one Excel instance to the other, conflicts can arise that result in  cryptic “Excel Interface Exception errors”

Resolution   

• Close any and all instances of Excel and nVision
• Start Task Manager, sort “Image Name” on the Processes tab, and end any and all instances of EXCEL.EXE and psnvs.exe
• Restart nVision

Shut Down

Best Practice

Close nVision from the nVision program, not from Excel

Consequences of incorrect shutdown

Incorrect shutdown of nVision can result in hung sessions of Excel and/or nVision in Task Manager which are not obvious to the user since no program icon is displayed in the user’s Task Bar. This can result in nVision not starting up the next time the user attempts to start nVision as described above.

Resolution

·       Close nVision by clicking on the nVision icon in the Task Bar and either navigating to File > Exit or by clicking the X as illustrated below