We are using the Texis Monitor service with our product. Occasionally, upon a clean install we are seeing errors when hitting our Vortex script. An "error reading licensing segment" is reported because Texis Monitor could not access it's config files. This might happen for awhile, and then go away, never to return. Is there something we can do to debug this or to ensure that it never happens?
Texis service
Texis service
Make sure all pertinent files are in place before executing monitor or any other texis program?