Res 3.2 log errors question

[our2]

backups no longer being done, credit cards not batching and couple other things, these are the errors I see in log below. The 3 interface messages are repeated frequently. I've searched and searched for any clues but no luck, support so far hasn't been able to help.
Thanks for any help.


Thu Mar 06 05:00:00 2014 | MICROS1 AutoSeqServ | 7A8 | Autosequence 10211 step 1 of type X has encountered a date range error...Failed to acquire specified date from source. |
Thu Mar 06 05:08:25 2014 | MICROS1 | IFS | 6C4 | Interface [Micros] failed to open TCP session with [ip#ort#]
Thu Mar 06 05:08:25 2014 | MICROS1 | IFS | 6C4 | Interface [Chain] failed to open TCP session with [ip#ort#]
Thu Mar 06 05:08:25 2014 | MICROS1 | IFS | 6C4 | Interface [CashierSim] failed to open TCP session with [ip#ort#]
Thu Mar 06 05:12:00 2014 | MICROS1 | AutoSeqServ | 7A8 | Signalling automatic reload |
Thu Mar 06 05:12:00 2014 | MICROS1 | AutoSeqServ | 7A8 | Autosequence Server Is Reloading. |
Thu Mar 06 05:12:00 2014 | MICROS1 | 3700d | 1f8 | Op step changed from [39] to [13] after [AutoSeqServ] [RELOADING] |
Thu Mar 06 05:12:00 2014 | MICROS1 | 3700d | 1f8 | Op step changed from [13] to [39] after [AutoSeqServ] [OPERATIONAL] |
Thu Mar 06 05:12:00 2014 | MICROS1 | AutoSeqServ | 7A8 | Scheduler has detected a NULL day_of_week list for a DAYS_IN_WEEK autosequence type! |

 

[DJensen999]

On the interface side, check in POSCFG, Devices, Interfaces. Verify that the Network Node is set properly on the general tab (should probably be the back office PC) and that the host and port on the interface tab is reachable/open for each item in the error log above (Micros, Chain, CashierSim).

On the AutoSeqServ error on first and last lines, check your schedules in Reporting, Schedule Classes and verify that the schedule assigned to Autosequence 10211 is configured properly.

 

[our2]

Should the End of Week schedule class have all the days unchecked?

Port is set to use 5009 and did verify Network Node is correct. Would these interfaces not connecting have anything to do with End of Day autosequence not working?

 

[DJensen999]

It depends on how your schedules are set up, but my "end of week" schedule shows one day (Monday) checked. If the dayend autosequence is not running, double-check the schedule class assigned to it.

The interfaces not working should not be interfering with autosequences. Next steps would probably be to figure out what each interface is doing - check in micros\res\pos\etc for the ISL files and pop them open with notepad. pms1.isl should correspond to interface #1 in the list and so on. From my limited experience, if you can't read past the first line, it's a compiled script and probably needs the IP and port on the "interface" tab set - otherwise, the values on that tab should probably NOT be set.

 

[our2]

hmmm when checked autosequence 10211 which is the end of day, pretty sure end of week schedule class is assigned to it but my memory blows its been whole 2 days. Makes no sense to me, would think end of day schedule class would be the one assigned. Will check it out next time get a chance. Next option check Monday and pray...

 

[our2]

Apparently credit card server went to off state late last night. Went in this morning and simply turned it back on via control panel. Maybe should bite the bullet and upgrade? $3200 gets me a switch,5 flash cards and upgrade from 3.2 to 5.2 believe on a new pc. Just have this feeling problems are going to get worse and worse.

 

[DJensen999]

That is probably a good bet, all things considered. Only 4.10 and newer (might be 4.11?) are PA-DSS compliant anymore, and nothing that runs on XP will be PCI-compliant in about three weeks.

 

[our2]

There is no isl files in micros\res\pos\etc so assume its not being used. Now if could get the autoseq working be happy.

 

[our2]

I found no isl files, grammar worse than usual when in a hurry.

One last question when highlight the autosequence 10211 which is end of day, should the schedule class be end of week assigned?

 

[Wildbar]

Typically no. But that depends on how things are programmed. Your end of day should run at the end of every day, usually after you close. You need to see how your schedule classes are set. Maybe you scheduled end of week is set to run everyday.

 

[our2]

Yes it does run at 5 am with the errors I posted.

 

[our2]

oops autoseq 10211(EOD)is set to schedule class End of Day Report and schedule data type for that report is set to Days in Week with all days checked. Can I manually run that autoseq or can only be run by the start time set for end of day report which is 5 am?

 

[Wildbar]

You can manually run it but you don't want to do that when you are open (have sales ringing in, people clocking in or out) and you don't want to manually run it close to when the auto sequence one is going to run.

 

[our2]

MICROS1 AutoSeqServ | 7A8 | Autosequence 10211 step 1 of type X has encountered a date range error...Failed to acquire specified date from source. |

Step 1 is rotate log so set it to skip hence wanted to run it before bar opened to check out log file.

MICROS1 | AutoSeqServ | 7A8 | Scheduler has detected a NULL day_of_week list for a DAYS_IN_WEEK autosequence type! |

That one I believe is due to no days checked for End of Week schedule class, Djensen mentioned had Monday checked.

What don't understand is how that autosequence stopped working after 12 years and fairly sure no one made any changes. Wish owner would just upgrade and make my life easier.

 

[our2]

Now the print closed check report is throwing a "has encountered a date range error...Failed to acquire specified date from source".

I have poured over dozen manuals to no avail, is there a source online where I could learn more about the programming part of Micros 3700 Res 3.2?

Wildbar if your around, you can go to

http://wpssportsbar.com/wpswccontact.html

and I will be able to contact you.