Topic Thread

Expand all | Collapse all

Cannot create ActiveX component.

  • 1.  Cannot create ActiveX component.

    Posted 05-22-2019 17:33
    Hi all,

    Here is the error message:
    ERROR: Internal : Could not execute code stage because exception thrown by code stage: Cannot create ActiveX component.
    While I try to Create Instance for Excel 
    Please help me with this thanks in advance

    ------------------------------
    guna vardhan meesala
    rpa developer
    ------------------------------


  • 2.  RE: Cannot create ActiveX component.

    Posted 05-28-2019 04:35

    Generally, this issue is associated with Microsoft Office product when utilising a Visual Basic call to invoke it. Therefore, I would suggest you seeking information from the Microsoft websites of forums.

    Also, please find the following knowledge base articles for further information.



    ------------------------------
    Jega Avinasinathan
    Customer Support Engineer
    Blue Prism
    ------------------------------



  • 3.  RE: Cannot create ActiveX component.

    Posted 05-28-2019 16:32
    Do you experience the error on your runtime resources only (in resourcepc mode)? Or do you experience it in debug mode as well?

    ------------------------------
    Peter Tarrant
    Blue Prism Operations Specialist
    Agilify
    ------------------------------



  • 4.  RE: Cannot create ActiveX component.

    Posted 07-15-2019 23:15
    Hi Peter, 
    We have this issue on Runtime Resource Only, but when we run in studio, don't have this issue. Do you have a fix for this? 

    THanks, 
    Karli

    ------------------------------
    Karli Quintana
    Automation Associate
    EQUINIX INC
    America/Los_Angeles
    ------------------------------



  • 5.  RE: Cannot create ActiveX component.

    Posted 07-17-2019 19:55
    Edited by Peter Tarrant 9 days ago
    When you run the Blue Prism application in resourcepc mode, are you running with highest privileges? You generally want to be running Blue Prism as an administrator.

    If you are utilizing RDP, competing terminal sessions can also interfere with a lot of application functions. Using the console command qwinsta can tell you what sessions are running on your device (really only applicable if you are using Windows Server)

    A brute force method can always be to re-install office or even re-imaging the runtime resource.

    ------------------------------
    Peter Tarrant
    Blue Prism Operations Specialist
    Agilify
    America/Detroit
    ------------------------------



  • 6.  RE: Cannot create ActiveX component.

    Posted 07-17-2019 21:51
    Hi Peter, 

    What is your recommendation for making the Resource PC run with highest privileges? Through the task Scheduler Options? 


    ------------------------------
    Karli Quintana
    Automation Associate
    EQUINIX INC
    America/Los_Angeles
    ------------------------------



  • 7.  RE: Cannot create ActiveX component.

    Posted 07-18-2019 13:26
    For runtime resources, yes, I would suggest creating a task to start Blue Prism in resourcepc mode upon logon of the domain account that your automation uses and set it to run with highest privileges. I prefer this so that if I RDP in to do maintenance on an admin account, I don't start Blue Prism. For interactive clients, I would suggest adjusting the setting on your desktop shortcut to always run as administrator.

    ------------------------------
    Peter Tarrant
    Blue Prism Operations Specialist
    Agilify
    America/Detroit
    ------------------------------



  • 8.  RE: Cannot create ActiveX component.

    Posted 07-18-2019 03:51
    Hi Peter, 

    Thanks for pointing us the right direction. We made it work in our 5.4 environment by running highest privileges. But the same method don't work in 6.4 environment though. Any further advice?

    Thanks
    Feng

    ------------------------------
    Feng Wang
    Sr Manager
    Equinix
    ------------------------------



  • 9.  RE: Cannot create ActiveX component.

    Posted 07-18-2019 14:55
    I presume the problem is the same, working fine in studio through the interactive client but not on runtime resources on resourcepc mode.

    If your 6.4 is a production environment, there may be additional security that is not allowing you to launch an application in this manner. And it could be the device needs to be re-imaged. We have encountered cases where devices were not regularly rebooted and started having a myriad of issues (including this one) and a re-image solved all of the issues.....

    ------------------------------
    Peter Tarrant
    Blue Prism Operations Specialist
    Agilify
    America/Detroit
    ------------------------------



  • 10.  RE: Cannot create ActiveX component.

    Posted 05-12-2020 15:48

    Hi Peter,

    I am getting this error in both Studio and Control Room, it was working fine until I added a language pack to Office, even after removing it the error persists.
    Most solutions I found online involve the DCOM config, but I can't make them work so far. 
    Hope there is a better solution than reinstall Office.

    Thanks a lot,
    Sebastian



    ------------------------------
    Sebastian Nuñez
    ------------------------------



  • 11.  RE: Cannot create ActiveX component.

    Posted 05-12-2020 16:33

    Hi, Sebastian.

     

    Try to uninstall and install office again.

     

    Best regards.

     

     

     

     






  • 12.  RE: Cannot create ActiveX component.

    Posted 05-12-2020 17:00
    At that point, it really is an issue with the OS not allowing the vb call to create the instance. That can be tied to your user or DCOM settings. You could try and do a gpupdate /force. You can also make sure the registry setting didn't get changed that allows active x components to run.

    Enable
    Registry HiveHKEY_LOCAL_MACHINE or HKEY_CURRENT_USER
    Registry PathSoftware\Policies\Microsoft\Windows\CurrentVersion\Internet Settings\Zones\3
    Value Name1200
    Value TypeREG_DWORD
    Value0

    cid:bec64311-1997-4b62-afa7-3d1d44d0154e

    Peter Tarrant | Product Design Architect

    4030 Vincennes Road | Indianapolis, IN 46268

    m: 317.343.7068 | e: peter.tarrant@agilifyautomation.com

    cid:image009.jpg@01D3D172.D8370E00cid:image010.jpg@01D3D172.D8370E00cid:image011.jpg@01D3D172.D8370E00cid:image012.jpg@01D3D172.D8370E00 

    CONFIDENTIALITY NOTICE:
    This email message and any accompanying data or files is confidential and may contain privileged information intended only for the named recipient(s). If you are not the intended recipient(s), you are hereby notified that the dissemination, distribution, and or copying of this message is strictly prohibited. If you receive this message in error, or are not the named recipient(s), please notify the sender at the email address above, delete this email from your computer, and destroy any copies in any form immediately. Receipt by anyone other than the named recipient(s) is not a waiver of any attorney-client, work product, or other applicable privilege.





  • 13.  RE: Cannot create ActiveX component.

    Posted 06-25-2019 00:21
    Hi

    Is this issue resolved or still pending, if it resolved, can I know the solutions​

    ------------------------------
    Vamshi Krishna Dasa
    Developer
    Fujitsu
    Asia/Kolkata
    ------------------------------



  • 14.  RE: Cannot create ActiveX component.

    Posted 11-26-2019 05:59
    Hi All,

    For me this issue was resolved by changing the Trust Center settings in the excel application of the resourcepc. The ActiveX controls were blocked by the excel application by default and by selecting the option 'Never show information about blocked content' in the Trust center settings solved this issue.

    But selecting this option may not be a good method if security is concerned.

    Thanks
    Abhijith

    ------------------------------
    Abhijith Babu
    Automation Engineer
    Freelance
    Asia/Kolkata
    ------------------------------



  • 15.  RE: Cannot create ActiveX component.

    Posted 06-30-2020 13:25
    Hi
    We ran into the same problem - the reason was that due to failures in the past Excel had more and more "recovered files" when opening. Hence the process got slower and slower until the point where it crashed and we got the ActiveX error message.

    So if you are  lucky this is the cause. Open Excel on the runtime resource and wipe all recovered files. 

    Now we just need to create a component that checks and wipes this automatically :D

    Brgds
    Christian

    ------------------------------
    Christian Jørgensen
    Senior System Analyst
    Yara International ASA
    Europe/London
    ------------------------------