The "steps to reproduce" may trace back quite some way.
Meaning what exactly? Are you suggesting that it is at the point of a NEW install of VP683 that this inability to consequently re-instate MM is failing? If that is the case, how come Paul and I are getting such different success results in reinstating MM? So maybe there is yet another "Babushka-like" unfathomable enigma, wrapped inside a conundrum, like a series of cross-linked maze-corridors to limp through?

If I am to read you correctly, then what I would need to do is to remove ALL traces of SONY products and reinstall in the same progressive way I have done in the past? Basically, rebuild the software platform from the bottom-up, just to reinstate MM.

I have had success in the past in reinstating MM: VP9 and VP10. Maybe it is just VP11 that's crook? And again, Paul ISN'T getting an issue reinstating MM.

So, it looks more and more likely that a restore of my System would be needed. A restore of a system that is working fine elsewhere. If that's the case, then how do we even bother reporting back bugs if we are forever falling back on complete restores? Is it possible that this is how the SCS team gets through their day? Come to that why bother reporting bugs if all I'm doing is restore to a status quo that works?

Interesting (not!).

Cheers

Grazie

"Are you suggesting that it is at the point of a NEW install of VP683 that this inability to consequently re-instate MM is failing?"

No. MM connects to a backend server, there's two parties involved here. The MM in VP has to be running the code to request a connection, the backend server has to know it should allow the connection. We don't know which is failing.
VP itself probably stores something in a registry entry so it knows to run the code for MM, that could be stuck or the SQL Server might have been told not to talk to the VP11 instance.

"If that is the case, how come Paul and I are getting such different success results in reinstating MM?"

I don't know the exact answer to that however there's more to this than just V11 that has to play nice as I explained above.

What frustrate me on your behalf is the lack of any visibility into the problem. Microsoft provide a number of tools so their SQL Server can be administered. Of course the problem may not lie in that area at all however it would be of some relief to eliminate that possibility. It's the lack of access to the backend of MM that put me right off it from the get go. No way am I going to invest my time stuffing data into a vault that I don't have the keys to.

Bob.

Bob, now THAT I understand. Very simple explanation of how you read it. I'm sure that the SQL is happening, it's simple MM appearance in VP11 thats now stuffed. Like the front end of a Data input form/report being greyed out.

SCS!? Give Bob the keys to the door!

Grazie

Actually this discussion led me to believe that someone who knows what they're doing (=not me) actually does have access to the backend of MM. At least sufficiently to get the data out into another program.

There really is a screaming gap in the market for a better media manager program.

I reread through all of that without noting anyone having any joy.
You can pretty easily get into a SQL server to access the system files. All they tell you is the structure of the tables, that doesn't give you access to the data in them.

I have written a few apps that suck data out of a SQL Server database via ODBC, took a while as I had to reverse engineer everything, heck even dates are stored differently compared to Access. It's not all that hard once you know what the data is used for so long as the tables have sensible names it becomes fairly self explainatory.

"

I thought SCS were promoting a 3rd party one at NAB a few years back.

Bob.

As I say, the DATA is there, the User Front End needs to be reconnected WITHIN the Vegas Workspace Pane/Window. And this still IS happening in VP10. Maybe that would fail if I disengaged that too?

The SQL works very well. It's solely me getting at it from within Vegas. Please guys don't forget that that is the issue. I want the Front End, which is jolly excellent, working again in VP11.

Grazie

What i find worrying about this is the lack of error messages.
You would expect if the data connection to the MSSQL database or the MM GUI could not do as intended, you would get a log or splash error? Vegas does have a start log (i think) , but you said you do see the Opening Media Files splash message at startup which suggests the data 'is' being access, just not displayed. Doubt if any Vegas log would show anything but could be worth a look.
At least your data is there and not gone missing. You see it in v10 - good!
Done a fair amount of SQL (mainly MySql) app programming here, shouldn't be too hard for someone to access the data and display it in a windows form, ready for drag drop onto Vegas TL. But its a job and would take time.
'Please guys don't forget that that is the issue. I want the Front End'.. yep.

Paul

.... in Vegas. As it was.

G

my bad. A ticking off for misquoting!

So i uninstalled the whole lot, control panel remove etc. The re-installed it again, re enabled it in Vegas - and its all back where it was, perfect. Even my test data was there.
This is very odd.

Paul.

Isn't it.

Stab in the dark, and hardly worth posting, but... Have a muck about with your Vegas window layouts. Make sure it's not somehow hiding, or if you can jolt it into life.

Nick Hope:
You are an intelligent dude.
JJK

JJK, did you see that Empty Media Manager Pane I posted? Where else could MM be hiding? That IS the correct Pane, it's not as if it has been collapsed, it's sitting there "blind" and empty of the MM Tree and so on.

Nick, I stripped down Vegas to the barest of windows - nothing. I open the "Default" Windows Layout - nothing.

Thanks for the suggestions guys, but I can't see where else it could be lurking?

Grazie

Only other thing I can think of is that it is maybe hiding on your second monitor. I had a problem like that for a while even with the second monitor switched off. It was caused by the video card driver of all things.
JJK

JJK, did you see my original screengrab, showing exactly what is happening? You can clearly see the Media Manager Pane. Seeing the Pane isn't the issue. It's where it should be. The trouble is is that THAT Pane is empty. It's not that it's hidining, it doesn't CONTAIN anything. I can move Pane about; make it bigger or smaller, makes absolutely no difference at all. It's empty! It's a DEAD Pane! If it hadn't been nailed to its perch, it'd be lying on its back with its legs up! It's a DEAD Pane. (Apologies to Monty Python..... ). "it's being a very very naughty boy!" (Different sketch, same sentiments!)

Grazie (Mrs)

It's just pining for the fjords.

More stabs in the dark...

- Make sure your Microsoft SQL Server 2005 is updated to SP4. Windows Update should take care of that but might be worth double-checking by installing from here: [url=http://www.microsoft.com/en-us/download/details.aspx?id=7218]. Back up your media libraries first.

- Maybe install 682 (32 bit) and see if it works in that?

- Clean install of 683? Isn't there some SCS migration wizard that will let you backup your settings?

I just tried to open Media Manager from SVP v9.0, and the window opened up but it was completely empty (nothing showing, totally white inside the borders). I fiddled with a few things to no avail, then I finally got it working.

I develop Windows programs using Microsoft Visual Studio 2010 Ultimate. VS-2010 includes a SQL Server Explorer View. I opened the Explorer window and saw all the versions of SQL Server installed on my PC. One of them was Sony_MediaMgr2. It wasn't running, but it was configured to connect to a media database I had created months ago, but since deleted. I tried starting the server but it failed. I then used the Visual Studio Server connection configuration tool, to reconfigure it for a connection to the default database. Then I restarted the server, and it started running.

With the default database connection restored, and the server service running, this time Media manager opened normally.

Gary ...

This may also help (possibly), running the "SQL Server 2005 Surface Area Configuration" application shows the current 'running' and 'stopped' status of the service.
Its startup type should be set to "Manual" . Because it is controlled by Vegas starting and stopping which in turn starts and stops the service.

May be worth checking the service is being controlled correctly during Vegas start stop.

Its normally located here:

"C:\Program Files (x86)\Microsoft SQL Server\90\Shared\SqlSAC.exe"

The service name is MSSQL$SONY_MEDIAMGR2
and the Dsiplay Name is SQL Server (SONY_MEDIAMGR2)

Paul.

You guys are amazing.

I've just come back from an all day shoot. A dozen pieces to camera, Learners doing Drama, chemistry, English and Sex Ed!

I have a raging cold and drinking lemon and stuff......

I'll get to your suggestions tomorrow.

Grazie

I'd add some brandy to the lemon stuff! LOL!
Get better soon.
Tom

Now what's going thru my mind is how did the insides of the window get shut off in the first place?
JJK

JJK, I'm not really interested ( well, in passing I am . . ), I want a solution.

Anyhoooo . .. Have sent email to SCS and had a response. An attempt at re-pro is going to be carried by the in-house QA team. So, let's see.

Cheers me dears!

G