File couldn't be opened - Apple Configurator

I'm getting an error when Configurator runs; "The File Couldn't Be Opened", Configurator then closes itself.
I've attempted to uninstall both via the App Store and App Zapper and the restarted, while the offending dialogue is up I am unable to access any other functions in Configurator.
Any ideas?

I have looked and tried to do the other suggestions on this site. They all say to go to the ~/Library/Containers folder. I do not have a containers folder.

Similar Messages

HT200261 Configurator Error. Apple Configurator could not open your library.The file couldn't be opened because it isn't in the correct format.

I was using configurator without trouble. Unfortunately, my battery died and my computer went down. I plugged my computer in, restarted it and tried to open configurator. Now this is the error I am getting. Apple Configurator could not open your library.The file couldn’t be opened because it isn’t in the correct format. How do I fix this?

Thank you for responding. The number 2 after the file final cut events is temporary so I can copy it to another drive while I am working on this. . i got a new message that reads...
Final Cut Pro must restore or move corrupted databases before opening.

I can't open apple configurator

Hi, immediately after starting apple configurator I get a message showing "The file couldn't be opened". I tried reinstalling configurator and still get the same message. Any thoughts?

You might have a corrupt download package. Uniinstall the application, restart, delete the original download file, redownload, and reinstall.

Printing from Preview produces error message "The file couldn't be opened".

Hi,
Ever since the upgrade to OS X 10.8, I get the error message "The file couldn't be opened" each time I want to print from Preview. I just have to click "OK" and then everything prints fine, but if anyone knows how to get rid of this message, it would be even better!
I have run "Verify disk permissions" without success.
The system is on an SSD volume whereas my home volume is on an internal HD. But other users with (smaller) accounts residing on the system volume have the same problem.
Each time I open the print dialog, the following message appears in the logs:
com.apple.Preview.TrustedBookmarksService[2159]: Failure to de-serialize bookmark data file.
I removed files related to Preview in ~/Library/Preferences/
There is no *.plist file in ~/Library/Application Support/Preview
Thanks!

Pages 5.2 Mac OSX 10.9.2
Start Pages app
Create a blank document
File > Save or <Command>+S
Select Mac Device and find your user folder or favorite, Desktop (not iCloud)
Error: the file "Untitled.pages" couldn't be opened!?!
Repeat giving the document a different name and it works
Since when do we write error messages with "n't"?
Usually a well written error message offers a suggestion as to what you might do about it?
Since it says opened and I clicked on Save, there is a bug in there somewhere.
All I was trying to do today was copy and paste some text from a website into numbers spreadsheet
Both Edit > Paste options but the text in one cell so I tried to save it as a text file first to try and import the data
Text Edit does not have a text only export format so before loading Terminal and starting vi or emacs, I tried pages. I'll go try XCode's editor or my Windows 7 vm with notepad and openoffice
I miss the old Pages with the Appleworks importer, this one needs more Quality Assurance Testing IMHO
WWSJD "What Would Steve Jobs do?"

The file couldn't be opened because you don't have permission to view it

Everytime I time to open a PDF file in Preview I get the msg, the file couldn't be opened because you don't have permission to view it. I have checked the GET INFO and all permissions are correct. Does anyone know how to solve this problem?
Thank you.

Back up all data.
Quit the application, if it's running.
Triple-click anywhere in the line below on this page to select it:
~/Library/Containers/com.apple.Preview
Right-click or control-click the highlighted line and select
Services ▹ Reveal in Finder (or just Reveal)
from the contextual menu. A Finder window should open with a folder selected. If it does, move the selected folder—not just its contents—to the Desktop.
The folder you're moving has a name that begins with "com." It is not the subfolder named "Data" or anything else.
Launch the problem application and test. If it works now, delete the folder you moved. Otherwise, quit again, and put the folder back where it was, overwriting the one that may have been created in its place.
Caution: If you delete some or all of the contents of the selected folder, but leave the folder itself in place, the application may not launch. Deleting the folder will cause it to be rebuilt automatically.

What is this prompt? The required index.xml file is missing. "file" couldn't be opened.

What is this prompt? The required index.xml file is missing. "file" couldn’t be opened.

Helps if you tell us what version of Pages and something about the file.
Probably you have 2 versions of Pages on your Mac.
Pages 5 is in your Applications folder.
Pages '09/'08 is in your Applications/iWork folder.
You are alternately opening the wrong versions.
Pages '09/'08 can not open Pages 5 files and you will get the warning that you need a newer version.
Pages 5.01 can not open Pages 5.1 files and you will get the warning that you need a newer version.
Pages 5 can open Pages '09 files but may damage/alter them. It can not open Pages '08 files at all.
Once opened and saved in Pages 5 the Pages '09 files can not be opened in Pages '09.
Once opened and saved in Pages 5.1 files can not be opened in Pages 5.
Anything that is saved to iCloud is also converted to Pages 5 files.
All Pages files no matter what version and incompatibility have the same extension .pages.
Pages 5 files are now only compatible with themselves on a very restricted set of hardware, software and Operating Systems and will not transfer correctly on any other server software than iCloud.
Apple has removed over 95 features from Pages 5 and added many bugs:
http://www.freeforum101.com/iworktipsntrick/viewforum.php?f=22&sid=3527487677f0c 6fa05b6297cd00f8eb9&mforum=iworktipsntrick
Archive/trash Pages 5, after exporting all Pages 5 files to Pages '09 or Word .docx, and rate/review it in the App Store, then get back to work.
Peter

Problem: "the file couldn't be opened"

When I try opening up a gb file or creating a new song in garage band, I get a message that pops up saying "the file couldn't be opened". Why is this and what can I do to fix it? I uninstalled the program and reinstalled it already with no success

After 2 weeks of trying everything I could think of, I did one last permissions repair from the recovery drive (I'd tried it before so I wasn't expecting much), and voila! It worked...I was ready to take it in to an Apple Store after reading your post, but I'm glad I don't have to make an extra trip now, haha.
Thanks, and happy new year to both of you!

Error: "File couldn't be opened for writing" with CinemaDNG sequence

Using a Premiere Pro > After Effects workflow with my colorist.
I created a project in Premiere CS6 and used MOV transcodes because Premiere CS6 does not read CinemaDNG sequences. I do not have CC installed on my computer. My colorist, on his computer (we are both using Mavericks), imported the .prproj into AE CS6. We tried to replace MOV files with CinemaDNG sequences, and AE returned this error:
After Effects error: File couldn't be opened for writing: "[file path]". ( 3 :: 0 )
Normally when you replace footage with a CinemaDNG sequence in AE, Adobe Camera Raw pops open so you can make changes before the file is important. I have never seen this error before.
My colorist has CC installed as well as CS6, so we tried that instead.
Colorist opened the Premiere CS6 project in Premiere CC, creating a new Premiere CC project. Replaced MOV files with CinemaDNG sequences within Premiere CC with no error, project plays fine in Premiere CC. Finally! So we imported the new Premiere CC project in AE CC, and all linked CinemaDNG sequences appear as color bars (unlinked footage). When testing to import a CinemaDNG sequence, AE CC returned the same error as AE CS6.
So we tried opening the same CinemaDNG files in Photoshop CS6 and Photoshop CC to see if there was an error with Camera Raw. Both versions of Photoshop open the CinemaDNG files correctly in Camera Raw (version 8.3). So now we have CinemaDNG files functioning properly in Premiere Pro, Photoshop, but... not AE?
Tried replicating this on a second, Mountain Lion computer with both versions of AE, and returned the same issue.
CinemaDNG files from a different source DID open in AE CC and AE CS6 on both computers, which leads me to believe there is some kind of permissions/metadata issue in this particular set of CinemaDNG files I'm using that's causing problems for AE, but NOT Premiere Pro or Photoshop. Anyone experience anything like this?

try the "oddball problems" fix:
http://www.bulletsandbones.com/GB/GBFAQ.html#oddballprobs
(Let the page FULLY load. The link to your answer is at the top of your screen)

I can't seem to open (view) my photos. I get an error message that says "the file couldn't be opened because you don't have permission to view it. To view or change permission, select the item in the finder and choose File. Get info."

I can't seem to open (view) my photos. I get an error message that says "the file couldn't be opened because you don't have permission to view it. To view or change permission, select the item in the finder and choose File. Get info." I have never had this happen before? Thanks!

Try the following:
1 - launch iPhoto with the Command+Option keys held down and rebuild the library.
2 - Run Option #1, Repair Permissions.
OT

Cannot open a downloaded pdf file..."The file couldn't be opened because it isn't in the correct format."

I have had this problem several times lately: I cannot open a downloaded pdf file. The error message reads: "The file couldn't be opened because it isn't in the correct format." But, of course, it is a pdf file.

My MacBook Pro (2.5 Ghz Intel Core i5) is running OS X 10.9.4. Here is what happens when reading an online user manual that I want to save to the Desktop and read later as a PDF file on my iPad or phone. With Safari I will select "Export As PDF" and the file shows up on the desktop. Even after multiple trials, there will be a dialogue box indicating the file cannot be opened. If I check the file info, the size is "zero." Trying to save the file as a pdf using the Print menu yields the same results. I have tried both of these methods using Preview, Adobe Reader, and PDF Pen Pro. This strange behavior also occurred several weeks ago and I finally abandoned the effort. But when the same thing happens twice, it becomes an issue that needs to be resolved.

HT2506 Hello I'm unable to open any pdf's with preview window opens up with message file couldn't be opened because you don't have permission to view it (none of the pdf's have any security thanks if you can assist

Hello this week I'm unable to open any pdf's with preview, when I select to open a window opens up with message "file couldn't be opened because you don't have permission to view it" none of the pdf's have any security thanks if you can assist

Back up all data. Don't continue unless you're sure you can restore from a backup, even if you're unable to log in.
This procedure will unlock all your user files (not system files) and reset their ownership and access-control lists to the default. If you've set special values for those attributes on any of your files, they will be reverted. In that case, either stop here, or be prepared to recreate the settings if necessary. Do so only after verifying that those settings didn't cause the problem. If none of this is meaningful to you, you don't need to worry about it.
Step 1
If you have more than one user account, and the one in question is not an administrator account, then temporarily promote it to administrator status in the Users & Groups preference pane. To do that, unlock the preference pane using the credentials of an administrator, check the box marked Allow user to administer this computer, then reboot. You can demote the problem account back to standard status when this step has been completed.
Triple-click the following line to select it. Copy the selected text to the Clipboard (command-C):
{ sudo chflags -R nouchg,nouappnd ~ $TMPDIR.. ; sudo chown -R $UID:staff ~ $_ ; sudo chmod -R u+rwX ~ $_ ; chmod -R -N ~ $_ ; } 2> /dev/null
Launch the Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
Paste into the Terminal window (command-V). You'll be prompted for your login password. Nothing will be displayed when you type it. You may get a one-time warning to be careful. If you don’t have a login password, you’ll need to set one before you can run the command. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator.
The command will take a noticeable amount of time to run. Wait for a new line ending in a dollar sign (“$”) to appear, then quit Terminal.
Step 2 (optional)
Take this step only if you have trouble with Step 1 or if it doesn't solve the problem.
Boot into Recovery. When the OS X Utilities screen appears, select
Utilities ▹ Terminal
from the menu bar. A Terminal window will open.
In the Terminal window, type this:
res
Press the tab key. The partial command you typed will automatically be completed to this:
resetpassword
Press return. A Reset Password window will open. You’re not going to reset a password.
Select your boot volume ("Macintosh HD," unless you gave it a different name) if not already selected.
Select your username from the menu labeled Select the user account if not already selected.
Under Reset Home Directory Permissions and ACLs, click the Reset button.
Select
 ▹ Restart
from the menu bar.

"The File couldn't be opened"

I am getting so frustrated because the farthest I can get on garageband is opening up the main screen. When I try to open a previous song or iPhone ringtones I get the message "The file couldn't be opened" be no further explanations. Someone please help!

well it is actually when I am just trying to open an empty project that hasn't been started or create a new one

Apple configurator says "The file couldn't be opened"

When starting Apple Configurator and it syas that message it then immediately closes. I have deleted, cleaned out the trash, and reinstalled. Still gives me the same message when starting up the new copy. Any ideas? What file is it missing? Can it be replaced?

I have looked and tried to do the other suggestions on this site. They all say to go to the ~/Library/Containers folder. I do not have a containers folder.

'The file couldn't be opened' & other 10.0.1 issues

I'm having a number of issues with FCPX 10.0.1 including this one:
This has only happened since the update. I am also experiencing problems with skimming in the timeline as well as problems with clips disappearing and then reappearing. 10.0.1 actually seems less stable than than 10.0.0.
I am running a brand new i7 and the stability of FCPX is causing me huge issues. Anyone else having problems with the updated version?

Just updated to Configurator 1.2.1 and it still will not open on Network accounts. I did get somewhat of a migration screen after I deleted ~/Library/Containers/com.apple.configurator. Be fore that I just get "Failed to save. Unknown store type, format, or version."
Log snips:
11/2/12 9:15:37.450 AM Apple Configurator: CoreData: error: (3) access permission denied
11/2/12 9:22:54.821 AM Apple Configurator: ERROR - 188ms Couldn't migrate main store: Error Domain=NSCocoaErrorDomain Code=134000 "Failed to save. Unknown store type, format, or version." (/SourceCache/AppleConfigurationUtility/AppleConfigurationUtility-169/Applicati on/Models/CDCoreData.m:354)

Can't save a file; error message says file couldn't be opened

Using Pages '09 ver. 4.3 and OSX 10.8.4
When I try to save a new document in pages, I get an error message that says "the file 'xxxx.pages-tef" couldn't be opened.
How can I fix this so that I can start saving files again?

Pages 5.2 Mac OSX 10.9.2
Start Pages app
Create a blank document
File > Save or <Command>+S
Select Mac Device and find your user folder or favorite, Desktop (not iCloud)
Error: the file "Untitled.pages" couldn't be opened!?!
Repeat giving the document a different name and it works
Since when do we write error messages with "n't"?
Usually a well written error message offers a suggestion as to what you might do about it?
Since it says opened and I clicked on Save, there is a bug in there somewhere.
All I was trying to do today was copy and paste some text from a website into numbers spreadsheet
Both Edit > Paste options but the text in one cell so I tried to save it as a text file first to try and import the data
Text Edit does not have a text only export format so before loading Terminal and starting vi or emacs, I tried pages. I'll go try XCode's editor or my Windows 7 vm with notepad and openoffice
I miss the old Pages with the Appleworks importer, this one needs more Quality Assurance Testing IMHO
WWSJD "What Would Steve Jobs do?"

File couldn't be opened - Apple Configurator

Similar Messages

Maybe you are looking for