Mediabin Services are not starting.

We are using Mediabin 4.5.

I try to connect to Mediabin client and I am getting error message -

"Unable to connect to server.Reason:Writing data to the server failed.You may have lost the connection to the server."

After this, when I am checking Mediabin Services, its running properly ,so I tried to restart the services.

While stopping the service I got error message "Could not stop the Mediabin Server Service on local computer.Error 1053:The service did not respond to the start or control request in a timely fashion."

After that service stops. When I tries to start the service, I am getting another arror message "Could not start the Mediabin Server Service on local computer.Error 52: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 problem is solved by rebooting the server.As the problem occurs frequently we can't reboot the server again & again.

Any solution except rebooting ?

Find more posts tagged with

Comments

Migrateduser

Hi pjalani,

We experienced and struggled with the same issue for years. We came to understand that it was a problem with our large network. In our case the server name was cached on WINS server on the Active Directory lookup.

Although we knew what the problem was, we could not find the specific WINS entry because the network architecture was too vast.

Consequently, we ended up creating a very simple VB6 tool which monitors the server and if the service dies, it would try to restart the service 3 times, if that was unsuccessful, my tool tries to sends an administrative email, and would reboot the server automatically.

How did we solve our problem? Our old hardware was "end of life" in our datacenter and we had to replace it it anyways. The new server does not have the issue.

[If you want the tool, I'm willing to share with a fellow MediaBin colleague.]

We never tried this but, if you have a static IP and the ability to change it, I would try that at your domain WINS level. Then, flush the WINS cache on the servers by forcing a group policy update. This should flush the WINS lookups. Of course, this will not work with your network if you have manually hand entered lookups for the WINS tables. Unfortunately, we did not have control of our WINS tables to try this.

Good luck.

Stacy