MAS 200 fails to launch tasks once 34 tasks are running.

Posted on 2006-04-06
Last Modified: 2013-11-21
we are running MAS 200 version 3.x
some users connect to the server with RDP and launch MAS from there.  others are joined to the domain and launch MAS from their desktop.

the problem we are having happens when our total tasks reaches 34.  at that point, if we try to launch another task (open a module, or log into MAS), a MAS 90 Client / Server window shows minimized in the taskbar, and nothing else happens.  i close that window, have another user close out of a module in order to bring the total tasks below 34, and then everything works fine... we can open tasks just fine as long at the total doesn't reach 34.

we are under our total user limit.  we have 20 licenses and this problem happens when we are under that limit.

i found a similar problem at the Sage Software forum.  it was suggested to switch from using MAS as a service to an application.  that did not resolve the problem for the person who posted the problem.

does anyone have other suggestions?
Question by:zephyr_hex
    1 Comment
    LVL 42

    Accepted Solution

    i have found the solution.

    When launching a new task in MAS 200 (e.g. Sales Order Entry, Customer Inquiry, Invoice Data Entry, Purchase Order entry, etc.), a blank, white screen appears rather than the task and MAS 200 will appear unresponsive. In addition, various error messages may appear at the server, including "Pvxwin32.exe DLL Initialization Error". Windows NT/2000/2003 may be limiting the number of processes that can run simultaneously. This issue occurs when a large number of users are running MAS 200 concurrently.

    By default Windows NT/2000/2003 systems are optimized for desktop applications over services. This means that more instances of a Windows program can opened as a desktop application than as a service. This issue surfaces frequently when the MAS 200 Host is configured to run as a service and there are at least 50 - 75 pvxwin32.exe tasks running at the same time.

    If your system is optimized to run more instances of desktop applications over services, which is the Windows NT/2000/2003 default, simply switching the MAS 200 Host to run as a desktop application from a service will, in all likelihood, instantly allow you to open 125 - 300 concurrent pvxwin32.exe tasks. In most cases this is all that will be needed to resolve this issue. It is highly recommended you attempt this solution before attempting to edit the Windows registry as detailed later in this document.

    Switching the MAS 200 Host from a Service to a Desktop Application

    1. Go to the Services applet and stop the "MAS90cs Host 10000" service. If the Port ID in the description is a number other than 10000 make a note of the number.
    2. Change the service Startup type from "Automatic" to "Manual". This is the reverse of the process detailed in the "Configuring the Service" section of the MAS 200 Installation Guides.
    3. Create a shortcut from ...\Mas90\Home\Host.exe to the desktop by right clicking on Host.exe and choosing "Send To" then "Desktop (Create Shortcut)". If the Port ID from Step 1 was not 10000, modify the properties of the shortcut that's now located on the desktop. In the properties, add a space and the correct Port ID to the end of the "Target Path":

    Example 1: D:\Apps\Mas90\Home\Host.exe 9500
    Example 2: "C:\Program Files\Best\Mas90\Home\Host.exe" 9999

    Notice in Example 2 that when a directory path contains spaces such as "Program Files", the entire path up to the filename must be quoted.

    4. A user account that is a member of the Administrators or Domain Administrators group must now always be logged on to the server, directly at the server, and then start the Host program. MAS 200 for SQL requires that the original account running the Host service always be logged on the server's desktop.

    General Information on the Registry Modification

    The following section provides information on the registry modifications needed to allow a greater number of processes to run simultaneously in Windows NT/2000/2003. This procedure is not recommended unless you must run the Host as a service or you are already running the Host as a desktop application and still need to increase the number of pvxwin32.exe tasks. Perform this procedure on the server where the MAS 200 Host resides.

    Warning: Modifying the registry incorrectly may cause serious damage to your system and require reinstallation of the operating system. Best cannot guarantee that you can solve problems that result from modifying the registry incorrectly. Prior to modifying the registry, perform a backup of the registry by creating an Emergency Repair Disk (ERD) and performing a full system backup or at least a backup of the Windows system state.

    This registry modification affects all programs that run on the server along with MAS 200. Some applications will be incompatible with certain values entered for the registry edit. Specifically, Backup Exec and Windows Task Scheduler have proven to be incompatible with the maximum value of 8192 assigned to the services heap value. It is your responsibility to verify that all your desktop applications and services start and run correctly with the registry changes.

    Note: The process limitation issue can usually be corrected by modifying a value in a string located in the following registry key:

    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\SubSystems\Windows

    This parameter may appear in one of the following forms:

    SharedSection=1024, 3072 (Windows NT 4.0 default)
    SharedSection=1024, 3072, 512 (Windows 2000 default)
    SharedSection=1024, 3072, 512,512 (Windows 2000/2003 with Terminal Services)

    1. Value one (1024) defines the maximum size of the Windows system-wide heap. Do not modify value one (1024).
    2. Value two (3072) defines the heap size for desktop applications.
    3. Value three (512) defines the heap size for services.
    4. Value four (512) is the Terminal Services heap size (this value might not exist on all systems running Windows Terminal Services). Do not modify value four (512).

    The third value is not specified by default on Windows NT 4.0 and will use the number in the second value if there is no third value present. Some applications will modify the third value so it does not inherit the second value. Best Software does not recommend omitting the 3rd value if it is present at the start of the edit. The first and the fourth values should not be modified.

    Registry Modification to run the Host as a Service

    Try the following setting if only two or three values exist:

    Try the following setting if four values exist:

    Note that the third value is changed from the default (from 512 to 4096) (Windows 2000/2003) or added (Windows NT 4.0). This is offered as a starting point for "tuning" the third value to an optimal setting compatible with all programs running on the server. After rebooting the server, view the System log and Application log in the Windows Event Viewer and look for any error messages, especially those of services failing to start. . If some applications or services do not start up or run properly after editing the registry, try lowering the third value in 512k increments and rebooting the server until you find a combination that works with all your programs. If problems do not occur, and you still need more concurrent pvxwin32.exe tasks you can raise the third value by increments of 512k to a maximum value of 8192. The maximum value is not recommended.

    Veritas Backup Exec™ and Windows Task Scheduler and other programs and services are known to be incompatible with the maximum (8192) setting. It is also possible some programs and services will be incompatible or be adversely affected with a high setting less than 8192. As mentioned above, consider 4096 as the starting point for "tuning" the 3rd value to an optimal setting compatible with all programs running on the server. It is your responsibility to test and verify that all programs and services are functioning correctly after making the edit and rebooting the server.

    Note: If you are running Veritas Backup Exec™ and must run the Host as a service and cannot tune the third value optimally to be compatible with both applications, consider running MAS 200 and Backup Exec on separate servers. The Backup Exec™ software will be loaded on one server and Backup Exec™ remote agent software will be loaded on the server running MAS 200. Please consult Veritas or your hardware professional for more information. Best Customer Support Services cannot provide assistance in this area.

    Registry Modification to run the Host on the desktop

    If you are running the Host on the desktop generally a registry modification is not required. However, if you are still running into the process limitation issue, consider the following:

    Try the following setting if only two or three values exist:

    Try the following setting if four values exist:

    Note that the second value is changed from the default of 3072 to 8192 (for Windows NT 4.0, Windows 2000, and Windows 2003) and that the third value is set to 512 (for Windows NT 4.0 as the third value is already 512 by default on Windows 2000/2003). This is offered as a starting point for "tuning" the second value to an optimal setting compatible with all programs running on the server. View the System log and Application log in the Event Viewer after rebooting the server to look for error messages, especially those of services failing to start. Also look for visual error messages on the screen. Also verify that all of your applications that run on the server continue to run normally.

    Currently there are no reports of applications or services that are incompatible with the second value set to the maximum 8192. If any applications or services do not start up or run properly as a result of changing the entry, the second value can be lowered in 512k increments. The valid range of vales for the 2nd number is between 3072 and 8192. It is your responsibility to test and verify that all programs and services are functioning correctly after making the edit and rebooting the server.


    Featured Post

    What Security Threats Are You Missing?

    Enhance your security with threat intelligence from the web. Get trending threat insights on hackers, exploits, and suspicious IP addresses delivered to your inbox with our free Cyber Daily.

    Join & Write a Comment

    Welcome to my series of short tips on migrations. Whilst based on Microsoft migrations the same principles can be applied to any type of migration. My first tip is around source server preparation. No migration is an easy migration, there is a…
    Sometimes a user will call me frantically, explaining that something has gone wrong and they have tried everything (read - they have messed it up more and now need someone to clean up) and it still does no good, can I help them?!  Usually the standa…
    It is a freely distributed piece of software for such tasks as photo retouching, image composition and image authoring. It works on many operating systems, in many languages.
    Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.

    734 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    21 Experts available now in Live!

    Get 1:1 Help Now