Solved Windows 10 Reboots
-
and since my boss jumped on it this morning because the customer emailed we have found : there are 2 instances of the software running at the same time to do 2 of our softwares opening different instances at the same time, which at the time of a "refresh" from alohamanager cause it to restart the back office.
-
@WrCombs said in Windows 10 Reboots:
and since my boss jumped on it this morning because the customer emailed we have found : there are 2 instances of the software running at the same time to do 2 of our softwares opening different instances at the same time, which at the time of a "refresh" from alohamanager cause it to restart the back office.
So AlohaPOS is running twice, by accident I assume?
Why does that cause it to restart?
-
@scottalanmiller said in Windows 10 Reboots:
@WrCombs said in Windows 10 Reboots:
and since my boss jumped on it this morning because the customer emailed we have found : there are 2 instances of the software running at the same time to do 2 of our softwares opening different instances at the same time, which at the time of a "refresh" from alohamanager cause it to restart the back office.
So AlohaPOS is running twice, by accident I assume?
Why does that cause it to restart?
Just a guess, but licensing seems like a likely reason.
-
@scottalanmiller said in Windows 10 Reboots:
@WrCombs said in Windows 10 Reboots:
and since my boss jumped on it this morning because the customer emailed we have found : there are 2 instances of the software running at the same time to do 2 of our softwares opening different instances at the same time, which at the time of a "refresh" from alohamanager cause it to restart the back office.
So AlohaPOS is running twice, by accident I assume?
Why does that cause it to restart?
yes, by accident.
Something in the coding Im sure.
It's a known issue within the aloha world apparently. -
@scottalanmiller said in Windows 10 Reboots:
@Obsolesce said in Windows 10 Reboots:
@Dashrender said in Windows 10 Reboots:
That seems a bit of the top for a suggestion - not saying it's wrong, but I've never seen the requirement to get a new machine because Windows 10 was installed and something was causing it to reboot.
Personally - I'd wipe and reload it long before buying a new machine, but you're remote, so that's a harder decision.
Have you used the MS Fixit tool for Windows Update? that might do the trick.
Maybe if he's making like $10 an hour then by all means dump a couple days into screwing around with an old PC with no drivers for the OS it's using. (if that's the issue... if not a reload or newer PC would soon pay for itself in given support already)
It's the impact to the customer, not the cost of his time that is the issue.
The impact to the customer is a machine that isn't doing its job for weeks while someone screws with it endlessly, instead of just reloading or refreshing it way sooner and getting it back into service.
-
@WrCombs said in Windows 10 Reboots:
It's a known issue within the aloha world apparently.
WTF, seems like something that they could fix easy. So Aloha itself "just reboots" the PCs sometimes?
-
@scottalanmiller said in Windows 10 Reboots:
@WrCombs said in Windows 10 Reboots:
It's a known issue within the aloha world apparently.
WTF, seems like something that they could fix easy. So Aloha itself "just reboots" the PCs sometimes?
it reboots on failure, more than one instance of the software running at the same time, and other reasons.
-
@scottalanmiller said in Windows 10 Reboots:
@WrCombs said in Windows 10 Reboots:
It's a known issue within the aloha world apparently.
WTF, seems like something that they could fix easy. So Aloha itself "just reboots" the PCs sometimes?
And a fresh load a week sooner would have ruled out the OS and drivers, and could have moved on to broken software realization then. If that's what it is, haven't been really following.
-
Now - all that shit said - eventually, you will likely find a solution.
I had a user complaining that their computer was going to sleep after 2 mins, all the time. Of course when I came and visited, it never happened, until it did.
In my case it ended up being a hidden time (hidden until a registry entry was changed to make it show up) that has to be manually changed (I can't find any way to change it via the registry or GPO, etc).
I spent time off an on for a year trying to solve this issue. Then one random day, I got the needed search terms to find this needle in a haystack...
All that said - I probably only spent about 20 mins over 4-5 times searching over that year.. that's still more than an hour of time.
-
@WrCombs said in Windows 10 Reboots:
@scottalanmiller said in Windows 10 Reboots:
@WrCombs said in Windows 10 Reboots:
It's a known issue within the aloha world apparently.
WTF, seems like something that they could fix easy. So Aloha itself "just reboots" the PCs sometimes?
it reboots on failure, more than one instance of the software running at the same time, and other reasons.
So - the boss knew about this reboot because of two instances things, and he only now decided to look at this machine after the client complained that two weeks happened and no fix.... wth?
Did you know about this reboot on failure situation?
Why was a ticket to AlohaPOS never opened? (I'm assuming one wasn't).
So is it fixed now? did your boss uninstall Aloha and reinstall to get rid of the double install?
-
@Dashrender said in Windows 10 Reboots:
@WrCombs said in Windows 10 Reboots:
@scottalanmiller said in Windows 10 Reboots:
@WrCombs said in Windows 10 Reboots:
It's a known issue within the aloha world apparently.
WTF, seems like something that they could fix easy. So Aloha itself "just reboots" the PCs sometimes?
it reboots on failure, more than one instance of the software running at the same time, and other reasons.
So - the boss knew about this reboot because of two instances things, and he only now decided to look at this machine after the client complained that two weeks happened and no fix.... wth?
yes, but with 2 different software installed he wasn't thinking about that.
Did you know about this reboot on failure situation?
Yeah, I knew that it could cause an issue, But i was ill informed on the whole situation.
Why was a ticket to AlohaPOS never opened? (I'm assuming one wasn't).
I asked for help and they told me to check if it was running on the back office server, which at the time it wasn't. it only runs 2 at a refresh because its restarting
So is it fixed now? did your boss uninstall Aloha and reinstall to get rid of the double install?
Im not exactly sure if it's fixed. I'm still the one doing all the work on it. he just got a me a list of things that have been known to fix it and I have made all of the changes.
Tomorrow we will be able to test before the store opens . -
So it was not a windows issue - It was the software running two or more instances of our mobile software at one time after a refresh.
What was happening was the software would restart, then try to open 2 or more at the same time causing the system to error and restart to try to clear it it's self.
Made changes to the settings in the system config files and have tested with 3 different refreshes today - It has not rebooted once.
Thanks for all the help with figuring this one out. I think i've gained a wealth of knowledge from this thread. -
@WrCombs said in Windows 10 Reboots:
So it was not a windows issue - It was the software running two or more instances of our mobile software at one time after a refresh.
What was happening was the software would restart, then try to open 2 or more at the same time causing the system to error and restart to try to clear it it's self.
Made changes to the settings in the system config files and have tested with 3 different refreshes today - It has not rebooted once.
Thanks for all the help with figuring this one out. I think i've gained a wealth of knowledge from this thread.to expand on this - the back office becomes one of the "terminals" as an interface. When the refresh was happening the "back office terminal" was the culprit.
