Sage 100

My question:

Why do some sites require spawn tasks to be checked - or users receive the "Connection Failure".

Other sites do not require spawn tasks to be checked - and do not generate a "Connection Failure."

I know the fix/workaround; however, most IT people press on this issue by asking why this option (spawn tasks) is or isn't required.

I'm unsure that Sage knows why spawn tasks may (or may not) be required.

Here are some key notes I took while on a call with Sage support a month or two ago regarding another issue.  

• KeepAlives should be unchecked.  Sage 100 doesn't benefit from this ProvideX feature.
• Re-Connect should be set to None. 
• Spawn tasks from application server under User Maintenance should only be checked for problem users, not all users.  See this KB, Spawn Tasks Information (sage.com).  If this is unchecked, the pvxwin32.exe process should be added as a firewall exception because it will use dynamic ports.
• If using the C/S ODBC driver, the pvxiosvr.exe process should be added as a firewall exception because it will use dynamic ports beyond the configured port (default is 20222).

My question:

Why do some sites require spawn tasks to be checked - or users receive the "Connection Failure".

Other sites do not require spawn tasks to be checked - and do not generate a "Connection Failure."

I know the fix/workaround; however, most IT people press on this issue by asking why this option (spawn tasks) is or isn't required.

I'm unsure that Sage knows why spawn tasks may (or may not) be required.

Spawn tasks from application server under User Maintenance should only be checked for problem users, not all users.

I seem to run into all-or-nothing situations. Within User Maintenance - I need to either (a) check "spawn tasks" for all users or (b) I don't need it for anyone. I'm not sure why.

Here are some key notes I took while on a call with Sage support a month or two ago regarding another issue.  

• KeepAlives should be unchecked.  Sage 100 doesn't benefit from this ProvideX feature.
• Re-Connect should be set to None. 
• Spawn tasks from application server under User Maintenance should only be checked for problem users, not all users.  See this KB, Spawn Tasks Information (sage.com).  If this is unchecked, the pvxwin32.exe process should be added as a firewall exception because it will use dynamic ports.
• If using the C/S ODBC driver, the pvxiosvr.exe process should be added as a firewall exception because it will use dynamic ports beyond the configured port (default is 20222).

My question:

Why do some sites require spawn tasks to be checked - or users receive the "Connection Failure".

Other sites do not require spawn tasks to be checked - and do not generate a "Connection Failure."

I know the fix/workaround; however, most IT people press on this issue by asking why this option (spawn tasks) is or isn't required.

I'm unsure that Sage knows why spawn tasks may (or may not) be required.

Spawn tasks from application server under User Maintenance should only be checked for problem users, not all users.

I seem to run into all-or-nothing situations. Within User Maintenance - I need to either (a) check "spawn tasks" for all users or (b) I don't need it for anyone. I'm not sure why.

Here are some key notes I took while on a call with Sage support a month or two ago regarding another issue.  

• KeepAlives should be unchecked.  Sage 100 doesn't benefit from this ProvideX feature.
• Re-Connect should be set to None. 
• Spawn tasks from application server under User Maintenance should only be checked for problem users, not all users.  See this KB, Spawn Tasks Information (sage.com).  If this is unchecked, the pvxwin32.exe process should be added as a firewall exception because it will use dynamic ports.
• If using the C/S ODBC driver, the pvxiosvr.exe process should be added as a firewall exception because it will use dynamic ports beyond the configured port (default is 20222).

My question:

Why do some sites require spawn tasks to be checked - or users receive the "Connection Failure".

Other sites do not require spawn tasks to be checked - and do not generate a "Connection Failure."

I know the fix/workaround; however, most IT people press on this issue by asking why this option (spawn tasks) is or isn't required.

I'm unsure that Sage knows why spawn tasks may (or may not) be required.

Here are some key notes I took while on a call with Sage support a month or two ago regarding another issue.  

• KeepAlives should be unchecked.  Sage 100 doesn't benefit from this ProvideX feature.
• Re-Connect should be set to None. 
• Spawn tasks from application server under User Maintenance should only be checked for problem users, not all users.  See this KB, Spawn Tasks Information (sage.com).  If this is unchecked, the pvxwin32.exe process should be added as a firewall exception because it will use dynamic ports.
• If using the C/S ODBC driver, the pvxiosvr.exe process should be added as a firewall exception because it will use dynamic ports beyond the configured port (default is 20222).

My question:

Why do some sites require spawn tasks to be checked - or users receive the "Connection Failure".

Other sites do not require spawn tasks to be checked - and do not generate a "Connection Failure."

I know the fix/workaround; however, most IT people press on this issue by asking why this option (spawn tasks) is or isn't required.

I'm unsure that Sage knows why spawn tasks may (or may not) be required.