Windows Technologies – Page 7

March 24, 2016Repackaging, Windows Technologies

Quick Fix MSI Uninstall Error "Product Removal failed" with Error Code 1603

Error: During uninstall of certain products you may encounter failures with below error messages in the uninstall logs: InstallShield 3:14:39: Invoking script function CleanUpPathInstallShield 3:14:39: CallScriptFunctionFromMsiCA() endsInstallShield 3:14:39: Cleaning up temp file C:\Users\admin01\AppData\Local\Temp\{B98BC354-AE61-46AB-964C-BCCE933AB1B9}\ISBEW64.exeInstallShield 3:14:39: Cleaning up temp file C:\Users\admin01\AppData\Local\Temp\{B98BC354-AE61-46AB-964C-BCCE933AB1B9}\ISRT.dllInstallShield 3:14:39: Cleaning up temp file C:\Users\admin01\AppData\Local\Temp\{B98BC354-AE61-46AB-964C-BCCE933AB1B9}\IsConfig.iniInstallShield 3:14:39: Cleaning up temp file C:\Users\admin01\AppData\Local\Temp\{B98BC354-AE61-46AB-964C-BCCE933AB1B9}\String1033.txtInstallShield 3:14:39: Cleaning up temp file C:\Users\admin01\AppData\Local\Temp\{B98BC354-AE61-46AB-964C-BCCE933AB1B9}\_isres_0x0409.dllInstallShield 3:14:39: Cleaning up temp file C:\Users\admin01\AppData\Local\Temp\{B98BC354-AE61-46AB-964C-BCCE933AB1B9}\setup.inxCustomAction CleanUpPath returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)Action ended 3:14:40: CleanUpPath. Return value 3.Action ended 3:14:40: INSTALL. Return value 3.Property(S): DiskPrompt = [1] Action 3:16:17: MZPInProgressClear. Action […]

November 29, 2015November 29, 2015Desktop, Web Technologies, Windows Technologies

FIX: Windows Edge Browser error “Hmm, we can’t reach this page.” for web pages

Scenario: All of sudden, Windows Edge browser starts resulting in error “Hmm, we can’t reach this page.” whenever you browse any web pages. However, you will be able to access the internet through other browsers on the same system. Cause: The Windows Edge browser depends on DNS resolution which is provided by “DNS Client” service. Edge browser fails to load page when “DNS Client” service is disabled on the system. Solution: Enable and start the “DNS Client” service on the system.

November 6, 2015November 6, 2015Repackaging, Web Technologies, Windows Technologies

Automating IIS Web tasks using AppCmd command

Requirement: You need to automate the management like create, start, stop, etc., of IIS Resources including Web Site, App, AppPool, etc. Solution: Microsoft provides a command line tool named Appcmd.exe which ships/installs along with IIS. It’s usually located at C:\WINDOWS\system32\inetsrv\appcmd.exe path. Automation Examples: Create an APPPOOL, with specified name, .Net Framework version, Managed pipeline mode, etc., C:\>C:\WINDOWS\system32\inetsrv\appcmd.exe ADD APPPOOL /name:TestAppPool /managedRuntimeVersion:v4.0 /managedPipelineMode:”Integrated” APPPOOL object “TestAppPool” added C:\> Stop an APPPOOL PS C:\> C:\WINDOWS\system32\inetsrv\appcmd.exe STOP APPPOOL TestAppPool “TestAppPool” successfully stopped PS C:\> Start an APPPOOL PS C:\> C:\WINDOWS\system32\inetsrv\appcmd.exe START APPPOOL TestAppPool “TestAppPool” successfully started. PS C:\> Create a web Application under […]