we're running multicompany direct on startup as a recurring task (1 min) . 9.05.701 . no problems
Having an issue where the multi-company direct process just sits in Scheduled as the startup task, and when I restart the appservers it just stays in scheduled with the "next run time" as the last time the task agent was restarted. Anyone encounter this before?
I just got the recommendation to move multi company direct from startup to interval last week.
Greg
===================================================
PAGE: 14812MPS
PROBLEM DESCRIPTION:
I've been asked to move my multi-company process from a startup schedule to an interval schedule - how do I do that?
PROBLEM RESOLUTION:
CREATE AN INTERVAL SCHEDULE:
1. Navigate to System Management > Utilities > System Agent.
2. Click on the Agent ID button and press the search button - select the first result and press OK.
3. Click File > New > New Schedule.
- Go to Schedules Tab
- In the Description field, enter 5 min int.
- Select Interval Schedule for the Schedule Type.
- Enter 500 for the interval (which means this schedule will run every 5 minutes).
- For the Next run time, select 5 minutes or more into the future. (basically allow enough time into the future to complete the remaining steps and restart ProcessServer and TaskAgent appservers)
- Click the Save button on the toolbar.
- Close the System Agent screen.
REMOVE THE MULTI-COMPANY PROCESS FROM STARTUP SCHEDULE:
1. Navigate to System Management > Utilities > System Monitor.
2. Click on Scheduled Tasks tab.
3. Actions > Display All Tasks and then click refresh on the toolbar.
4. Highlight the Multi-Company process and then click X on the toolbar.
5. Click on Active Tasks tab.
6. Highlight the Multi-Company process and then click X on the toolbar.
7. Wait for the Multi-Company process to clear from Active Tasks and then close out of the System Monitor screen.
RESUBMIT MULTI-COMPANY DIRECT PROCESS (if using Direct):
1. Navigate to System Management > Utilities > Multi-Company Direct Server Process if using Direct OR
System Management > Utilities > Multi-Company Server Process if using Sonic.
2. Select 5 min int from the Schedule drop down.
3. Uncheck 'Continuous Processing'.
4. Click File > Submit.
5. Close out of the window.
Restart the ProcessServer and TaskAgent appservers after going thru the steps above.
VERSIONS:
9.05
KEYWORDS:
schedule
startup
interval
mc
==================================================
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Monday, July 28, 2014 4:00 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Multi-Company Direct stays as Scheduled Task
Having an issue where the multi-company direct process just sits in Scheduled as the startup task, and when I restart the appservers it just stays in scheduled with the "next run time" as the last time the task agent was restarted. Anyone encounter this before?
CONFIDENTIALITY NOTICE
The information contained in this communication, including attachments, is privileged and confidential. It is intended only for the exclusive use of the addressee. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us at 727-578-6280 and immediately delete the communication.
"This (document/presentation) may contain technical data as defined in the International Traffic In Arms Regulations (ITAR) 22 CFR 120.10. Export of this material is restricted by the Arms Export Control Act (22 U.S.C. 2751 et seq.) and may not be exported to foreign persons without prior approval form the U.S. Department of State."
Greg,
Is this a known problem with multi company processing? We have not had this issue...yet. But it might be smart to make the changes before we notice the problem. Thanks,
John
Hey guys, turns out it was a task agent problem instead. E9 support did recommend to us that we run off the interval instead of startup/continuous processing however that won't work for our business.
I had changed our multi-company direct and global alerts/email to run on interval schedules. Direct started hanging every few days. The multi-company log had "Inbound Processor Failed" messages. I had to stop and restart appservers to restart the process. Support suggested I try some different time intervals which didn't work; said the processes was tripping over itself. They recommended I change it back to the start up schedule. We're on 9.05.701. Keep an eye on it after you change it, apparently the interval schedule doesn't work for everyone. No problems with the global alert/email on an interval process although I changed that back when I changed the multi-company back.
Sue
Sue