No more IRP stack locations

24/11/2003 - 09:18 por Astazou | Informe spam
Saludos.

Hace ya unos meses lancé esta pregunta y todo lo que recibí de
respuesta fue que tenía algo del ordenador defectuoso (memoria,
VGA...).

Bien, ha pasado todo este tiempo y he cambiado uno por uno todos los
componentes que me dijeron que podían tener defectos.

Y me sigue dando el mismo problema. Se resetea solo cuando le da la
real gana, dandome este error. Hay veces que en 24 horas no me ocurre
nada, y otras en 2 horas se me cuelga 3 veces.

¿De verdad que no existe solución a esto?

Gracias y un saludo.
 

Leer las respuestas

#1 Antonio Amengual MSMVP
24/11/2003 - 09:25 | Informe spam
buscando en la KB de MS aparece esto, a ver si algo te sirve:

Changes in IRP Stack Size in Lanman Server
Applies To
This article was previously published under Q198386
IMPORTANT: This article contains information about modifying the
registry. Before you modify the registry, make sure to back it up and make
sure that you understand how to restore the registry if a problem occurs.
For information about how to back up, restore, and edit the registry, click
the following article number to view the article in the Microsoft Knowledge
Base:
256986 Description of the Microsoft Windows Registry

SYMPTOMS
When you access shares on a computer running Windows NT Server from a
Windows NT client and the IRPstackSize parameter is set too low on the
server, you may receive the following error message:



Not enough server storage is available to process this command.
CAUSE
Depending on the hardware configuration of a specific computer, the
default value may not be large enough for the Srv service to properly
administer shared directories on some of the physical drives. You may see
one or both of the following event messages:

Event ID: 2011 Source: Srv
The server's configuration parameter "irpstacksize" is too small for
the server to use a local device. Please increase the value of this
parameter.

Event ID: 0
Source SRV
Description: Description for Event ID 0 could not be found. It
contains the insertion string \device\LanManServer

You may receive one of the above error message when a Windows NT
client tries to access certain shared directories on such a server.

When a Windows for Workgroups client tries to access the same shared
directories, the following message will be generated:



Path not found.
RESOLUTION
To resolve this problem, obtain the latest service pack for Windows NT
4.0 or Windows NT Server 4.0, Terminal Server Edition or the individual
software update. For information on obtaining the latest service pack,
please go to:

a.. http://www.microsoft.com/windows/servicepacks/ -or-


b.. 152734 how to obtain the latest windows nt 4.0 service pack
For information on obtaining the individual software update, contact
Microsoft Product Support Services. For a complete list of Microsoft Product
Support Services phone numbers and information on support costs, please go
to the following address on the World Wide Web:

http://support.microsoft.com/defaul...p&FR=1



Service Pack (SP) 5 sets a minimum allowed of 7. It ignores all
smaller values, and sets a default of 7 if none is specified.

SP6 sets a minimum allowed of 7. It ignores all smaller values and
sets a default of 11 if none is specified.
WORKAROUND
To work around this problem, modify the registry by using the
following information.

WARNING: If you use Registry Editor incorrectly, you may cause serious
problems that may require you to reinstall your operating system. Microsoft
cannot guarantee that you can solve problems that result from using Registry
Editor incorrectly. Use Registry Editor at your own risk.


The registry value IRPstackSize, which may be listed at

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer
\Parameters

defaults to 0x4 if the value is not explicitly present. Valid values
range from 0x1 to 0xC (1 to 12).

To increase the value of the parameter when it is not already present,
go to the key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services
\LanmanServer\Parameters

NOTE: The above registry key is one path; it has been wrapped for
readability. For the IRPStackSize change to take effect, the Server has to
be rebooted.

The value of IRPStackSize defaults to 0x4 if it is not explicitly
present. If the key is not present, click Add Value in Registry Editor. The
Value Name should be IRPStackSize and the Data Type is REG_DWORD.
STATUS
Microsoft has confirmed that this is a problem in Windows NT 4.0 and
Windows NT Server 4.0, Terminal Server Edition. This problem was first
corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0,
Terminal Server Edition Service Pack 4.
The information in this article applies to:
a.. Microsoft Windows NT Server 4.0 Terminal Server Edition
b.. Microsoft Windows NT Server 4.0
Last Reviewed: 10/14/2002 (1.0)
Keywords: kbprb KB198386




Contact Us


© 2003 Microsoft

Bienvenidos al sitio de MVP de Microsoft
http://mvp.support.microsoft.com/

Recuerda: Una Consulta, Un Foro:


news://msnews.microsoft.com/microso...lic.es.ie6
news://msnews.microsoft.com/microso....windowsxp
news://msnews.microsoft.com/microso...ookexpress
news://msnews.microsoft.com/microso...p.hardware
news://msnews.microsoft.com/microso....seguridad
news://msnews.microsoft.com/microso...nstalacion
news://msnews.microsoft.com/microso...licaciones

Este mensaje se proporciona "como está" sin garantías de ninguna clase, y no
otorga ningún derecho.

This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.




XP Pro-2600-limpia+SP1

por favor
respuestas al grupo; asi nos beneficiamos todos
no se responde personalmente

saludos

Antonio
ms mvp windowsxp

"Astazou" wrote in message
news:
Saludos.

Hace ya unos meses lancé esta pregunta y todo lo que recibí de
respuesta fue que tenía algo del ordenador defectuoso (memoria,
VGA...).

Bien, ha pasado todo este tiempo y he cambiado uno por uno todos los
componentes que me dijeron que podían tener defectos.

Y me sigue dando el mismo problema. Se resetea solo cuando le da la
real gana, dandome este error. Hay veces que en 24 horas no me ocurre
nada, y otras en 2 horas se me cuelga 3 veces.

¿De verdad que no existe solución a esto?

Gracias y un saludo.

Preguntas similares