

If you are having problems getting Grid 2 to start please phone the help desk for advice.
This article is intended for use by experienced IT support staff for fault-finding and repair start-up problems with The Grid 2 where remote support is not possible.
Occasionally Grid 2 won’t start. Sometimes you get a ‘Runtime Error 0’ message or it freezes and Windows announces there is a problem and it has closed the program. File locations in this article are for 64 bit versions of Windows. On 32 bit editions use the following folders:
C:\Program Files (x64)\Sensory Software -> C:\Program Files\Sensory Software
C:\Windows\SysWow64 -> C:\Windows\System32
Make sure all Windows updates are installed.
To force the sensory updater to do a ‘repair’ install delete the file:
C:\Program Files (x64)\Sensory Software \The Grid 2\The Grid 2.exe.manifest
and then run the on-line installer. This will check all files for corruption and are up to date.
If you don’t have access to the on line installer it is important to use the latest version of the installer CD. This can be downloaded from www.sensorysoftware.com/downloads/iso/the_grid_2. Failure to use the latest version of the installer can result in mismatched components.
Force Grid 2 to start in Grid Explorer by renaming the file:
C:\Users\Public\Documents\Sensory Software\The Grid 2\Preferences.xml
Reboot the machine and then try to start Grid 2. If it starts in Grid Explorer goto Step 3.
If you still cant start Grid Explorer, the problem is most likely to be one of the following:
Anti Virus software blocking access to either Sensory Licence Manager or Sensory Speech.
The installer failed to register/update some of the shared Microsoft dlls.
Location for the User folder is missing. Make sure the folder
“C:\Users\Public\Documents\Sensory Software\The Grid 2\Users”
exists and you can create files in that location.
Some anti-virus products have an option to pause their protection but it is necessary to completely uninstall the product to be certain. Be especially careful to check for out of date versions of AVG, McAfee and Norton. We find Microsoft Security Essentials one of the least intrusive products. McAfee and Norton frequently cause problems.
You can test Sensory Speech using the program:
C:\Program Files (x86)\Sensory Software\Common\Speech\Sensory Speech Test.exe
When setting exceptions, most AV products require separate settings for computer scans and real time protection. See How to configure exceptions for Microsoft Security Essentials for more details.
Occasionally programs running in the background block access to some of the shared Microsoft DLLs (MSWINSCK.OCX, mscomctl.ocx and mscomm32.ocx) during the install process. On startup, Grid 2 will normally raise a dialog naming the dll. To fix:
Open an elevated console window and CD to C:\Windows\SyWow64
Unregister and delete the three files:
regsvr32 /u xxx.dll
del xxx.dll
Rerun the installer.
If you have problems deleting the files you may need to start in safe mode to delete the files.
Once any Grid Explorer start-up problems have been resolved you should try to open a new user. Creating a new user ensures the problems are not related to corrupt user files. If Grid 2 crashes when opening a new user is most likely to be due to one of three problems:
Internet Explorer missing or corrupt.
Windows Media Player missing or corrupt.
AV products blocking access to Sensory Speech.
Open Internet Explorer to confirm it is working correctly (it need not have access to the internet, but it must be able to open correctly). You should also check for signs of malware in Internet Explorer (e.g. unwanted adverts). If you suspect malware we suggest you scan the machine with Malwarebytes (www.malwarebytes.org).
Occasionally corrupt media files cause Windows Media Player from starting. You may need to rename folders containing your media and then reset the library.
To test for problems with sensory speech, start Grid 2 into Grid Explorer and then, from Grid Explorer, select the new user and select ‘User Settings’ and test the speech from the speech settings dialog. If you experience problems at this stage they are most likely due to Anti Virus products.
Restore the preferences file to its normal name (see Step 2) and see if Grid 2 will start. If Grid 2 can open a newly created user, but crashes or hangs when trying to open a specific user is most likely to be a corrupt file in the users area. The name of the startup user is in the Preferences File as “<startuser>Fast Talker 2</startuser>”
Try deleting the touch type prediction file (where xxx is the username):
C:\Users\Public\Documents\Sensory Software\The Grid 2\Users\xxx\Settings0\Dictionary\touchtype_personal.lm3
If, after completing the above steps you are still having problems, please run sensory diagnostics to collect information and send the log file to support@smartboxat.com. Please also include details of any AntiVirus software you are running and your contact details.
Join the Smartbox mailing list for regular updates and news.
You can change your mind at any time by clicking the unsubscribe link in the footer of any email you receive from us, or by contacting us at hello@thinksmartbox.com.
We use MailChimp as our marketing email platform. When you join, you acknowledge that the information you provide will be transferred to MailChimp for processing in accordance with their Privacy Policy and Terms.
Cookie | Duration | Description |
---|---|---|
AWSALBCORS | 7 days | This cookie is used for load balancing services provded by Amazon inorder to optimize the user experience. Amazon has updated the ALB and CLB so that customers can continue to use the CORS request with stickness. |
cookielawinfo-checkbox-advertisement | 1 year | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Advertisement". |
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
PHPSESSID | session | This cookie is native to PHP applications. The cookie is used to store and identify a users' unique session ID for the purpose of managing user session on the website. The cookie is a session cookies and is deleted when all the browser windows are closed. |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
Cookie | Duration | Description |
---|---|---|
__zlcmid | 1 year | This cookie is used by Zendesk live chat and is used to store the live chat ID. |
player | 1 year | This cookie is used by Vimeo. This cookie is used to save the user's preferences when playing embedded videos from Vimeo. |
Cookie | Duration | Description |
---|---|---|
_gat | 1 minute | This cookies is installed by Google Universal Analytics to throttle the request rate to limit the colllection of data on high traffic sites. |
Cookie | Duration | Description |
---|---|---|
_ga | 2 years | This cookie is installed by Google Analytics. The cookie is used to calculate visitor, session, campaign data and keep track of site usage for the site's analytics report. The cookies store information anonymously and assign a randomly generated number to identify unique visitors. |
_gat_UA-65566191-1 | 1 minute | This is a pattern type cookie set by Google Analytics, where the pattern element on the name contains the unique identity number of the account or website it relates to. It appears to be a variation of the _gat cookie which is used to limit the amount of data recorded by Google on high traffic volume websites. |
_gid | 1 day | This cookie is installed by Google Analytics. The cookie is used to store information of how visitors use a website and helps in creating an analytics report of how the website is doing. The data collected including the number visitors, the source where they have come from, and the pages visted in an anonymous form. |
_hjFirstSeen | 30 minutes | This is set by Hotjar to identify a new user’s first session. It stores a true/false value, indicating whether this was the first time Hotjar saw this user. It is used by Recording filters to identify new user sessions. |
vuid | 2 years | This domain of this cookie is owned by Vimeo. This cookie is used by vimeo to collect tracking information. It sets a unique ID to embed videos to the website. |
Cookie | Duration | Description |
---|---|---|
_hjAbsoluteSessionInProgress | 30 minutes | No description |
_hjid | 1 year | This cookie is set by Hotjar. This cookie is set when the customer first lands on a page with the Hotjar script. It is used to persist the random user ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID. |
_hjIncludedInPageviewSample | 2 minutes | No description |
_hjShownFeedbackMessage | 1 day | No description |