Sage 100

I have a customer that I upgraded about a monthly ago to Sage 100 2023 Advanced. Their system has been running trouble free for the last month. They shut down their old server which appears to have also been hosting an on-prem exchange server. This caused paperless to suddenly stop sending emails. They caught this and with the help of IT they updated the SMTP info. Everything seemed fine.

Then today - which they think is about two days after the old server was shut down - they receive - Connection failure to host: [TCP]server:port number:NODELAY;STREAM. It's a smaller 3 user site and both users were suddenly gettign this.

I am familiar with the usual suspects as outlined in the Sage KB.

What works here is to go into each user under user maintenance and on tab 2 - preferences - check off "Spawn Tasks from Application Server". When I do this the problem stops and the users can login to Sage. 

I have one other customer where I had to use this very same 'trick' ( which is what made me try it ).

My question - does anyone know specifically why Spawn Tasks from Application Server would have fixed this type of issue? This one has me curious because up until today they say they were working fine. I can't think of what might have caused it from shutting down the old server.

This also could have been some odd tweak that the IT folks made while shutting down their former server.

I've just never been able to figure exactly why this works and while Sage suggests trying the option there's nothing that says why it might work ( what problem is it overcoming?).

TIA

We most commonly get this with new users on an existing Advanced system.  Either everyone should use the Spawn Tasks option, or nobody should. 

(I don't know why).

Same experience. 

I was hoping that this customer suddenly needing to have the option set might unravel some of the mystery. Unfortunate, when we don't manage the network we also can't know 100% that some other configuration change wasn't made that might have caused the issue.

Carmen, is this what you're referring to:

Cannot create a new session with a large number of users

Attachment(s)

Cannot create a new session with a large number of users.pdf   81 KB 1 version

Original Message:
Sent: 07-16-2023 16:22
From: Carmen Cruz
Subject: Why would spawn tasks from server fix a suddenly appearing Connection failure to host: [TCP]server:port number:NODELAY;STREAM

Hi Wayne,

Have you tried sizing up the heap size to get past this message with DELAY STREAM: SPAWN TASKS. When you raise the heap size over, turning on the spawn task in Sage, your users are still allowed to work like they're all in a different line in a store. When you turn that switch on, they're all in the same line which slows down production just like it would, if you were in a store, waiting to pay for purchases.  Generally, I avoid turning on that switch because it can in fact cause more issues than resolve. 

	Carmen Cruz Sage Consultant carmen.cruz@compudata.com 215-969-1000 Ext. 279 www.compudata.com Work Smarter... Together
CompuData, Inc. • 325 Chestnut St, Ste 700 • Philadelphia • PA • 19106