i have suite created in InstallShield which contains multiple packages. One of them requires .net 3.5 so in the package view i added Windows Feature NetFx3. Everything worked perfectly but today i got hands on a machine where instalation is terminated with the following errors in the log:
5-17-2017[02:03:10]: Getting feature list for initial feature items 'NetFx3'
5-17-2017[02:03:10]: Getting feature items for OS version 1000 (Client)
5-17-2017[02:03:10]: Final feature list for current item is: NetFx3
5-17-2017[02:03:10]: Installing Windows features for parcel 'PackageXY'...
5-17-2017[02:03:10]: Engine: property 'ISInstallStatus' value now 'Windows-Funktionen/-Rollen werden installiert …'
5-17-2017[02:03:10]: Engine: property 'ISParcelStatus' value now ''
5-17-2017[02:03:10]: CWindowsFeatureParcel::Install: using DismAPI on Windows 8 or newer
5-17-2017[02:03:10]: Engine: request for proxy handler, 0, 1
5-17-2017[02:03:10]: No source paths specified for DismEnableFeature
5-17-2017[02:05:19]: UI DLL: Resource 'Header_bckgnd.png' -> 'C:\Users\dummy\AppData\Local\Temp\{270DDFC5-A522-4510-8282-DE76EBB713E6}\Header_bckgnd.png'
5-17-2017[02:05:20]: UI DLL: Resource 'Header_bckgnd.png' -> 'C:\Users\dummy\AppData\Local\Temp\{270DDFC5-A522-4510-8282-DE76EBB713E6}\Header_bckgnd.png'
5-17-2017[02:05:26]: CWindowsFeatureParcel::CallDismApi result: 0x00000001
5-17-2017[02:05:26]: Windows feature install result status: 0x80070001
5-17-2017[02:05:26]: Failed installing Windows features for parcel 'PackageXY', error 0x80070001
5-17-2017[02:05:26]: Engine: property 'ISInstallStatus' value now 'IDS_SUITE_INTERRUPTED'
I have tried following:
run DISM /Online /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:x:\sources\sxs and other variations of this command that i wasnt really sure what are supposed to do
disabled the feature manualy and re-enabled, multiple times in different order together with the .net 4.7 and run the setup with different configuration of the checked features.
Without luck so far, the thing that bothers me the most is its only happening on this particular Virtual Machine, which is up to date with the Windows Update.
edit: It is happening on every machine that has Creators Update installed, which comes with the .net 4.7
edit2: i did not solve this issue, i just removed the funcionality that is allowing the windows feature for the packages.
Our application requires .NET 3.5 and internal testing indicates that .net framework 3.5 still gets installed using the suite prerequisite feature install.
I have seen times in the past where I had similar issues but that was an issue with VMWare Workstation and using NAT instead of Bridged network settings. In all of these cases, as you indicated, running DISM from powershell or a cmd prompt would also fail. Switching to Bridged allowed this to work. I cannot explain why.
Unfortunately we are dependent on .Net 3.5 due to 3rd party software dependencies, one of which is SQL Server 2012 believe it or not!
Related
I'm running CouchDB 2.0 on Windows for development purposes. After applying the Windows 10 Creators Update, the CouchDB service doesn't start anymore. When I try to start it manually, I get a generic "unable to start service" error message.
CouchDB 2.0 on Windows uses the Non-Sucking Service Manager (NSSM) to run itself as service. Apparently, NSSM has problems after the creators update has been applied:
2017-04-26: Users of Windows 10 Creators Update should use prelease build 2.2.4-101 to avoid an issue with services failing to start.
Thus, the problem can be fixed by using the mentioned build of NSSM:
Download the pre-release build 2.2.4-101 from https://nssm.cc/download
Stop the CouchDB service through the Windows Services dialog (paused is not enough)
Overwrite nssm.exe in <CouchDbInstallDir>\bin with the one from the downloaded ZIP file (make sure you pick the right version 32 bit / 64 bit)
Start the CouchDB service
While installing my msi i get the follwing error
Error 1935. An error occurred during the installation of assembly component {98CB24AD-52FB-DB5F-A01F-C8B3B9A1E18E}. HRESULT: 0x800736B3. assembly interface: IAssemblyCacheItem, function: Commit, assembly name: Microsoft.VC80.CRT,type="win32",version="8.0.50727.42",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86"
I do carry Microsoft_VC80_CRT_x86.msm in my MSI. But the problem is that i do not see this issue in all machines. This is faced only on a 2012 Windows Virtual machine.
Can anyone please tell me why this error would normally come?
I think you have a corrupted windows O/S. Otherwise it is correct to test on VM's configured with a variety of virgin operating systems that you want to support. Additionally I highly advise to never use this merge module. Instead using a bootstrapper/chainer (WiX Burn, InstallShield Setup Prereqs or Suite Installation ) to install the stand alone versions of the redist from Microsoft. This helps draw a line in the sand between a Microsoft problem and a problem with your installer. It also makes upgrade servicing easier.
I got the same error message on windows 7 (32bit).
This was caused by a failure in windows update for my case.
After that, I cannot install any other program on the computer. I searched from internet and found suggestions made by Microsoft engineers: repair the system from Original Installation disc with "update to latest" choice unchecked.
However, I found another simple solution which also works for my case.
1． Click START>> and type “regedit” to run register editor;
2． Find the following directory in register: HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Control;
3． search by F3 for the key RegistrySizeLimit and double click the DWORD;
4． Change the key value into ffffffff(Hex) or decimal 4294967295, then click OK;
5． restart the computer;
6． run cmd.exe with Administrator's privilege, and type SFC /SCANNOW followed by Enter in command line; this scanning may take several minutes until the status is 100% and finishes;
Then the problem can be fixed!!
I got this error in my Win7x64 VM after I installed .NET Framework 4.5 required by my MSI. I had a fresh OS install with no Windows updates, plus VS2005 SP1. I ran this Microsoft FixIt: http://support.microsoft.com/kb/976982/en-us, but it did not help until I restarted the VM. Once I restarted the VM, the error disappeared. I think all I needed was a restart, but I provide the above details in case it was the FixIt that actually fixed it.
On a windows 2016 server, I solved the problem by resetting DCOM security to default
launch dcomcnfg
then set Default Authentication Level to Connect
and Default Impersonation Level to Identify
We have an old Powerbuilder app running on Server 2000 and need to move it. I am having a problem with moving the Powerbuilder app ver 7.0, to a newer platform - Server 2003.
We basically moved the directory with the app in it and all the Dlls. Then I registered the ones that would allow it. We also had to set up Informix client-side software and verified that it was able to connect to the Database.
The app basically takes 2 parameters then checks for data in a remote database, then generates a return code to be used by another app. The return code we get is unexpected and I have no luck in looking up the number:
-1073741811
The app is run from the command line. When I run the app I get a Windows error that mentions Sybase and msvcr80.dll and a dump, and the return code mentioned above - Here is the error from the manifest text:
Server=watson.microsoft.com
UI LCID=1033
Flags=99088
Brand=WINDOWS
TitleName=Sybase Inc. Product File
DigPidRegPath=HKLM\Software\Microsoft\Windows NT\CurrentVersion\DigitalProductId
RegSubPath=Microsoft\PCHealth\ErrorReporting\DW
ErrorText=This error occurred on 2/14/2013 at 7:56:14 AM.
HeaderText=Sybase Inc. Product File encountered a problem and needed to close.
Stage1URL=/StageOne/cert_lsi_exe/7_0_3_10180/msvcr80_dll/8_0_50727_6195/0001e6d5.htm
Stage2URL=/dw/stagetwo.asp?szAppName=cert_lsi.exe&szAppVer=7.0.3.10180&szModName=msvcr80.dll&szModVer=8.0.50727.6195&offset=0001e6d5
ErrorSig=AppName: cert_lsi.exe AppVer: 7.0.3.10180 ModName: msvcr80.dll ModVer: 8.0.50727.6195 Offset: 0001e6d5
DataFiles=C:\DOCUME~1\smarkley\LOCALS~1\Temp\2\WER1.tmp.dir00\cert_lsi.exe.mdmp|C:\DOCUME~1\smarkley\LOCALS~1\Temp\2\WER1.tmp.dir00\appcompat.txt
Heap=C:\DOCUME~1\smarkley\LOCALS~1\Temp\2\WER1.tmp.dir00\cert_lsi.exe.hdmp
ErrorSubPath=cert_lsi.exe\7.0.3.10180\msvcr80.dll\8.0.50727.6195\0001e6d5
I am surprised by the msvcr80.dll request, because this app was written around 2003 and I didnt think that c compiler was at ver 8 yet. I have used Dependency Walker and see no complaints there. I am probably in DLLHell with this thing, though... does anyone have any ideas what to look for?
Thanks in Advance!
I still have a few PB 7 applications around.
Did you try Application Compatibility?
Navigate to the folder and right click on the executable and choose the Compatibility tab.
I suggest trying
Run this program in compatibility for Windows XP (Service Pack 3)
Privilege Level [x] Run this program as administrator
You may need to use Windows XP (Service Pack 2) or an earlier version of Windows.
I'm trying to deploy some Vb6 components on a Windows Server 2003 Standard x64 R2. I normally run these in a com+ application and I went through the normal routine of creating the COM+ application and adding all the components. Everything seemed to work fine until I actually tried to use any of the components. I would some kind of "ActiveX component can't create object" or "Application-defined or object-defined error" or something similar to that.
To remove as many variables a possible I created a very simple VB form to consume the simpliest of the components and tried that. Nope. So I created a simple install to install the component, and whooo hoooo it worked. So I tried one of the more envolved components with high hopes ... but no after the install I still can't call the component successfully. Using Dependency Walker I discovered that for some reason the msvbvm60.dll is not properly registerd.
I've downloaded VBRUN60.exe and VBRUN60SP6.exe and tried installing them. Even going so far as to do a run as with the administrator account and removing the check box for "Run this program with restricted access". I've tried to manually register the msvbvm60.dll in the SysWow64 directory.
Nothing seems to work. It just won't register. Does anybody have any suggestions? At this point I'll try just about anything.
Thanks
If you are registering the components manually you need to pay extra attention. As you are on a 64-bit OS there are two versions of regsvr32.exe. When registering VB6 components you must make sure to use the 32-bit version of regsvr32, which is located under the following location:
%WINDIR%\SysWOW64\regsvr32.exe
If you just type regsvr32 on the command prompt, normally the 64-bit version is chosen (because %WINDIR%\system32 is contained in the %PATH% environment variable), so please make sure to use the full path as above.
If you are using a 32-bit MSI to install your components, this version will be selected automatically and the registration should work just fine.
In case you haven't already done, you should give a try to Process Monitor - one of the best tools I have used on dll registering problems.
The following links will provide some usufull clues:
An excelent tutorial on using Process Monitor for problem solving;
ActiveX component can't create an object
RESOLVED! ActiveX Component Can't Create Object: Cube build failure against SQL Server 2005 Analysis Services
Hope it helps :D
I've had trouble with unregistered components for Visual Basic 6 - although not tried to use the same one as you are mentioning. Manually registering never resolved things, no matter which reg server was used
The problem (eventually) turns out to be Internet Explorer 10. Uninstalling that (due to the way Windows 7 handles IE as Windows updates, this meant unistalling newer versions first to expose the older ones) worked. Afterwards, reinstalling the latest IE brings no problem.
In VS2010 Beta 2, from the Help Library Manager, after selecting local help, and downloading the VS Documentation, it won't launch.
Here's what I have installed:
Here's what I'm clicking in the Start Menu:
Here's the result:
Ideas?
Thanks,
Adam
I recommend reporting this bug on Microsoft Connect so that the Visual Studio product team can take a look at this.
This seems like a rather specific problem and not a general programming question.
I also had problems with VS 2010 Beta 2 help, or rather with MS Help 3, which is new with 2010 . There is a known issue with the Help Listener Service trying to listen on port 80. MS document a procedure to change this port, and my help was back up after following it. From the the ReadMe_ENG.htm file that is installed with MS Help:
Removal of Help 3.0 will not remove content from user's machine;
they should run HLM to remove content
Product Documentation shortcut will not work after uninstall of Help
3.0
Help Library Manager requires the BITS service to be running if you
want to use the “Check for Updates” or
“Find Content online” features.
Removing content and installing
content locally does not require the
BITS service.
Help Library Manager will hang if you attempt to install offline
content but there is not sufficient
disk space for the BITS service to
download the content
If port 80 is used by another process (not via the http.sys service)
then the Help listener will not be
able to attach and use port 80 and
will fail. The port number can be
changed by adding a string registry
value ListenerPort under
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Help3
with the value of the port to use (eg.
81). Due to the http.sys ACL settings
it is necessary to run the following
http.sys configuration command from an
admin elevated command line. On
Vista, Win2k8, and Windows 7 run the
following native command: netsh http
add urlacl url=http://127.0.0.1:/help/ sddl=D:(A;;GX;;;WD)
On Windows Xp, and Win2K3 run the
following command:
httpcfg set urlacl /u
http://127.0.0.1:/help/
/a D:(A;;GX;;;WD)
If the command is not found then it
might be necessary to download the
httpcfg.exe from Microsoft as part of
the Windows XP Service Pack 2 support
Tools
(http://www.microsoft.com/downloads/details.aspx?amp;displaylang=en&familyid=49ae8576-9bb9-4126-9761-ba8011fabf38&displaylang=en).
Now the Microsoft Help Listener will
run on the selected port number.
ADDENDUM:
I also ended up installing MS Help 3 manually, and using the Help->Manage Help Settings menu command. On the VS 2010 installation 'disk', I ran WCU\Help\HelpSetup.exe, after removing help via Add/Remove programs. Note the folder HelpSetup installs to, and then in VS 2010, open the Help Library Manager (Help->Manage Help Settings), then Find Content on Disk, and then supply the location HelpSetup installed to. Help 3 will take it from there.