Media Manager 2.0

CrashKC wrote on 4/4/2006, 6:07 AM
Everytime I start-up Vegas60, I get an error message that reads,
"MSSQL$SONY_MEDIAMGR Service does not exist or the current account does not have enough privelege to manage it". Could anybody tell me what this means and how can I fix this.

I'm using XP and the Vegas software does launch, I just don't get the Media Manager feature.

Thanks!

Comments

JohnnyRoy wrote on 4/4/2006, 8:03 AM
It sounds like you may have a corrupt install. I would reinstall Vegas and see if that fixes it. Otherwise you could investigate and see if what the error message is saying is true. The error is actually saying that two things can be wrong. Ether the services don’t exist or they don’t have the correct privileges to start. Let’s take them one at a time:

Does the MSSQL$SONY_MEDIAMGR Service exist on your PC? To find out go to:

Start > Control Panel > Administrative Tools > Services

Scroll down the list and make sure MSSQL$SONY_MEDIAMGR is listed as a service. You will also need SQLAgent$SONY_MEDIAMGR too as the MSSQL$SONY_MEDIAMGR depends on this service. Try and start the MSSQL$SONY_MEDIAMGR and see if it starts. If it doesn’t, you will have to determine why. I would bet from the error message that it won’t start.

As for the privileges, I assume you need to be using an account that has administrative privileges (most XP users do). The Log On tab of those services log on as the local account which is whatever account you are using. Make sure it’s an administrator.

If I were you I would call Sony Tech Support and have them walk though this with you. It is not an easy thing to debug.

~jr
R. Heffels wrote on 4/5/2006, 2:54 PM
You can also disable the Media Manager.
Options> Preferences> General Tab>Enable Media Manager (second last option)

Personally I've never seen any use for it :-)

Vegas also starts a faster without the Media Manger.
JohnnyRoy wrote on 4/5/2006, 3:10 PM
> Personally I've never seen any use for it :-)

I agree that some people won’t have a need for it on some projects, but if you have a lot of stock footage to manage or very large projects with combinations of wide, medium, tight shots, etc. that require cataloging and finding quickly, you will find the Media Manager extremely useful.

> Vegas also starts a faster without the Media Manger.

That use to be true, but not by much anymore. Maybe one or two seconds (unless you have a slow PC). The new Media Manager 2.1 starts much faster than it use to. I use to keep it turned off when I was programming because I’d be constantly invoking Vegas to debug a script but now I just leave it enabled all the time. I can't feel a difference.

~jr
Cliff Etzel wrote on 4/5/2006, 8:08 PM
So how does one get the latest verion of Media Manager? I too have disabled mine just because of how slow it makes Vegas run...
JohnnyRoy wrote on 4/5/2006, 8:40 PM
The latest version is included with the Vegas 6.0d update. It is also included in the ACID Pro 6.0 software. I believe downloading ACID Pro 6 trial will install it and when you uninstall the trial it will leave it. But try the Vegas 6.0d update first. (I have both so it’s hard for me to tell now where I got it from)

ACID Pro 6 now displays what it’s doing on the splash screen so you can see all the VST’s loading and stuff. When it gets to “Initializing the Media Manager”, it just flashes for a split second and moves on to the next task. Very lean.

~jr
DrLumen wrote on 4/5/2006, 11:56 PM
As to the OP, I get the same error. When I check the logs it says it was unable to find the file and has the path to where it is looking. I have tried re-installing 6.0d, tried running config for the SQL server but get a password error, checked the ODBC settings and even went in to the registry to try to find and fix the pointer to the correct location but no luck. I think this is what Sony was referring to when they mention problems when installing to a directory other than the default...

Perhaps the only way to fix the problem may be to un-install Vegas and then start from the disks and then to the 6.0d update. Personally, I'm not sure it is worth all of that for no more than I would use MM. However, it may have been quicker to re-install than going through all of the above. ;-/

intel i-4790k / Asus Z97 Pro / 32GB Crucial RAM / Nvidia GTX 560Ti / 500GB Samsung SSD / 256 GB Samsung SSD / 2-WDC 4TB Black HDD's / 2-WDC 1TB HDD's / 2-HP 23" Monitors / Various MIDI gear, controllers and audio interfaces

Grazie wrote on 4/6/2006, 1:28 AM
"The latest version is included with the Vegas 6.0d update. . .."


Well, not in my case John. It was only when I got ACID6 that it "kick-out" the jams! In fact I was told, by Sony, that 6d would be doing catch-up AND that I'd had to wait for ACID6Pro to actually succeed. Tested V6d and MM loading was still freezing Vegas - Having Acid6P has brought in this MM2.1, and, well MM is just flying along .. so far . ..

Grazie
PeterWright wrote on 4/6/2006, 3:24 AM
"MSSQL$SONY_MEDIAMGR Service does not exist or the current account does not have enough privelege to manage it"

I got exactly the same message. My solution was to uninstall Vegas, Media Manager and Acid Pro 6 and start again. It was a nuisance, because all my Vegas setups were lost, but it solved this problem, and MM now works fine.
ForumAdmin wrote on 4/6/2006, 11:02 AM
If you are having Media Manager problems in Vegas 6.0d, please try installing ACID 6 (trial is ok). Media Manager is a shared component, Vegas will use the components updated by the ACID 6 installation. This has helped Grazie and others...and we'd be interested in your results.

ACID 6 trial: http://www.sonymediasoftware.com/download/Step2.asp?DID=661
Stuart McKears wrote on 4/19/2006, 11:43 AM
I've tried this but still doesn't work.

Install gives setup failed to configure the server....etc which means that it never appears as a service so that starting Acid Pro gives

The database service failed to initialize properly (MSSQL$SONY_MEDIAMGR)

and popups appear

Unable to adjust the security on service MSSQL$SONY_MEDIAMGR

running XP Pro under an admin user.

I do wonder whether this has anything to do with MSSQL$SQLEXPRESS which is also running on this box.

Stuart

www.mckears.com