Error 1608 While Executing Batch
360 games PC games an error occurred while executing batch error message is error creating window handle Windows games Windows phone games Entertainment All Entertainment ssms error creating window handle Movies & TV Music Business & Education Business Students & educators error creating window handle sql server management studio Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet error code Explorer Microsoft Edge Skype OneNote OneDrive Microsoft Health MSN Bing Microsoft Groove Microsoft Movies & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets PC accessories Xbox & games Microsoft Lumia All Windows phones Microsoft HoloLens For business Cloud Platform Microsoft Azure Microsoft Dynamics Windows for business Office for business Skype for business Surface for business Enterprise solutions Small business solutions Find a solutions provider Volume Licensing For developers & IT pros Develop Windows apps Microsoft Azure MSDN TechNet Visual Studio For students & educators Office for students OneNote in classroom Shop PCs & tablets perfect for students Microsoft in Education Support Sign in Cart Cart Javascript is disabled Please enable javascript and refresh the page Cookies are disabled Please enable cookies and refresh the page CV: {{ getCv() }} English (United States) Terms of use Privacy & cookies Trademarks © 2016 Microsoft
Français Deutsch 日本語 Español Help Video Screencast Help Windows System Error Codes (exit codes) Description Created: 28 Jan 2009 • Updated: 20 Dec 2010 | 9 comments Language TranslationsMachine TranslationsDeutsch Français Español 简体中文 日本語 Sidd +19 19 Votes Login to vote Tweet Application installation (legacy setup applications or Windows installer applications) sometimes fails without any error message. These tasks will return exit/error codes when log file is generated. The following script will help in getting the Exit/Error code of Application installation https://support.microsoft.com/en-us/kb/945892 else on can get it from log file. Dim oShell, MyApp, i Set oShell = CreateObject("WScript.Shell") MyApp = """C:\MyApplication\Setup.exe"" /Q" i = 0 i = oShell.Run(MyApp, 1 ,True) WScript.Echo "Exit Code is: " & (i) Set oShell = Nothing Note: Use Silent switches according to the application. The table below describes system Exit/Error codes when a http://www.symantec.com/connect/articles/windows-system-error-codes-exit-codes-description task is executed. The description of codes may help in identifying and troublshooting the issues. Code Description 0 The operation completed successfully. 1 Incorrect function. 2 The system cannot find the file specified. 3 The system cannot find the path specified. 4 The system cannot open the file. 5 Access is denied. 6 The handle is invalid. 7 The storage control blocks were destroyed. 8 Not enough storage is available to process this command. 9 The storage control block address is invalid. 10 The environment is incorrect. 11 An attempt was made to load a program with an incorrect format. 12 The access code is invalid. 13 The data is invalid. 14 Not enough storage is available to complete this operation. 15 The system cannot find the drive specified. 16 The directory cannot be removed. 17 The system cannot move the file to a different disk drive. 18 There are no more files. 19 The media is write protected. 20 The system cannot find the device spe
sage line50 on one particular windows 7 professional PC. On installing the error 1608: unable to create installdriver instance, return code: -2147467262 pops up, I have tried the install on an identical machine and it installs correctly. I http://exceptionin.com/q/1608-unable-to-create-installdriver-instance-return-code-2147467262-windows-7 can't figure out what is wrong. Any help? 3answers windows 7 sage line50 error 1608 installdriver instance Comments See all(0) Cancel Edit Add comment Anonymous 0 August 16, 2011 Hi I have tried your method but to no avail. I have formatted and re-install win 7 then sage installed properly. Thanks for your help Comments See all(0) Add comment Anonymous 0 August 16, 2011 you must try to uninstall the iss engine. error creating Here the information from Flexera The following options have been known to resolve this error message in the majority of cases: Reinstall the InstallScript engine by running the "isscriptx.msi" file located in the following location, where x is the version of InstallShield being used: