Im not having any problems with my v5.7 systems...
Maybe there is a reason why autosequence bomb out with EOD?
Have you took a look in the ETC log file?
I find using custom labor reports to be the problem with EOD.
Try changing any custom labor, typically a labor + emp tip report, to the standard 37 Employee Time Card and Jobs Detail report.
yes, autosequence server is running on my v5.7 box.
now after going back through your post, I see that you are using EM.
Sorry, I have used EM since the old Lyons/Denny's Rest days.
-BUT-
In my experience, anytime any micros service stops unexpectedly, there is usually an error in windows log and/or micros ETC log file.
Yes I have been doing this for 25. This is a raw db, not EM'd yet and I step my system from 5.5.4 to PRE 5.6 then RES 5.6 then PRE 5.7 then RES 5.7. only after I reboot on the RES 5.7 install does the service stop working. 3700d.log is rotating like it should. No MDS Host or MDS Printer because I have not fired up Control Panel.
Do you show SQL Anywhere 16 and 17 in your Program Files(x86)?
I am having the same issue, can you give me more detail on how you fixed it. How did you recreate the auto sequence service most specifically. Thank you
I noticed that happening on our lab as well. The most interesting part is that you could see in the logs it was starting up, and the issue was that rather than doing the proper service startup, it was actually starting autosequences. It was doing this in a blocking manner which essentially causes the service controls to time out. Wonder what they changed to cause behavior like that that just reinstalling it could fix.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.