Run error 429

run error 429

This Error Code appears when the PC user attempts to access web pages that contain content that utilizes ActiveX. This Runtime Error happens when an. Runtime Error - ActiveX Component can not Create Object - Error Received When Emailing. How do I resolve "Run-time error '': ActiveX component can't create object"? · Have you installed the Microsoft Scripting Engine? · Is that not. run error 429


When you use the New operator or the CreateObject function in Microsoft Visual Basic to create an instance of a Microsoft Office application, you may receive the following error message:

Run-time error '': ActiveX component can't create object

This error occurs when the Component Object Model (COM) cannot create the requested Automation object, and the Automation object is, therefore, unavailable to Visual Basic. This error does not occur on all computers.

This article describes how to diagnose and resolve common problems that may cause this error.

More Information

In Visual Basic, there are several causes of error The error occurs if any of the following conditions is true:

  • There is a mistake in the application.

  • There is a mistake in the system configuration.

  • There is a missing component.

  • There is a damaged component.

To find the cause of the error, isolate the problem. If you receive the "" error message on a client computer, use the following information to isolate and resolve the error in Microsoft Office applications.

Note Some of the following information may also apply to non-Office COM servers, run error 429. However, this article assumes that you want to automate Office applications.

Examine run error 429 code

Before you troubleshoot the error, try to isolate a single line of code that may be causing the problem.

If you discover that a single line of code may be causing the problem, complete these procedures:

  • Make sure that the code uses explicit object creation.

    Problems are easier to identify if they are narrowed down to a single action. For example, look for implicit object creation that's used as one of the following.

    Code sample 1

    Code run error 429 2

    Both of these code samples use implicit object creation, run error 429. Microsoft Office Word does not start until the variable is called at least one time, run error 429. Because the variable may be called in different parts of the run error 429, the problem may be difficult to locate. It may be difficult to verify that the problem is caused when the Application object is created or when the Document object is created.

    Instead, you can make explicit calls to create each object separately, as follows.

    When you make explicit calls to create each object separately, the problem is easier to isolate. This may also make the code easier to read.

  • Use the CreateObject function instead of the New operator when you create an instance of an Office application.

    The CreateObject function closely maps the creation process that most Microsoft Visual C++ clients use. The CreateObject function also permits changes in the CLSID of the server between versions. You can use the CreateObject function with early-bound objects and with late-bound objects.

  • Verify that the "ProgID" string that is passed to
    CreateObject is correct, and then verify that the "ProgID" string is version independent. For example, use the "sprers.euation" string instead of using the "sprers.euation.8" string. The system that fails may have an older version of Microsoft Office or a newer version of Microsoft Office than the version that you specified in the "ProgID" string.

  • Use the Erl command to report the line number of the line of code that does not succeed. This may help you debug applications that cannot run in the IDE. The following code tells you which Automation object cannot be created (Microsoft Word or Microsoft Office Excel ):

    Use the MsgBox function and the line number to track the error.

  • Use late-binding as follows:

    Early-bound objects require their custom interfaces to be marshaled across process boundaries, run error 429. If the custom interface cannot be marshaled during CreateObject or during New, you receive the "" error message. A late-bound object uses the IDispatch system-defined interface that does not require a custom proxy to be marshaled. Use a late-bound object to verify that this procedure works correctly.

    If the problem occurs only when the object is early-bound, the problem is in the server application. Typically, you can reinstall the application as described in the "Examine the Automation Server" section of this article to correct the problem.

Examine the automation server

The most common reason for an error to occur when you use CreateObject or New is a problem that affects the server application. Typically, the configuration of the application or run error 429 setup of the application causes the problem. To troubleshoot, run error 429, use following methods:

  • Verify that the Office application that you want to automate is installed on the local computer. Make sure that you can run the application. To do this, run error 429, click Start, click
    Run, and then try to run the application. If you cannot run the application manually, the application will not work through run error 429 the application as follows:

    1. Click Start, and then click Run.

    2. In the Run dialog box, type the path of the server, and then append /RegServer to the end of the line.

    3. Click OK.

      The application runs silently. The application is re-registered as a COM server.

    If the problem occurs because a registry key is missing, these steps typically correct the problem.

  • Examine the LocalServer32 key under the CLSID for the application that you want to automate. Make sure that the LocalServer32 key points to the correct location for the application. Make sure that the path name is in a short path (DOS ) format. You do not have to register a server by using a short path name. However, long path names that include embedded spaces may cause problems on some systems.

    To examine the path key that is stored for the server, start the Windows Registry Editor, as follows:

    1. Click Start, and then click Run.

    2. Type run error 429, and then click OK.

    3. Move to the HKEY_CLASSES_ROOT\CLSID key.

      The CLSIDs for the registered automation servers on the system are under this key.

    4. Use the following values of the CLSID key to find the key that represents the Office application that you want to automate. Examine the LocalServer32 key of the CLSID key for the path.

      Office server

      CLSID key











    5. Check the path to make sure that it matches the actual location of the file.

    Note Short path names may seem correct when they are not correct. For example, both Office and Microsoft Internet Explorer (if they are installed in their default locations) have a short path that is similar to C:\PROGRA~1\MICROS~X\ (where
    X is a number). This name may not initially appear to be a short path name.

    To determine whether the path is correct, follow these steps:

    1. Click Start, and then click Run.

    2. Copy the value from the registry, and then paste the value in the Run dialog box.

      Note Remove the /automation switch before you run the application.

    3. Click OK.

    4. Verify that the application runs correctly.

      If the application runs after you click OK, the server is registered correctly. If the application does not run after you click OK, replace the value of the LocalServer32 key with the correct path. Use run error 429 short path name if you can.

  • Test for possible corruption of the template or of the resource file, run error 429. Problems may occur when you automate Microsoft Word or Microsoft Excel if either the template in Word or the resource file in Excel is corrupted. To test these files, run error 429, search the local hard disks for all instances of or of

    Note Run error 429 may find multiple copies of these files, run error 429. There is one copy of each of these files for each user profile that is installed on the system.

    Temporarily rename the files or the files, and then rerun your automation test. Word and Excel both create these files if they cannot find them. Verify that the code works. If the code works when a new file is created, delete the files that you renamed, run error 429. These files are corrupted. If the code does not run error 429, you must revert these files to their original file names to save any custom settings that are saved in these files.

  • Run the application under the Administrator account. Office servers require Read/Write access to run error 429 registry and to the disk drive. Office servers may not load correctly if your current security settings deny Read/Write access.

Examine the system

System configuration may also cause problems for the creation of out-of-process COM servers. To troubleshoot, use the following methods on the system on which the error occurs:

  • Determine whether the problem occurs with any out-of-process server. If you have an application that uses a particular COM server (such as Word), test a different out-of-process server to make sure that the problem is not occuring in the COM layer itself. If you cannot create an out-of-process COM server on the computer, reinstall the OLE system files as described in the "Reinstalling Microsoft Office" section of this article, or reinstall the operating system to resolve the problem.

  • Examine the version numbers for the OLE system files that manage automation. These files are typically installed as a set. These files must match build numbers. An incorrectly configured setup utility can mistakenly install the files separately. This causes the files to be mismatched. To avoid problems in automation, examine the files to make sure that the files builds are matched.

    The automation files are located in the Windows\System32 directory. Examine the following files.

    File name


    Date modified

    September 29,


    March 29, run error 429,


    May 3,


    September 29,

    September 29,

    To examine the file version, run error 429, right-click the file in Windows Explorer, and then click Properties. Note the last four digits of the file version (the build number) and the date that the file was last modified. Make sure that these values are the same for all the automation files.

    Note The following files are for Windows 10 Versionbuild These numbers and dates are  examples only. Your values may be different.

  • Use the System Configuration utility ( to examine the services and system startup for third-party applications that might restrict running code in the Office application. For more information about, see the following Microsoft Knowledge Base article:

     System Configuration Utility Advanced Troubleshooting Settings For example, Outlook Automation applications may fail because you are running an antivirus program that has "script blocker" features.

    Note Disable the antivirus program only temporarily on a test system that is not connected to the network.

    Alternatively, follow these steps in Outlook to disable third-party add-ins:

    If run error 429 method resolves the problem, run error 429, contact the third-party antivirus vendor for more information about an update to the antivirus program.

    1. On the File menu, click Options, and then click Add-ins.

    2. Click Manage COM add-ins, and then click Go.

      Note The COM add-ins dialog box opens.

    3. Clear the check box for any third-party add-in, and then click OK.

    4. Restart Outlook.

Reinstall Office

If none of the previous procedures resolve the problem, remove and then reinstall Office.

For more information, see the following Office article:

Download and install or reinstall Office or Office on a PC or Mac


For more information about Office automation and code samples, go to the following Microsoft website:

Getting started with Office development

Hey all, run error 429, Hope you are doing good, but I also know you are getting & facing Runtime Error  ActiveX Component Can&#;t Create Object Windows PC code problem on your Windows PC as well as sometimes on your smartphone device too. So today for that we are here to help you in this Error matter, by our so easy and straightforward solutions and the guides methods.

This error occurs when a user tries to open ActiveX dependent pages. This error may also occur when the COM (Component Object Model) cannot create the requested Automation object. This Error Code appears when the PC user attempts to access web pages that contain content that utilizes ActiveX. This Runtime Error happens when an automation sequence fails to operate the way it&#;s scripted. This error is the results of conflicts between 2 or run error 429 programs. This runtime error occurs if the automation server for Excel link was not registered correctly. This error issue includes your PC system freezes, crashes & some virus infection too. This runtime error happens when an automation sequence fails to operate the way it&#;s scripted. This Runtime Error indicates an incompatibility of essentials files that pastel requires to run.

This shows an error code message like,

Runtime Error

Windows Runtime Error  Active component can&#;t create object

Causes of Runtime Error ActiveX Component Can&#;t Create Object Windows Issue:

  • Runtime error problem
  • ActiveX component can&#;t create object Windows
  • ActiveX Windows PC error issue
  • Google play store error
  • Too many requests issue

You may also check;

So, here are some quick tips and the tricks for easily fixing and solving this type of Runtime Error  ActiveX Component Can&#;t Create Object Windows PC Code problem for you permanently.

How to Fix & Solve Runtime Error ActiveX Component Can&#;t Create Object Windows Issue

1. Uninstall the Microsoft .NET Framework & Reinstall it again on your PC &#;

Uninstall the .NET framework and reinstall it again

  • Go to the start menu
  • Search or go to the Control Panel
  • Click on the &#;Programs and Features&#; option there
  • Select the &#;.NET framework&#; Software there &
  • Right-click on it & select Uninstall to uninstall it
  • After that, close the tab
  • Now, again reinstall it again
  • That&#;s it, done

By uninstalling and reinstalling the .NET framework can also fix and solve this Runtime Error ActiveX Component can&#;t create run error 429 problem for you.

2. Delete the Temporary Files Folder from your Windows PC &#;

Delete the Temporary Files

  • Go to the start menu
  • Open &#;My Computer&#; there
  • Now, right-click on the driver containing the installed game
  • Select Properties option there
  • Click on the Tools option
  • & Click on &#;Check Run error 429 to check any error it is having
  • After completing, close all the tabs
  • That&#;s it, done

By deleting all the temporary files can get rid out of this Runtime Error Active X component can create object problem.

3. Fix by the (CMD) Run error 429 Prompt on your Windows PC &#;

Fix by Command Prompt

  • Go to the start menu
  • Search or go to the Cmd (Command Prompt) there
  • Click on it and opens it
  • A Pop-up will open there
  • Type these following commands there
  • Then, press Enter there
  • A succeeded message will show there
  • Now, type this command
  • Then, press Enter there
  • A succeeded message will show again there
  • That&#;s it, done

NOTE*: &#;This command is for run error 429 the Bit and the Bit processor.

By running the regsvr32 command in the command prompt will quickly fix this Runtime Error ActiveX component can&#;t create object problem.

4. Fixing by the Registry Cleaner on your Windows PC &#;

Clean or Restore the Registry

You can fix it by fixing the registry cleaner from any registry cleaner software, and it can also fix and solve this Runtime Error ActiveX component can&#;t create object Windows XP problem.

5. Create a System Restore Point on your Windows PC &#;

Fix System Restore Features

  • Go to the start menu
  • Search or go to the &#;System Restore.&#;
  • Clicks on it and open it there
  • After that, tick on the &#;Recommended settings&#; or &#;Select a restore point&#; there
  • After selecting, click on the Next option there
  • Now, follow the wizard
  • After completing, close the tab
  • That&#;s it, done

So by trying this above guide, you will learn to know about how to solve & fix this IDS Runtime Error Windows 10 ActiveX component can&#;t create object problem issue from your Windows PC entirely.

&#; OR &#;

Run System Restore & Create a Restore Point

  • Go to the start menu
  • Search or go to the &#;System Properties.&#;
  • Click on it and opens it
  • After that, go to the &#;System Protection&#; option there
  • Now, click on the &#;System Restore&#; option there
  • & Create a Restore point there
  • After completing, close the tab
  • That&#;s it, run error 429, done

Run a system restore and creating a new restore point by any of these two methods can solve this pinnacle game profiler Runtime Error Windows 10 problem from your PC completely.

6. Run the sfc /scannow command in the CMD (Command Prompt) &#;

Fix by running sfc/scannow in Cmd

  • Go to the start menu
  • Search or go to the Command Prompt
  • Click on that and opens it
  • A Pop-up will open there
  • Type this below the following command
    &#; sfc/scannow &#;
  • After that, run error 429, press Enter there
  • Wait for some seconds there
  • After complete, close the tab
  • That&#;s it, done

Run an sfc/scannow command in the command prompt can quickly fix and solve this Runtime Error ActiveX Windows 10 code problem from your PC.

7. Fix by MSConfig Command on your Windows PC &#;

Fix by Cleaning Boot

  • Go to run error 429 start menu
  • Search for &#;; in the search box and press Enter there
  • Click on the User Account Control permission
  • & click on the Continue option there
  • On the General tab there,
  • Click on the &#;Selective Startup&#; option there
  • Under the Selective Startup tab, Click on &#;Clear the Load Startup&#; items check box
  • Click on the services tab there,
  • Click to select the &#;Hide All Microsoft Services&#; checkbox
  • Then, click on the &#;Disable All&#; & press Ok button there
  • After that, close the tab
  • & restart your PC
  • That&#;s it, done

By cleaning the boot, you can quickly get back from this Runtime Error VBA Windows 8 problem.

8. Delete or Remove all the Third-Party Drivers on your Windows PC &#;

Delete or Remove all the third-party Drivers

  • Go to the start menu
  • Go to the &#;My Computer&#; or &#;Computer&#; there
  • Click on the &#;Uninstall or change a program&#; there
  • Now go to the driver which you want to uninstall
  • Right-click on it there
  • & Click on &#;Uninstall&#; there to uninstall it
  • That&#;s it, done

By deleting or removing all the third-party drivers will quickly fix this Runtime Error Windows 7 problem.

These are the quick and the best way methods to get quickly rid of this Runtime Error  ActiveX Component Can&#;t Create Object Windows PC Code problem for you entirely. Hope these solutions will surely help you to get back from this Runtime Error ActiveX can&#;t create object problem.

Also, read;

If you are facing or falling in this Runtime Error  ActiveX Component can&#;t create object Windows PC Code problem or any error problem, then comment down the error problem below so that we can fix and solve it too by our top best quick methods guides.

How do I resolve "Run-time error '': ActiveX component can't create object"?

My company has a VB6 application using Crystal Reports 7 which a client has asked to be installed on Windows 7 32 bit. It is currently installed on Windows XP 32bit SP2 machines at the client. Connection to the DB is done via ODBC to SQL Server instance on another server.

On Windows 7, the installation works fine, however when you try to open the application, the error is given.

I have looked at the following:

  • Registering all the dll's and ocx files using regsvr Some will not register as they either are registered already run error 429 the following message is given "Make sure that "[name].dll" is valid DLL or OCX file and then try again." I read this forum thread regarding this:
  • Monitored run error 429 opening of the application using a ProcessMonitor application to try and spot if there is a missing dll or ocx file - this does not seem to be the case.
  • Reviewed the application according to this list and nothing seems to be against these guidelines

I've noticed two items in the knowledge base that relate to this

  • - the comdlgocx bundled with the application is version and the one in the system32 folder on the dev machine (WinXP 32 bit) is However if this was the issue then surely it would not work currently?
  • - I'm not sure how to confirm that this is the issue

Finally, due to complexities, I am not allowed to make code changes to this application. Even if I was, I'm not a VB6 programmer, just the guy who got the terribly support project! If code changes are required, then I'll have to investigate using WinXP mode.

Update: I get the same error in XP Mode. That's a Win XP with Run error 429 VM. This runs on a Win XP SP2 VM, is there potentially something in SP3 that would have caused this to occur? Or is it just a fact of it being XP Mode?

ErrorActivex Component Can't Create Object

For Customers who received an ErrorActivex  Component can't create object error after installing latest service pack update
  1. Close Team Manager for Swimming
  2. Right click on Desktop icon for Team Manager
  3. Left click on Properties
  4. Click on Compatibility tab
  5. Select Run this program in compatibility mode
  6. Select from list version of Windows you are running (for Windows 10 select Windows 8)
  7. Click Apply, then close out of icon
  8. Open Team Manager for Swimming
  9. If error persists go back to Compatibility tab on Team Manager icon
  10. Uncheck box to Run this program in compatibility mode
  11. Check option to Run this program as an administrator
  12. Click Apply, the open Team Manager

Was this article helpful?   YES   NO

Restore your computer to peak performance in minutes!

  • Step 1: Download and install ASR Pro
  • Step 2: Open the program and click "Scan"
  • Step 3: Click "Repair" to start the repair process
  • Get a faster

    You may be experiencing runtime Error Windows XP SP3. There are several steps you can take to fix this issue and we will get to that shortly. This read error is activated when the plan tries to access netbeans zend framework error file that does not exist, is malicious, or is not registered with Windows.

    There is a computer at your workplace with software thatSome stopped working after a remote startup security update on the forum/domain database. When opening the school, a runtime error appears – Unable to create an item for the ActiveX component. The program is launched first when one of the CRM/Billing/etc programs from the package of acts in the selector base is launched. I know that the Infoscreen program has a built-in IE control for displaying manufacturer’s posters (Visma) and has a database connection, run error 429. I think updating the database changed something.

    In some programs, it was difficult to diagnose errors and determine the cause. I thought I knew enough about debugging to determine the cause, but a simple opening with the Walker habit program finds missing DLLs.

    How and what program should be used to find out what is wrong with the program? Instead of fixing a specific problem, this suspect aims to provide more information on how to fix these types of problems in the future.

    How to fix runtime error ActiveX can t create object Windows 7?

    make sure you start run -> type “regsvr32” and click the entire file is missing from the above list, or if the above list does not help, owners may need to download and run the latest script update from most Microsoft websites. Download the update and save here:

    My consultant has a VB6 application using Reports crystal 7 that the client isAsked for installation in bit version of 7 windows, run error 429. It is typically installed on bit SP2 machines running Windows XP when the client file. The connection is made via ODBC to the database of a SQL server instance with another server.

    However, in Windows 7, the installation of components works when you think about opening the application normally, an error usually

  • Registering dll and ocx files with regsvr Some do not actually register because they are usually already registered or receive the following message: “Make sure “[name]” marketing, run error 429. Is a dll” is probably a valid DLL document or OCX, please try again and”. I rate this forum against this thread:
  • Monitor the opening of certain applications using the ProcessMonitor application to try to determine if there is a transfer of Run error 429 or ocx files – it does not seem to be.
  • I checked the application in the retail store function and found no violations of these rules. noticed
  • How to fix Run time error ActiveX component can t create object?

    Program the specified a virus for Windows System File and repair the system changes with system restore.

    I have two items in the knowledge base that indicateto this

  • – cause comdlgThe provided ocx in the application is package and the one found in the system32 folder of product 32 on-dev (bit is 6 winxp).1. However, if this is a problem, was then at the moment it is not? Job
  • – not sure how the market can confirm this
  • Finally, due to the complexity, I’m no longer allowed to make any changes to the code to help you with this application. Even if it were me, I’m not a VB6 programmer, just the guy who supported the project so passionately! actual code changes are needed, I will check for you if you can use WinXP mode.

    How do you fix run time error ?

    Solution 1 – Run an SFC scanWorkaround: Re-register the affected sprers.euound: Resave 3 the file that is mentioned in this error sprers.euon 4: Reinstall the Microsoft Windows script for (Windows XP and Windows Server users only)

    Update: I keep getting the same error in XP mode. It’s an XP one win VM with sp3, run error 429. Running this on a Win XP SP2 VM, maybe there’s something small in SP3 that could do this? call Or until it’s XP mode?

    Run-time ActiveX error ; ActiveX component can&#;t create object

    The issue applies to all IDAutomation products that include ActiveX or .NET COM DLLs such as Barcode ActiveX Controls and 2D Font Run error 429 as the 2D QR-Code Font and Encoder.


    This error may occur because the ActiveX or .NET COM DLL being accessed is not registered on the system.

    1. Install the Microsoft .NET Framework if run error 429 is not installed.
    2. Close all open applications and delete files in the %TEMP% run error 429. To easily access this folder, run error 429, open the command prompt and type the following pressing Enter after each line:
      CD %TEMP%
      DEL *.* /S
    3. Obtain the latest version of the IDAutomation Barcode product being used.
    4. Reinstall the component package. Run error 429 should automatically register the DLL.
    5. If problems continue, try the run error 429 process below.

    To register the DLL manually, perform the following:

    • Open the command window as Administrator. This is usually located in Start &#; Programs &#; Accessories or type CMD from the search area.
    • Change to the directory the DLL is located in; which is usually the %systemroot%\System32 directory. On 64 bit systems, the DLL may also be in %systemroot%\syswow In bit versions of Windows, there are two versions of the Regsvexe files:
      The bit version is %systemroot%\System32\regsvrexe, where 64 bit DLLs are located.
      The bit version is %systemroot%\SysWoW64\regsvrexe, where 32 bit DLLs are located.
    • Type the following at the command prompt:
      where is the name of the DLL to be registered.
    • If a DLL entry-point DllRegisterServer error is received after error 001 expected token regsvr32, the DLL must be registered with instead. To do this, verify the .NET Framework is installed and type the following at the command run error 429 For .NET Framework
      C:\Windows\\Framework\v\ /codebase /tlb
      For .NET Framework 4:
      C:\Windows\\Framework\v\ /codebase /tlb
      where is the name of the DLL to be registered and C:\Windows\\Framework\* is the path to the file.


    Leave a Comment