Same QT X Problem different Cause: Can't open QT Files

I'm having some similar problems with QT X as many of you but mine has evolved from a different source. I recorded an hour or so of DVCPro 50 on a Firestore FS100. I had the Firestore set to record QT file rather than P2. I transfered the files as I have been doing for many months but this time, now that I have upgraded to Snow Leopard, the files won't import into FCP. They won't open in QT X OR QT 7. I reinstalled QT 7 from the SL disk from the install options. The FS 100 had to be reformatted for a new shoot so I no longer have the originals. I tried taking the files off of the one computer and opening on another machine that doesn't have SL. All to no avail. My client is not going to be happy nor am I if I can't get this footage into FCP. Does anyone have any ideas? If I can get the files to open then I can save them in something that FC understands.

Under the Safari Help menu choose "Installed Plug-ins". This will confirm your QuickTime install.
Under Safari Preferences/Security make sure you've got plug-ins enabled.
Try dragging the email attachment to the Desktop and see if it plays from there.

Similar Messages

Error while opening pdf in reader in windows 8:Can't open this file. There's a problem with file format

I have a problem with a pdf file which does not open with reader in windows 8 but it opens properly with adobe pdf reader. All other pdf can be opened in reader.But when i open a pdf(see this link for pdf for which i got error http://incometaxsoft.com/temp/Form.pdf)
it gives error as "Can't open this file. There's a problem with file format".
The same file opens properly in adobe pdf reader.You can check the pdf file which i have mentioned in the link above.But the reader which comes with windows 8 can open some other pdf in the same PC.What may be the error causing this??

This has turned out to be an enormous issue for me as I sell PDF files as ebooks. I have done a fair amount of investigating this for my system.
My files have to be compatible not just across readers but across operating systems.
To date, I have over 200 PDFs that have functioned flawlessly across Mac, PC (Windows 7 and below), Android, iPhone/iPad, Linux.
I personally test my PDFs using a variety of readers and PDF editors including
PDF XChange (my favorite)
Foxit (runner up for me and I recommend for most people)
Adobe (the bloated monster)
Nitro 9 (great for moving graphical elements around)
ABBYY
And the Nuance PDF Create toolsets
Those are off the top of my head. There are a bunch on Android that I test with too.
I am running the Windows 10 Pro Tech Preview and I have this same problem so I know it isn't fixed yet in any kind of pre-release way (-sigh-)
Here is what I've learned for my situation
The PDFs I created using NUANCE'S PDF CREATE PROFESSIONAL VERSION 8
all fail using the built-in Windows 8/10 PDF reader.
When I look at the PDF properties for these Nuance created files, the underlying engine used to write them is called "ImageToPDF". Using ABBYY it indicates their own engine as does everyone else that I've tried. It is easy for you to check to see
what created your PDF by doing a "Control D" (look at the document properties). Perhaps there's a common engine causing issues.
If I use the exact same source files to create a PDF using any of my other tools I have no issues. I checked the PDF versions made by the tools and they are all set to 1.5.
A customer mentioned being able to convert them in a way they worked by saving them without having to do any kind of extraction, but I have not been able to duplicate that. Perhaps he did a "print" which seems like it could work.
In summary, the workaround everyone is talking about, using an alternate reader, of course works. But not everyone wants to change.
The culprit I have found is my Nuance PDF Creation tools that are using the ImageToPDF engine.
I hope it gets FIXED as I really don't want to have to regenerate all of my PDF files.

Office Web Apps 2013 - Sorry, there was a problem and we can't open this document. If this happens again, try opening the document in Microsoft Word

Hello
I had configured Office Web Apps for SharePoint 2013 which was working fine for about 2 months until this morning.
The error message I get for WORD, PDF and Excel files is:
The ULS logs on the WFE give me this:
WOPI (CheckFile) Proof Data: AccessToken Hash '1572676699' [1054 bytes], URL
01/08/2014 11:01:58.01*   w3wp.exe (0x1368)                          0x09B4   SharePoint Foundation
    WOPI                             afk59   Monitorable
WOPI                             agxqc   Medium     WOPI Signature verification
attempt failed with public key 01/08/2014
11:01:58.01    w3wp.exe (0x1368)                          0x09B4   SharePoint Foundation
    WOPI                             agxqc   Medium     WOPI
Signature verification attempt failed with public key
01/08/2014 11:01:58.01    w3wp.exe (0x1368)                          0x09B4   SharePoint Foundation
    WOPI                             agxqb   Medium     WOPI
Signature verification attempt failed - no public key   e75ead18-af27-4d44-ba50-b38b408011e8
01/08/2014 11:01:58.01    w3wp.exe (0x1368)                          0x09B4   SharePoint Foundation
    WOPI                             ahdzz   Monitorable   WOPI
Proof: All WOPI Signature verification attempts failed   e75ead18-af27-4d44-ba50-b38b408011e8
01/08/2014 11:01:58.01    w3wp.exe (0x1368)                          0x09B4   SharePoint Foundation
    WOPI                             ag7pj   Unexpected   WOPI
(CheckFile) - Invalid Proof Signature for file Letterhead Template.docx url: http://site.contoso.com/_vti_bin/wopi.ashx/files/9c5d0d7077aa43e9a9538c02deb57580?access_token=eyJ0eXAiOiJKV1QiLCJhbGciOi
The ULS Logs on my Office Web Apps server gives me this:
Error message from host: Verifying signature failed, host correlation:    d197d187-ef9d-42f6-ae4f-c4b8199c1078
WOPICheckFile,WACSERVER FileNotFound
WOPI CheckFile: Catch-All Failure [exception:Microsoft.Office.Web.Common.EnvironmentAdapters.FileUnknownException: WOPI 404
Any idea what may have caused this issue all of a sudden?
Thank you.
Yoshi

Hi Waqas
Thanks for your help with this. I had a look at both posts, the URL works fine from the WAC server and I am not using a System account to test docs.
Also, this is a production site that is accessible over the Internet, so we are using https therefore the WOPIZone is external-https.
Issue #3 in the above blog link does not reflect the same error I see on my servers.
I also had a look at the information in this link: http://technet.microsoft.com/en-us/library/ff431687.aspx#oauth
Problem: You receive a "Sorry, there was a problem and we can't open this document" error when you try to view an Office document in Office Web Apps.
If you added domains to the Allow List by using the
New-OfficeWebAppsHost cmdlet, make sure you’re accessing Office Web Apps from a host domain that’s in the Allow List. To view the host domains in the Allow List, on the Office Web Apps Server open the Windows PowerShell prompt as an administrator and run
the Get-OfficeWebAppsHost cmdlet. To add a domain to the Allow List, use the
New-OfficeWebAppsHost cmdlet.
I have not added any domains to the Allow list so this did not help either. Should I add the domain?
Any further help with this is much appreciated.
Thanks again.
Yoshi

I am getting error when hovering on document in sharepoint online "sorry there was a problem and we can't open this document.If this happens again, try opening the document in Microsoft Word"

I am getting error when hovering on document in sharepoint online "sorry there was a problem and we can't open this document.If this happens again, try opening the document in Microsoft Word".I am sure that document is not corrupted and
all. something it showing the preview and sometimes it throwing this error. I hope this error is intermident. When clicking on the link also it throws this error but on refreshing it working fine. I dont know why it is happening. Please helpme to resolve
this issue.

Hi Waqas
Thanks for your help with this. I had a look at both posts, the URL works fine from the WAC server and I am not using a System account to test docs.
Also, this is a production site that is accessible over the Internet, so we are using https therefore the WOPIZone is external-https.
Issue #3 in the above blog link does not reflect the same error I see on my servers.
I also had a look at the information in this link: http://technet.microsoft.com/en-us/library/ff431687.aspx#oauth
Problem: You receive a "Sorry, there was a problem and we can't open this document" error when you try to view an Office document in Office Web Apps.
If you added domains to the Allow List by using the
New-OfficeWebAppsHost cmdlet, make sure you’re accessing Office Web Apps from a host domain that’s in the Allow List. To view the host domains in the Allow List, on the Office Web Apps Server open the Windows PowerShell prompt as an administrator and run
the Get-OfficeWebAppsHost cmdlet. To add a domain to the Allow List, use the
New-OfficeWebAppsHost cmdlet.
I have not added any domains to the Allow list so this did not help either. Should I add the domain?
Any further help with this is much appreciated.
Thanks again.
Yoshi

I have an MS word doc saved from a Macbook in my flash drive. Now i want to print this from an IBM compatible laptop. problem is -- I can't access the file. Please help.

I have an MS word doc saved from a Macbook Pro on m flash drive. Now i want to print
th same doc from an IBM Compatible laptop. Problem is, I can't access the file. Please help.

I suggest you post your question on Microsofts own forums for their Mac products as it's their software you're having issues with:
http://answers.microsoft.com/en-us/mac

I wanted to erase my file,cause I hv about 65 G in my user disk, but I can't open my file. need help

I wanted to erase my file,cause I hv about 65 G in my user disk, but I can't open my file. need help

The advice you've received previously seems pretty solid, so let's troubleshoot the problem.
evefromOz wrote:
PLease help tech unsavvy struggler. After a grey screen and damaged HD that will not repair I was advised to copy my HD and Leopard installation to a new drive, then erase the HD and reinstall. But now can't open anything as my password wont work anymore.
Let's concentrate on this portion of text only.
Gray screen: usually means non-woriking or uninstalled HD
Won't repair: makes perfect sense, since you no longer have access to HD
Advised to copy HD and Leopard installation to a new drive, then erase the HD and reinstall: This is the most important text. It seems you don't use a backup drive. And since your HD is damaged/not working, you need to do the following: (1) remove the faulty drive, (2) install the new drive, (3) when you turn on your MBP, you may need to erase the newly installed HD, and this is where you have the problems. Describe, in detail, what's happening on your MBP screen. Is it still gray? What message are you getting? Where is it asking you for a password, and when?
I'm intereste: since your MBP drive is dead, how are you accessing this forum?

HT5361 I can't shut down my computer because it says mail is open. It says to close mail and continue shut down. Problem is I can't open or close mail now. Can't shut down my computer at all. What can I do?

I can't shut down my computer because it says mail is open. It says to close mail and continue shut down. Problem is I can't open or close mail now. Can't shut down my computer at all. What can I do?

If you cannot get mail to quit/force quit, you can always remove power from your Mac.
NOTE: removing power is a bad idea, and can result in data loss, but sometimes it is the only thing left to do.
Press and hold the power button for 5 to 10 seconds, and the Mac will power off.
When you power back on, the Mac should reboot.

I have PSD cc, had cs6 ex I did update, can't open ANY files, reinstalled, same..dead programs

I work in PSD cs6 ex constantly, recently i updated to cc. Today I can't open any file, Recent, old, make a new, open from library etc, NOTHING will open, i request a file, programs act like they are deaf. They arent locked up, just dont open or create files. Everything on my com is updated. I uninstalled and reinstalled and same. Also I no longer can install cs6 just CC.

Even the term "I request a file" is ambiguous.
Please provide more detailed information. Ideally, show some screen grabs showing what you are seeing, and identify just what isn't working.
Best advice, based on no specific information provided, is to uninstall using the Adobe Creative Cloud Cleaner Tool / process to really get everything cleaned up, then reinstall.
http://www.adobe.com/support/contact/cscleanertool.html
-Noel

I changed my HD "C". After reinstalling P Element 2 I got a problem. I can't open Photoshop Element. Error message is "Your working disc is full" But I have 61Go free on "C" HD and more than 1To free on "D" disc.

I changed my HD "C". After reinstalling P Element 2 I got a problem. I can't open Photoshop Element. Error message is "Your working disc is full" But I have 61Go free on "C" HD and more than 1To free on "D" disc.

Try resetting the pse 2 preferences and see if that clears things up.
reset preferences
Press and hold down the Shift+Ctrl+Alt keys just after starting the launch of pse 2
Keep holding the keys down until you get a dialog asking if you want to Delete the Adobe Photoshop Elements Settings File
Press Yes

Garage Band Problem: I can not open my existing files on Garage Band. They appear in a light gray. I can only open recent files. How do I open the existing files?

I would like help opening my existing files in Garage Band? I recorded 22 songs earlier this month which I want to edit, but I can not open these files.
The only files I can open are the more Recent files.
Please advise me what to do?
Thanks,
Bonnieta

It's not an apple solution but you can try MailRaider by 45 RPM software. I have not used it personally but it was one of the hits that came up when I did a google search for .msg on Mac.
Hopefuly the link posts but if not then just head over to macupdate and do a search for MailRaider
http://www.macupdate.com/app/mac/31845/mailraider
Hope this helps.

Error message: "Dreamweaver can't open .jpg files"

I'm using DW 8, and I have installed the 8.0.2 update. I'm
having trouble inserting certain JPG images into a site. I get an
error message pop-up that states "Dreamweaver can't open .jpg
files". It will allow me to insert some jpg files, but not all of
them. I've tried drag & drop and going through the Insert menu.
The files are not large at all. Doesn't appear to be any problem
with png's or gif's. It's incredibly frustrating. Anyone have any
suggestions? TIA.

> why was i taught that all my web images need
> to be in 72dpi if it doesn't really matter?
most people suggest 72 because it was an old standard with
the early
macintosh DTP programs. For web use it's easier to
standardize on it because
when you make an image, you have to put ~some~ number in the
resolution box
and it might as well be 72 as any other number. It simplifies
moving image
files around in different applications if they are all the
same resolution.
For display in a browser, these will all have the same file
size and display
size in a web page:
600x600 pixels at 1dpi
600x600 pixels at 72dpi
600x600 pixels at 6000dpi
It's when they are used in other applications or when a
direct url like
/photos/1.jpg is printed out that they may display in the
resolution, not
the pixel dimension.
I came across a page once where the designer always saved his
images with a
resolution of 6000 dpi or some other odd number because he
thought that if
people dragged the image off the page to save it- most of
them wouldn't be
able to resize it. or some other idiot reason maybe.
Alan
Adobe Community Expert, dreamweaver
http://www.adobe.com/communities/experts/

Can't open PNG files in Photoshop CS5...??

I'm seeing lots of threads with this problem but none of them seem to have an answer.
For some reason right now when I try to open a PNG file in Photoshop it just crashes. I end up with a neverending "hour glass".
I had all of my website project directories on a network share. As I'm no longer sharing all of these files with an office of people I decided to move all of these project files back to my own local machine. Ever since I've done that I can't open PNG files in Photoshop anymore.
Any information on what could have caused this, or more importantly, how to fix it would be greatly appreciated. Thanks!

I was able to edit PNG files just fine up until today, and the only thing I've done is move the files from the network share to my local hard drive.
Any PNG, large or small won't work right now. All of the other threads I see where people are talking about this say it's happening with their GIF files, too. I just tried one here and the same thing happened. From within Photoshop I did File -> Open, browsed to my image directory and the moment I clicked on one of the GIF files it locked up.
So yeah, I'm certain it's isolated to my machine right now. I just have no idea at all what could possibly be causing this. The other threads are mentioning netework shares, too, but usually still trying to open over the network. In my case it was working fine when I did it over the network, but now that I'm opening local files it's failing.

Some clients Can't open XLSX files in Libraries using template.dotx but can open xlsx files in libraries using template.doc

If I create a new library using any Excel/Word template - DOC, DOTX, XLS, XLTX and then upload a XLSX document (or docx) then some of my clients experience issues opening the document. My work around in the past has been to resave the document
as XLS or DOC. Interestingly Old Libraries (Libraries using template.doc) don't have a problem with xlsx or docx documents. (This only works because most of the clients experiencing the problem only open a few documents and we only have to
resave a few documents. I don't know why these clients have this problem though.)
We are now testing a new Terminal Server implementation. One with OpenOffice instead of Microsoft Office. We can't open xlsx files on new libraries but can on old libraries. (docx files are not a problem though) I found a couple of
work arounds.  One work around is to click on the down arrow by the document name and select "Edit in Excel" which fails, but then clicking on the document name after will then prompt you to Open/save the document. Clicking on Open
successfully opens the document in OpenOffice. (So rather tedious for the users but nothing has to be changed to make it work.)
The other option is to create a template from one of the libraries that is working and then use it to create a new library and save my documents to the new library. Then I'm prompted to Open/Save the xlsx documents in the library.  This
option is less tedious for the user but then I have to go through and recreate any libraries using template.dotx. Creating a new library using the standard Document Library option and selecting Word or Excel 2003 does not resolve the issue - it has to
be created from a template created from an existing library that works in the Terminal Server implementation.
My boss is opting for the latter option unless I can come of with an alternative that doesn't mean additional steps for the users. Training is an issue because most of the Terminal Server users are shop floor workers.
My question is, is there a patch or fix that addresses this issue or any other work arounds that would be less work?
Additional Info: Our Sharepoint implementation is the Enterprise version is installed but we do not have the Excel related Features activated (and these can't be activated due to licensing). I'm not sure if that matters or not but it is
a different configuration from how most SharePoint installations are configured. SP1 is installed. I have not installed any recent CU's. Versions I see in Patch Status screen include 14.0.6029.1 (primarily) with some additional features
reporting 14.0.6105.5, 14.0.6107.5, 14.0.6112.5 and 14.0.6114.5.
Nancy Forbes

We have tried a couple of additional things.
We uninstalled OpenOffice and are testing LibreOffice. I also installed CMIS from the SharePoint Administrator's toolkit, added the solution, and deployed it to my sites. The "Producer" feature is activated on the site I am testing with.
I created a new library and posted some docx, doc, and xlsx files to it. All files can be opened as Read-only from the Library list. The only way I have found that I can edit the files is to Open the Library with Explorer.   I then deactivated
the producer feature and tested opening the SharePoint documents from Explorer and it worked the same.
So am I misunderstanding what the CMIS Producer feature is for?
Nancy Forbes

The ask me for an viewer can't open an file

The ask me for an viewer can,t open an file!!

I am having the same problem. In my hotel when I connect my laptop a screen will pop up and you have to hit the button "I Accept Terms". However I can't do that with the ATV. I called the internet provider and they said they could not help me. Any ideas? Do you think the guy just doesn't know what he can do for me? I am thinking I will call later and hope to get a different technician who might know how to help connect me.

#3125 error. I can not open the file

We work on a Mac and a Win machine. We share the files via a NAS. We now encounter the problem that the muse-site saved by the Win machine can no longer be openend by the Mac. (#3125 error. I can not open the file). The only option to continue is to work via the Win machine.... ;-((( Please give us a solution. Ed

A 3125 error indicates the operating system returned an error when Muse attempted to open the file.
It's highly unlikely there's anything wrong with the file. If you haven't already confirmed, if you copy the file to the Mac's local drive it will open fine.
I'm suspicious of file/folder permissions. Is it possible the account used to mount and write to the NAS from Windows has different user permissions than the account that's attempting to read it on the Mac? I could theorize a 3125 error might occur if one user with the necessary permissions wrote a file to the NAS and then a second user with insufficient permissions attempted to open it.
Also, two users cannot simultaneously open the same .muse file on the NAS. Is that what's being attempted in this case? Muse goes to great lengths to attempt to prevent this and should put up an error about the file already being open in another copy of Muse. However, how that's detected is dependent on OS APIs that have subtly different behaviors on different servers and server protocols.

Same QT X Problem different Cause: Can't open QT Files

Similar Messages

Maybe you are looking for