Messenger service registration on XP SP2

[Damien S]

I have a pair of XP Service Pack 2 machines, with the Intel Pro 100VE NICs,
running as DHCP clients.

Sometimes when they bootup, the messenger service starts without error but
won't send or recieve messages. Running nbtstat -n doesn't show the messenger
service registrations. If the messenger service is restarted, the nbt
registrations occur correctly.

The only thing I've been able to find is kb article 878468, but it only
applies to Win2k and XP SP1.

Any ideas?

 

[Vincent Xu [MSFT]]

Hi Damien,

Would you please check the article KB878468 again? Because I see the
article applies to :

Microsoft Windows XP Service Pack 2
Microsoft Windows XP Service Pack 2
Microsoft Windows XP Tablet PC Edition 2005
Microsoft Windows XP Service Pack 2

http://support.microsoft.com/?id=878468

And in this KB artilce, it shows we workaround this problem by restarting
messenger service.

As you described this issue happens randomly, it may be caused by accident
and you have done the right step to restart the messenger service.

Thanks.

Best regards,

Vincent Xu
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 this issue.
======================================================
This posting is provided "AS IS" with no warranties,and confers no rights.
======================================================



--------------------

 

[Damien S]

Looks like I might have pasted the wrong article number. The one I was
thinking of was 306257 which describes the problem a little better. There is
some vendor written software that runs on these effected PCs that requires
the Windows Messenger service in order to run properly.

Hi Damien,

Would you please check the article KB878468 again? Because I see the
article applies to :

Microsoft Windows XP Service Pack 2
Microsoft Windows XP Service Pack 2
Microsoft Windows XP Tablet PC Edition 2005
Microsoft Windows XP Service Pack 2

http://support.microsoft.com/?id=878468

And in this KB artilce, it shows we workaround this problem by restarting
messenger service.

As you described this issue happens randomly, it may be caused by accident
and you have done the right step to restart the messenger service.

Thanks.

Best regards,

Vincent Xu
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 this issue.
=====================================================This posting is provided "AS IS" with no

warranties,and confers no rights.

 

[Vincent Xu [MSFT]]

Hi Damien ,

First, pleae let me know if the adapters are Bridged Network Adapters. I
ask this because I found a internal article describered that NetBIOS name
machinename<03> unregistered after reboot if a couple of Network Cards to
be Bridged Network. At the boot time, The Messenger Service enumerate
NetBIOS Interfaces and count number of Interfaces. If computer has only one
Bridged Network, it wasn't initialized at this time, Because, Messenger
Service cannot get correct lana's information. GlobalData.NumNets was 0

If it is not your case, please try:

1. Go to %systemroot%\system32 and check the msgsvc.dll.
2. Right click this dll and select properties. Check the version if it is
later than 5.1.2600.1168
3. If it is later than 5.1.2600.1168, please try to re-register it by using
: "regsvr32 msgsvc.dll" to check the results.

Hope this helps.


Best regards,

Vincent Xu
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 this issue.
======================================================
This posting is provided "AS IS" with no warranties,and confers no rights.
======================================================



--------------------

 

[Damien S]

The msgsvc.dll on the effected systems is version 5.1.2600.2180, so I'll try
re-registering them and restarting. The network adaptors are Intel Pro 100/VE
and are connected to a Cisco Catalyst switch. There are errors in the event
log referencing dhcp renewal being canceled by the user on startup, as well
as a trio of "link up, link down, link up" messages in the event log on
startup. The three link state events all occur within a few seconds (so the
time difference between the first and 3rd is maybe 6 seconds.)
Does that internal article offer a fix for the issue you've described?

Hi Damien ,

First, pleae let me know if the adapters are Bridged Network Adapters. I
ask this because I found a internal article describered that NetBIOS name
machinename<03> unregistered after reboot if a couple of Network Cards to
be Bridged Network. At the boot time, The Messenger Service enumerate
NetBIOS Interfaces and count number of Interfaces. If computer has only one
Bridged Network, it wasn't initialized at this time, Because, Messenger
Service cannot get correct lana's information. GlobalData.NumNets was 0

If it is not your case, please try:

1. Go to %systemroot%\system32 and check the msgsvc.dll.
2. Right click this dll and select properties. Check the version if it is
later than 5.1.2600.1168
3. If it is later than 5.1.2600.1168, please try to re-register it by using
: "regsvr32 msgsvc.dll" to check the results.

Hope this helps.


Best regards,

Vincent Xu
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 this issue.
=====================================================This posting is provided "AS IS" with no

warranties,and confers no rights.

 

[Vincent Xu [MSFT]]

Hi Damien ,

Thanks for your reply.

I noticed you said the event about dhcp, please let me know the exact event
log.

Per the internal file, this problem will not be fixed until Vista. Sorry
for any inconvenience.

Thanks.


Best regards,

Vincent Xu
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 this issue.
======================================================
This posting is provided "AS IS" with no warranties,and confers no rights.
======================================================



--------------------

 

[Damien S]

Well, I can't register msgsvc.dll as it tells me "DLLRegisterServer entry
point was not found".

The DHCP event log message is event ID 1003 from source DHCP and says "Your
computer was not able to renew its address from the network (from the DHCP
Server) for the Network Card with network address 001143CACE92. The following
error occurred: The operation was canceled by the user. . Your computer will
continue to try and obtain an address on its own from the network address
(DHCP) server."

The link state events are from the NIC driver (E100B) and says little more
then "Adaptor link up", "Adaptor link down".

Hi Damien ,

Thanks for your reply.

I noticed you said the event about dhcp, please let me know the exact event
log.

Per the internal file, this problem will not be fixed until Vista. Sorry
for any inconvenience.

Thanks.


Best regards,

Vincent Xu
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 this issue.
=====================================================This posting is provided "AS IS" with no

warranties,and confers no rights.

 

[Vincent Xu [MSFT]]

Hi Damien ,

My suggestions are:

1. Open connection and go to TCP/IP advanced settings to enable Netbios
over TCP/IP.

2. run NBTStat -rr to check the results.

If t he problem still occurs, please run : netsh int ip reset resetlog.txt
to reset TCP/IP

If the problem persists, I suggest you collect some system information
using Microsoft Configuration Capture Utility , and please send the CAB
(Zip) file to me.

Please download the tool:

http://download.microsoft.com/download/b/b/1/bb139fcb-4aac-4fe5-a579-30b0bd9
15706/Mpsrpt_network.exe

For more information and overview, please refer to link below:

KB818742 Overview of the Microsoft Configuration Capture Utility
(MPS_REPORTS)

http://support.microsoft.com/?id=818742

Note: The CAB file will be generated for your convenience in the
%systemroot%\MPSReports\Network\Report\Cab directory called
%COMPUTERNAME%_MPSReports_.CAB. The CAB file will contain the reports
generated by the MPS Reporting Tool. If the CAB file isn't produced, please
compress all of the result files under
%systemroot%\MPSReport\Network\Report as a Zip file. (Note: %systemroot% is
the folder where you install Windows.)

Please send me the CAB file via the email : (e-mail address removed)

Thanks.


Best regards,

Vincent Xu
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 this issue.
======================================================
This posting is provided "AS IS" with no warranties,and confers no rights.
======================================================



--------------------

 

[Guest]

Hi Damien:

I have the same problem with a couple of XP SP2 workstations, the only
solution I have is to assign static IP and the messenger works fine and the
error message from event Id gone.

I was wondering If you got the solution.

Thanks