Script Packager Error Codes
Scripts packaged with the ASE Script Packager will return the Win32 Error code that is returned by the script. However, if the script is unable to run, the following Script Packager errors may be returned:
|
-1 |
Packaged script attempted to unpack itself on a network drive |
|
-2 |
Packaged script could not process its configuration information (settings, paths, etc.) |
|
-3 |
Packaged script executable is corrupt |
|
-4 |
Packaged script attempted to apply credentials on a FAT volume |
|
-5 |
Packaged script attempted to apply credentials on system older than Windows 2000 |
|
-6 |
Temporary target folder for script file storage is encrypted |
|
-10 |
Unknown error. See Event Viewer for Win32 error code. |
Note: These negative numbered errors indicate an internal error being returned from the packaged script itself (and not that of the script you are trying to execute.) Positive error number indicate a Win32 error. To translate these positive error code numbers into meaningful information, use the Admin Script Editor Error Code Lookup feature.
Quickly Determine Error Level
Does your script appear to not be running at all? The Windows Event Viewer should provide the answer, but ASE 3.x introduces another quick way to see what is happening: by renaming your packaged executable to end with "_debug", the packaged executable will display its error level to a pop up message dialog.
- Simply rename the script from <packagename>.exe to <packagename>_debug.exe and run the package to see what error level is being returned.
Some commonly reported Win32 Errors
1: Incorrect function
This error may indicate and invalid script name, or call to a file that does not exist in your package.
2: Failed to execute process.
This error may indicate that the script interpreter is not available in the path of the system where the executable is being run. If using KiXtart or AutoIt, you may include the script interpreter in the package using the "Additional Files" feature of the Script Packager. For VBScript, you will need to have the Windows Script Host (WSH) installed on any target systems beforehand. Additionally, in earlier versions of ASE a full path may have been specified in the "Process Name" field of the Script Packager- ensure this field contains only the process name (and no path). Though this was a problem in an earlier release of ASE, if you open a script created with this older version, the full path may still persist if it was saved in the script settings.
1326: Failed to execute process under user <username>, domain <domain>.
This error has been reported when the domain and username are correct, but the password is incorrect.
1327: Logon failure: user account restriction. Possible reasons are blank passwords not allowed, logon hour restrictions, or a policy restriction has been enforced.
This error has been reported when there is a problem such as an expired password with the account specified for alternate credentials. Try logging onto a system with the account you are specifying to ensure it is able to log onto the network.
1332: No mapping between account names and security IDs was done
Ensure you have entered proper credentials. An invalid domain name, or user name will generate this error.
1789: The trust relationship between this workstation and the primary domain failed
This can normally be attributed to an invalid/expired computer account on the workstation. See MS KB162797 for more details.
6012: Failed to apply EFS
This error normally indicates that there is an expired EFS recovery agent on the network. To correct this, renew the EFS recovery agent for the domain. For more help troubleshooting EFS, see this article at Microsoft TechNet.