HT5132 Aperture mobileme migrating message problem

I keep getting this message every time I open Aperture. How can I get it to stop?

That is not the normal behaviour. By now Aperture should have stopped nagging, since you cannot download your content any longer.
When the message appears, click the "Learn more" button, not the o.k. button.
In Aperture, open the Preferences and go to the "Web" tab. If you still see "MobileMe" in the "Accounts" pane, remove the account.
If you do not see "MobileMe" in the "Accounts" pane, but Aperture is prompting you to migrate nevertheless, quit Aperture, open your User Library and clear the Caches (the library is hidden:
Use the Finder's "Go" menu to open it: Click "GO" and hold down the "Options" key, until "Library" appears in the drop-down menu - select it) and navigate to the "Caches" folder.
Remove the file "mmsunset.plist" to the Desktop. This file tells Aperture how long to prompt for "MobileMe". Maybe it is corrupted.
If this still does not suffice remove your preferences from the user library (you home folder ~
/Library/Preferences/com.apple.Aperture.plist), and try again. After removing the preferences file, you will have to reset all preferences you set using the preferences panel however.
Good Luck
Léonie

Similar Messages

HT5132 Aperture, MobileMe locking

No matter what I do, the process never completes and Aperture locks up. Oddly, I have no web MobileMe Gallery and never have. Online advice that I found does not solve the problem. How do I totally get rid of MobileMe and get my Aperture back?

Probably MobileMe is enabled in the Aperture Preferences Web panel.
Quit (if necessary, force quit) Aperture.
Before you launch it again, disable your internet connection - disable Wi-Fi or disconnect your ethernet.
Then launch Aperture.
From the Aperture main meu bar select: File > Web Accounts > Edit Web Accounts
In the "Web" panel select "MobileMe" and press the "-" button.
Quit Aperture.
Now you can enable your Internet Connection again.
As a precaution: If you force quit Aperture, rebuild your Library:
Repairing and Rebuilding Your Aperture Library
Regards
Léonie

IPhoto - MobileMe gallery subscription - problem with password-protected

I am having a peculiar problem with subscribed galleries from MobileMe in iPhoto 08 and iPhoto 09. For galleries that have password-protection enabled, the full URL of the gallery subscription feed is pulled through as the Subscription title instead of the gallery title.
For example "http://gallery.e.com/ACCOUNT-NAME/XXXXXX/?webdav-method-truthget&depth=infinit y&feedfmt=atom....
This doesn't occur for public MobileMe galleries. The title of the gallery comes across and the URL of the subscription is hidden.
Anyone having similar problems? Local Genius Bar couldn't help and assumed it was just a bug, but it doesn't seem to be typical of Apple.
As an aside, it would also be nice to have these feed subscriptions behave similarly to the way RSS subscriptions work in Mail, with the ability to select how often the feed is queried and indicate the number of new items. This would alert users of changes to feeds.
Joe

Upon further research, it appears that this problem occurs when publishing from either iPhoto or Aperture to MobileMe. The problem seems to be when a gallery is published and one chooses not to have the gallery appear on the main gallery page (hidden). It seems to have nothing to do with whether or not one protects the gallery with a password.
So, Apple, if you are listening, can you provide any information on how to have the title of the gallery come through when subscribing using iPhoto while at the same time not listing the gallery on the main MobileMe gallery page? This seems to be a fixable bug.

Aperture/MobileMe quality

I recently purchased Aperture and have created 2 MobileMe albums.
The problem I am having is the quality of the MM gallery. The pics look pretty bad. A lot of noise, artifacts, banding in the sky, etc. Also when I click on the photo info button in my gallery, all of the metadata is gone. No camera, no shutter, aperture etc. Another problem is under the file info it says the file size is only 75-145k.
I am not sure what exactly is going on. Is it an Aperture problem, or a MM problem that I can fix. Are there quality settings I can't find? It seems that it is uploading the thumbs only. I am at a loss.
I didn't have these problems with other galleries created in iPhoto 08, but that was done a while ago so I don't know if something changed in MM or what.
Thanks for any suggestions.

TyWahn wrote:
I recently purchased Aperture and have created 2 MobileMe albums.
The problem I am having is the quality of the MM gallery. The pics look pretty bad. A lot of noise, artifacts, banding in the sky, etc. Also when I click on the photo info button in my gallery, all of the metadata is gone. No camera, no shutter, aperture etc. Another problem is under the file info it says the file size is only 75-145k.
I am not sure what exactly is going on. Is it an Aperture problem, or a MM problem that I can fix. Are there quality settings I can't find? It seems that it is uploading the thumbs only. I am at a loss.
I didn't have these problems with other galleries created in iPhoto 08, but that was done a while ago so I don't know if something changed in MM or what.
Thanks for any suggestions.
Aperture and iPhoto compress the JPEGS even further as part of MobileMe integration. In the Gallery it is unavoidable. One way to get around it, you need to publish to Web Pages/Journals at high rez displays and default Preview JPEG settings.
Follow the instructions here:
http://www.apple.com/aperture/tutorials/#publishoutput-webgallery

MobileMe migration event corrupted my library!

I guess I agreed to let iPhoto do an automatic dump of all my mobileMe Gallery images into my iPhoto Library. I let the process run and then after a few days decided to look inside when I started thinking about this... Aren't MobileMe Gallery images smaller, more compressed jpegs than the originals in your local iPhoto Library? WIll this MobileMe migration overwrite your larger originals? I never found out, because I right away noticed that over 1800 of my images in this massive MobileMe event folder were all named the same name. Even many of my videos that were on the MobileMe server were renamed as this same jpeg name. These were not duplicates either. When looking in all my existing albums or Events from the past, indeed all the same photos I saw in the MobileMe event all now had the same wrong file name. I immediately panicked and restored my entire iPhoto Library from June 29th before this auto migration event was created. Problem solved. I hope my corruption was unique! However I still wonder for the rest of you- what happens to your original full quality images if you run this MobileMe Migration? I fear that your originals will be replaced by smaller more compressed jpegs that were generated when you published your images to the MobileMe Gallery.
When I restored the iPhoto library all iOS devices see the library as brand new, so now I have to rebuild iphoto libraries on 2 iPads, 2 iPhones, and an iPod.
DOn't open iPhoto while this is happening! I made that mistake and the entire mac crashed and now my iPad seems to be corrupted as well as all data in the bar chart in iTunes shows up as "Other"
But that is another story!

2 things I want to add. One is I rebooted my iPad and now it is continuing in its merry way to completly load my newly restored iPhoto library. It is not corrupted as I had feared.
Second thing is iPhoto Library size. I noticed that my libray was 110 GB after this MobileMe Migration, and the one I restored from last week is 90GB. I though all my images were overwritten by mobile me and not dublicated, but this must not be the case as my library grew by 20 gigs. However I could not FIND the original images in my events or albums that had the correct file names.
I am glad I restored. This MobileMe migration was a useless and dangerous thing for me to do and I am not sure why I clicked on it. All your Gallery images are already in your iPhoto Library most likely anyway! Unless others posted pics if you have friends/family who do that sort of thing.

Continuing the "status message problems" issue...

in response to ralph johns suggestion to delete the buddy list file from my library to solve the outdated status message problem...
RJ- haha.. i'm not sure i'm going to try the "beat it with a stick" approach quite yet.. i think i found out whats causing the problem. when i would use iChat on campus using our school's wireles, i didnt have the problem of outdated status messages. but when i come home, i do.. and i believe the reason is because i'm using a Belkin G Wireless router. although i do hard line, i'm almost positive this is the problem. i did some research online and it isnt one of the approved routers for iChat.
so is my only option to buy a new compatible router to solve the problem? or is there somewhere i can go that can tell me what ports to open for a belkin router?? we're getting close... i can feel it!!! haha thanks..
-brent

Hi Anders,
in order to quickly fix that problem, I would just adapt the provisioning function where the warning shows up and make sure that the function uError is called so that an error is created instead of a warning.
Are you using the SAP Provisioning Framework or a custom provisioning framework. Which repository are you using?
Best regards
Holger

Aperture, MobileMe, AppleTV...Which Forum?

Hopefully this forum will work for me...
Anyone else having issues with Aperture images published to MobileMe that don't show up on AppleTV? Or at least gives you trouble on AppleTV?
First of all the MobileMe albums don't show up UNLESS I publish an image via iPhoto. It's like iPhoto "pushes" the Aperture images through. When I publish one photo via iPhoto, my Aperture/MobileMe albums show up. Un-publish the iPhoto image and the Aperture albums disappear from AppleTV.
THEN..... when I get the Aperture/MobileMe albums to show up (because I published one from iPhoto), AppleTV won't allow me to view them because it keeps telling me the login-in formation is incorrect--but it's not. I have the albums protected and locked on MobileMe and that's why I have to enter it on AppleTV. Whatever, I cannot view my MobileMe albums on AppleTV at all, no matter what I do. I will also post to the other forums, but I wanted to see if anyone here is familiar with this issue.
I hope this makes sense. Any help, anyone?

Not 100% about this solution but from what I've read this could be one solution if it's more important to show the images on TV more immediately.
1. Eye-Fi cards all now have direct mode which enables them to automatically transmit jpeg (Connect X2) and jpeg / RAW (Pro X2).
2. If you had a Nikon D7000 with dual card slots, you could save a RAW file to one card for importing into Aperture later and save a jpeg to the Eye-Fi card slot for wireless distribution.
3. You can wirelessly send the jpegs to an iPad2 from the Eye-Fi card using Direct Mode.
4. With an iPad2 you can mirror the iPad's screen onto an Apple TV (the small black ones) and therefore as soon as the jpeg is sent to your iPad it can be viewed instantly and automatically on your Apple TV.
5. This should also work for jpegs if you have a D90 but I'm not too sure about what happens if you shoot RAW and jpeg on the D90.
It's a possible solution and food for thought anyway...
Clown Guy

"Blocked plug-in message" problem on my OS X 10.6.8. (Safari's 5.1.10). Any solutions for a non-techie (step 3 on Adobe Flash's instructions leads to dead end). Thanks.

"Blocked plug-in message" problem on my OS X 10.6.8 (Safari's 5.1.10). Any solutions for a non-techie (step 3 on Adobe Flash's instructions leads to dead end, i.e. product for sale). Thank you.

Prior to updating flash player, you must first uninstall all previous versions. Make sure you are downloading from the proper Adobe website = Adobe Flash Player Software
Flash Player Uninstaller
Repair permissions and restart your computer after the installations.

HT1349 Hi all,I have just purchased new iphone but have difficulty in completing the itunes download with message : problem with Windows installer package. A program run as part of the setup did not finish as expected.

Hi all,I have just purchased new iphone but have difficulty in completing the itunes download with message : problem with Windows installer package. A program run as part of the setup did not finish as expected.
Would appreciate help...its driving me up the wall!!

Perhaps let's first try updating your Apple Software Update.
Launch Apple Software Update ("Start > All Programs > Apple Software Update"). Does it launch and offer you a newer version of Apple Software Update? If so, choose to install just that update to Apple Software Update. (Deselect any other software offered at the same time.)
If the ASU update goes through okay, try another iTunes install. Does it go through without the errors this time?

I get message, Problem scanning. Something went wrong. Please try again.

My printer was working fine when scanning, but now I get a message:
Problem scanning. Something went wrong. Please try again. I turned my printer off, rebooted my computer...updated the printer from hp website...but nothing. I can see the document in preview, and I hear the scanner working. HELP!!

Hey there @leandermw , Welcome to the HP Forums
I understand you're having scanning problem with your Deskjet 2540, on Windows 8.1 and would like to help you.
I would first suggest that you run the Print and Scan Doctor, and choose "fix scanning" to see if the tool can correct the issue. Send me the results in your reply as well.
If you have the printer connected to a network, either wireless or ethernet, try power cycling the network devices:
Turn off the printer and computer and unplug the router for 1 minute (do not press any buttons on the router).
Plug the router back in and wait another minute, next turn on the printer and computer and try scanning.
You can also power reset the printer itself:
Press the Power button to turn on the product.
With the product turned on, disconnect the power cord from the rear of the product.
Unplug the power cord from the wall outlet.
Wait at least 15 seconds.
Plug the power cord back into the wall outlet.
Reconnect the power cord to the rear of the product.
If the product does not turn on by itself, press the Power button to turn it on.
Ensure the printer is plugged in directly to the wall outlet, avoiding power bars and surge protectors. This ensures the printer is receiving full power and may help greatly.
Try scanning from the HP scan software on your computer, and also make a copy from the front of the printer.
Write me back with the results
R a i n b o w 7000I work on behalf of HP
Click the “Kudos Thumbs Up" at the bottom of this post to say
“Thanks” for helping!
Click “Accept as Solution” if you feel my post solved your issue, it will help others find the solution!

Migration Assistant: Problems transferring data from PC (XP SP3) to new Mac Pro 2012 - can not get Migration Assistant to work as PC will not display verfify passcode

Migration Assistant: Problems transferring data from PC (XP SP3) to new Mac Pro 2012 - can not get Migration Assistant to work as PC will not display verfify passcode
Hello, I am having problems migrating data from my old PC running XP (SP3) to my new Mac Pro 2012 using the Migration Assistant.
- I downloaded and installed the Windows Migration Assistant from Apple
- My Mac recognized PC and displays passcode
- The sasscode does not show / display on my PC
- My Mac is then stuck in "authenticating" loop and the PC is stuck "waiting for Mac to connect."
- Both computers are connected on same network (have connected PC on WIFI and using ethernet to Reuter)
I have looked on support site and only response I saw says to reinstall Windows Migration Assistant (which I have done)
Any ideas? If cant get this to workare there instructions for manually bring across relevant data eg itunes music and apps, photos, picasa data etc?

Why not turn off the Windows firewall and uninstall any other firewall software you have installed?
If you are using a Norton product uninstall it and discard it. To fully unistall most Norton products you have to go to the Norton website and download a soecial program to completely get rid of it. The normal uninstall feature built into the program will not remove all of it.

New and Persistent MobileMe Error Message

A new and persistent MobileMe Error Message keeps hounding me. No troubles since the demise of MobileMe until lately. Please see the attached photo.
So far, I've deleted all references to MobileMe within my Keychain, re-checked my information in Apple Mail my "Mac.com/Me.com" account, gone to System Preferences to make sure the old MobileMe options (member name and password) are blank ... I'm OS-maxed-out at Snow Leopard, and deleted all plist files with references to MobileMe.
Any ideas for me? Thanks so very much.

Yes, those are no longer vaild, no idea why it's just happening now!?
Being IMAP, you should be able to delete that account, but for safety I'd backup at least your Mail.
You cannot use .mac or MobileMe as type of Account, you have to choose IMAP when setting up, otherwise Mail is hard coded to change imap.mail.me.com to mail.me.com & smtp.mail.me.com to smtp.me.com, no matter what you try to enter.
iCloud Mail setup, do not choose .mac or MobileMe as type, but choose IMAP...
On second step where it asks "Description", it has to be a unique name, but you can still use your email address.
IMAP (Incoming Mail Server) information:
    •    Server name: imap.mail.me.com
    •    SSL Required: Yes
    •    Port: 993
    •    Username: [email protected] (use your @me.com address from your iCloud account)
    •    Password: Your iCloud password
SMTP (outgoing mail server) information:
    •    Server name: smtp.mail.me.com
    •    SSL Required: Yes
    •    Port: 587
    •    SMTP Authentication Required: Yes
    •    Username: [email protected] (use your @me.com address from your iCloud account)
    •    Password: Your iCloud password
Also, you must upgrade your password to meet the new criteria: 8 characters, including upper and lower case and numbers. If you have an older password that does not meet these criteria, when you try to setup mail on your mac, using all of the IMAP criteria listed above, it will still give a server error message. Go to   http://appleid.apple.com         then follow directions to change your password, then go back to setting up your mail using the IMAP instructions above.
Thanks to dpepper...
https://discussions.apple.com/thread/3867171?tstart=0

I do not use or have not signed up for a MobileMe Account but I am getting duplicates in my iCal for some reason. All discussions I read are pointing to the MobileMe being the problem but it is not. Please help me. There must be another reason.

I do not use or have not signed up for a MobileMe Account but I am getting duplicates in my iCal for some reason. All discussions I read are pointing to the MobileMe being the problem but it is not. Please help me. There must be another reason all my entries appear twice.

If you wish to submit comments to Apple, the best way is to use their feedback pages.
http://www.apple.com/feedback/itunesapp.html
It's not likely that anyone from Apple will see your comments here among the thousands of other posts.
Regards.

Trying to upgrade to 10.6 so my iPhone could synch...I'm getting this error message "Problem with this Windows (XP) Installer package. A program required for this install to complete could not be run." Any ideas?

I had iTunes 10.2.1.1 but needed to upgrade to 10.6 so my iPhone could synch...I'm getting this error message "Problem with this Windows (XP) Installer package. A program required for this install to complete could not be run." Any ideas?

This has been fixed. Answer is that I needed to go to "Apple Software Update" and repair it. (From my Control Panel).

!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.jface".

Hi experts,
when in Design Studio, I have selected, Tools, Preferences and then Backend Conections, appears this problem with eclipse,
What happend?,
Thanks in advance,
!ENTRY org.eclipse.jface 4 2 2014-05-27 12:37:08.751
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.jface".
!STACK 0
java.lang.NullPointerException
at com.sap.ip.bi.zen.connectivity.ConnectivityPlugin.getRouterDescription(ConnectivityPlugin.java:68)
at com.sap.ip.bi.zen.ui.internal.preferences.SapLogonLabelProvider.getColumnText(SapLogonLabelProvider.java:24)
at org.eclipse.jface.viewers.TableColumnViewerLabelProvider.update(TableColumnViewerLabelProvider.java:70)
at org.eclipse.jface.viewers.ViewerColumn.refresh(ViewerColumn.java:152)
at org.eclipse.jface.viewers.AbstractTableViewer.doUpdateItem(AbstractTableViewer.java:400)
at org.eclipse.jface.viewers.StructuredViewer$UpdateItemSafeRunnable.run(StructuredViewer.java:485)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
at org.eclipse.jface.viewers.StructuredViewer.updateItem(StructuredViewer.java:2167)
at org.eclipse.jface.viewers.AbstractTableViewer.createItem(AbstractTableViewer.java:278)
at org.eclipse.jface.viewers.AbstractTableViewer.internalRefreshAll(AbstractTableViewer.java:758)
at org.eclipse.jface.viewers.AbstractTableViewer.internalRefresh(AbstractTableViewer.java:650)
at org.eclipse.jface.viewers.AbstractTableViewer.internalRefresh(AbstractTableViewer.java:637)
at org.eclipse.jface.viewers.AbstractTableViewer$2.run(AbstractTableViewer.java:593)
at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1443)
at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1404)
at org.eclipse.jface.viewers.AbstractTableViewer.inputChanged(AbstractTableViewer.java:591)
at org.eclipse.jface.viewers.ContentViewer.setInput(ContentViewer.java:280)
at org.eclipse.jface.viewers.StructuredViewer.setInput(StructuredViewer.java:1690)
at com.sap.ip.bi.zen.ui.internal.LocalUihandler.createUiForBWConnectionsFromSapLogon(LocalUihandler.java:162)
at com.sap.ip.bi.zen.ui.internal.LocalUihandler.createUiForPreferencePageBackendSystems(LocalUihandler.java:119)
at com.sap.ip.bi.zen.ui.internal.preferences.PreferencePageBackendSystems.createContents(PreferencePageBackendSystems.java:88)
at org.eclipse.jface.preference.PreferencePage.createControl(PreferencePage.java:232)
at org.eclipse.jface.preference.PreferenceDialog.createPageControl(PreferenceDialog.java:1502)
at org.eclipse.jface.preference.PreferenceDialog$14.run(PreferenceDialog.java:1259)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
at org.eclipse.jface.preference.PreferenceDialog.showPage(PreferenceDialog.java:1253)
at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.showPage(FilteredPreferenceDialog.java:675)
at org.eclipse.jface.preference.PreferenceDialog$10.run(PreferenceDialog.java:709)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.eclipse.jface.preference.PreferenceDialog$9.selectionChanged(PreferenceDialog.java:705)
at org.eclipse.jface.viewers.StructuredViewer$3.run(StructuredViewer.java:888)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
at org.eclipse.jface.viewers.StructuredViewer.firePostSelectionChanged(StructuredViewer.java:886)
at org.eclipse.jface.viewers.StructuredViewer.setSelection(StructuredViewer.java:1726)
at org.eclipse.jface.viewers.TreeViewer.setSelection(TreeViewer.java:1139)
at org.eclipse.jface.preference.PreferenceDialog.selectSavedItem(PreferenceDialog.java:1055)
at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.selectSavedItem(FilteredPreferenceDialog.java:730)
at org.eclipse.jface.preference.PreferenceDialog$4.run(PreferenceDialog.java:376)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.eclipse.jface.preference.PreferenceDialog.createContents(PreferenceDialog.java:372)
at org.eclipse.jface.window.Window.create(Window.java:432)
at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1104)
at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.createDialogOn(WorkbenchPreferenceDialog.java:102)
at org.eclipse.ui.dialogs.PreferencesUtil.createPreferenceDialogOn(PreferencesUtil.java:192)
at org.eclipse.ui.dialogs.PreferencesUtil.createPreferenceDialogOn(PreferencesUtil.java:116)
at org.eclipse.ui.internal.handlers.ShowPreferencePageHandler.execute(ShowPreferencePageHandler.java:57)
at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:290)
at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:243)
at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:224)
at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:167)
at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499)
at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:213)
at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:850)
at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(HandledContributionItem.java:743)
at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$7(HandledContributionItem.java:727)
at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(HandledContributionItem.java:662)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1057)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4170)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3759)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at com.sap.ip.bi.zen.ui.internal.application.ZenApplication.start(ZenApplication.java:36)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
at org.eclipse.equinox.launcher.Main.run(Main.java:1450)

I just tried it on my machine; no issues in Local mode
I recommend opening a ticket/incident with SAP Support to better troubleshoot what the issue might be.
Be sure you installed the support pack with 1.2 and not the new install

HT5132 Aperture mobileme migrating message problem

Similar Messages

Maybe you are looking for