The vcredist2015 really pollutes "ferventcoder/win2012r2-圆4-nocm" but now draftsight 2018 installs without error. "ferventcoder/win2012r2-圆4-nocm" does not have any Microsoft Visual C++ Redistributable installed so I installed it Action register_FxVistaPreviewDll, location: C:\Windows\SysWOW64\, command: regsvr32 /s "C:\Program Files\Dassault Systemes\DraftSight\bin\FxVistaPreview.dll" Contact your support personnel or package vendor. A program run as part of the setup did not finish as expected.
MSI (s) (2C:F4) : Product: DraftSight 2018 SP0 圆4 - Error 1722.There is a problem with this Windows Installer package. MSI (s) (2C:F4) : Note: 1: 1722 2: register_FxVistaPreviewDll 3: C:\Windows\SysWOW64\ 4: regsvr32 /s "C:\Program Files\Dassault Systemes\DraftSight\bin\FxVistaPreview.dll" On Dec 22, 2017, at 6:04 PM, Bob Tanner wrote: But when the vendors specifically states your operating system is not supported I think we need to petition to update the operating system in chocolatey-test-environment or petition "the powers" for an exemption in the package verifier for DraftSight 2018.Ī way to identify the package verifier's operating system and support multiple testing environments. It's the main reason I did PR #23 on chocolatey-test-environment. The Microsoft treadmill keeps moving and it's get updated or get left behind. I think the problem is the package verifier runs Windows Server 2012 R2 and DraftSight 2019 SP0 System Requirements specifically states, "Windows Server 2012 R2 64-bit x86 (No longer supported by R2017x)". Windows Server 2016 testing environment.
#Draftsight 2018 how to
How to locate the cause of error code 1603 in a verbose MSI log file.List tracking stuff that might be helpful
0 kommentar(er)
