Many of our customers run EViews from a network file share especially when using a concurrent server license. Also, the appearance of the Register Components dialog is not licensing related - this check happens for all license types.
The Register Components dialog was designed for exactly this type of network installation where a user might be running EViews without having run our installer program (which performs the proper registrations for you at the end of the installation). So when EViews runs for the first time, it sees that there are components that are not registered on the local machine and displays the dialog. It does this check once a day the first time you run EViews.
If you wish to suppress the Register Components dialog from appearing again, you can click the "Stop daily check of component registration" checkbox on the Register Components dialog the first time it appears:
- stop_regcom.png (12.92 KiB) Viewed 25516 times
This setting is saved in the user's EViews32.ini file usually located in this directory:
Code: Select all
%AppData%\IHS EViews\EViews\EViews32.ini
which usually resolves to:
Code: Select all
C:\Users\<username>\AppData\Roaming\IHS EViews\EViews\EViews32.ini
If you open this file, and look for "Component Check v10=" for EViews 10 32-bit, or "Component Check v10 x64=" for EViews 10 64-bit, you can turn it off by setting both values to zero.
Without proper registration, some functionality (such as our Excel Add-In, COM Automation support, and the ability to share data with R & MATLAB) will not be available to the user on their local machine.
Under normal circumstances, the Register Components dialog should be able to register everything that it can (assuming all of our files are available in the same folder) as long as the current user is a local administrator of the machine. If you're seeing some items remaining "Unregistered" even after clicking the "Yes(All)" button, I would double-check your ability to write to the Windows Registry (which is how most components are registered with Windows). If available, logout and then login as someone else that does have full authority on the machine and try REGCOMPONENTS again to see if that works better. Or right-click the EViews 10 shortcut and select "Run as Administrator", and then run REGCOMPONENTS to try the re-registration again with EViews that has already been elevated.
If you're still having issues, send us a screenshot of the dialog showing the Unregistered components (along with your EViews serial number) to
support@eviews.com and copy me as well (
steve@eviews.com).
Steve
By the way, you can pre-register all of our components for your users by running the following command line:
Also, our CHM help file (which you can display by pressing F1 from within EViews) tends to have display issues when being run from a network file share due to Windows security restrictions. We provided a quick way to allow an exception to the EViews network folder via another command line:
If you run both of these commands for each of your users (perhaps in an elevated login script), then when they run EViews, they should have full functionality and they shouldn't see the Register Components dialog appear either.