MediaBin 4.6 -Server Hanging Daily

Hello,

We recently upgraded to MediaBin version 4.6 and have many server hang ups.

We are having to reboot,or restart the services several times daily.

We are recieving this error, does anyone know what this could be or if this could be contributing to our hang ups?

Event Type: Error
Event Source: .NET Runtime
Event Category: None
Event ID: 0
Date: 10/30/2007
Time: 6:16:24 AM
User: N/A
Computer: US01-MB1
Description:
The description for Event ID ( 0 ) in Source ( .NET Runtime ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Unable to open shim database version registry key - v2.0.50727.00000.

Find more posts tagged with

Comments

msrinivas

What do you mean by hanging? Are you not able to login or are you able to login but not do much else?

Is your asset server and web client on the same machine? Do you see the issue with all the clients?

As part of the upgrade did you upgrade your DB also? What were the steps of your upgrade?

Terbs

Hello,

We can login but after that nothing much else is happening.

Our Server set up is as follows:
Application/Web -Shared
DA-own server
SQL -own server

We did a clean install on all new hardware we had an Interwoven Consultant come out and do this for us. I can email you our upgrade process, it wouldn't let me attach it.

msrinivas

I would highly recommend opening a support case first. Do you have any custom applications talking to MB? It looks like you had a SQL server upgrade also. Was this system every stable in the first place after the upgrade?

Migrateduser

Your errors look suspiciously like .NET Framework is not installed correctly or the service is not able to communicate with the registry.

You might this on for size. http://support.microsoft.com/kb/918642

The key message in your Windows Event Log error is the last sentence. "Unable to open shim database version registry key - v2.0.50727.00000." Search the World Wide Wait on that phrase in quotes and you'll find some good articles.

lyman

the first best place to diagnose server errors is in the MBP.log. Now there are some errors that are benign, for example deadlocks are sometimes inevitable and harmless if the logs indicate that they resolve themselves, but feel free to report on anything dire looking.

Cheers,

Lyman Hurd