Warning: include_once(Support/PParts/ArticleHeader.php): failed to open stream: No such file or directory in /usr/home/trivectus/public_html/trivectus.com/Support/SLP/Problems/SLP060100P-04.php on line 29
Warning: include_once(): Failed opening 'Support/PParts/ArticleHeader.php' for inclusion (include_path='.:/usr/local/lib/php') in /usr/home/trivectus/public_html/trivectus.com/Support/SLP/Problems/SLP060100P-04.php on line 29
Warning: include_once(Support/PParts/ManifestationHeader.php): failed to open stream: No such file or directory in /usr/home/trivectus/public_html/trivectus.com/Support/SLP/Problems/SLP060100P-04.php on line 30
Warning: include_once(): Failed opening 'Support/PParts/ManifestationHeader.php' for inclusion (include_path='.:/usr/local/lib/php') in /usr/home/trivectus/public_html/trivectus.com/Support/SLP/Problems/SLP060100P-04.php on line 30
You have Client set to auto-activate after a period of inactivity, but it never does. You are running version 4.0.0.
Warning: include_once(Support/PParts/DiscussionHeader.php): failed to open stream: No such file or directory in /usr/home/trivectus/public_html/trivectus.com/Support/SLP/Problems/SLP060100P-04.php on line 42
Warning: include_once(): Failed opening 'Support/PParts/DiscussionHeader.php' for inclusion (include_path='.:/usr/local/lib/php') in /usr/home/trivectus/public_html/trivectus.com/Support/SLP/Problems/SLP060100P-04.php on line 42
This is a known bug caused by an overflow condition within Client. It displays itself whenever the activation delay is set to more than five minutes.
Warning: include_once(Support/PParts/SolutionHeader.php): failed to open stream: No such file or directory in /usr/home/trivectus/public_html/trivectus.com/Support/SLP/Problems/SLP060100P-04.php on line 54
Warning: include_once(): Failed opening 'Support/PParts/SolutionHeader.php' for inclusion (include_path='.:/usr/local/lib/php') in /usr/home/trivectus/public_html/trivectus.com/Support/SLP/Problems/SLP060100P-04.php on line 54
This bug was fixed in version 4.0.1; therefore, the recommended solution is to upgrade to version 4.0.1 or later. If this is not feasible, a work-around is to keep the delay set to five minutes.