EventId: 4356

I have just checked this event appearing occasionally on different workstations, that has Windows XP with service pack 2, for no apparent reason. I am starting to believe that it could be linked to some strange network problem that is happening. The network problem is that sometimes a workstation wont be visible from the network, no remote access and not even a response from ping. Is there anyone else who is seeing the below event log:

Source: EventSystem
Category: (52)
EventId: 4356

The COM+ Event System failed to create an instance of the subscriber partition:{41E90F3E-56C1-4633-81C3-6E8BAC8BDD70}!new:{6295DF2D-35EE-11D1-870 7-00C04FD93327}. CoGetObject returned HRESULT 8000401A.

The issue that you are facing can occur when there is no DC while logging on workstations. To fix this problem, you might need to use the Regsvr32 tool to unregister the Mobsync.dll file by following the below method:

1. First of all click Start, click Programs, click Accessories, and then click Command Prompt.
2. After that you can type the following line, and then press ENTER:
   "regsvr32 "%systemroot%\system32\mobsync.dll" /u" (without the quotation
3. marks)
4. Now you can quit Command Prompt.

Thanks for the workaround, I will try that and let you know. So, you sure that this could be the cause of our network connectivity issues, the network problem is sometimes a workstation that will not be visible from the network, no remote access, not even a response from ping? There is also something else that could be similar which is that these machines have all had DHCPMediaSense disabled (Q326152) in order to prevent eventId: 1054.

Can I take it that the routine is carried out on the workstation - not on the server?

I have a client with the same Event reported. He has an XP SP3 machine and reports that, at certain times of the day - typically after business hours - he is unable to save files to a drive mapped to their SBS R2 Service Pack 2 Build 3790. He has not reported experiencing the problem during regular business hours. He is the only user that reports the problem. I found this Event reported at the time he last experienced the problem. Do you think this is the cause?

Thanks for any help you can provide!