The groundhog may have seen his shadow, but we’re still getting ready for spring. This week, take some time to do a little housekeeping to ensure you’re prepared for whatever the season brings.
KHS part number updates: KHS has changed a large number of part numbers in their system in order to allow for product expansions. However, Ascend will need some TLC in order to accept these new part numbers without creating duplicate products. Set aside some time to give our support line a call to run the queries to get your system ready for these changes.
Windows® woes: Are you having trouble getting Ascend to recognize your inventory scanner? Have you recently run updates for Windows® 10? It’s a good bet that some of your Windows® settings may have been reset.
We’ve previously touched on this issue. Unfortunately, we’ve seen evidence that these settings could continue to be reset by future Windows® updates. While we continue to strive for a permanent solution, we recommend that you save our knowledge base article or Ascend University module to your inventory computer’s Windows® Desktop for easy access to the steps for the DIY fix.
- Right-click in a blank area of your Windows® Desktop and choose New > Shortcut.
- In the Type the location of the item field, enter the URL for your desired link and click Next.
- In the Type a name for this shortcut field, enter a description that will make it easy for you to find the shortcut (e.g. Mobile Device Center fix) and click Finish.
That’s it! Now you can just double-click this shortcut to open your preferred instructions.
If you’re still having trouble with your scanner after running this fix, or if Windows Mobile Device Center is launching correctly, check our other troubleshooting tips in our knowledge base article or Ascend University module.
“Locked” transactions: In the Winter 2017 version, we introduced a feature to prevent transactions from being opened on multiple workstations, as we discovered that several bugs were being caused by this situation. But this change has uncovered some additional problems which users are no longer able to simply overlook.
When a transaction is opened on a workstation, a “flag” is automatically set to tell Ascend that the transaction is now in use. If someone else tries to open that same transaction, they’ll receive a message that it’s already open on another workstation. Under normal circumstances, the transaction is “released” when the user saves and exits it.
But sometimes, an issue can arise that causes Ascend to freeze (prompting the user to perform an “End Task”) or crash. In this instance, the “flag” is never removed, so every workstation – including the one it was opened on before the freeze/crash – which tries to access the transaction receives the message that it’s still open on another workstation. The Ascend support team must then run a query to remove the “flag.”
This should be an extremely rare occurrence. If you’re seeing a large number of instances of Ascend freezing or crashing, please give our support line a call as soon as it’s happening. There are likely underlying issues that are causing this, and if ignored, can cause other serious issues (including possible loss of data) down the road.
If you’re seeing instances of this messages at times when Ascend seems to have no problems, please ensure the following:
- Check that the transaction isn’t, in fact, open on another workstation. The message will tell you the name of the user and workstation on which the transaction is open.
- All workstations are assigned unique Workstation Names. If you’re unsure how to set these up, you can find step-by-step instructions in our knowledge base article.
- Do not run multiple instances of Ascend. This isn’t a normal setup, but some older shops may still have this legacy setting enabled.
- Make sure you’re on the latest version of Ascend (currently Winter 2017, or 1.107 if you’re in Oregon).