Failed With Return Code 133 And Error Message
Contents |
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 sophos management communications system installation failed with error 0x643 Tweet Application installation (legacy setup applications or Windows installer applications) sometimes fails without any sophos installation program finishing with code 134 error message. These tasks will return exit/error codes when log file is generated. The following script will help in getting the sophos error 0x643 Exit/Error code of Application installation 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 installation program finishing with code 145 is: " & (i) Set oShell = Nothing Note: Use Silent switches according to the application. The table below describes system Exit/Error codes when a 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
Sophos Return Code 16
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 specified. 21 The device is not ready. 22 The device does not recognize the command. 23 Data error (cyclic redundancy check). 24 The program issued a command but the command length is incorrect. 25 The drive cannot locate a specific area or track on the disk. 26 The specified disk or diskette cannot be accessed. 27 The drive cannot find the sector requested. 28 The printer is out of paper. 29 The system cannot write to the specified device. 30 The system cannot read from the specified device. 31 A device attached to t
Sign in Pricing Blog Support Search GitHub This repository Watch 13 Star 380 Fork 82 adametry/gulp-eslint Code Issues 3 Pull requests 1 Projects 0 Pulse Graphs
Sophos Error 134
New issue failOnError does not exit with status code 1 #133 Closed there was an unexpected problem with the installation of sophos endpoint security and control yavorski opened this Issue Jan 22, 2016 · 3 comments Projects None yet Labels None yet sophos install error 134 Milestone No milestone Assignees No one assigned 2 participants yavorski commented Jan 22, 2016 Hi, Tests fails under windows 8. λ node -v v4.2.1 ypivanov at YPIVANOV in ~/dev/gulp-eslint on http://www.symantec.com/connect/articles/windows-system-error-codes-exit-codes-description master λ npm t --verbose npm info it worked if it ends with ok npm verb cli [ 'c:\\Program Files\\nodejs\\node.exe', npm verb cli 'c:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js', npm verb cli 't', npm verb cli '--verbose' ] npm info using npm@2.14.7 npm info using node@v4.2.1 npm verb run-script [ 'pretest', 'test', 'posttest' ] npm info pretest gulp-eslint@1.1.1 > gulp-eslint@1.1.1 pretest c:\Users\ypivanov\dev\gulp-eslint > jscs *.js test/*.js https://github.com/adametry/gulp-eslint/issues/133 && gulp test Error: Path *.js was not found. at null.
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership https://www.veritas.com/support/en_US/article.000026482 Newsroom Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet Informix backup fails with a VERITAS NetBackup (tm) error 6, and onbar return code 133. Article:000026482 Publish: Article URL:http://www.veritas.com/docs/000026482 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account failed with now! Welcome First Last Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem Informix backup fails with a VERITAS NetBackup (tm) error 6, and onbar return code 133. Error Message /opt/informix9.40/bin/onbar_d complete, returning 133 (0x85) Solution Something installation program finishing similar to the following is displayed in the BAR_ACT_LOG when attempting to back up an Informix 9.40 instance: 2003-12-09 17:28:12 25613 25611 /opt/informix9.40/bin/onbar_d -b 2003-12-09 17:28:12 25613 25611 An unexpected error occurred: ld.so.1: /opt/informix9.40/bin/onbar_d: fatal: /opt/informix9.40/lib/ibsad001.so: open failed: No such file or directory. 2003-12-09 17:28:12 25613 25611 Could not open XBSA library /opt/informix9.40/lib/ibsad001.so. 2003-12-09 17:28:12 25613 25611 /opt/informix9.40/bin/onbar_d complete, returning 133 (0x85)The NetBackup activity monitor might also show a NetBackup error 6 for the backup. While NetBackup error 6 is "the backup failed to back up the requested files," onbar return code 133 is listed in the IBM/Informix Backup and Restore Guide version 9.4 as:133 Failed to load the XBSA library functions. Verify that you are using the correct XBSA for the storage manager. Ensure that the BAR_BSALIB_PATH value in the ONCONFIG file points to the correct location of the XBSA shared library. For information, consult your storage-manager manual.The VERITAS XBSA library that is used with Informix is located in the /usr/openv/netbackup/bin directory, and (depending on the platform) has a name similar to infxbsa.so. Informix links to this library