Solved

The server was unable to allocate a work item 53 times in the last 60 seconds.

Posted on 1997-12-04
6
7,503 Views
1 Endorsement
Last Modified: 2013-12-23
NT 4 workstation with a file share. I am recieving a lot "The server was unable to allocate a work item x times in the last 60 seconds." messages in the system event log. When the error occurs and users trying to access the share hang briefly.

I initially thought that this was a workstation vs server limitation but I've been unable to reproduce the error by trying to diliberately overloading another NT workstation.

Any ideas ?

Brian V
1
Comment
Question by:brianv
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
6 Comments
 
LVL 1

Expert Comment

by:mert
ID: 1569454
The problem may be this:

The default system pages are not enough for the server due to
many pages being locked down during transmission.
 
For resolution try this:
 
To work around this problem, increase the number of system pages for the server in the registry
 
1. Start Registry Editor (REGEDT32.EXE) and locate the following Registry subkey in the HKEY_LOCAL_MACHINE subtree:
 
\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management
 
2. Select SystemPages. From the Edit menu, select DWORD.
 
3. For Data, enter 20000 (Decimal).
 
4. Click OK and quit Registry Editor.
 
5. Shut down and restart Windows NT.

0
 

Author Comment

by:brianv
ID: 1569455
Tried it at 20,000 Dword as suggested...errors are still occuring. I'll set it higher and update you tomorrow. For what it's worth the errors seem to be generated when a remote user tries to compile c++ code that exists on the workstations share.

When this happens a single user can have over 40 opens.

Brian V
0
 

Author Comment

by:brianv
ID: 1569456
Bumped it to 40,000 DWord and the errors continue.

Any other suggestions

Brian V
0
Efficient way to get backups off site to Azure

This user guide provides instructions on how to deploy and configure both a StoneFly Scale Out NAS Enterprise Cloud Drive virtual machine and Veeam Cloud Connect in the Microsoft Azure Cloud.

 
LVL 2

Accepted Solution

by:
gantriis earned 300 total points
ID: 1569457
Hi Brian.

You might like to increase the value of MaxWorkItems to 64 which is the upper limit for a Windows NT Workstation.

So, fire up RegEdt32 once again and enter the value

MaxWorkItems: REG_DWORD: 64 (decimal)

under the key

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters

I believe that the default value is 32 on a  workstation and 512 on a server so the change should double the max value.

And while you are at it you might also like to adjust the InitWorkItems value under the same key. Add this as a DWORD value if it does not already exist. The max value you can specify for this one is 512. (Have a look at the Windows NT 4.0 resource kit file regentry.hlp for more information about these parameters.) However,  I suggest that you start by only adding the MaxWorkItems value.

Let me know how the workstation is doing after that change and a reboot.

Cheers
Gantriis
0
 

Author Comment

by:brianv
ID: 1569458
Thanks, the max workitems appears to have fixed it !!!

And more importantly I wasn't aware of regentry.hlp (great tool)

Thanks again

Brian V

0
 

Expert Comment

by:chuckRichards
ID: 1569459
Thanks a lot, gentriis, for your advice.  I will be trying it to see if it solves my problem.

For the reference of others that may have a similar problem, my symptoms have been:

Running NT Workstation 4.0 ServicePack 3 on a Dell...
Creating a filesystem share
(let's say, \\COMPUTER\share at C:\directory)
and redirecting a drive on the same \\COMPUTER
(let's say, X:\)
to access that share.
Most of the time things work fine, but when there is a large build with MS DevStudio of a lot of small source files that are contained within X:, delays happen and sometimes the X:\ stops working for any application (EXPLORER.EXE says that the computer is not accessible).
Subsequent investigation of the EventQueue shows a series of Srv Event 2021 ("The server was unable to allocate a work item (#) times in the last 60 seconds"), with some Rdr Event 3013 ("The redirector has timed out a request to COMPUTER").
The problem can be temporarily solved by running ControlPanel->Server and DisconnectingAll, but will eventually re-occur.

0

Featured Post

PeopleSoft Has Never Been Easier

PeopleSoft Adoption Made Smooth & Simple!

On-The-Job Training Is made Intuitive & Easy With WalkMe's On-Screen Guidance Tool.  Claim Your Free WalkMe Account Now

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

We recently endured a series of broadcast storms that caused our ISP to shut us down for brief periods of time. After going through a multitude of tests, we determined that the issue was related to Intel NIC drivers on some new HP desktop computers …
An article on effective troubleshooting
Michael from AdRem Software explains how to view the most utilized and worst performing nodes in your network, by accessing the Top Charts view in NetCrunch network monitor (https://www.adremsoft.com/). Top Charts is a view in which you can set seve…
Monitoring a network: why having a policy is the best policy? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the enormous benefits of having a policy-based approach when monitoring medium and large networks. Software utilized in this v…

717 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