Dear Mr. Alfke, Thank you for the information! I am in the process of printing your reply out and read it with very close scrutiny.
I am deeply appreciative!! (An good luck to your Calgary Flames!) Grant W. Boice, Jr. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, March 01, 2004 2:17 PM To: [EMAIL PROTECTED] Subject: RE: Need help in solving a UniRPC service error!!!! UniData 5.1 and Backup Exec don't always coexist well (the word I got from IBM that seemed very apt was 'inconsistent'). We had clients that ran for years without issue and others that couldn't run for hours without issue. The problem seems to be mostly in the 'noninteractive desktop heap'. UD 6.0 should solve this issue. Here is an excerpt from a support call that I have. There was also a nice write-up done recently that should be in the archives (www.indexinfocus.com). There was also an article on the veritas website that explained the problem quite well. Of course, if possible we remove the backup exec software from the server and back it up 'remotely'. hth -- Colin Alfke Calgary, Alberta Canada "Just because something isn't broken doesn't mean that you can't fix it" Stu Pickles user32.dll errors are almost always directly related to the size of the noninteractive desktop heap. This paramater can be found at HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Control Session Manager SubSystems Windows it usually looks like: %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 where the sharedsection of 1024,3072 is set with the third value missing, which defaults to the second value. In many instances where we see user32.dll errors the third value is set to 512. This is usually fixed by removing the third value or setting the third value to 8192. This increases the amount of heap available to single desktops. So say a single process is using a desktop and requires a great deal of strings or hooks to do its job, if it runs out of heap space on its current desktop a user32.dll error can result. now the total amount of heap space available is 48 meg for all desktops on a system. So if a large number of desktops are created a user32.dll error can occur as well, which is what microsoft usually see's as a problem. With Windows being so gui based running out of desktops is usually the cause so they usually recommend the number be set to 512. though it is set to 3072 (or nothing) by default. We are in a unique position because UniData is not a gui app! What this means is we need more heap space for single desktops to work correctly, consequently increasing the third value tends to be the fix. Though in a few limited cases we have seen lowering the third value to 128 to be the fix. There is another possibility as well, this may be somehow related to a security issue. If a process is launched that does not have proper security access to the window station and the desktop associated with it. Perhaps they have made some changes to the security structure on this machine? I'll also mention, Veritas backup Exec is prone to accelerating these errors on a machine as well. >-----Original Message----- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] >Sent: Monday, March 01, 2004 11:52 AM >To: [EMAIL PROTECTED] >Subject: Need help in solving a UniRPC service error!!!! >Importance: High > > >Hello Group! > > I am in desperate need of some help in solving an UniData >UniRPC error. The problem started last week when we started >getting the following errors randomly (not necessarily in this order): > > * RPC error 81015 > * RPC call timeout > * RPC server is too busy to complete this operation. > >There seems to be no pattern to this with the exception of >that it is happening during the night some time, and every >morning I have to re-boot the server. We can not isolate >what is causing the problem. We were told that it might be >are backup software program, but we can not prove or disprove this. > >Can anyone out there give me any solutions to the problems? It >is a software problem? Hardware? Networking? Me? >(I'm tired of walking in every morning getting my "head bitten off".) > >We are using UniData 5.1, which is running on Windows NT 4.0, >SP 6. Veritas Backup Exec Version 8.6 is the backup software >we are using. > >Any help will be appreciated!!! > >Sincerely, > >Grant W. Boice, Jr. >-- >u2-users mailing list >[EMAIL PROTECTED] >http://www.oliver.com/mailman/listinfo/u2-users > -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
