2k3 event error SRV 2012

Good Day,



Windows 2003 Enterprise Server with SP1. This server has Exchange 2003 with
SP2 on it. This is a member server. All updates have been applied as of
April.



Out of the blue I started getting these errors, so far they have been once
in a while. So far I may get one to three and then they stop. Per the log
this may happen and I should not be worried about it but I am trying to
figure out what is causing the problem. I know the Nic is good and the
drivers are fairly up to date. Never had an issue before. I did what they
said and clicked on Words and I see the following numbers below and tried a
Google but nothing showing up that I can tell or read. If anybody has any
idea what this stuff means or how to read I would appreciate somebody
pointing me in the right direction.



Error below


Event Type: Warning

Event Source: Srv

Event Category: None

Event ID: 2012

Date: 4/25/2007

Time: 6:15:54 AM

User: N/A

Computer: HSMAIL

Description:

While transmitting or receiving data, the server encountered a network
error. Occassional errors are expected, but large amounts of these indicate
a possible error in your network configuration. The error status code is
contained within the returned data (formatted as Words) and may point you
towards the problem.



For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Data:

0000: 00040000 00540001 00000000 800007dc

0010: 00000000 c0000184 00000000 00000000

0020: 00000000 00000000 0000097a



Thanks

Adam Raff

Hello,

Thank you for using newsgroup!

First thing I recommend you is to optimize memory configuration on the
Server. Please refer to the following KBs:

How to optimize memory usage in Exchange Server 2003
http://support.microsoft.com/kb/815372/en-us
Use of the /3GB switch in Exchange Server 2003 on a Windows Server
2003-based system
http://support.microsoft.com/kb/823440/en-us

For 2012 event, this basically is an error that the network driver is
giving SRV on the send IRPs. Perhaps 3rd party network software that is
bound to the server. You can see this by checking the following registry
key:

HKLM\SYSTEM\CCS\Services\LanmanServer\Linkage
Bind : REG_MULTI_SZ

Please export all the registers under LanmanServer to a txt file, post the
file into newsgroup, so that we can perform further troubleshooting.

Thanks & Regards,

Mike Luo

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Mike,

Thanks for your help, attached you will find the txt file that you wanted

The memory was already configured so I do not think that is an issue. This
system has been running fine with out any issues for four years. This
problem just started to happen. I am not sure if it's hardware releated or
not. I know the drivers have been updated about a year ago and never gave
me an issue. The system is an HP Prolient Server DL380

During the April update I rebooted the server and the problem seemed to have
went away about a week later the problem came back.

Thank You
Adam Raff

"Mike Luo [MSFT]" <v-miluo@online.microsoft.com> wrote in message
news:aVG0Jj8hHHA.5272@TK2MSFTNGHUB02.phx.gbl...
> Hello,
>
> Thank you for using newsgroup!
>
> First thing I recommend you is to optimize memory configuration on the
> Server. Please refer to the following KBs:
>
> How to optimize memory usage in Exchange Server 2003
> http://support.microsoft.com/kb/815372/en-us
> Use of the /3GB switch in Exchange Server 2003 on a Windows Server
> 2003-based system
> http://support.microsoft.com/kb/823440/en-us
>
> For 2012 event, this basically is an error that the network driver is
> giving SRV on the send IRPs. Perhaps 3rd party network software that is
> bound to the server. You can see this by checking the following registry
> key:
>
> HKLM\SYSTEM\CCS\Services\LanmanServer\Linkage
> Bind : REG_MULTI_SZ
>
> Please export all the registers under LanmanServer to a txt file, post the
> file into newsgroup, so that we can perform further troubleshooting.
>
> Thanks & Regards,
>
> Mike Luo
>
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
>
> =====================================================
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>

Mike,

One other thing,

Can you please explain what is an IRPs. Never heard of them and I can not
find any thing about them.


"Adam Raff" <araff@newsgroup.nospam> wrote in message
news:uQbv3MAiHHA.960@TK2MSFTNGP03.phx.gbl...
> Mike,
>
> Thanks for your help, attached you will find the txt file that you wanted
>
> The memory was already configured so I do not think that is an issue.
> This system has been running fine with out any issues for four years.
> This problem just started to happen. I am not sure if it's hardware
> releated or not. I know the drivers have been updated about a year ago
> and never gave me an issue. The system is an HP Prolient Server DL380
>
> During the April update I rebooted the server and the problem seemed to
> have went away about a week later the problem came back.
>
> Thank You
> Adam Raff
>
> "Mike Luo [MSFT]" <v-miluo@online.microsoft.com> wrote in message
> news:aVG0Jj8hHHA.5272@TK2MSFTNGHUB02.phx.gbl...
>> Hello,
>>
>> Thank you for using newsgroup!
>>
>> First thing I recommend you is to optimize memory configuration on the
>> Server. Please refer to the following KBs:
>>
>> How to optimize memory usage in Exchange Server 2003
>> http://support.microsoft.com/kb/815372/en-us
>> Use of the /3GB switch in Exchange Server 2003 on a Windows Server
>> 2003-based system
>> http://support.microsoft.com/kb/823440/en-us
>>
>> For 2012 event, this basically is an error that the network driver is
>> giving SRV on the send IRPs. Perhaps 3rd party network software that is
>> bound to the server. You can see this by checking the following registry
>> key:
>>
>> HKLM\SYSTEM\CCS\Services\LanmanServer\Linkage
>> Bind : REG_MULTI_SZ
>>
>> Please export all the registers under LanmanServer to a txt file, post
>> the
>> file into newsgroup, so that we can perform further troubleshooting.
>>
>> Thanks & Regards,
>>
>> Mike Luo
>>
>> Microsoft Online Partner Support
>> Get Secure! - www.microsoft.com/security
>>
>> =====================================================
>> When responding to posts, please "Reply to Group" via your newsreader so
>> that others may learn and benefit from your issue.
>> =====================================================
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>
>
>

Hello,

Thank you for the update!

IRP means Initial Response Package. I am sorry for the unclarity!

I checked the register, that is fine. Based on my research, Occassional
errors are expected. If you didn¡¯t encounter network access issue on the
client, you may ignore this event.

Thanks & Regards,

Mike Luo

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

>
> IRP means Initial Response Package. I am sorry for the unclarity!
>

Not to add confusion, but as far as I know, IRP actually means "IO Request
Packet"
- IO's travel *down* the *IO stack* in the form of an IRP.
- The IRP will have a Major and Minor *codes* to describe the operation to
the drivers (for a device)
- Examples of operations would be open / close / read / write / control (and
many more...)

Furthermore, first thing I would check that you have the latest network
drivers for your NIC's.
If they are HP/OEM cards, check with HP for updated drivers (or firmware),
if you put additional cards in yourself, check with the manufacturer.

rgds,
Edwin.

Thanks for the explanation on what IRP means.



I spoke to HP and they do have a newer driver that what I have now but again
that doesn't make any sense as out of the blue I started getting these
errors. They are not all the time either; I would get them in the morning
perhaps four of them and then perhaps one or two after that. After talking
to HP they said that the network card seems fine on the server as I have no
hardware errors. The only other strange thing is that I get no errors on
Weekends at all. Friday night we shut down all PC and the like as we are a
small business. Could this error be from a bad nic on another PC trying to
connect to our Exchange server?



Thanks again for your help

Adam Raff


"Edwin vMierlo [MVP]" <EdwinvMierlo@discussions.microsoft.com> wrote in
message news:eeXbyzwiHHA.4552@TK2MSFTNGP04.phx.gbl...
>
>>
>> IRP means Initial Response Package. I am sorry for the unclarity!
>>
>
> Not to add confusion, but as far as I know, IRP actually means "IO Request
> Packet"
> - IO's travel *down* the *IO stack* in the form of an IRP.
> - The IRP will have a Major and Minor *codes* to describe the operation to
> the drivers (for a device)
> - Examples of operations would be open / close / read / write / control
> (and
> many more...)
>
> Furthermore, first thing I would check that you have the latest network
> drivers for your NIC's.
> If they are HP/OEM cards, check with HP for updated drivers (or firmware),
> if you put additional cards in yourself, check with the manufacturer.
>
> rgds,
> Edwin.
>
>

> I spoke to HP and they do have a newer driver that what I have now but
again
> that doesn't make any sense as out of the blue I started getting these
> errors.

Yes, I have seen many errors which seems to be "out of the blue", but in
fact it was a known bug in a driver, and suddenly the error condition
appeared because of a very small change in the environment. (to small to
notice... chaos theory, the butterfly effect)

> Could this error be from a bad nic on another PC trying to
> connect to our Exchange server?
>

yes, that could be too

still, I would start with drivers/firmware upgrade on your server.

Hello,

Well still having the issues, so I decided to relent and updated the Nic
driver to the latest today. Will have to see what happens. In the mean
time I am still looking around on the network to see if it's a computer
issue that is causing the problems. Does anybody know of a way that I can
see what system if it's a system could be causing this. Is there any clue
in the errors?

Any way thanks for the help
Adam Raff




"Edwin vMierlo [MVP]" <EdwinvMierlo@discussions.microsoft.com> wrote in
message news:OIY1YiziHHA.3452@TK2MSFTNGP04.phx.gbl...
>
>> I spoke to HP and they do have a newer driver that what I have now but
> again
>> that doesn't make any sense as out of the blue I started getting these
>> errors.
>
> Yes, I have seen many errors which seems to be "out of the blue", but in
> fact it was a known bug in a driver, and suddenly the error condition
> appeared because of a very small change in the environment. (to small to
> notice... chaos theory, the butterfly effect)
>
>> Could this error be from a bad nic on another PC trying to
>> connect to our Exchange server?
>>
>
> yes, that could be too
>
> still, I would start with drivers/firmware upgrade on your server.
>
>

I wanted to follow up with this email with some more info. As of today I am
still getting the errors after updateing the Nic driver to the latest. So
far when I turn off all the PC's within the company I get no errors as I
tried that during the week and told everybody that all systems need to be
shut down as we do on the weekends. No errors showed up in the morning.

If anybody knows a way to determine the offending Nic if there is one it
would be a great help without being a detective.

Thanks
Adam Raff


"Adam Raff" <araff@newsgroup.nospam> wrote in message
news:O8BvCxNjHHA.1216@TK2MSFTNGP03.phx.gbl...
> Hello,
>
> Well still having the issues, so I decided to relent and updated the Nic
> driver to the latest today. Will have to see what happens. In the mean
> time I am still looking around on the network to see if it's a computer
> issue that is causing the problems. Does anybody know of a way that I can
> see what system if it's a system could be causing this. Is there any clue
> in the errors?
>
> Any way thanks for the help
> Adam Raff
>
>
>
>
> "Edwin vMierlo [MVP]" <EdwinvMierlo@discussions.microsoft.com> wrote in
> message news:OIY1YiziHHA.3452@TK2MSFTNGP04.phx.gbl...
>>
>>> I spoke to HP and they do have a newer driver that what I have now but
>> again
>>> that doesn't make any sense as out of the blue I started getting these
>>> errors.
>>
>> Yes, I have seen many errors which seems to be "out of the blue", but in
>> fact it was a known bug in a driver, and suddenly the error condition
>> appeared because of a very small change in the environment. (to small to
>> notice... chaos theory, the butterfly effect)
>>
>>> Could this error be from a bad nic on another PC trying to
>>> connect to our Exchange server?
>>>
>>
>> yes, that could be too
>>
>> still, I would start with drivers/firmware upgrade on your server.
>>
>>
>
>

Hello Adam,

We can trace the problem computer, but this process is complex. Tracing the
problem needs to use serveral tools, and some tools are only for CSS
engineers, not published on the web. I recommend you contact CSS, so you
can receive a more qualified assistant.

Thanks & Regards,

Mike Luo

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Adam,

how many machines are we talking about ?

do what you did before, shutdown the client PC's (but now half of them, no
all)
-> problem exist, then the problem is with the PC's which are left on
-> problem does not exist

You can then repeat this excersies, and in a couple of days you might find
it (not 100% guaranteed)

however, you can only do this if you have a manageable amount of machines.



"Adam Raff" <araff@newsgroup.nospam> wrote in message
news:u0kh5h1jHHA.4516@TK2MSFTNGP03.phx.gbl...
> I wanted to follow up with this email with some more info. As of today I
am
> still getting the errors after updateing the Nic driver to the latest. So
> far when I turn off all the PC's within the company I get no errors as I
> tried that during the week and told everybody that all systems need to be
> shut down as we do on the weekends. No errors showed up in the morning.
>
> If anybody knows a way to determine the offending Nic if there is one it
> would be a great help without being a detective.
>
> Thanks
> Adam Raff
>
>
> "Adam Raff" <araff@newsgroup.nospam> wrote in message
> news:O8BvCxNjHHA.1216@TK2MSFTNGP03.phx.gbl...
> > Hello,
> >
> > Well still having the issues, so I decided to relent and updated the Nic
> > driver to the latest today. Will have to see what happens. In the mean
> > time I am still looking around on the network to see if it's a computer
> > issue that is causing the problems. Does anybody know of a way that I
can
> > see what system if it's a system could be causing this. Is there any
clue
> > in the errors?
> >
> > Any way thanks for the help
> > Adam Raff
> >
> >
> >
> >
> > "Edwin vMierlo [MVP]" <EdwinvMierlo@discussions.microsoft.com> wrote in
> > message news:OIY1YiziHHA.3452@TK2MSFTNGP04.phx.gbl...
> >>
> >>> I spoke to HP and they do have a newer driver that what I have now but
> >> again
> >>> that doesn't make any sense as out of the blue I started getting these
> >>> errors.
> >>
> >> Yes, I have seen many errors which seems to be "out of the blue", but
in
> >> fact it was a known bug in a driver, and suddenly the error condition
> >> appeared because of a very small change in the environment. (to small
to
> >> notice... chaos theory, the butterfly effect)
> >>
> >>> Could this error be from a bad nic on another PC trying to
> >>> connect to our Exchange server?
> >>>
> >>
> >> yes, that could be too
> >>
> >> still, I would start with drivers/firmware upgrade on your server.
> >>
> >>
> >
> >
>
>

Good Day,



We have about 50 machines that I am looking at. I started that process and
thought that I had it but the error showed up again after hours. I asked
the Art department to shut down some PC that are always on except for the
weekend to see if I did not have the error. The first time no errors then
the second time I got an error early in the morning. I did find that one of
the users left his PC on while it was rendering a drawing. I have to go
back over the event logs to see when the errors appeared. I do not see any
issues on the network as of yet so I do not think the problem is anything
that I need to worry about but still I would feel better if I could find out
what is causing the problem. I have noticed that the error has spread to
other servers not as much but I have found one or two errors on them now.



I can't see it being a network problem as nothing on the network has
changed. I am reviewing that as well. I changed the port that the server
was on the switch that did not help as well.



If anybody has any other methods that I can try without calling for CSS
right now it would be a help at least it may point me in the right direction
instead of me shooting in the dark.



"Edwin vMierlo [MVP]" <EdwinvMierlo@discussions.microsoft.com> wrote in
message news:%23T%23AZchkHHA.680@TK2MSFTNGP06.phx.gbl...
> Adam,
>
> how many machines are we talking about ?
>
> do what you did before, shutdown the client PC's (but now half of them, no
> all)
> -> problem exist, then the problem is with the PC's which are left on
> -> problem does not exist
>
> You can then repeat this excersies, and in a couple of days you might find
> it (not 100% guaranteed)
>
> however, you can only do this if you have a manageable amount of machines.
>
>
>
> "Adam Raff" <araff@newsgroup.nospam> wrote in message
> news:u0kh5h1jHHA.4516@TK2MSFTNGP03.phx.gbl...
>> I wanted to follow up with this email with some more info. As of today I
> am
>> still getting the errors after updateing the Nic driver to the latest.
>> So
>> far when I turn off all the PC's within the company I get no errors as I
>> tried that during the week and told everybody that all systems need to be
>> shut down as we do on the weekends. No errors showed up in the morning.
>>
>> If anybody knows a way to determine the offending Nic if there is one it
>> would be a great help without being a detective.
>>
>> Thanks
>> Adam Raff
>>
>>
>> "Adam Raff" <araff@newsgroup.nospam> wrote in message
>> news:O8BvCxNjHHA.1216@TK2MSFTNGP03.phx.gbl...
>> > Hello,
>> >
>> > Well still having the issues, so I decided to relent and updated the
>> > Nic
>> > driver to the latest today. Will have to see what happens. In the
>> > mean
>> > time I am still looking around on the network to see if it's a computer
>> > issue that is causing the problems. Does anybody know of a way that I
> can
>> > see what system if it's a system could be causing this. Is there any
> clue
>> > in the errors?
>> >
>> > Any way thanks for the help
>> > Adam Raff
>> >
>> >
>> >
>> >
>> > "Edwin vMierlo [MVP]" <EdwinvMierlo@discussions.microsoft.com> wrote in
>> > message news:OIY1YiziHHA.3452@TK2MSFTNGP04.phx.gbl...
>> >>
>> >>> I spoke to HP and they do have a newer driver that what I have now
>> >>> but
>> >> again
>> >>> that doesn't make any sense as out of the blue I started getting
>> >>> these
>> >>> errors.
>> >>
>> >> Yes, I have seen many errors which seems to be "out of the blue", but
> in
>> >> fact it was a known bug in a driver, and suddenly the error condition
>> >> appeared because of a very small change in the environment. (to small
> to
>> >> notice... chaos theory, the butterfly effect)
>> >>
>> >>> Could this error be from a bad nic on another PC trying to
>> >>> connect to our Exchange server?
>> >>>
>> >>
>> >> yes, that could be too
>> >>
>> >> still, I would start with drivers/firmware upgrade on your server.
>> >>
>> >>
>> >
>> >
>>
>>
>
>

On May 10, 10:03 am, "Adam Raff" <a...@newsgroup.nospam> wrote:
> Good Day,
>
> We have about 50 machines that I am looking at. I started that process and
> thought that I had it but the error showed up again after hours. I asked
> the Art department to shut down some PC that are always on except for the
> weekend to see if I did not have the error. The first time no errors then
> the second time I got an error early in the morning. I did find that one of
> the users left his PC on while it was rendering a drawing. I have to go
> back over the event logs to see when the errors appeared. I do not see any
> issues on the network as of yet so I do not think the problem is anything
> that I need to worry about but still I would feel better if I could find out
> what is causing the problem. I have noticed that the error has spread to
> other servers not as much but I have found one or two errors on them now.
>
> I can't see it being a network problem as nothing on the network has
> changed. I am reviewing that as well. I changed the port that the server
> was on the switch that did not help as well.
>
> If anybody has any other methods that I can try without calling for CSS
> right now it would be a help at least it may point me in the right direction
> instead of me shooting in the dark.
>
> "Edwin vMierlo [MVP]" <EdwinvMie...@discussions.microsoft.com> wrote in
> messagenews:%23T%23AZchkHHA.680@TK2MSFTNGP06.phx.gbl...
>
>
>
> > Adam,
>
> > how many machines are we talking about ?
>
> > do what you did before, shutdown the client PC's (but now half of them, no
> > all)
> > -> problem exist, then the problem is with the PC's which are left on
> > -> problem does not exist
>
> > You can then repeat this excersies, and in a couple of days you might find
> > it (not 100% guaranteed)
>
> > however, you can only do this if you have a manageable amount of machines.
>
> > "Adam Raff" <a...@newsgroup.nospam> wrote in message
> >news:u0kh5h1jHHA.4516@TK2MSFTNGP03.phx.gbl...
> >> I wanted to follow up with this email with some more info. As of today I
> > am
> >> still getting the errors after updateing the Nic driver to the latest.
> >> So
> >> far when I turn off all the PC's within the company I get no errors as I
> >> tried that during the week and told everybody that all systems need to be
> >> shut down as we do on the weekends. No errors showed up in the morning.
>
> >> If anybody knows a way to determine the offending Nic if there is one it
> >> would be a great help without being a detective.
>
> >> Thanks
> >> Adam Raff
>
> >> "Adam Raff" <a...@newsgroup.nospam> wrote in message
> >>news:O8BvCxNjHHA.1216@TK2MSFTNGP03.phx.gbl...
> >> > Hello,
>
> >> > Well still having the issues, so I decided to relent and updated the
> >> > Nic
> >> > driver to the latest today. Will have to see what happens. In the
> >> > mean
> >> > time I am still looking around on the network to see if it's a computer
> >> > issue that is causing the problems. Does anybody know of a way that I
> > can
> >> > see what system if it's a system could be causing this. Is there any
> > clue
> >> > in the errors?
>
> >> > Any way thanks for the help
> >> > Adam Raff
>
> >> > "Edwin vMierlo [MVP]" <EdwinvMie...@discussions.microsoft.com> wrote in
> >> > messagenews:OIY1YiziHHA.3452@TK2MSFTNGP04.phx.gbl...
>
> >> >>> I spoke to HP and they do have a newer driver that what I have now
> >> >>> but
> >> >> again
> >> >>> that doesn't make any sense as out of the blue I started getting
> >> >>> these
> >> >>> errors.
>
> >> >> Yes, I have seen many errors which seems to be "out of the blue", but
> > in
> >> >> fact it was a known bug in a driver, and suddenly the error condition
> >> >> appeared because of a very small change in the environment. (to small
> > to
> >> >> notice... chaos theory, the butterfly effect)
>
> >> >>> Could this error be from a bad nic on another PC trying to
> >> >>> connect to our Exchange server?
>
> >> >> yes, that could be too
>
> >> >> still, I would start with drivers/firmware upgrade on your server.- Hide quoted text -
>
> - Show quoted text -

Hi there,

I was wondering if you were able to resolve your issue yet, because
are experiencing a similar issue with one of our servers... Similarily
it is also an HP server and we contacted HP and they also recommended
to upgrade our NIC driver, which that didn't resolve the issue...

Hi,
I am also having the same problem. I have a dell poweredge T300 and i get event error 2012. at the same time all the users can't access the network shared drivers. i don't know what is the problem can anybody help me!