Argus IT · Squirrel · Technical Reference
Rebooting the Squirrel Server — the Full Sequence
Skip a step and you lose room charge, credit cards, or the tablets.
⚠
Why this order matters A Squirrel server reboot takes several dependent processes offline. Done out of order, you can end up without: the ability to charge to guest rooms through Squirrel, credit cards via Moneris, or the tablets.
✋
If Squirrel Support wants to reboot the server That's okay — but tell them a few things need to be done around it, and watch that they do all of them. Squirrel Support has missed steps many times, and they will not care about integration with your PMS. You own this checklist, not them.
🔄 The sequence
1 Turn off the Opera Interface for Squirrel. If this isn't done, everything after this point is wasted effort — to repeat: you will have wasted your time. See Opera Interface Documentation and Troubleshooting for how to turn an interface off and restart it. 2 Turn off the Tablet VMs. Use the procedure in Restart Tablet VMs for Squirrel Mobility (KB-170005) — but turn them off rather than restarting. Only once Squirrel has completely restarted do you restart VMware and start each VM. 3 Restart the Squirrel server. The Manteo server can take up to 5 minutes. Once you have access: confirm the Squirrel Service is started — if Back Office loads, you're good; if not, wait a few minutes and retry before calling Squirrel Support. Then restart all Squirrel terminals. 4 Start the Tablet VMs — same documentation as step 2. 5 Start the Eigen Gateway (Eldorado only) — see Moneris Gateway Restart (KB-170004). 6 Start the Squirrel Opera Interface back up.
✅ After the sequence
Verify all three: a room charge posts through to Opera, a Moneris credit card transaction goes through, and the tablets reconnect (exit and restart VNC on each tablet — they need to be reconnected to their VMs after a VM restart).
ArgusIT KB# 170002 · Tags: squirrel · interface · opera · tablet · vm · mobility · post
|
