Comments

Former user wrote on 7/28/2014, 8:22 PM
Are you opening the files from within Vegas or double-clicking on the veg icons?

have you tried transferring them to the internal drive?

Is the media with the veg files?
impact wrote on 7/29/2014, 7:47 AM
I have tried to open the files by double clicking on them and trying to open them in Vegas. The response is the same...unable to open. I have not tried to transfer them, because other files on the external hard drive open in Vegas or by clicking on them. For example, rendered videos in DVD Archetect 5 and other music files. It seems only the .veg files won't open. The media is on the same drive as the veg files.
Former user wrote on 7/29/2014, 8:08 AM
My next step would be to transfer one of the projects and it's media to an internal drive. It could be permissions thing on the external drive.
impact wrote on 8/28/2014, 7:57 AM
Thank you, I'll give it a try.
FilmingPhotoGuy wrote on 8/28/2014, 11:31 AM
If your VEG project file used 3rd party FX's which are not installed on your present system then it'll give you that error and won't open the file. If you open that VEG file with Vegas 11 or 12 then it'll give you an error but will open the project but without the FX's you had installed when you created the VEG.
cold ones wrote on 8/28/2014, 2:42 PM
Don't know if this helps, but I had a similar issue recently with Vegas 13. Older veg files would not open, probably created under Vegas 11 or 12 on another computer. Luckily, I had saved multiple earlier versions of the file, and could go back in time till I found one that opened.

In my case, I believe I tracked it to a missing VST dll. It's possible that Vegas doesn't handle this well. When I installed the VST, the veg file opened again. I'm trying to be disciplined at the end of a project to inventory everything that a veg file needs: fonts, video effects, audio effects, etc. It's kind of daunting...

Perhaps unrelated, but I recently restored some 2 year old veg files which would not open. Eventually, I checked them with HexBrowser and found that they were filled with 0's, nothing else. To Windows, they had appropriate creation/modification dates, file size, etc, but they had somehow been damaged in the backup. Out of a couple thousand files, 16 bad veg files and 6 bad movies.
Rob Franks wrote on 8/29/2014, 5:39 AM
Has your drive lettering changed? Make sure all your drives are labeled the same as they were before. The veg files are expecting certain bits of information in certain places on your machine and it can't find that info if all the drive lettering and folder names are different. COLD_ONES is also right on the money with the vst's. All relevant information to that veg file must be available and in the same place for the veg to find.
impact wrote on 8/29/2014, 8:20 AM
Thank you everyone for your reply. I did not use third party effects in the veg. files. The veg. files open and can be manipulated. It's when I go to render that I get the error. I will try suggestions about file conformity and also check on my template conformity. I'm also concerned about a conflict with Vegas and Windows 7. Again, I had no problem before my hard drive crashed. It's when I installed a new hard drive and Windows 7 professional that my problems began.
ChristoC wrote on 8/29/2014, 5:59 PM
impact:
"My hard drive crashed and I had to replace it. Installed Windows 7 professional and installed my Vegas 9.0 program. "
and....
"Thank you everyone for your reply. I did not use third party effects in the veg. files. "

.... so which one is it??? A whole bunch of people tried to help, seemingly on a false premise.
VegasPro9 was written for Microsoft® Windows® XP 32-bit SP2 (SP3 recommended) or Windows Vista® 32-bit or 64-bit (SP1 recommended)... perhaps Win7 is one your problems.