Sage 100

We have a MAS200 client that is running 4.4.06 and is getting the connection failure to host message. They have about 20 to 30 users in the system at once. We have checked the spawn flag as but then when trying to run a crystal report they get the ""unable to spawn a new session. The command line required for the server process is too long. Anyone seen this?

This is frustrating,. I found a entry on Sage with the exact error but it won't pull up. it is ID 495923. I wonder is the database is offline :(

Running as Service or App? In User Maintenance have you unchecked the spawn flag?

Where is Alnoor when you need him? Speaking of Alnoor, has anyone seen or heard from him lately?

I emailed him a couple days ago and haven't heard from him. @AlnoorCassim Where are you!!

Resolution Details TITLE : ""Unable to spawn new session"" or ""Unable to spawn a new session. The command line required for the server process is too long"" when printing Crystal reports in Sage MAS 200 DETAILS : ""Unable to spawn new session"" or ""Unable to spawn a new session. The command line required for the server process is too long"" when printing Crystal reports in Sage MAS 200 Entry Type: Informational Product: Sage MAS 200 ERP Application: Library Master Version Reported: 4.00 Subject: ""Unable to spawn new session"" or ""Unable to spawn a new session. The command line required for the server process is too long"" when printing Crystal reports in Sage MAS 200. Possible Resolutions: The user may not have sufficient permissions to the ..\Mas90 folder. Grant the user sufficient permissions to run reports. For more information, see related article below. If the error still occurs, clear the Spawn Session from Application Server check box. Note: Do not perform this step if the check box was selected to resolve connection issues, for example ""Connection failure to host..."" (see related article below). Expand Modules, Library Master, and Main. Double-click User Maintenance. Select the user ID. Click the Preferences tab. Clear the Spawn Session from Application Server check box. Click Accept. Repeat for each affected user. If the error still occurs, and the report is on the Custom Reports menu, the path and file name may be too long. Delete the report from the Custom Menu. Rename the file to a shorter name. Note: Try 55 characters or less for the entire path and file name. Some experimentation may be required. The exact length that causes the error is still being researched. Add the report back to the Custom Menu. Related Articles: #spawn #crystal

I've run across this. I think the KB article was the solution. Also in the past we've had extreme issues running MAS200 as a service for sites over some high number of users (lets call it 25).

Too bad this is still an issue. Some time back, Alnoor published a hack for running MAS as a service with a large number of users. Which begs two questions, why is it still an issue and why do you have to do a registry hack to fix it????

I have always had pretty good luck with a lot of users. @JeffSchwenk , Are you refering to SS-3003. That is a fix to increase the Memory heap size for the services. I call it a configuration instead of a ""Hack"" :)

Not sure. I just have Alnoor's article in my technical file.

@JimWoodhead - get this info for me. Use these steps: 1. DFDM Sy_menu.m4t change the Key to KMENUOTF 2. Type in ModuleCode + 000 + name of custom report e.g. type in: S/O001Sales by Territory (or a partial report name is fine) 3. When you find the record, take the value of what's in the TaskKey and copy into the clipboard. 4. Now DFDM Sy_Task and paste in the Key field at bottom paste in taskKey 5. Once record appears, copy what's in Field 11 to the clipboard and paste back into your reply here

Just had this last week. Had client enable the Spawn ckbox in User Maint for the 1 user who was having the issue - and that appeared to resolve it.

Brett - In this case, Spawn Tasks is already checked and error occurs when running custom Crystal report off the menu.