| Symptom |
|---|
Importing a Custom ITScript presents an error. The error, cause, and solution will vary; this doucment will cover each individually.
| Errors |
|---|
Note - The following errors list a specific file and/or Script name. These may vary in your environment.
Script metadata is missing or incorrect.
Error
[Window Title]
Script Importer
Script Importer
[Main Instruction]
The script 'C:\testx.ps1' failed to import.
[Content]
Script metadata is missing or incorrect.
Cause
This is typically caused by the header information/metadata either not existing in the ps1 file, missing required information, or being incorrectly formatted.
Solution
Review the section on Metadatain the Guidelines for Creating a Custom ITScripts, verify the Metadata is accurate and present.
A script '...' already exists, but was signed by a different authority
Error
[Window Title]
Script Importer
[Main Instruction]
The script 'C:\test.ps1' failed to import.
[Content]
A script 'Set Target Machine Verbose Logging' already exists, but was signed by a different authority
Cause
The UID value within the ps1 files Metadata matches the value of a script that is already imported into Protect. This specific error is typically seen when the UID matches one of the Shavlik default ITScript UID values.
<stScript uid="333a27e3-a651-4a30-9150-63757e689a19" schemaVersion="1.0.0.0">
uid value has already been used for a ITScript called 'Set Target Machine Verbose Logging'.
Example:
<stScript uid="333a27e3-a651-4a30-9150-63757e689a19" schemaVersion="1.0.0.0">
uid value has already been used for a ITScript called 'Set Target Machine Verbose Logging'.
Solution
Change the uid to a unique value.
The contents of file '...' may have been tampered because the hash of the file does not match the hash stored in the digital signature. The script will not execute on the system. Please see "get-help about_signing" for more details.
Error
[Window Title]
Script Importer
Script Importer
[Main Instruction]
The script 'C:\test.ps1' failed to import.
[Content]
The contents of file C:\test.ps1 may have been tampered because the hash of the file does not match the hash stored in the digital signature. The script will not execute on the system. Please see "get-help about_signing" for more details.
Cause
The .ps1 file has been modified since the signature/hash value in the file was generated.
Solution
Re-sign the .ps1 file.
A script '...' by author '...' already exists
Error
[Window Title]
Script Importer
The script 'C:\test.ps1' failed to import.
A script 'Test' by author 'Shavlik' already exists
Script Importer
[Main Instruction]
The script 'C:\test.ps1' failed to import.
[Content]
A script 'Test' by author 'Shavlik' already exists
Cause
The ps1 file contains the same Name and Author value:
<name>Test</name>
<author>Shavlik</author>
Example:
<name>Test</name>
<author>Shavlik</author>
Solution
This likely indicates the script you're trying to import already has been added. If you would still like to add do any of the following:
- Change the Name value
- Change the Author value
- Delete the Script that is already imported into Protect.
The '...' start tag on line # position # does not match the end tag of '...'. Line #, position #.
Error
[Window Title]
Script Importer
[Main Instruction]
The script 'C:\test.ps1' failed to import.
[Content]
The 'options' start tag on line 9 position 4 does not match the end tag of 'optixons'. Line 14, position 5.
Cause
The listed tag does not have a matching set of opening and closing values.
<options>
</optixons>
Example:
<options>
</optixons>
Solution
Correct the tag's text and verify each opening tag/node has a corresponding closing tag/node.
The script '...' failed to import. Scripts cannot have the same ID or Name as another imported script. Please check your script to ensure it has unique metadata entries for those fields.
Error
[Window Title]
Script Importer
[Main Instruction]
The script 'C:\test.ps1' failed to import.
[Content]
The script 'C:\test.ps1' failed to import. Scripts cannot have the same ID or Name as another imported script. Please check your script to ensure it has unique metadata entries for those fields.
Cause
The UID value of the .ps1 file is already in use by another custom ITScript.
Solution
Change the UID value to a unique value.
A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file
Error
[Window Title]
Script Importer
[Main Instruction]
The script 'C:\test.ps1' failed to import.
[Content]
A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file
Cause
- The system Date/Time is incorrect.
- The Root Certificates on the Protect Console computer are out of date.
Solution
- Correct the system Date/Time.
- Update the root certificates.
- Related Document: Correcting Agent issues caused by out of date root certificates
Could not find any recognizable digits.
Error
[Window Title]
Script Importer
[Main Instruction]
The script 'C:\test.ps1' failed to import.
[Content]
Could not find any recognizable digits.
[OK]
Cause
- The GUID in the ps1 file has a non-hexadecimal value.
Solution
- Verify the GUID in the ps1 file contains only hexadecimal values (A-F, 0-9).
The following required fields are empty:...
[Window Title]
Script Importer
[Main Instruction]
The script 'C:\test.ps1' failed to import.
[Content]
The following required fields are empty: purpose
[OK]
Cause
- The listed element/node is does not contain any information.
Solution
- Enter information into the listed element/node
Example: In the listed example, the node 'Purpose' did not contain content. Adding something between the opening and closing tags fixes this issue.
The required element '...' is missing.
[Window Title]
Script Importer
[Main Instruction]
The script 'C:\test.ps1' failed to import.
[Content]
The required element 'purpose' is missing.
[OK]
Cause
- The listed element is missing from the ps1 file. Certain elements are required, and if they are missing they cause this issue. See this document on required elements.
Solution
- Add the listed/missing element.
Example: In the listed example, the element 'Purpose' was not in the ps1 file. Adding the element back into the ps1 file within the Description tags fixes the issue.
| Related Information |
|---|
Guidelines for Creating Custom ITScripts
| Affected Product(s) |
|---|
Shavlik Protect 9.x