Differences

This shows you the differences between two versions of the page.

--- troubleshooting:slotting:setup_yes [2019/02/28 23:46] – [Slotting Script Ran Correctly] Scott Cunliffe
+++ troubleshooting:slotting:setup_yes [2025/01/21 22:07] (current) – external edit 127.0.0.1
@@ Line 19: / Line 19: @@
 Did your scheduler run the slotting script?
+==== Slotting Script Not Running ====
+If the scheduler did not run the script, contact your Network Administrator to diagnose why your scheduler is not running the slotting scripting.
+Common problems to look for:
+Task no longer enabled.
+Task triggers no longer correct.
+Not installed on the same server as TapeTrack framework server.
+Insufficient privileges to run script on network.
+Scheduler not set to run when user not logged in.
 ==== Slotting Script Ran Correctly ====
@@ Line 26: / Line 39: @@
 Error text:
+[[#Logon failed: User-ID is undefined]] \\
+[[#Logon failed: Authorization failure]] \\
+[[#Logon failed: Logon failed as access has been revoked]] \\
+[[#Customer List successful: Customers(0) Excluded( )]] \\
+[[#Resolution of hostname failed: No such host is known]] \\
+[[#Slot Allocation Error: Slot Exceeds Maximum Allocated]] \\
+[[#Different error or Unable to identify error]]
 === Logon failed: User-ID is undefined ===
@@ Line 58: / Line 80: @@
 ----
+=== Customer List successful: Customers(0) Excluded( ) ===
+An error of **Customer List Successful: Customers(0)….** is caused when the logon is successful but the login ID has no access rights to Customer-ID's.
+This may be caused by someone editing the access rights to the Slotting User-ID or the group that the Slotting User-ID is assigned to.
+Check the User-ID access rights via TapeMaster by either logging in to using the Slotting ID credentials or using a tapemaster enabled User-ID to access the Slotting-ID in the Group/User Administration panel.
+----
+=== Resolution of hostname failed: No such host is known ===
+Incorrect host DNS. Check the spelling of host name or IP address is correct. Ping the server address using TMSS10Ping to see if there is access from your computer running the script.
+----
+=== Slot Allocation Error: Slot Exceeds Maximum Allocated ===
+There are more Volumes queued for slotting than there are slots available. Remove sufficient Volumes from slots or increase slots available to the repository to accommodate queued volumes and run [[cli:tmss10slotallocation|TMSS10SlotAllocation]].
+----
+=== Different error or Unable to identify error ===
+Contact GazillaByte for Additional Support.  \\ \\ [[common:support_details|Contact GazillaByte for software support]].  Include the file slotting_error.txt and slotting_report.txt, as well as any further information that you think,  may help to diagnose the problem (such as when the problem started, limited to a customer or global, any changes in environment etc) in your correspondence.