Ошибка contact your support personnel

Environment

• Microsoft Windows Server 2012

• Microsoft BHOLD

Problem Statement

Unable to install BHOLD Core module on Windows Server 2012 box. Received this error during attempt:

---

Windows Installer Verbose Log

Action 11:32:26: StartServices. Starting services
Action start 11:32:26: StartServices.
Action ended 11:32:26: StartServices. Return value 1.
MSI (s) (14:CC) [11:32:26:420]: Doing action:
CA_CoreProductGetWebsiteExists
Action 11:32:26: CA_CoreProductGetWebsiteExists.
Action start 11:32:26: CA_CoreProductGetWebsiteExists.
Error 1720. There is a problem with this Windows Installer package. A script required for this install to complete could not be run. Contact your support personnel or package vendor.  Custom action CA_CoreProductGetWebsiteExists script error -2147217394, : 
Line 66, Column 1, 
MSI (s) (14:B4) [11:33:17:411]: Product: Microsoft BHOLD Suite — Core — Error 1720. There is a problem with this Windows Installer package. A script required for this install to complete could not be run. Contact your support personnel or package vendor. 
Custom action CA_CoreProductGetWebsiteExists script error -2147217394, :  Line 66, Column 1, 

Action ended 11:33:17: CA_CoreProductGetWebsiteExists. Return value 3.
MSI (s) (14:CC) [11:33:17:443]: Note: 1: 2265 2:  3: -2147287035
MSI (s) (14:CC) [11:33:17:443]: Machine policy value ‘DisableRollback’ is 0
MSI (s) (14:CC) [11:33:17:443]: Note: 1: 1402 2: HKEY_LOCAL_MACHINESoftwareMicrosoftWindowsCurrentVersionInstallerRollbackScripts 3: 2

MSI (s) (14:CC) [11:33:17:443]: Note: 1: 1402 2: HKEY_LOCAL_MACHINESoftwareMicrosoftWindowsCurrentVersionInstallerRollbackScripts 3: 2

MSI (s) (14:CC) [11:33:17:443]: No System Restore sequence number for this installation.
MSI (s) (14:CC) [11:33:17:443]: Unlocking Server
Action ended 11:33:17: INSTALL. Return value 3.
Property(S): VirtualMemory = 1522

The highlighted section implies this issue is related to finding web site/IIS problem. According to the
BHOLD Core install document, it shows the following snippet regarding installation on Windows Server 2012:

Cause 

 It turns out that all of the sub-components under this need to be selected as well, as depicted below:

Resolution

Add these components(no reboot required) and ran install again, it succeeded.

trofimchuk	#1 Оставлено : 10 февраля 2016 г. 0:27:26(UTC)
Статус: Новичок Группы: Участники Зарегистрирован: 10.02.2016(UTC) Сообщений: 3	система windows 10. Разархивировал, как сказано где-то на форуме, файл. Лог прилагаю log.txt (72kb) загружен 4 раз(а). В логе насколько я вижу ругается на: «Ошибка 1719. Windows Installer service could not be accessed. Contact your support personnel to verify that it is properly registered and enabled. MSI (c) (78:B0) [23:47:39:737]: Продукт: КриптоПро ЭЦП Browser plug-in — Ошибка 1719. Windows Installer service could not be accessed. Contact your support personnel to verify that it is properly registered and enabled.» При этом установщик запущен. Рестарт службы не помог. Также перестал запускаться Internet Explorer 11: открывается, «не отвечает», закрывается. Произошло где-то по ходу установки Криптопро. Запуск в командной строке sfc /scannow ошибку не исправил. Лог прилагаю. CBS.zip (779kb) загружен 1 раз(а).. Перед установкой 4.0 удалял весь криптопро через панель управления, а также запускал утилиту очистки.

trofimchuk	#2 Оставлено : 10 февраля 2016 г. 9:31:57(UTC)
Статус: Новичок Группы: Участники Зарегистрирован: 10.02.2016(UTC) Сообщений: 3	Именно установка криптопро 4.0 ломает эксплорер (хоть с удалением предыдущей версии, хоть поверх). Также перестают открываться некоторые части панели управления windows10, например, Программы и компоненты. Отредактировано пользователем 10 февраля 2016 г. 9:34:25(UTC)  | Причина: Не указана

Андрей Писарев	#3 Оставлено : 10 февраля 2016 г. 9:34:59(UTC)
Статус: Сотрудник Группы: Участники Зарегистрирован: 26.07.2011(UTC) Сообщений: 11,736 Сказал «Спасибо»: 451 раз Поблагодарили: 1838 раз в 1421 постах	Автор: trofimchuk Именно установка криптопро 4.0 ломает эксплорер (хоть с удалением предыдущей версии, хоть поверх). Также перестают открываться некоторые части панели управления windows10, например, Программы и компоненты. Здравствуйте. Устанавливали последнюю сборку КриптоПро CSP 4.0.9680 (Markov) от 29.12.2015?
Техническую поддержку оказываем тут Наша база знаний
	WWW

trofimchuk	#4 Оставлено : 10 февраля 2016 г. 12:01:23(UTC)
Статус: Новичок Группы: Участники Зарегистрирован: 10.02.2016(UTC) Сообщений: 3	здравствуйте, да, проблема оказалась в сборке скачанной у продавца поставил Марков — заработало.

Быстрый переход
 

Вы не можете создавать новые темы в этом форуме.

Вы не можете отвечать в этом форуме.

Вы не можете удалять Ваши сообщения в этом форуме.

Вы не можете редактировать Ваши сообщения в этом форуме.

Вы не можете создавать опросы в этом форуме.

Вы не можете голосовать в этом форуме.

Description

Error: “1904. Module failed to register. HRESULT -<##########>. Contact your support personnel.”, when installing Sage 100 or installing the Workstation Setup for Sage 100

Example: “Error 1904.Module C:Program Files (x86)SAP BusinessObjectsCrystal Reports for .NET Framework 4.0CommonSAP BusinessObjects enterprise XI 4.0win32_x86crtslv.dll failed to register. HRESULT -2147010895. Contact your support Personnel. “

The file mentioned in “failed to register” message could be any one of the following: crtslv.dll, pageobjectmodel.dll, reportrenderer.dll, saxmlserialize.dll, commonobjmodel.dll, objectfactory.dll, saxserialize.dll, undomanager.dll, datadefmodel.dll, sacommlayer.dll, cubedefmodel.dll, rptdefmodel.dll, rptcontrollers.dll, requestmodel, clientdoc, exportmodellev.dll, prompt.dll, or dtsagent.dll.

Disclaimer

Network Warning

This solution requires advanced knowledge of your network. First, contact your system administrator for assistance. Modifying Windows security incorrectly can severely affect system operations.

Sage is not responsible for operation issues caused by incorrectly modifying your Windows security. Always create a backup of your data before proceeding with advanced solutions.

Operating System Warning

This solution requires advanced knowledge of your computer’s operating system. First, contact your system administrator for assistance. Modifying your Windows Registry incorrectly can severely affect system operations. Sage is not responsible for operation issues caused by incorrectly modifying your Windows Registry. Always create a backup of your data before proceeding with advanced solutions.

Cause

This issue can occur when one or more of the following conditions is true:

• File is not installed correctly.
• The file is damaged.
• Other programs, including memory-resident and anti virus programs, are running and using any version of the file.
• User or account does not have the proper Windows security or permissions.
• Windows updates were installed but Mandatory reboot has not occurred.

If error occurs during Sage 100 workstation install:
If receiving a Sage 100 Workstation Installer Information message: “Error 1904. Module C:Program Files (x86)SAP BusinessObjectsCrystal Reports for .NET Framework 4.0CommonSAP BusinessObjects Enterprise XI 4.0win32_x86crtslv.dll failed to register. HRESULT -2147010895. Contact your support personnel.”, this can be caused by missing prerequisite(s) including .NET Framework 3.5.

NOTE: If error mentions Error: “1904. Module ..mas90CMSOTAWIZ.OCX failed to register. HRESULT -2147220473. Contact your support personnel” see Related Resources.

Resolution

Note: Error 1904 is a well-known Windows operating system error. Microsoft’s support web site and various on-line resources discuss and cover various instances of DLL registration failure for a variety of reasons.
Resolution 1:

• Click Ignore. In some situations, this completes the client installation and Sage MAS 90 or 200 functions correctly.

Resolution 2:
Reinstall with additional security/permissions opened:

1. First of all, make sure to map a drive to the shared location above the “..MAS90” directory, on the server where Sage 100 ERP is installed.
2. Then log onto the workstation as an Administrator with Full Control of the “..MAS90” directory on the server where Sage 100 ERP is installed.
3. Next, from the workstation’s Windows desktop, open Start, Control Panel, User Accounts, Change User Account Control Settings (if the option is not there, use the Search Control Panel field to search for “Change User Account Control Settings”) to set it to “Never Notify”
   (Note: This may require a reb.oot. On Windows Vista machines, this is a radio button option).
4. Access the mapped drive location (e.g. “X:\MAS90WkSetup” (where “X” is the mapped drive letter).
   Finally, right-click Autorun.exe and select “Run as Administrator”, then install Workstation Setup

Resolution 3:
Register the file manually. To register a specific ActiveX object, follow the steps below:

1. Click the Start button and click Run
2. Next, in the Open field, type the command below, where [path and file] are specified in the error:
   REGSVR32
3. Click OK. A message stating that the file was registered should appear

Resolution 4:

• Consider re-acquiring the installation files, then extract again (if needed) and reinstall.

Resolution 5:
If Windows Updates were recently installed, restart the machine getting the error and then install Sage 100.
Workstation install error during SAP Crystal Reports files:

1. Cancel workstation installation.
2. See Related Resources for more details on Sage 100 Workstation install.
3. Re-start Sage 100 Workstation install by selecting the Autorun.exe (right-click and select “Run as Administrator”) instead of Workstation.MSI file which does not install required prerequisites.

If error mentions Error: “1904. Module ..mas90CMSOTAWIZ.OCX failed to register. HRESULT -2147220473. Contact your support personnel” see Related Resources.

Support

If necessary, seek the assistance of Acute Data Systems to help provide assistance with this process.