Skip to main content
R
RSaundersAdobe
Participant
April 14, 2017
Question

Connect unable to use Powerpoint in Mac Sierra 10.12.4

  • April 14, 2017
  • 1 reply
  • 1126 views

When Mac Office 2016 came out, the Adobe Connect add-in couldn't talk to Powerpoint 2016.  OK, fine, I'll keep using Powerpoint 2010.

With the latest MacOS Sierra update (10.12.4) Adobe Connect is unable to use Powerpoint 2010, and I no doubt don'thave an earlier version of Powerpoint.  It would seem that powerpoint presentation capability (.pptx conversion) would be a critical feature of Adobe Connect, and this would be tested.  It's not OK to just say "Just save as .PPT, as that conversion handles embedded images soo poorly that they are illegible.  It's been almost 6 months since this trail of problems started, what's the solution??

This topic has been closed for replies.

1 reply

Jorma_at_Knox
Jorma_at_Knox
Legend
April 17, 2017

What is the issue you are facing? Connect itself doesn't "talk" to PPT, but rather allows you to upload PPT(X) files and then converts them on the server to display in Connect.

Are you getting an error on uploading to the Share pod?

R
RSaundersAdobeAuthor
Participant
April 17, 2017

In Connect, when I choose "Share a file from my computer" and

then choose a PPTX file I get Image A, asking to give Powerpoint
access to "SimpleName.pptx".  This is a new message, but I'm a
team player to I choose "Grant Access".  Then I get Image B, telling

me that I am screwed.

Image A

Image B

J
johnswhitehead
Participant
July 25, 2017

Hi

I get the same weird request for SimpleName.pptx and the same conversion warning. But all I had to do is click Proceed and it converted fine. I was using PowerPoint 2016 and the conversion was perfectly acceptable. I've seen a similar message in the Windows version and I think it's just warning you that the fancy effects listed won't work after conversion but other stuff will.

What the SimpleName thing is all about I have no idea. Perhaps they struggle with macOS's liberal attitude to filenames, allowing all sorts of punctuation and things that upsets other systems. But the workaround seems kludgey, to say the least.

Best

J

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices