Error Code 2738 Windows 7 64 Bit
Contents |
comment. Error Code 2738 When Running A Microsoft Fix it Solution! ★★★★★★★★★★★★★★★ bmahafMarch 31, 2009133 0
Error 2738 Vbscript Windows 7
0 0 Problem description When running a Microsoft Fix it solution error 2738 microsoft fix it you may encounter an error code 2738. This error occurs because the Windows Script Engine is not internal error 2738 windows 7 properly registered. Error message details The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2738.
Internal Error 2738 Windows 7 64 Bit
Fix it for me To fix this problem automatically, click the Fix this problem link. Then, click Run in the File Download dialog box, and following the steps in the wizard. Fix this problem Comments (133) Cancel reply Name * Email * Website Anonymous says: October 10, 2016 at 8:00 pm Cool - it fixed the problem
Error Code 2738 Citrix
with PhysX installer. Reply Anonymous says: October 10, 2016 at 8:00 pm I facing the same situation like Jan Heines. Fix did not work out for me. Still no installation. Reply Anonymous says: October 10, 2016 at 8:00 pm I facing the same situation like Jan Heines. Fix did not work out for me. Still no installation. Reply Anonymous says: October 10, 2016 at 8:00 pm i hav the exact same problem and find microsoft to be of absolutely NO HELP at all unless you pay them. if u take a good hard look at their "self help" or any "microsoft troubleshooting help" they make it look like its so simpl and then they take u to their useless sites and u can count on repeated troubleshooting searches with these assholes. usually to a "24 hour long" microsoft community jabber by thousands of others having problems..no real microsoft help and once u get on their site troubleshooting index the hav liss of " useless-moronic" questions that u already know
be down. Please try the request again. Your cache administrator is webmaster. Generated Mon, 10 Oct 2016 21:22:58 GMT by s_ac15 (squid/3.5.20)
2738 on Vista while running light.exe from WiX v3.0 ★★★★★★★★★★★★★★★ Aaron StebnerApril 1, 200815 0 0 0 Recently, while attempting to build a Japanese MSI using WiX v3.0, I https://blogs.msdn.microsoft.com/astebner/2008/04/01/how-i-resolved-windows-installer-error-code-2738-on-vista-while-running-light-exe-from-wix-v3-0/ received an error message that looked like the following: light.exe : error LGHT0217 https://community.spiceworks.com/how_to/1577-solving-the-error-code-is-2738 : An unexpected external UI message was received: ????????????????????????????????????????????????????????????? ???? 2738 ??? I wanted to see the full text of this error message, so I temporarily changed the product language setting in my WXS file from 1041 (the LCID for Japanese) to 1033 (the LCID for English) and re-ran the build. When I error 2738 did that, the error message was more readable: light.exe : error LGHT0217 : An unexpected external UI message was received: The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2738. This message made more sense to me, so from there, I looked at the Windows Installer Error Messages reference for error code 2738 2738 windows 7 and found the following: Could not access VBScript run time for custom action [2]. While attempting to narrow down this error further, I found a couple of useful blog posts. As described in this blog post by Heath Stewart, error code 2738 can occur on Windows Vista systems (like the one I was using in the above scenario) if an MSI contains a script-based custom action and the VBScript runtime is registered in the HKEY_CURRENT_USER hive instead of or in addition to the HKEY_LOCAL_MACHINE hive. Also, as described in this blog post by Bob Arnson, four of the Windows Installer Internal Consistency Evaluators (ICEs) are implemented in VBScript. The offending ICEs are ICE08, ICE09, ICE32 and ICE61. In my build output, I noticed that light.exe had reported some warnings for ICE03 before displaying this 2738 error. From this, I made an educated guess that it was probably failing while running one of these four ICEs. Then, I used some of the advice that I listed in one of my previous blog poststo unregister vbscript.dll and jscript.dll from HKEY_CURRENT_USER to resolve this error: Click on the Start menu, choose Run, type cmd and click OK To unregis
an unexpected error installing this package. This may indicate a problem with this package. The error code is 2738.” This installer error is not just for Skype. Steps (5 total) 1 Take a look in Event Viewer I looked in Event Viewer to find out what MSI-file that generated the error message and found: Log Name: Application Source: MsiInstaller Date: 23.09.2010 21:58:26 Event ID: 1040 … … Description: Beginning a Windows Installer transaction: C:\ProgramData\Skype\{D103C4BA-F905-437A-8049-DB24763BBE36}\SkypeToolbars.msi. Client Process Id: 6564. 2 Running MSIEXEC with logging options I started a “Command Promt” and used the command: “cd C:\ProgramData\Skype\{D103C4BA-F905-437A-8049-DB24763BBE36}” to navigate into the folder containing the MSI-file. Now using the command: “msiexec /i SkypeToolbars.msi /lv log.txt” (msiexec options: /i = Install, /lv = Log + Verbose output). After clicking away the error message I just wrote “log.txt” in my “Command Promt” to open the log-file. Near the bottom of the log-file I found this line: DEBUG: Error 2738: Could not access VBScript runtime for custom action 3 DEBUG: Error 2738 After a quick search at Google I found out this error indicates that the VBScript engine is not registered on the computer. The solution for a Windows Vista or Windows 7 32bit: - Click Start -> All Programs -> Accessories - Right click “Command Promt” and click on “Run as administrator” - Write “cd %windir%\system32” and hit Enter - Write “regsvr32.exe vbscript.dll” and hit Enter - You should now get a message that says: “DllRegisterServer in vbscript.dll succeeded.” - Click “OK” The solution for a Windows Vista or Windows 7 64bit: - Click Start -> All Programs -> Accessories - Right click “Command Promt” and click on “Run as administrator” - Write “cd %windir%\syswow64” and hit Enter - Write “regsvr32.exe vbscript.dll” and hit Enter - You should now get a message that says: “DllRegisterServer in vbscript.dll succeeded.” - Click “OK” 4 Try again... Now I tried once more to run “msiexec /i SkypeToolbars.msi /lv log.txt” (I kept the /lv log.txt option to look for changes if the i