Memory not available (INtime for Windows) If you receive a message about license failure, inspect the cases in the “License Failures” section. Possible failures may include the following: Look for error messages from the INtimeKernelManager service, which should explain why the kernel failed to start. Open the Windows Event Viewer and inspect the INtime log. To access the event log, click on INtime status monitor icon and select Event Viewer from popup menu. I started the INtime kernel but it did not start (INtime for Windows) If you have multiple development kits each with their own key, be sure to use the correct key with each development kit. A fingerprint with RAID enabled will create a license that will be invalidated after a disk reformat. Make sure that RAID is disabled in the BIOS before reformatting the disk drive to avoid invalidating the license for future drive reformatting. Some default BIOS settings enable RAID even with only one disk. However, if the storage medium is a RAID volume then there is no unique disk ID so the license reverts to using the Windows volume ID. After INtime 5 the disk hardware ID is used instead so this is no longer an issue. If you replace or reformat the disk drive then your license will be invalidated. Prior to INtime 5, a node-locked license is keyed in part from the volume ID of the system volume of the Windows installation. Reformatting the hard drive will invalidate the license Incorrect license installedīe careful that when installing a license generated from a fingerprint that the license is being installed on the correct host. Restoring the clock value will allow the system to continue to function. If your clock battery failed or the system clock was changed back by more than one day after you install the software, the license management software considers this action as an attempt to defeat the licensing, so will fail. See the documention on License Manager for more information. This topic lists problems you may encounter while running INtime software, and explains how to avoid or resolve those problems. The system freezes when I start my application.It isn't the most intuitive either and takes some time to get the hang of, but this is likely the case with most timekeeping systems. Also fixes seem to be delayed at times, we are still waiting on a fix for fields that are not populating when filled in via the app, and therefore they are blank on the CSV for timekeeping. Although it seems some agencies are able to get updates done, which then changes it for everyone with no input. There doesn't seem to be a formal process for getting something updated. CONSįeatures requests or updates are not handled efficiently. InTime has some great features and once you get the hang of it, it is very useful in daily scheduling and overall timekeeping. But overall it is a great product and suits our needs. We've had some suggestions for improvements/changes that would make it easier for us and likely other agencies but have not seen any of them come to fruition yet. Along the way our InTime contacts have been great. We started with just department scheduling, then added the court module and now just integrated with Munis for our timekeeping. I have been involved in InTime transition since the beginning.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |