Known Issues
Issue: Workstation Terminals do not Register even with all the above Completed
Sometimes the workstation terminals do not register even with all the above completed. Solution
1.In Microsoft Internet Explorer, click Tools, click Internet Options, click the Security tab, click Trusted Sites, click Custom level..., and set these Security Settings:
2.If configuring the above still does not allow the terminal to register or Java to launch, we recommend uninstalling all client side components and then deleting the Opera folder at C:\Program Files (x86)\Micros Systems, Inc\Opera.
3.Also delete the Opera folder at C:\ProgramData\Oracle\Opera. If you cannot delete these folders, this means that some process is still running and workstation bounce may be needed.
4.After restarting the workstation, reinstall all client side components (RegTerm, Adobe Reader, Jinit, Java JRE, OperaPrintCtrl, and ScreenWiz, as Administratoruser.
5.If TermReg is still not working, then try Restore advanced settings and Reset...on the Advanced tab as seen below:
6.On the Privacy tab, deselect (turn off)Pop-up Blocker:
7.Then close the browser and launch again.
Issue: Opera Workstation Undefined or Keeps Prompting to Install RegTerm, OperaPrintCtrl, Adobe Each Time Login Screen is opened
Depending on the version of OPERA installed and other software running on the workstation, it is possible to encounter an issue documented in Oracle support document ID 2193783.1.
When opening the shortcut to access the OPERA login screen, the prompt to install TermReg, JinitCheck, OperaPrintCtrl, and Adobe keep popping up, even if these have already been installed.
Or
Terminal Name remains UNDEFINDED even though TermReg has been installed.
Cause
1)This could be due to the Anti-Virus program on the workstation stopping the install from completing or blocking access to certain OPERA component files located in folders such as:a)C:\program files (x86)\micros systems, inc\opera\* b)C:\programdata\oracle\opera\*
2)It could be due to the Windows User having insufficient rights to install or access the OPERA components.
3)TermReg.ini might need to be manually created in the correct location.
Solution See the above reference support document for solution options that include re-running some of the installers as administrator, temporarily disabling AV file locking, or manually creating the required files.