Resources > Troubleshooting Tips > Troubleshooting: Dispatch and Scheduling
Troubleshooting: Dispatch and Scheduling
The following are troubleshooting tips for Dispatch Console.
Issue
Troubleshooting Tip
Dispatch Console fails to launch and displays Invalid Session ID error message or white screen.
Salesforce session timeout in the parent window from where the Dispatch Console was launched causes this. Refresh the parent window to get a valid Salesforce session and launch the Dispatch Console again.
Dispatch Console fails to launch when using Google Chrome.
This can happen if Flash is not allowed to run in the websites. You can allow the flash to run by executing the following steps:
1. Go to Chrome Settings page, click Show advanced settings... link at the bottom of the page.
2. Click Content settings in the Privacy section.
3. Go to Flash section, select radio button Allow sites to run Flash.
4. Relaunch the Chrome browser and launch Dispatch Console.
Error 'Initialization failed- please check the client id, swf location, version and network availability.' displayed on launching the map
Launching Flash Map throws this error. From September 2014, it is not supported. Only JavaScript-based Map is supported.
Dispatch Console fails to launch when using Internet Explorer.
If the Internet Explorer version is 8, 9, or 10, ensure that the browser Compatibility Mode is turned off.
"Apex heap size too large" error is thrown on launching / manually or automatically refreshing / switching Queues/Views in Dispatch Console.
This can happen when the volume of data is very high. To address this, adjust the configuration settings related to batching. For more details, see section Performance Considerations.
When a user owns a large number (say 15000) closed work orders for work order history, opening the Dispatch Console throws a shockwave error/timeout and does not load due to the predefined view "My Work Orders" being the default. Is there a setting that will allow this user to login to the Dispatch Console?
You can set a standard or custom Dispatch Console Work Order View as the default view for this user, so that this user can launch Dispatch Console successfully.
Perform the following steps:
1. Launch Dispatch Console as another user who is a Super Dispatcher, select any required standard or custom Work Order View as the default view.
* 
Super Dispatcher is a ServiceMax packaged field in the Salesforce User object.
2. Click Deploy.
3. Select the affected user's team/territory, move the affected user from Available Dispatchers to Selected Dispatchers list box.
4. Select the required settings.
5. Click Deploy.
* 
Performing these steps overwrites all the other user setting values also with the values set by the super dispatcher.
The following error is displayed when scheduling a work order:
Access Violation :OBJECT_ACCESS_VIOLATION <field name>
This issue occurs because of the incorrect FLS and sharing settings permissions to fields. To resolve this issue, set the GBL031 setting to False.
For more information about the GBL031 setting and the FLS and sharing settings levels, see Enforcement of CRUD and FLS and Technical Details.
When there are two identical Technician/Equipment records, Dispatch Console assigns work order events to incorrect technician even after the user schedules it to a specific technician.
This issue occurs even if the technicians with same name belong to different service teams.
This issue may occur if two or more technicians are associated with the same Salesforce user profile. It is recommended to associate a Salesforce user profile with only one technician.
Partners and Community users are unable to launch Dispatch Console.
Perform the following checks:
Ensure that Partners and Community users have the correct access and permissions. For more information, see Community User Access and Permissions.
Ensure that the related global settings (GBL039, GBL040, and GBL041) have correct values. For more information, see Common - Global Settings.
Was this helpful?