System error 52/duplicate name exists on the network...

Recently our MediaBin server started throwing an error and then the MBPServer service dies. The mbp.log and net.log do not catch the death however in the Windows Event log I have a few interesting error messages.

System error 52 has occurred.

You were not connected because a duplicate name exists on the network. Go to System in Control Panel to change the computer name and try again.

The system failed to register pointer (PTR) resource records (RRs) for network adapter.

I believe that this is strictly a network problem. however, I spoke with our network guys/gals and they told me that our PTRs are manually added, our WINS are static, and Active Directory only has one server with that name.

What is the error bubbling up from MediaBin?

Find more posts tagged with

Comments

lyman

I have to admit this is a new one to my experience! If you have net.log turned on, you will notice that requests/replies come paired. Can you figure out towards the end of the file what requests report starting and not ending? This may give some hints.

Thanks,

Lyman Hurd

Migrateduser

Thanks Lyman! I'm taking it up with our network team. Thanks for confirming what I thought.

suj

Hi,

I'm getting the same error with my MB server this morning.

The MediaBin Server service terminated with the following error:
You were not connected because a duplicate name exists on the network. Go to System in Control Panel to change the computer name and try again.

Were you able to find a resolution to this problem?

TIA

lyman

I do not know the resolution but the same advise applies. Do you see this on attempted start-up? Is this a single machine or a cluster? One plausible place where it could fall down is when MediaBin is attempting to reach the database.

Cheers,

Lyman Hurd

Migrateduser

Unfortunately, we did not come to a resolution.

Instead, I built a little server monitoring tool that tries to connect to MediaBin every 10 minutes. If it fails, then I try to recycle the mbpserver service 3 times with 5 minutes intermissions between each attempt. If that does not work, then the tool sends an administrative alert to the administrators of that box, and the tool reboots the machine.

After reboot, it usually fixes the issue but, I'm still not happy with the cause/affect.

Tell me if you find anything, I'm dying to know how to fix it.

suj

This is a single server and the database is also on the same machine. The last few lines in MBP.log does indicate a database error. I'll probably try a system reboot. Thanks for the inputs.

biswas_126

Well ... we faced the problem and the problem was solved by restarting the system.

It seems that while stopping the service there is a timeout.

If you find something which does not involve restarting system then please post...

lyman

Can you give more specifics as this was a two year old post! You are getting a "duplicate name" error?

Cheers,

Lyman Hurd

Migrateduser

I have found that when this error exists there are files in MBDataDirectory\temp that are not being deleted on service restart.

A service stop, delete these temp files and re-start seems to do the trick.

Peter

biswas_126

to answer lyman's question, yes it was a duplicate name error and we are using mediabin 4.5.3 on windows 2003 server with sqlserver 2000 sp4