|
#1 | Link |
Registered User Join Date: Apr 2019 Posts: 8 |
BD Rebuilder start-up problem For the last couple weeks every time I try to open BD Rebuilder, I get the following error; System error &H80004023 (-2147467229). A Microsoft installer error was encountered. I have spent a lot of time on the phone with Microsoft and could not fix the problem. This error does not happen with any other applications on my computer. I have nowhere else to turn but ask the gang of experts on this forum for some advice. I hope I am not violating any forum rules with my ask for advice on this problem. |
|
|
|
#2 | Link |
Elit Amans Join Date: Feb 2005 Location: Sweden Posts: 275 |
A quick google search gave me this from the MS community.. Quote: This error might be a result of some issues with the Windows Installer service or it might be an issue with the package that you have downloaded. So, I would suggest you to try downloading the package again and then try installing it. Let’s try some troubleshooting steps and check if that helps: Method 1: Check the Windows Installer Service and also unregister and re-register the Windows Installer Step 1: Check the Windows Installer Service a) Press “Windows Logo” + “R” and type “service.msc” b) In the “Service” window scroll down and find the “Windows Installer” service. Double-click “Windows Installer” in the Services list to open its properties window. c) On the “General” tab, make sure the service is started under “Service status”. d) If the service was stopped, under “Service status”, then start the service by clicking on the “Start” button, and then click “OK”. Step 2: Unregister and re-register the Windows Installer a) Press “Windows Logo” + “R” to open the Run Command Window. b) In the run command window type the following command and click on “Ok”. MSIEXEC /UNREGISTER c) Press “Windows Logo” + “R” to open the Run Command Window again. d) In the run command window type the following command and click on “Ok”. MSIEXEC /REGSERVER e) Now, try installing the package again and check. |
|
|
|
#3 | Link |
Join Date: Mar 2006 Location: Barcelona Posts: 5,034 |
Quote:
Originally Posted by HH2 For the last couple weeks every time I try to open BD Rebuilder, I get the following error; [B]System error &H80004023 (-2147467229). Did you run the «REG_MSCOMCTL.BAT» as described in the first post of this thread? |
|
|
|
#4 | Link |
Registered User Join Date: Apr 2019 Posts: 8 |
Thanks for the input, I tried all the above and the problem is the same. My computer would not run, REG_MSCOMCTL.BAT |
|
|
|
#6 | Link |
Registered User Join Date: Apr 2019 Posts: 8 |
Thanks for the suggestions, I will work on this later today or tomorrow. It sure looks that the first link is relating to the same problem. |
|
|
|
#7 | Link |
Registered User
Join Date: Sep 2003 Location: Berlin, Germany Posts: 3,062 |
I do not use BD-RB, but AVStoDVD is also written in VB6 and also needs a correctly registered mscomctl.ocx. And Win10 users had the same problem which you are experiencing. The problem is that the included REG_MSCOMCTL.BAT file is not smart enough for Win10. A while ago I made an improved version for AVStoDVD which should also work for BD-RB. Download here: https://www.sendspace.com/file/2iwmqm I included a newer version of the OCX file, but generally the older file which comes with BD-RB should work under Win10. Just place the ocx file and the batch file in the same folder and double-click the batch file. This batch file will not delete mscomctl.ocx in one of the Windows system folders. If there is already an incompatible or faulty ocx present in System32 or SysWOW64 then these files will be kept. This means that after executing the batch it could happen that BD-RB will still refuse to start. In this case you have to delete all previous versions of the mscomctl.ocx file from your system folders and then execute the batch file again. Good luck
Last edited by manolito; 7th May 2019 at 16:38.
|
|
|
|
#8 | Link |
Registered User Join Date: Jan 2009 Posts: 1,368 |
It’s smart enough just fine. Rightclick bat file > run as admin > done |
|
|
|
#10 | Link |
Registered User Join Date: Apr 2019 Posts: 8 |
I tried the bolded below but really don’t understand how to modify the path, etc; So its probably better to open an Administrative CMD prompt (Start -> Windows System -> right click on CMD Prompt -> More -> Run As Administrator)… When it launches, while in the window change to the BD-Rebuilder directory, and run the batch file from there (that is where the BAT file and the OCX file reside)…. OR edit the BAT file, specify the path to the OCX file… then save/run it. I always get the same error as stated at the beginning of my post (ref. above). |
|
|
|
#11 | Link |
Registered User Join Date: Jul 2012 Posts: 1,208 |
Have you tried manolito’s bat file? It might work |
|
|
|
#12 | Link |
Registered User Join Date: Apr 2019 Posts: 8 |
I have not tried it yet, not sure of the process, I need a more detailed explanation. |
|
|
|
#13 | Link |
Registered User
Join Date: Sep 2003 Location: Berlin, Germany Posts: 3,062 |
What exactly is not clear to you? The archive contains the files REG_MSCOMCTL.BAT and mscomctl.ocx. The ocx file is just a newer version of the file which comes with BD-RB, it should not be needed. All you have to do is extract REG_MSCOMCTL.BAT into your BD-RB folder (where the original file by jdobbs is located) overwriting the original file. Then right-click the BAT file and run it as an administrator. Only if this does not work the following applies: Quote: If there is already an incompatible or faulty ocx present in System32 or SysWOW64 then these files will be kept. This means that after executing the batch it could happen that BD-RB will still refuse to start. In this case you have to delete all previous versions of the mscomctl.ocx file from your system folders and then execute the batch file again. Fire up Explorer, select the Windows\System32 folder and look for mscomctl.ocx. If you find the file, delete it. Do the same thing for the Windows\SysWOW64 folder. Finally run the REG_MSCOMCTL.BAT file again. |
|
|
|
#14 | Link |
Registered User Join Date: Apr 2019 Posts: 8 |
Sorry, I still don’t understand the steps to take, I apologize, I’m not very technical. When I extract BD_RBV06004.zip, I get the following; Misc File folder When I right click REG_MSCOMCTL.BAT and choose, Run as Admin, I get the following error; There is also an open window that reads, C:\WINDOWS\system32>regsvr32 MSCOMCTL.OCX |
|
|
|
#15 | Link |
Registered User
Join Date: Sep 2003 Location: Berlin, Germany Posts: 3,062 |
In this BD-RB folder DO NOT use the original file REG_MSCOMCTL.BAT. Instead you need to download this file: Then extract my version of REG_MSCOMCTL.BAT from this file into the BD-RB folder overwriting the existing file. Finally run the batch file. (maybe turn off your Antivirus software temporarily before running the batch file). |
|
|
|
#16 | Link |
Registered User Join Date: Apr 2019 Posts: 8 |
Fixed it, thanks manolito for all your advice, I really appreciate your help!!!!!!!!!!!!!!!!! |
|
|
|
#17 | Link |
Registered User
Join Date: Sep 2003 Location: Berlin, Germany Posts: 3,062 |
Good to hear that it worked… @jdobbs Cheers
Last edited by manolito; 17th May 2019 at 18:56.
|
|
|
|
#18 | Link |
Registered User Join Date: Apr 2019 Posts: 8 |
And I have Windows 10 as well, everything works great for the first time in a month (after the installation of Office 365 a month ago, not sure if that caused the problem, but problem began around the time of 365 install)
Last edited by HH2; 18th May 2019 at 12:29.
|
|
|
|
#19 | Link |
Registered User Join Date: Nov 2014 Posts: 3 |
Need Manolito’s version of REG_MSCOMCTL>BAT Quote:
Originally Posted by manolito In this BD-RB folder DO NOT use the original file REG_MSCOMCTL.BAT. Instead you need to download this file: Then extract my version of REG_MSCOMCTL.BAT from this file into the BD-RB folder overwriting the existing file. Finally run the batch file. (maybe turn off your Antivirus software temporarily before running the batch file). I’ve got the same problem that I suspect would be fixed with the use of Manolito’s version of REG_MSCOMCTL.BAT . Any chance someone could point me to where I might find that? The sendspace link has expired. Thanks! |
|
|
|
#20 | Link |
Registered User Join Date: Jan 2010 Posts: 224 |
Quote:
Originally Posted by Lstew I’ve got the same problem that I suspect would be fixed with the use of Manolito’s version of REG_MSCOMCTL.BAT . Any chance someone could point me to where I might find that? The sendspace link has expired. Thanks! do as I suggested here -> https://forum.doom9.org/showthread.p…94#post1853094 (also linked earlier in this thread) Just edit the bat file included in BD-RB… Change… Code: regsvr32 MSCOMCTL.OCX to Code: regsvr32 c:\bd-rb\MSCOMCTL.OCX where c:\bd-rb\ is the drive and folder where the bat file and ocx file reside. Save it, and right click/run as administrator. OR Find Command Prompt on your start menu (usually under the Windows System group), right click it and run as administrator. While in the window, change to the drive and folder containing the BAT and OCX files, and run the bat file. Another way is to just copy the OCX and BAT files from BD-RB folder into c:\windows\system32 folder and run the bat file as admin. |
|
|
Overmind
Убедитесь, что сама служба правильно запущена (в службах она называется Windows Installer).
Затем, что можно попробовать 1-й, это перерегистрировать его:
Нажмите Пуск, Выполнить и введите MSIEXEC / UNREGISTE R, а затем нажмите кнопку ОК. Даже если вы делаете это правильно, может показаться, что ничего не происходит. Затем нажмите «Пуск», «Выполнить» и введите MSIEXEC / REGSERVER, а затем нажмите «ОК». Даже если вы делаете это правильно, может показаться, что ничего не происходит. Не проблема; попробуйте программу установки Windows снова.
Если это не помогает, запустите sfc / scannow для проверки целостности.
Если это не сработало, некоторые связанные с ними исправления можно найти здесь
- Remove From My Forums
-
Вопрос
-
Добрый день!
После установки Office 2013 x64 перестал работать скрипт VBA для отправки почты из Excel
Sub MSOutlook()
Dim oOutloock As New Outlook.Application
With oOutloock — ошибка происходит на данной строке
.Session.Logon
With .CreateItem(0)
.To = “”
.CC = “”
.Subject = «»
.display
End With
End With
End Sub
Выходит ошибка:
Run-time error ‘-2147467229(80004023)
Automation error
Ошибка установщика программного обеспечения.
Как можно устранить данную проблему?
Офис переустанвливался
На другом компьютере с такой же конфигурацией всё работает.
-
Перемещено
1 июня 2017 г. 7:23
-
Перемещено
- Remove From My Forums
-
Question
-
Hi, I had installed a version of Office
97 on my machine, but I have a license for
Office 365 .. so I uninstalled Ofice
97 and install Office ProPlus
(From my license 365).
But when you start your computer,
this error System Error
& h80004023
(-2147467229)In addition, I have installed a program
called Sisthemis tax, not if
the error is not caused by
that Office 97 was successfully removed or
is no conflict with the tax program?Any ideas…?
A few of our users have some custom macros in Excel that automatically pulls information via an ODBC connection into a spreadsheet, formats the data and emails it.
After upgrading our database system to a new version one of our software developers had to make changes to the macros for them to continue working, but on one of the systems the email report stage fails with the below error:
The VBA Debugger highlights the following line of code in the macro:
Text
Set outApp = CreateObject("Outlook.Application")
Previously, the macros were running on 32-bit Office 2010, but now the department is using 64-bit Office 365. As much as I would like to revert back to 32-bit office for testing purposes, we really need to get this working on the 64-bit system as there are some spreadsheets that these users deal with that exceed the memory limitations of 32-bit applications.
In trying to hunt down a solution, I stumbled across some forum posts on other websites that pointed to Office 2010 not cleanly uninstalling and leaving incorrect registry data behind. This post Opens a new window mentions the relevant registry entries. I renamed them then did a repair install of Office 365 and am still experiencing the error.
I will give the disclaimer that I am not a software developer, and have extremely limited knowledge of VBA and how it works. Our software developer that was tasked with updating these macros is also unable to get them working for this user. The email report function works on the developer’s computer as well as another machine in this department that went though the same upgrade from 32-bit Office 2010 to Office 365
My thought process is that using the Office Removal tool to completely nuke MS Office and reinstall it plus the macros would be next, but I want to get some additional input before proceeding.
Thanks in advance!