Reformatted message
Mas200 4.5.07
Terminal Server on Server 2008
Error Scenario
Windows XP client
Windows Terminal Server login xx-10
Mas login mary The user gets a "connection failure to host...NODELAY;STREAM" etc when posting an invoice while logged into our terminal server.
No Error Scenario
Windows XP client
Windows Terminal Server login xx-20
Mas login mary
No error when posting an invoice.
We only have one Terminal Server
The error seems tied to the Windows user, since the
same MAS user is used under the two windows logins.
Anyone have additional pieces of the puzzle to offer??
Tried creating a new terminal server user.
Still errors out, when connecting from one specific pc, but
only during the posting process. All other MAS duties
performing fine.
In the error connection failur to host:[tcp]ans-mas-data;50121;NODELAY;STREAM;
Anyone know what the 50121 inidicates?? Port ##, Process ID
Thanks
Today we replaced the pc with a new pc.
The posting problem has gone away.
Still connecting to the same terminal server.
Still using the same MAS user.
Since the point of processing (Terminal Server to MAS Server),
has not changed, the remaining element is the Remote Desktop,
and components delivering the Terminal Server session to the
client desktop.
I believe this error was tied to the version of Remote Desktop.
Going to test the old computer in our development environment.
ps. Happy User
Lots of info in the knowledgebase on this error.
Typically, turning on the "spawn tasks" option in User Maintenance resolves this error.
Think I found one of the threads you may be referring.
Couple questions.
Impact of Spawn Tasks settings?
Does MAS 2013 still carry this issue?
*Community Hub is the new name for Sage City