Subject: UniVerse and Backup Exec
Gwen, We found the following Techtip (#1299) from Epicor to help with Backup Exec and Universe. It has to do with a registry setting to allow Universe and Backup Exec to play nice on a Windows NT server, the same setting might work for a Windows 2000 Server. I don't know if it will help with your problem or not. Let me know off list how you like running Universe 10 and Windows 2000, we are planning the same upgrade later this year. HTH, Steve Moore Amerex Corporation [EMAIL PROTECTED] Tech Tip #: 1299SDG Product: Ardent Date Added: 2/12/01 Version: 5.1 Date Changed: 6/5/01 Module: UniData Option: Summary: Telnet sessions disconnecting/ Unable to connect Detail: telnet sessions start dropping off when you get close to the user limit: unidata admin on the server shows that the user session is still ongoing and has to be killed manually Applies to: Windows NT servers running UniData and UniVerse. Problem: (1) Occurrences of the message: "User32.dll" or "Kernal32.dll failure" at the server. This will cause the process that generated the error message to hang until an operator intervenes at the NT console, resulting in client computers that fail to operate correctly with no apparent cause, (2) The NT server slows to a crawl with no other indications of a problem, or (3) There is a problem logging in users to UniData or UniVerse up to the fully licensed limit. (4) Telnet sessions start dropping off when you get close to the user limit: (5) Unidata admin on the server shows that the user session is still ongoing and has to be killed manually (6) TNET.DLL failed to initialize (7) TNET CLIENT/SITE licensing setup failed Cause: Services consume a small amount of memory each time they are started. When multiple services log on as the same account the system may not have enough memory to create a new desktop heap (pre-allocated memory) for the service being started. Microsoft has confirmed this to be a problem in Windows NT version 4.0. UniData and UniVerse are then unable to allocate memory for new sessions. Background: This problem was brought to our attention on systems running Seagate Backup Software. Seagate makes a change to a registry setting to get around User32.dll errors in Windows NT (per Seagate's attached Tech Note). Seagate obtained this information from Microsoft's Knowledge Base Article Q142676 (also attached). Ardent tech support believes that Microsoft's solution causes Kernal32.dll errors on servers running UniData and/or UniVerse, so they recommend a different solution. The poor RDBMS performance and low number of users allowed to login is due to an insufficiently sized non-interactive heap. Increasing this setting has resulted in noticeably improved server performance. Solution: The following solutions should be tried one at a time. After each fix, check the server to see if the problem has been corrected. It is strongly recommended to NOT apply every step at one time. Make only the minimum changes necessary to correct the problem. Excessive registry modifications may cause conflicts in other areas that will be very difficult to troubleshoot. (1). Check the virtual memory setting, located in START | Settings | Control Panel | System. This opens the "System Properties" applet. Select the "Performance" tab. The Virtual Memory setting is displayed and can be changed from here. (2). Open the following registry key using REGEDIT or REGEDT32. HKEY_LOCAL_MACHINE/System/CurentControlSet/Control/SessionManager/SubSystem/ Windows The entire string will be similar to: %SystemRoot%\system32\csrss.exe ObjectDirectory=\Windows SharedSection=1024,3072 Windows=On SubSystemType=Windows ServerDll=basesrv,1 ServerDll=winsrv:UserServerDllInitialization,3 ServerDll=winsrv:ConServerDllInitialization,2 ProfileControl=Off MaxRequestThreads=16 Look for the sub-string: SharedSection=XXX,YYY,ZZZ XXX - is the size of the global heap in kilobytes. YYY- is the size of the interactive desktop (system wide) heap in kilobytes. ZZZ- is the size of the non-interactive (hidden) desktop heap in kilobytes. If ZZZ is increased then more objects can be created per desktop. This value is a Multi-String (edit it using Multi-String on the Edit menu). The default value says 1024,3072. This should be changed to: If the user is using SEAGATE change to 1024,3072,1024 If the user is not using SEAGATE change to 1024,3072,8192. NOTE: Microsoft's solution is to change ZZZ to 512. This occasionally results in Kernal32.dll errors. Epicor recommends setting ZZZ to 8192. Reboot to effect the change. (3). Delete RegistrySizeLimit from HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control (4). Set PagePoolSize to 0 at HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\SessionManager\Memory Management. (5). If the problem persists then try this step as a last resort. Open the registry key HKEY_LOCAL_MACHINE/System/CurrentControlSet/Services/Afd/Parameters and add 4 new keys. Each key should be of type REG_DWORD: Key Name Hex Value Decimal Value InitialLargeBufferCount 0x1e 30 IrpStackSize 0x8 8 LargeBufferSize 0x1000 4096 MediumBufferSize 0xbc0 3008 Reboot to effect the change. Epicor Software Corporation © 2000 All Rights Reserved. This message has been scanned for viruses by Webshield E500, Groupshield for Exchange, and McAfee Virus Enterprise
-- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users