ActiveX files for FactoryTalk View SE


July 3, 2019 at 6:15 am


Life Doctor Fix It Member

 Ken Moore Avatar

Registered: 2004

Location: May North, West, South Carolina

Posts: 3 229

Idle Diagnostics is an Active X plugin for building RSView32. It is typically used to log out the current user and log in with read-only permissions. It looks like someone or your project migrated to a new PC/server and didn’t install the Active X plugin. You need to replace the plugin.

Siemens Certified Functional Safety Specialist,
ID: SFSP17010238
NRA benefactor


I am very, very new to RSView software. You recently got your own sample program, but when I try to open a graphic display (let’s say a display file called Page01), My computer tells me: “Could not shrink ActiveX control to display page 01: DSE_OCX_02.CMD: ActiveX control not found Cause: DSE_INPUT_02.Input_Box: ActiveX control not available, detected on computer” Can anyone help me how can i find the ActiveX control required to open some graphic display?are these files because of the original pc of this service or do you need to install something else on my pc?

FactoryTalk View SE ActiveX Controls

An ActiveX control is an engineering object of a component that can be reused by many applications on a computer or between multi-tiered computers. This is a Microsoft technology that works with the Rockwell Automation FactoryTalk SE HMI application for graphics.

Importance Of Having The Right ActiveX Files

Let’s put the ieframe.dll ActiveX file aside for a demo and make sure you have a valid ieframe.dll on your server where your FactoryTalk SE HMI application resides, otherwise you could end up with unresolved issues throughout your application and and failure of the HMI server.

First, you need to pinpoint which edition of Windows Server you’re using the most by right-clicking

about work and choice of skills. This should show exactly which version of Windows Server you are typically using.

You should be prompted so you can see what version of Windows these owners have, and you can note these facts as you will use the element to make sure the version of ieframe.dll is correct for the version of Windows Server you are running. .

Check All Versions Of Ieframe.dll

To check the version of ieframe.dll, you must first obtain the version number, which is very easy to do with our tool that FactoryTalk has developed absolutely for this process, which comes with the ‘origin’ setting of almost all FactoryTalk Software Studio listed. This tool is probably called GetVers.exe and is in the same location as the HMI and standalone projects, except there is an ActiveX Control Configuration folder in the project folder.

Location in Windows 5,Windows Server R2, 2008 and Windows Server 2012:

Here is the GetVers.exe file, but you can’t just use the file from here because it was created specifically to work with Windows CMD.exe

Open CMD.exe from this menu, run it, and when it is published, enter the following CD: C:User\Public\Documents\RSView Enterprise\ActiveX Control Setup, then press Enter.

This will direct your CMD.exe to your ActiveX control installation folder.

Now type ieframe.dll into CMD.exe in GetVers and according to the media, you will get the personal version of ieframe.dll that you are actually using so families can write down the information at this point and thus close CMD . exe – Command line.

Compare Most Ieframe.dll Files With Windows Server That Edition

Now that you have the version associated with your edition of Windows Server and the version of ieframe.dll, customers can now check to see if ieframe.dll often matches the advertised version of Windows Server.

IEframe.dll is the Internet ActiveX directory for Explorer, so just check the Microsoft website for the correct product. If you check the Microsoft online store, it says that Windows Server 2008 R2 should work It is running ieframe.dll 8.0.7600.20955, i.e. Internet Explorer 8.

After checking that the files match, and maybe not, you can decide if the correct version works or not, and if not, you might run into weird unresponsive problems in the HMI application. Maybe

You can do this with most of your ActiveX files on the server that is likely to host our HMI application.

FactoryTalk View SE clients can automatically install the correct versions of ActiveX controls used for graphic displays.

To effectively deploy ActiveX controls, you must create .cab documents for ActiveX controls and optionally place the .cab files in the same folder where you installed FactoryTalk View SE.

To do this, run the CABARC.exe program from the HMI server web page. CABARC.exe is present in:

  • (Windows 7 Professional, Windows Vista, Windows Server 2008)
    ..\Users\Public\Documents\RSView Enterprise\SE\ActiveX Control Setup
  • (Windows XP, Windows Server 2003) ..\Documents with Settings\All Users\Shared
    Documents\RSView Enterprise\SE\ActiveX Control Setup
  • For more information about creating CAB files, see the MakingCabFiles.txt text file inIn the ActiveX control configuration folder. The binding text file contains examples of creating .taxi files, information and conventions used.

    Often, when you open a screen image that contains uninstalled ActiveX controls, it will launch, but a colored box will appear instead of the ActiveX control.

    Creating the .cab file is probably done using CMD Rapid on Windows. First open a CMD prompt and then enter the location of the CD file, for example because in our case we showed above that the home CD would be C:\Users\Public\Documents\RSView Enterprise\ActiveX Control Setup.

    So the cmd prompt will immediately point to this file location, which you can use to use CABARC-exe.

    To then quickly create a new CAB file in CMD, enter a specific file name in CABARC N.

    Let’s say we wanted Keypad.ocx to really help with this, so how should the first CMD be searched.

    Then press Enter to create the desired file. At the moment you are using the generated file, but the actual CAB file. To create it, you need to enter CABARC N, then the name of the CAB application and the name of this CAB file.

    If you decide to create a keyboardocx.CAB file, it should look like this.

    Then press type, this will create a new CAB file and also load the ocx file you created.

    If you open the CAB statement again, I would say it should now contain an ocx file.

    Note that this method only creates new files if they don’t exist, it doesn’t match files between patient and server, client computers must match ActiveX files on the server for all graphics and other conditions to work. right.

    Often you can just copy the created movies and then paste them into a file in the same location on the owner’s computer, but this depends on the situation, so if you do this, it’s a good idea to back up old files. In fact, if nothing changes, you can restart your PC.

    I hope this was helpful, and while there are any comments or pros and cons, please leave me a comment that appears below or in the contact section and a link to this site. We hope to to learn from you a successful answer.