Micros 3700 4.7 to 5.7 Error Connecting to Autosequence PC

[mvelazquez]

thread693-1753299

Hello everyone,

For some time I began to perceive that micros frequently marks the following error when executing reports.

Error Connecting to Autosequence PC

In my experience this error can arise from many issues, from a bad configuration of the Hosts, Ip's, etc ... but the most frequent is due to a failure in the autosequence service.

Perhaps it becomes so frequent to me since we support more than 70 restaurants and when one does not report it, another reports it.

When it started to happen frequently I thought that maybe with an update it began to happen and with a patch it would be solved but I have had to see it in the following configuraciones.

Micros 3700 4.7 running on Win Server 2003, 5.4 and 5.5 on Win Server 2012 up to 5.7 MR6 running on Win Server 2016.

One of the recommendations that I have seen to solve it is:

Restart

Autosequence Service​

Remoting Service​

IIS Service​

In most cases it solves it, sometimes by restarting more than twice and waiting a moment.

What I would like to know is what generates this situation or how to prevent it.

I have searched logs but have never been able to detect it.

 

[mvelazquez]

Does anyone else have the same thing or have any recommendations?

 

[K_Mos]

Run the following in Admin Command Prompt:

net stop "MICROS Autosequence Server"
sc delete "MICROS Autosequence Server"
sc create "MICROS Autosequence Server" binPath=D:\MICROS\common\bin\AutoSeqServ.exe start=auto
net start "MICROS Autosequence Server"
net restart "MICROS Remoting Service"
net restart "W3SVC"

That should remove and recreate the service which has helped me with other Micros services.
Then restart all the other dependent services.

 

[mvelazquez]

Thanks K_Mos

I did not see your answer. I will try the steps as well as you comment the next time it happens and I mention the results here.

We hadn't really tried to recreate the services.