> For the complete documentation index, see [llms.txt](https://sandbox-docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sandbox-docs.verifone.com/adk-5.0-programmers-guide/readme/pg_system_diagnosis_and_troubleshooting/pg_vss_extra_troubleshooting.md).
# Extra VSS Troubleshooting
#### Tableof Contents
* [VSS script failed to load for the script slots over 7 (VOS1)](#sec_vss_appendix_b)
## VSS script failed to load for the script slots over 7 (VOS1)
There are several reasons why VSS script may fail on installation/loading. Most of those are described in the [VSS Troubleshooting Guide](/adk-5.0-programmers-guide/readme/adk_programming_interfaces/pg_vss_documentation/vss_documentation.md#sec_vss_appendix_b). Below are some extra troubleshooting steps that can be taken if the issue is not resolved after following the guide.
In particular here we will troubleshoot the issue of VSS scripts failing to load for the script slots with numbers over 7.
There were several major VSS upgrades defining the number of scripts supported:
| ADK version | TTL number of scripts supported | Number of 'usr' scripts supported | Number of 'sys' scripts supported |
| ---------------- | ------------------------------- | --------------------------------- | --------------------------------- |
| Pre ADK 4.4 | 8 | 8 | Not supported |
| ADK 4.4, ADK 4.6 | 64 | 64 | Not supported |
| ADK 4.7 | 96 | 96 | Not supported |
| ADK 4.8 | 192 | 96 | 96 |
The number of scripts supported should be automatically upgraded with an ADK upgrade. Though if customer was using more than 8 VSS scripts (or have installed scripts in script slots with numbers >7) before the upgrade, the automatic upgrade might fail sometimes.
The reason why that happens exactly for the slots with numbers >7 is that the first 8 scripts' data registry is stored in a separate vsslist.dat file, which was initially designed to support only 8 scripts. The data registry for scripts with numbers >7 is stored in the lately added vsslist2.dat file, which should then be updated each time the supported number of VSS scripts changes. If the automatic upgrade of the latter fails, all the scripts in the slot numbers over >7 will fail to load on the device (as on VOS1 VSS scripts are being reloaded on the device on each boot).
Current solution to this issue is a hotfix that can be applied by the installation of a **dl.vsslistsync-prod.tgz** package (or **dl.vsslistsync.tgz** package - for DEV devices) on the terminal. This package can be requested from Verifone Support Team.
The aforementioned hotfix will update the vsslist2.dat file to support the number of scripts defined by the ADK version installed on the device, which should resolve the issue of VSS scripts failing to load for the script slots with numbers over 7. After a successful installation and fixing the issue, this package will be autoremoved from the device. There's no need to reinstall it on the device on each ADK upgrade, unless the issue appears again after the upgrade.
#### Attention
Please, note that the hotfix will reboot your device up to 3 times during the installation and fixing process, so make sure to install it at the time when the device can be rebooted without any issues.
{% hint style="info" %}
If you were already using VSS scripts stored in slot numbers more than 7 before the upgrade, those would still be present on the device after applying the hotfix (so no need for re-installation), and should now successfully load on the device.
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://sandbox-docs.verifone.com/adk-5.0-programmers-guide/readme/pg_system_diagnosis_and_troubleshooting/pg_vss_extra_troubleshooting.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.