When an application begins behaving unexpectedly, there are several foundational troubleshooting steps you can perform before reaching out to support. These steps apply broadly to most software—not just eOne products—and can often resolve issues quickly without waiting for assistance
1. Restart the application
The first and most effective troubleshooting action is to close and relaunch the application. Many issues stem from temporary glitches, memory conflicts, or processes that fail to reset properly. Restarting clears the active session and frequently resolves unexpected behavior.
2. Reboot the Workstation
If restarting the application does not resolve the issue, reboot the computer. Systems that remain powered on continuously or are only put to sleep can accumulate resource conflicts over time. A full reboot refreshes the operating environment and eliminates many underlying issues that an application restart alone cannot fix.
3. Determine Whether the Issue Is User-Specific or Workstation-Specific
Identifying whether the problem is tied to a user profile or a specific machine is an important diagnostic step. This can be done by swapping users and workstations:
Example Scenario
- User David encounters an error on his workstation
- User Erik uses the same application on his workstation without issues.
To isolate the cause:
- Have David log in on Erik’s workstation.
- Have Erik log in on David’s workstation.
Interpreting the Results
- If the error follows David to Erik’s workstation: The issue is related to David’s user account, not the machine.
- If the error stays on David’s workstation and Erik now receives it: The issue is workstation‑specific.
Next Steps
- Workstation‑specific issue: Reinstall or repair the application on the affected machine.
- User‑specific issue: Review and compare user permissions, security roles, or configuration settings.
4. Review the Error Message Carefully
Error messages vary in clarity. Some are vague and offer little diagnostic value, while others explicitly identify the problem.
Examples:
- A generic Windows error such as “An unspecified error occurred during System Restore (0x8000ffff)” provides minimal direction.
- An eConnect error like “The Customer Class ID is empty… a Customer Class is required” clearly identifies the missing data.
Reading the message closely can often point you directly to the root cause.
5. Search for the Exact Error Message
If you have a specific error message, search for it using the software vendor’s Knowledge Base or FAQ resources. Most software providers maintain online documentation that includes common issues and resolutions. The eOne Knowledge base can be accessed here: eOne KnowledgeBase
If the vendor’s site does not provide results, use a general search engine. Many issues have been encountered and documented by other users in forums, blogs, or community discussions.
6. Contact Support
If you have completed all the steps above and the issue persists, it is time to contact support. Having already performed these preliminary checks will help streamline the troubleshooting process and reduce resolution time.
A follow‑up article will outline the information you should gather before opening a support case.
