Sage 100

New WIN 10 WS, v2018 ADV. Second time I have received the error message. I found a KB that suggested rebooting the server. I did and problem resolved. Now it is back. Hard to believe that server (v2012) that has been running for a year now is an issue. Rebooted the server and connection works. Thoughts?

Bad NIC, cable or port on the switch?

But why would rebooting the SERVER fix that?

Only in the World of Windows is reboot a 'Magical Fix"".

I hope you are being sarcastic. You can reboot the server all day and if the workstation NIC, cable or the port in the switch is bad a server reboot isn't going to fix it.

yes of course, but it does amaze me how many times a reboot is the fix. sigh...

@JeffSchwenk The server reboot COULD reset the port on the switch, so maybe that is why the server reboot fixed it. It could just be a flaky NIC and on workstation and when the workstation re-connects to the server everything is OK... for a while.

If it is only one computer that this is happening to then it seems that the issue would be occuring somewhere between the workstation and the server... so workstation, NIC, cable, switch.

Only one because that is the only one V2018 is installed in. Will keep my eyes peeled. Thanks

Did you disable keep alives when setting up the service?

Have you seen this?

@DougHiggs - Yes, I did see that KB, the user running the service is the same user running the v2016 service and was set up according @AlnoorCassim ""how to set up a service user"" post from back in the day. The port is using 9600 for v2018. PEP is shut off. I didn't do the command stuff. I found another KB about rebooting the server for low resources. I am running the CS ODBC so maybe the memory leak is an issue now. I need to check to see if I installed the CS ODBC program that came with v2018. I did tell the HW tech to make sure the NIC doesn't go to sleep so maybe I need to recheck that. And @DougHiggs - Me be sarcastic???? Really???

Who is @AlnoorCassim ? What does he know?

He is just a singer in a rock and roll band.....

OK, The story gets more interesting. Some additional details/observations. This issue pops up once a week on Thursday night. I run a five person PR in v2018 ADV at that time. And EVERY week, this error message appears immediately AFTER I print the PR checks. Tonight I realize the coincidence. I finish the PR cycle in STD mode, then reboot the server. Run the PR a second time. Import the hours, run the PR calc, switch to manual taxes and change all five employee's state taxes to whole dollar amounts (in IA, the state does not want you to report cents, in prior versions of PR you could elect whole dollar state deduction, in 2018 you can't). Rerun the calc and print the audit report. Print the tax summary. Print the checks to a PDF. The error appears again before I can print the check register. I do NOT have the v2018 client installed on another workstation or server because I am avoiding the Crystal reports issue (uninstall all prior versions & drop the .config file in the home directory of prior versions). So I don't know if this would happen on another workstation. As noted, I don't have the connection issue in STD mode. It happens with the CS ODBC on or off for the user. It occurs whether I print on paper or to a PDF driver. I have cycled through various scenarios five times tonight. It blows every time immediately after check printing.

Disconnected from the Azure cloud server that calculates the payroll taxes?

I was wondering about that, So I cycled through to the check register update in STD then went back via ADV, was able to reprint checks before the connection broke again. However, not sure if this test as I don't recall if the tax calc happens locally in STD.

Hey @MoiraGoggin - Was 90M able to get a Sage tech support hot line directly to a higher level support person? Might have to use it on this one.....

Have you checked, or rather unchecked the spawn tasks from server? I believe we had a similar issue. Something new on the v2018 installs.

To spawn or not to spawn, that is the question. @AlnoorCassim ?? Mine is on. Will try the alternative.