Bought the B&H $99 deal on 6.0, then used that SN for the $149 upgrade to Vegas7+DVD - install went fine (new machine, most junk flushed out, Media Center Edition of XP)

Then I downloaded the updates for both Vegas and DVDA; when I tried to install the Vegas update, I got the message "CRC mismatch - abort [OK]" - I then re-opened Vegas, clicked Help-about, and found a blank where they wanted a serial # (I'd already given it in install??!?) so I filled that in, closed Vegas, and re-tried the update - same thing.

Apparently Sony's techs are too busy to answer an email in an 8-hour day, because I've still not heard back from them; I also searched the knowledge base and came up empty for that message.

Anyone else had this message? If so, can you enlighten me? I'd really appreciate it, as I told Sony I'm trying to get this workstation put together as quickly as possible so I can use it for a current project... Steve

Oh, did I mention that I HATE acronyms?

Make sure you're installing the update to the same folder in which your existing 7.0 installation was installed. If that still doesn't work, try to uninstall the old version and reinstall with the new. Vegas updates are more than just patches, they're the entire program.

Man, that was quick; thanks Jarrod, I'll give it a shot... Steve

Removed all the Vegas stuff and did a system restore to just before the first install, then tried install direct from the 7b download - same thing. Then tried on another machine, same thing. Finally googled "CRC mismatch", and found out it stands for Cyclic Redundancy Check - usually caused by bad media. I'll be re-downloading the update tomorrow, hopefully it won't be corrupted this time... Steve

That makes sense. Good luck. :)

Yes, generally speaking CRC errors are caused by a bad download. Re-downloading will usually solve that problem.

Thanks Jarrod and Ed - I did re-download and the file now works - however, now I'm getting messages about SQL server during Mediamgr 2.2 install - kind of odd, because the FIRST time I installed 7 from disks everything went fine. It was only when I tried to upgrade that problems started, and now NOTHING works. I just restored to a point prior to all this, but need to hit the hay for tonite.

Hopefully tomorrow nite'll bring better things, I'd really like to do this next project in Vegas if possible, since it's my first 2-cam shoot... Steve

Hi, I've got the same error message as you - "CRC mismatch". Took 6h30m to download 7.0b trial version yesterday. Looks like I'm going to have to download it again :-(

Mine's installed properly now. Only took 45m to download this time.

Good luck with your install Steve

Yeah, Grant, their site's really weird on speeds - tried last nite to dnl the DVDA update again (just in case the other one's corrupt too) and it was back down to around 9k a second, just after the Vegas update came in at around 80k - also, it's a good thing I found the CRC error info on my own, because Sony STILL hasn't returned an answer to my email. (Going on 3 days now)

That's one of the reasons I went to Vegas in the first place, I was tired of total apathy on the part of the SW "support". Hoping I didn't make a mistake on that choice... Steve

Re-installed from disk after rolling back, still get message window titled "Microsoft SQL Server Desktop Engine", the message is "Setup failed to configure the server. Refer to the server error logs and setup error logs for more information."

Tried that and found about a 1000 page log - screw this. Gotta go to work, anybody have any grenades they're not using??!? Grrrr..... Steve

It's now 4 days since I asked Sony for help, absolutely no response whatever other than an automated "we'll get to it as soon as possible" thing -

I've updated my findings on their "incident" site but doubt if anyone's listening.

Has anyone here had this problem with the SQL Server messages, and if so can you share the "fix"? So far, the only help I've gotten on this is from this forum. I'm hoping at least one of the members here has been through this and can offer suggestions for a solution since I'm running out of ideas, short of reformatting and installing a new, full version of XP Pro and starting over (my next plan)

Anyone? Need a system info dump for more info first? I can do that if it'll help... Steve

Question for the guru's - is there any reason why I MUST use the media manager, or can I just disable it in Vegas? This seems to be the only sticking point in this excercise in frustration, still no resolve. Tried multiple install/de-install's, roll-backs, regedits to remove all references to SQL, NOTHING works. Now the registration server doesn't even wanna talk to me, vegas gives me 30 days when I click on "register later", whatever...

Douglas, Ed, anybody with a CLUE - puhleeeze throw some ideas out there, I'm rapidly becoming borderline INSANE with this fiasco - can't understand why it has to be so (*&#* difficult.... Steve

when media starts to install, jsut hit cancel bro.. u dont need it if u have no use for it and IMO it slows things down considerably when it comes to fishing for ur morsels of material.

If u know how to plan your folders, u dont need media manager.. if u plan on reusing clips and archiving, then it may come in handy, but 80gb of mps, 200gbs of stock footage in MOV and AVI formal, 4 projects and 8 HDD's going all at once, and im yet to find a use for media manager..

u cana also disable media manager by going to options preferences and scroll down, and disable it from launching from there..

Thanks Peter, pretty much did just that after posting - no apparent ill effects, and like you I'm used to figuring out my OWN storage plans, so far so good. I went ahead and installed latest updates for both prog's along with Ultimate S, it's about 4:30 am here and I should go to bed before daylight, but having too much "fun" figuring out the differences between Vegas, Premiere and Magix Movie Edit Pro, the first NLE I started on early this year.

Still, it bugs me that a brand new machine with all latest XP updates can't find its arse with both hands - oh well, on to the quad cam learning experience. Thanks again for confirming that I won't burst into flames if I can't load the stubborn mm2.2/sql server stuff... Steve

It is definitely NOT a requirement. Many people love it - many people disable it. Not sure why you're having installation issues. The usual first step is to see if you can start the service manually. However, media manager installation/starting issues virtually always have to be referred to tech support.

Thanks Ed - I'm 99.9% sure this is a Micro-slop bug since I've found a few links to admitted boo-boo's; only problem is, there are several versions of MSDE/SQL Server depending on processor, build of windows, etc, and no "click here to fix" buttons - the one that sounded most like my symptoms didn't fix anything.

Apparently if you have an older version of SQL server installed and then a program tries to install a newer version (in some cases) you get this error.

As most are probably aware, Microsoft has OEM agreements in place with vendors so that if you buy your computer from Charlie's computer emporium, CHARLIE is your tech support; if you finally realize charlie doesn't know squat about computers and want Microsoft to help, you PAY. Did this - $35 and 2 hours later, Microsoft did no better than "charlie", I pulled an all-nighter and fixed that problem myself, and won't EVER go there again.

Hopefully Sony will get more of these incidents and eventually bring out a "fix" that checks for previous versions of SQL in places where it would be installed, and deletes these BEFORE trying to install over them - meantime, I lived without a media manager for about a year; as long as media manager can live without me, we'll BOTH be happy :=))

If this ever DOES get resolved, I'll post an update - meantime, thanks again guys... Steve

On a more positive note - spent about half of today playing with this stuff, now have my choice of preview thru firewire to my 13" broadcast Trinitron, or to a second 19" LCD monitor, using Canopus TwinPact100 for this setup and loving it. Got the trinitron set up on color bars out of the Canopus, looks fantastic.

Had to increase the lag by 2 frames (total of 6) in preview to sync the sound. Got 1-1/2 hours on each of two cameras plus external audio track all captured and synced up, tomorrow (today actually) will install new versions of Sound forge and Noise reduction (audio needs quite a bit of tweaking to minimise background noise) - basically, life is good again, think I'm gonna like Vegas once I figure out how to do a few more things with it- NOT particularly missing media manager :=) Steve

Just curious - has anyone here actually gotten an answer back from Sony's email support? It's been 8 days now and NOTHING.

On top of that, I paid for and downloaded upgrades to Sound Forge and NR plugin - tried to install Sound Forge and get a yes/no dialog box about SF needing Microsoft .net framework 1.1 - since I'd already installed version 2.0, I answered "no" - this ended the install with no other dialog, so I started over - this time I said "yes", it takes me to Microsoft's site where I can download v1.1, but WHY SHOULD I ??!?

I then searched Sony's "knowledge base" for ".net", and come up with nothing useful - no reason why SF 8 can't figure out that v1.1 is older than what I've already got on my machine.

Jeez, no WONDER I try to avoid upgrades for at least 5 years at a minimum :=(

Tomorrow I'm gonna find SOMEONE with a PULSE at Sony to talk to (if there's anyone who actually WORKS there) and see if they can tell me anything useful, besides "you have to PAY for phone support" - and I thought Magix was apathetic... Steve

Steve, .NET Framework 1.1 and 2.0 are two different animals. Those of us who had Vegas 6 and now Vegas 7 have both of them on our machines as V6 required 1.1 while V7 requires 2.0. No problems with co-existence.

As far as email support from Sony, I had an issue some time back that took about as long to get the first response from Sony. After the initial suggestion for a fix though, subsequent responses were extremely quick.
I do agree with the feeling of a lack of support from them which is why I "solve" most of my issues with help from members on the various forums.

Mike, thanks for sharing that - I was VERY hesitant about "torpedoing" my Vegas install, since it hadn't come easy, hence my reluctance to install an older version of ANYTHING Vegas needed to function.

I think I'm going to go ahead on the .NET 1.1 (got some fairly "forensic" editing to do on the audio tracks of the current project and could use the help from SF and the NR plug), besides I'm curious if Sony will EVER follow up on my original complaint without my nagging them.

If installing the older framework messes up the newer one, guess I can re-install the 2.0 version. Thanks again, wish me luck... Steve

Hi Steve,

I had the same problem, with the installation and with Sony support response. It was finally solved with the local distributor's help.

I had Business Contact Manager installed (Office 2003) on my PC. This program seems to write at the same registy address as does the Media manager, both writing different data though.

I have uninstalled the Business Contact Manager and Medai Manager works now fine.

Maybe this may help you. If not, look for some other programs using MS SQL.

George

George, thanks for the heads up - since my last post I've installed the Sound Forge/NR upgrades on my Toshiba laptop, then Vegas - no hitches whatsoever, including Media Manager (I still disabled it tho) - I'll look for Business Contact Manager, but that was a new machine that only offered a trial version of Office which I drug to the recyle bin (don't want ANY of Microsoft's office products on this machine)

I'm set up now with external firewire drives for most projects (with the option of an internal 10,000 rpm Raptor for more intense ones) and this seems to be working pretty good - I can open any .veg and work on it with either machine depending on where I am, simply by unplugging the associated external drive and putting it into my laptop bag, then when I get back plugging the drive into the faster machine with no hiccups - sweet.

Still tracing down resource hogs on BOTH machines, and I'll have a look for YOUR particular gremlin while I'm at it, thanks mate... Steve