MBP Server Initialization failed

Hello,

We are currently having an error with our Media Bin Application server, this just started occuring last night.

The two services running on this machine -

MediaBin Publication Service and
MediaBin Server

They both start up fine, and have no errors in the event viewer. Except when you try to open MediaBin enterprise Manager, and connect to the local server, it pops up with a message saying "The Server is currently not running. Would you like to restart it?".

I say Yes to this prompt, and try connecting again and i get this error - "Unable to connect to server. Reason : Opening a connection to the server failed (0x8004041d)"

After the failed connection, when i check the Event Viewer - Application. The following Error is there -
Source - MBPServer
Description - MBP Server initialization Failed. Check logs and event viewer

Any help anyone has regarding this would be much appreciated, as i explained in another thread i'm quite new to Media Bin (i didn't even do the initial installation).

(this is seperate from the web client issue we are having that is described in a different thread, as this had been working fine for the last couple weeks, while the web client hadn't)

Thanks

Find more posts tagged with

Comments

msrinivas

Looks like the guy on vacation is having one **** of a time!

Anyway, do you know if any windows patches etc. were applied to the server? They might be having some fun.

What is the OS (SP level) that you are running MB on?

Of course, I have to add please open a support case.

HTH

mediabin_mimo

Ha, ya, i bet he's loving it!

We're running Windows 2003 R2 Standard Edition (SP1)

As for updates, the last time the servers were patched August.19th, and the issue didn't start happening until about 4 days after that.

I do have a support case open as well, just awaiting a reply back from them Smiley Happy

Thanks,
Jeff

mediabin_mimo

Ok, just in case anyone else has this problem, after working with interwoven support, we determined the Server could not connect to the mediabin database, and so the server could not intialize.

Apparently if you change the password of the account in the ODBC Connection it does not get updated in the registry (its stored there as well). This causes the connection to fail between the app server and the database server

We got it all changed and updated, and its working again, thanks for the replies!

Jeff

msrinivas

That is very interesting. Based on what you have said that you were able to access it from the windows client the impression was the server was up and running fine. Anyway, glad that its all good now.

mediabin_mimo

Ah, that was the other issue we were having, Where our web client doesn't work, but the Windows Client would connect, this issue caused everything to stop working correctly

lyman

Glad everything was resolved. I should mention that aside from the Windows Event Viewer, the other place to look for start-up errors is the file mbp.log which should be in the logs subdirectory of the directory in which the server was installed.

For further clarification, the MediaBin server stores the ODBC password in the registry twice once in encrypted form and once in unencrypted form. On server start-up if it finds anything in the unencrypted field, it encrypts it and blanks the unencrypted field. This is how you can change the password without a special API and without having to know the encryption algorithm. Note that after server start-up the password is no longer in cleartext in the registry.

Cheers,

Lyman Hurd