TS1277 "iPhoto was unable to connect to Photo Stream" error after upgrading to mountain lion

Has anyone gotten this error after upgrading to mountain lion on a computer that already had a user setup on it?
My iphoto was working with photostream and now it will not connect at all.
I ran fix disk permissions and once it showed up in iphoto, photostream was loading and then it disappeared again.
help!

FWIW I fixed mine when I realised I'd probably downloaded iPhoto using an AppleID from the App Store but logged into iCloud with a different AppleID. I deleted iPhoto and it's related files (but not the iPhoto Library) using CleanApp, entered the App Store with my usual AppleID and downloaded iPhoto again. Once the App Store, the downloaded iPhoto and iCloud logins were the same iPhoto Stream worked again.

Similar Messages

Error enabling photo stream "iphoto was unable to connect to Photo Stream"

Whenever I try to enable Photo Stream, it times out after awhile, and I get the following error: "iPhoto was unable to connect to Photo Stream." (see below [1]). I "tcpdump" shows that the computer is trying to open connections to akamai (unrelated?) but not apple. I am using iPhoto 9.2 build 626.
There is one oddity in this scenario : I have one iCloud account that I am trying to use between three computers. I was able to register iPhoto on my mac book pro, but it is failing on my second.
thanks in advance,
-tom
08:26:35.984082 STP 802.1d, Config, Flags [none], bridge-id 8000.98:fc:11:54:7a:9e.8002, length 35
08:26:37.417858 ARP, Request who-has dd-wrt (Broadcast) tell 192.168.6.122, length 46
08:26:38.032082 STP 802.1d, Config, Flags [none], bridge-id 8000.98:fc:11:54:7a:9e.8002, length 35
08:26:39.977873 STP 802.1d, Config, Flags [none], bridge-id 8000.98:fc:11:54:7a:9e.8002, length 35
08:26:42.025748 STP 802.1d, Config, Flags [none], bridge-id 8000.98:fc:11:54:7a:9e.8002, length 35
08:26:42.435600 ARP, Request who-has dd-wrt (Broadcast) tell 192.168.6.122, length 46
08:26:43.971461 STP 802.1d, Config, Flags [none], bridge-id 8000.98:fc:11:54:7a:9e.8002, length 35
08:26:46.019515 STP 802.1d, Config, Flags [none], bridge-id 8000.98:fc:11:54:7a:9e.8002, length 35
08:26:47.453197 ARP, Request who-has dd-wrt (Broadcast) tell 192.168.6.122, length 46
08:26:47.965198 STP 802.1d, Config, Flags [none], bridge-id 8000.98:fc:11:54:7a:9e.8002, length 35
08:26:49.606268 IP 192.168.6.122.filenet-rmi > 239.255.255.250.ssdp: UDP, length 339
08:26:49.708805 IP 192.168.6.122.filenet-rmi > 239.255.255.250.ssdp: UDP, length 348
08:26:49.811498 IP 192.168.6.122.filenet-rmi > 239.255.255.250.ssdp: UDP, length 379
08:26:49.914098 IP 192.168.6.122.filenet-rmi > 239.255.255.250.ssdp: UDP, length 405
08:26:50.016310 IP 192.168.6.122.filenet-rmi > 239.255.255.250.ssdp: UDP, length 401
08:26:50.017171 STP 802.1d, Config, Flags [none], bridge-id 8000.98:fc:11:54:7a:9e.8002, length 35
08:26:50.118847 IP 192.168.6.122.filenet-rmi > 239.255.255.250.ssdp: UDP, length 401
08:26:50.221214 IP 192.168.6.122.filenet-rmi > 239.255.255.250.ssdp: UDP, length 393
08:26:51.958833 STP 802.1d, Config, Flags [none], bridge-id 8000.98:fc:11:54:7a:9e.8002, length 35
08:26:52.368490 ARP, Request who-has dd-wrt (Broadcast) tell 192.168.6.122, length 46
08:26:54.006909 STP 802.1d, Config, Flags [none], bridge-id 8000.98:fc:11:54:7a:9e.8002, length 35
08:26:55.004001 IP susans-pc.52389 > a173-223-237-54.deploy.akamaitechnologies.com.https: Flags [.], seq 187854:189302, ack 103254, win 65535, options [nop,nop,TS val 1073825952 ecr 2280611493], length 1448
08:26:55.004213 IP susans-pc.52389 > a173-223-237-54.deploy.akamaitechnologies.com.https: Flags [.], seq 189302:190750, ack 103254, win 65535, options [nop,nop,TS val 1073825952 ecr 2280611493], length 1448
08:26:55.004264 IP susans-pc.52389 > a173-223-237-54.deploy.akamaitechnologies.com.https: Flags [P.], seq 190750:191283, ack 103254, win 65535, options [nop,nop,TS val 1073825952 ecr 2280611493], length 533
08:26:55.004415 IP susans-pc.52389 > a173-223-237-54.deploy.akamaitechnologies.com.https: Flags [P.], seq 191283:191688, ack 103254, win 65535, options [nop,nop,TS val 1073825952 ecr 2280611493], length 405
08:26:55.035678 IP a173-223-237-54.deploy.akamaitechnologies.com.https > susans-pc.52389: Flags [.], ack 189302, win 4116, options [nop,nop,TS val 2280641050 ecr 1073825952], length 0
08:26:55.053470 IP a173-223-237-54.deploy.akamaitechnologies.com.https > susans-pc.52389: Flags [.], ack 190750, win 4116, options [nop,nop,TS val 2280641068 ecr 1073825952], length 0
08:26:55.060158 IP a173-223-237-54.deploy.akamaitechnologies.com.https > susans-pc.52389: Flags [.], ack 191283, win 4116, options [nop,nop,TS val 2280641074 ecr 1073825952], length 0
08:26:55.066460 IP a173-223-237-54.deploy.akamaitechnologies.com.https > susans-pc.52389: Flags [.], ack 191688, win 4116, options [nop,nop,TS val 2280641081 ecr 1073825952], length 0
08:26:55.209380 IP a173-223-237-54.deploy.akamaitechnologies.com.https > susans-pc.52389: Flags [P.], seq 103254:103691, ack 191688, win 4116, options [nop,nop,TS val 2280641223 ecr 1073825952], length 437
08:26:55.209522 IP susans-pc.52389 > a173-223-237-54.deploy.akamaitechnologies.com.https: Flags [.], ack 103691, win 65535, options [nop,nop,TS val 1073826154 ecr 2280641223], length 0
08:26:55.952463 STP 802.1d, Config, Flags [none], bridge-id 8000.98:fc:11:54:7a:9e.8002, length 35
08:26:57.386190 ARP, Request who-has dd-wrt (Broadcast) tell 192.168.6.122, length 46

Good catch, nifmus. I'm kicking myself for not checking system.log earlier! I have very similar messages in mine.
By any chance is your Library folder (or part of it) relocated to a separate disk? Or your entire home folder? I have part of my Library folder on a SSD for speed, but my home folder and some of the larger Library subdirectories are on a regular disk because they wouldn't fit on the small SSD. It's all tied together with symbolic links, and without problems... until Photo Stream came along and didn't like it.
I knew that sandboxd was involved somehow, but your post prompted me to focus on it. It's definitely the problem here. I found the following sandbox profile file inside the iPhoto application bundle:
/Applications/iPhoto.app/Contents/Library/LoginItems/PhotoStreamAgent.app/Conten ts/Resources/PhotoStreamAgent.sb
Inside this file are a bunch of definitions to control what PhotoStreamAgent is allowed to do. There are a bunch of lines under an allow-file-write* declaration which should allow PhotoStreamAgent to write to the above files listed in your log. Lines such as:
(home-regex #"/Library/Application Support/iLifeAssetManagement")
(home-regex #"/Library/Preferences/com\.apple\.iLifeAssetManagement\.crash\.plist(\.[^/]+)? $")
And many others. In my case, I suspect that the problem may be related to the fact that the final absolute path of those files may differ from what you'd get if you just substituted my home directory in for "home-regex" since I have stuff relocated around. Although since I was able to get it working with a blank home directory, also put in place via a symbolic link (so the final path differs), I'm not 100% sure of this.
What I do know right now is that there is a quick "hack" that fixed it for me. I don't like the hack and would strongly recommend against it, because it's likely to break the next time there's a software update for iPhoto. But it works until I can find a permanent solution.
To make it work, I edited the above file and changed the second line from "(deny default)" to "(allow default)". This, of course, defeats the whole purpose of the sandbox by allowing PhotoStreamAgent to do anything it wants, but it also allows stuff that is really supposed to be allowed but fails anyway for us.
If you want to try this, it helps to be familiar with the unix underpinnings of OS X. There's probably a way to do it in the normal graphical user interface, but as a longtime unix guy, I just jumped to the command line and did a "sudo vi (that long filename)". To do it via the gui method, you'll have to navigate to that folder in Finder (quickest way is to hit Cmd-Shift-G and copy/paste the path, or right-click iPhoto and "Show Package Contents", then drill down to the file), edit the file, save a copy (because you don't have permission to modify it), then copy the new version over the old (it will ask for an admin password).
Again, I don't recommend this because it's likely to break in the future and defeats the security that Apple intended with the sandbox, but it's a quick fix. I'll continue to investigate as I have time, trying to find out precisely what's causing the failure with the default sandbox profile.

IPhoto was unable to connect to photo stream

When I try to enable Photo Stream I get the error message that is the title of this post. How do I fix this?

Hi LN,
It's iPhoto 9.2.1
In iCloud System Preference I selected the Photo Stream button but when I go to iPhoto to enable it there it fails with the message "unable to connect to Photo Stream" and when I go back to iCloud System Preference I find that the button has been UNselected.
Yes, it was working happily on all my devices. The problem cropped up after I did a reset on my iPhone. I don't know what that has to do with it, though, because both it and my iPad are happily connected to Photo Stream and pics I take with my phone show up on my iPad.
Thanks!

Aperture was unable to connect to Photo Stream

Aperture was unable to connect to Photo Stream. Help!

That didn't work for me. However I found an alternate fix. You just need to move ~/Library/Application Support/iLifeAssetManagement to the trash and then reboot, and it should work.

IPhoto says "unable to connect to Photo Stream"

So I just re-did my OS on my iMac, so everything was started from a clean slate.
I started adding user accounts, and had no problems whatsoever setting up my iCloud and PhotoStream in iPhoto. With that being said, after creating my moms user account, adding her iCloud, iPhoto says "unable to connect to photostream"
Any thoughts or ideas as to why it would say that?
Thanks!

Everything is where it should be After giving up last night for a bit I went to bed and decided to try it again this morning and suprisingly it worked. This was after I left all the Keychain Access items with the AppleID deleted.
Thanks!

My internet connection stops after attempting to connect to the iTunes store after upgrading to Mountain Lion.

I have been unable to stay connected to my server since I have upgraded to Mountain Lion. I went to my local Apple Store and was able to download the latest software. I could not do that at home as the download would freeze. I brought my mac-pro notebook home and the same problem persists. While trying to match my music, iTunes fails to stay connected to the internet, the circle going round and round forever. Anyone else with the same or similar problem?

Same here (iPhone 5S). And a friend of mine has the same problem on his iPhone 5. I just installed the newest iOS update (7.1.2) and the problem persists. Although it seems to affect several people yet I can't find anything related to this on the web. If I really want deliberately to trigger the problem I just need to delete a song from the music app and the message will pop up for sure. I am also somewhat reluctant to do a full restore because frankly I expect the same outcome as the thread starter. So hopefully Apple will fix this soon. The main reason for me to buy a $ 800+ phone is to have a device that 'just works' but apparently that's long gone since iOS 7...

Unable to see certain folders on server after upgrading to mountain lion

Hello, I recently upgraded from lion to mountain lion on my MacBook Pro.
With lion I would connect to the server at work through finder under shared. Now with mountina lion, the server still shows up but when I connect to it only shows 3 folders there now when there are a lot more than that in there. I finally was able to connect to the folder I needed by hitting command + K and tryping out the path with smb.
The folder appears as an external disk icon when I connect to it like this so I guess maybe mountain lion recategorizes it as such and no longer displays it in finder when I connect to the server. Does anyone know how to fix this?

Hello nikkjazz. Welcome to the Apple Discussions!
The 802.11n AirPort Extreme Base Station (AEBSn) supports USB storage devices that use a block size of 512 bytes ... and is true whether the device is formatted for HFS+, FAT16 or FAT32. If yours is not, then it may explain why you can see the folders when the drive is directly attached to the Mac, but not so when connected to the AEBSn.

Iphot is unable to connect to photo stream

I recently updated my software, and now my Iphoto is unable to connect to photo stream. I enabled it in icloud, but nothing changed. Any suggestions?

I restarted my computer, and redid icloud settings

Aperture unable to connect to photo stream

Aperture 3 and Photostream were working fine for me but now it's not. I think this started happing after Apple replaced the logic board and video card in my 2008 iMac. I'm using Lion and all software is fully up to date. I have photostream enabled in the mac icloud settings and turn it on in the aperture settings. It spins for a while and then says "aperture was unable to connect to photo stream", which also then disables photo stream in the icloud settings. I have uninstalled Aperture and all prefrences files using AppCleaner and reinstalled. I have also done some tricks which others have reported as working, such as logging out of icloud and then logging in as a different user and deleting preference files from ~/Library. I have also tried creating a fresh Aperture library. So far nothing has worked. If I look at the console I get a crash log caused by the PhotoStreamAgent that contains the following:
Process:         PhotoStreamAgent [1239]
Path:            /Applications/Aperture.app/Contents/Library/LoginItems/PhotoStreamAgent.app/Con tents/MacOS/PhotoStreamAgent
Identifier:      com.apple.photostream-agent
Version:         2.0 (2.33)
Build Info:      PhotoAgent-2033000000000~12
Code Type:       X86-64 (Native)
Parent Process: launchd [132]
Date/Time:       2012-01-09 19:49:26.382 -0500
OS Version:      Mac OS X 10.7.2 (11C74)
Report Version: 9
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
objc[1239]: garbage collection is OFF
*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[NSKeyedUnarchiver initForReadingWithData:]: incomprehensible archive version (4294967295)'
*** First throw call stack:
          0   CoreFoundation                      0x00007fff955b9286 __exceptionPreprocess + 198
          1   libobjc.A.dylib                     0x00007fff93512d5e objc_exception_throw + 43
          2   CoreFoundation                      0x00007fff955b90ba +[NSException raise:format:arguments:] + 106
          3   CoreFoundation                      0x00007fff955b9044 +[NSException raise:format:] + 116
          4   Foundation                          0x00007fff93af46ef -[NSKeyedUnarchiver initForReadingWithData:] + 2611
          5   Foundation                          0x00007fff93b2364e +[NSKeyedUnarchiver unarchiveObjectWithFile:] + 129
          6   CoreMediaStream                     0x00000001001ccbb0 -[MSCupidStateMachine initWithPersonID:] + 380
          7   CoreMediaStream                     0x00000001001b117d -[MSSubscriber initWithPersonID:baseURL:] + 57
          8   CoreMediaStream                     0x00000001001b0916 +[MSSubscriber subscriberForPersonID:] + 178
          9   CoreMediaStream                     0x00000001001a7e5c -[MSMediaStreamDaemon _boundSubscriberForPersonID:] + 43
          10 CoreMediaStream                     0x00000001001a85d0 -[MSMediaStreamDaemon pollForSubscriptionUpdatesForPersonID:] + 48
          11 PhotoStreamAgent                    0x0000000100003c3b -[AssetManagementDaemon startDaemon] + 491
          12 PhotoStreamAgent                    0x00000001000036c7 -[AssetManagementDaemon run] + 151
          13 libdispatch.dylib                   0x00007fff9232b224 dispatch_once_f + 53
          14 PhotoStreamAgent                    0x0000000100002d8c +[AssetManagementDaemon run] + 124
          15 PhotoStreamAgent                    0x0000000100001f73 main + 67
          16 PhotoStreamAgent                    0x0000000100001f24 start + 52
terminate called throwing an exception
abort() called
When I switch to Aperture on my old black Macbook photostream works fine. I'm stumped and frustrated. Short of wiping my drive and reinstalling the OS, does anyone have any thoughts on this? Thanks in advance.
Spencer

Well if this just started happening since the iMac was worked on by Apple you should contact Support. You should still be under warranty for the repair so they should take care of it.
regards

Iphoto was unable to connect to iCloud photos on my mac. What should i do?

iPhoto was unable to connect to iCloud photos on my Mac. How do I solve this?

absolutely no idea sicne you provide no information
Best guess is to upgrade to iPhoto '11
Maybe if you provided some information including versions of iPhhoto and of the OS, details of exactly what you are doing, details of whathappens that keeps you from connection
LN

After upgrading to mountain lion i keep getting an error message saying my startup disc is full. it shouldnt be full because there is barely anything on there and i was running windows with bootcamp prior to this with no issues

after upgrading to mountain lion i keep getting an error message saying my startup disc is full. it shouldnt be full because there is barely anything on there and i was running windows with bootcamp prior to this with no issues. my computer now freezes and programs close randomly. The usual command for opening windows with bootcamp doesnt work. once in restarted my computer after it froze and it rebooted in windows automatically. i really just want to know if there is a way to take the upgrade off my laptop because it is very annoying.

Hi Memalyn
Essentially, the bare issue is that you have a 500GB hard drive with only 10GB free. That is not sufficient to run the system properly. The two options you have are to move/remove files to another location, or to install a larger hard drive (eg 2TB). Drive space has nothing to do with SMC firmware, and usually large media files are to blame.
My first recommendation is this: download and run the free OmniDiskSweeper. This will identify the exact size of all your folders - you can drill down into the subfolders and figure out where your largest culprits are. For example, you might find that your Pictures folder contains both an iPhoto Library and copies that you've brought in from a camera but are outside the iPhoto Library structure. Or perhaps you have a lot of purchased video content in iTunes.
If you find files that you KNOW you do not need, you can delete them. Don't delete them just because you have a backup, since if the backup fails, you will lose all your copies.
Don't worry about "cleaners" for now - they don't save much space and can actually cause problems. Deal with the large file situation first and see how you get on.
Let us know what you find out, and if you manage to get your space back.
Matt

After upgrading to Mountain Lion, launching iPhoto reboots MBP

After upgrading to Mountain Lion, when I go to launch iPhoto, my MBP re-boots. This happens every time I try to launch iPhoto. The re-boot has occured randomly when using Safari and iMovie. Looking for help.

I was hopeful thAt this would help, but it did not. Still experiencing the same behaviors.

IPhoto Library won't open after upgrade to mountain lion

One of my iPhoto libraries (stored on a WD Pasport Studio) won't open properly after upgrade to Mountain Lion 4oo5 open ok. One opens but disc symbol keeps spinning and Iphoto stops responding. Any ideas?

See if anything in here will fix it:
1. Hold down the Command and Option keys as you click the iPhoto icon.
The Photo Library First Aid window opens:

After upgrading to mountain lion, i find that my mail app does not have a "VIP" Tab. Was wondering if anyone else has this issue and what it is about?

after upgrading to mountain lion, i find that my mail app does not have a "VIP" Tab. Was wondering if anyone else has this issue and what it is about?

First, select sender(s) as VIPs. Then the VIP category will appear.
To select a sender as a VIP, open an email from that sender, then hover over their name and a star icon will appear to the left. Click the star, and that sender will be set as a VIP (and the category will appear in the pane on the left).

Connection issues after upgrade to Mountain Lion

Very strange internet connection problem here after upgrade to Mountain Lion.
I just upgraded MacBook (early 2009) to Mountain Lion. After upgrade, I'm having problems connecting to certain websites (ESPN, CNN, etc.), and I can't connect to the computer using LogMeIn.
BUT, I do have an internet connection. Skype works, Messages works, email works, some websites work. I tested using speedtest.net and it shows good download speed, but the upload speed is so slow that it can't even perform the test. A Windows PC on the same network works fine.
Next, I tested the MacBook on another wi-fi network at a coffee house, and everything works fine there!
So it might appear to be something wrong with the router? I have an Cisco (Linksys) E3200 and have upgraded to the latest firmware (1.0.4). But still doesn't work.
The firewall in Mountain Lion is turned off, and I temporarily turned off the firewall on the router and that didn't help, so doesn't appear to be any sort of firewall issue. I've never heard of an operating system being incompatible with a specific router anyway.
Can anyone thing of any setting or something in Mountain Lion that would causing internet connection problems with a specific router?

I don't know if this will 'fix' your problem, but have you tried the 10.8.5 Supplemental Update -> http://support.apple.com/kb/DL1686?
Clinton

TS1277 "iPhoto was unable to connect to Photo Stream" error after upgrading to mountain lion

Similar Messages

Maybe you are looking for