Register Components

For questions regarding installation and registration of EViews.

Moderators: EViews Gareth, EViews Jason, EViews Steve, EViews Moderator

lpapakonstantinou
Posts: 7
Joined: Wed Jan 24, 2018 1:34 am

Register Components

Postby lpapakonstantinou » Thu Jan 25, 2018 5:18 am

Hi all,

in Eviews-10 installation with application running on a Network Server (same server which License Server is installed on)
every time a user launches application gets a prompt window in order to Register Components .
After registering them (press Yes(All) and verify via ProgReg.ini file) we see a few components registered
and a few still unregistered, although we pressed Yes(All) button.

Is that related to the specific licensing scheme we have purchased ?

Since we do not want users to be notified about the registered components, every time that they launch the application,
is there any way in order to prevent that initial window from showing up ?

Thank you in advance

EViews Steve
EViews Developer
Posts: 524
Joined: Tue Sep 16, 2008 3:00 pm
Location: Irvine, CA

Re: Register Components

Postby EViews Steve » Thu Jan 25, 2018 9:31 am

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
stop_regcom.png (12.92 KiB) Viewed 846 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:

Code: Select all

EViews10.exe /regcomsilent


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:

Code: Select all

EViews10.exe /helpregistersilent


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.

lpapakonstantinou
Posts: 7
Joined: Wed Jan 24, 2018 1:34 am

Re: Register Components

Postby lpapakonstantinou » Mon Jan 29, 2018 12:52 am

Thank you very much for your prompt response. I have tried pre-registration command in a test-workstation (opened cmd with elevated privileges) as provided in your former post but there are still unregistered components, so according to your comment I should rather send you a screenshot with all the components which are shown as "Not-Registered".

As far as suppress of the dialog box is concerned, I made necessary changes in the values in EViews32.ini file as per your guidance and the register components dialog box is not appearing in the first run of Eviews

lpapakonstantinou
Posts: 7
Joined: Wed Jan 24, 2018 1:34 am

Re: Register Components

Postby lpapakonstantinou » Mon Jan 29, 2018 1:28 am

Furthermore, prior to sending an email to Eviews support, we would like to clarify another problem we are facing

Some of our users reported that when they open a specific workfile and they have selected panel regression with period random effect (with list square estimation) when selecting an equation and in the equation window View >> Residual Diagnostics >> Eteroskedasticity Tests the below error message is shown up and no test is being performed

Is it possible that this problem is related to the incomplete registration of part of the components or it is a totally different issue that should be also examined via Eviews support ??

Thanking you in advance
Attachments
Eviews10_Error.PNG
eviews10_error
Eviews10_Error.PNG (13.37 KiB) Viewed 800 times

EViews Steve
EViews Developer
Posts: 524
Joined: Tue Sep 16, 2008 3:00 pm
Location: Irvine, CA

Re: Register Components

Postby EViews Steve » Mon Jan 29, 2018 8:27 am

"This feature requires EViews 9.5" is a bug on our part. It will be fixed in the next EViews 10 patch, sometime this week.

As to why you're getting unregistered components after a register all, make sure you have all EViews 10 subfolders in your network file share as a lot of the components that get registered exist in those subfolders.

lpapakonstantinou
Posts: 7
Joined: Wed Jan 24, 2018 1:34 am

Re: Register Components

Postby lpapakonstantinou » Mon Jan 29, 2018 8:59 am

Hi Steve,

under Eviews10 network file share there is a subfolder named as "EDX_40" containing the below subfolders and .dll files.
Kindly check below attached screenshot

Eviews10_Subfolder.PNG
Eviews10_Subfolder.PNG (10.38 KiB) Viewed 782 times

Is it possible that the aforementioned sub-folders should be located at an upper directory level (e.g. under Eviews10 folder)?

EViews Steve
EViews Developer
Posts: 524
Joined: Tue Sep 16, 2008 3:00 pm
Location: Irvine, CA

Re: Register Components

Postby EViews Steve » Tue Jan 30, 2018 10:20 am

There were some surprising findings from this issue that I'd like to share with anyone trying to run EViews from a network file share.

When you run REGCOMPONENTS from within EViews that is running from a network folder, our external .NET EDX database libraries are not getting registered properly due to a UAC issue. Specifically, when our .NET DLLs are registered with Microsoft's REGASM, REGASM is translating the file path to into a UNC path -- and for some reason, this UNC path is not accessible by the local SYSTEM account whenever EViews tries to access the library (all .NET libraries are hosted by mscoree.dll when they are used by a COM client such as EViews). I believe this has to do with permissions of the local SYSTEM account.

A solution is to use drive letters instead. The caveat here is that a mapped drive letter is not automatically available to the elevated user account so you have to first manually re-map the same drive letter to the network folder while being elevated, and then re-register all of our components using that drive letter. Here are the steps I used to resolve this issue:

  • On the client machine, open an elevated DOS command window.
  • Use the NET USE <drive letter>: <UNC path to network folder> command to create the drive mapping (e.g. NET USE Z: \\servername\folder)
  • Switch to the new drive (e.g. Z:)
  • Navigate to the EViews folder on the mapped drive.
  • Launch the main EViews executable by typing in the EXE name and hitting Enter.
  • In EViews, run the REGCOMPONENTS command and click the "Yes (All)" button. Wait for the success message.
  • Re-run REGCOMPONENTS to verify that all database elements are now marked as "Registered"

You will have to make sure this drive letter is available each time you login so that Windows will be able to find the libraries on the network whenever EViews asks for it. It's possible that you may need to put the NET USE command into an elevated login script for each of your users in order to be sure of this.

lpapakonstantinou
Posts: 7
Joined: Wed Jan 24, 2018 1:34 am

Re: Register Components

Postby lpapakonstantinou » Wed Jan 31, 2018 9:08 am

Dear all,

as per Steve's guidance, please be informed that following the above mentioned steps we managed to complete components registration in a simulated environment that we have created, by mapping the UNC path to an unused network drive.

We have created a simple batch script including the net use command in order to perform the drive mapping to the network file share.
Since our end users may belong to different OU's thus making the solution of creating a new GP Object not preferable, could you please advise whether we can do it by another way (granting to our users elevated/admin privileges does not meet our requirements)

Thank you


Return to “Installation and Registration”

Who is online

Users browsing this forum: No registered users and 1 guest