Side-by-side installation of Skype for Business and Lync 2011 is not supported on Mac. Microsoft recommend that you perform a clean uninstall of Lync for Mac 2011 prior to installing Skype for Business for Mac. You can also see your Skype status icon displayed in the system tray at the bottom of your screen. If you close the Skype window, the Skype logo and status icon still appear in the system tray. To remove Skype from the system tray, right click the status icon in the system tray and select Quit Skype.

Steps • Log out and quit Skype for Business. • Go to Finder > press Command+Shift+G > type in /users//library > delete the following files: • Containters > com.microsoft.SkypeForBusiness • Internet Plug-Ins > MeetingJoinPlugin.plugin • Logs > LwaTracing • Saved Application State > com.microsoft.SkypeForBusiness.savedState • Preferences > com.microsoft.skypeforbusiness.plugin.plist • Open Keychain Access from /Applications/Utilities folder. • Delete all keychains starting with Skype For Business. Note: You may have to unlock your keychain by using your password.

Download office 2016 home and student offline installer for mac. If you know you’re going to be happy with Office 2016 for more than two years and these limitations don’t bother you, it may be a better deal to stick with Office 2016. So, if you’re the kind of person that likes to upgrade every time a new version of Office comes out, get Office 365. If you need more than one copy of Office, Office 365 Home seems like a much better deal.

I am currently in the process of deploying our company SharePoint 2013 solution. I am having problems with regards to Office Web Apps, specifically I cannot get it to work. Our infrastructure team set up the OWA Server and i have followed the instructions given here: However when I have completed the set up and try to create a document anywhere whithin SharePoint I get the following error messages: Word Document: 'Sorry, there was a problem and we can't open this document. If this happens again, try opening the document in Microsoft Word.' Excel Document: 'We couldn't find the file you wanted. It's possible the file was renamed, moved or deleted' PowerPoint: 'Sorry, we ran into a problem. Please try again' One Note:'Sorry, you don't have permission to edit this notebook.'

However after each of the above actions a document of the relevant type is created in the SharePoint library but I can then open the documents using the relevant client application. I have been trying to resolve this for several hours now with no success, does anyone have any ideas. Thanks in advance.

@Fat Dragon, I solved my problem 1/2 hour ago (finally), after 5 cups of coffee, numerous cans of RedBull, and bag of Tylenol. Hope this help your trouble shooting. Turned out on my Office Web App server, even thou everthing is mapped to HTTPS, external, etc. I found an entry in the ULS said WOPI Check: Unexpected WOPI Check, non-200 return [code:Forbidden, url:780d8be3-6d3b-45ae-a4ad-b5356ceff424 when I was trying to preview a PPTX file. Doesn't make sense again, because all the blindings are set to use HTTPS.

I went in the SP2013 CA, dug up the Web Application's AAM. I have the Default zone as HTTP, then an Extranet zone as HTTPS. I flipped the Default zone to use HTTPS, and removed the Extranet zone (We all use HTTPS both in or out of the office anyway), and the Preview, Editing, everything started working magically.

You can also initiate scans for connected devices like external hard drives. Furthermore, it offers drag-and-drop scanning for individual files and phishing protection, along with the ability to scan external drives and attached volumes for potential infections. It’s effective and free for non-commercial use, providing on-demand tools for quickly performing full-system malware scans, as well as sifting through specific email threads, attachments, and various web activities like web pages, downloads, and JavaScripts. The best free antivirus for Mac Avast Security for Mac Avast Security for Mac is one of the most popular security suites available, and it’s easy to see why. Many of them are made by the same companies that produce the solutions. Virus checker avg.

So now I have all HTTPS settings, blindings, AllowOAuthOverHttp=false, everthing seems working. Not sure if my issue was related to the fact that I overwrote my New-OfficeWebAppsFarm with HTTPS over my prior HTTP, because if you did so the cmdlet have an warning message saying: 'The cmdlet will overwrite the settings of the existing Office Web Apps Server farm and may result in unintende side-effects. Continue with this operation?' Anyway, I can still see some BroadcastServicesWatchdog_Wfe checking my X.X.X.X:80 even after all SP2013 preview, editing are working.

I'm planning to put it aside first, and trouble shoot this again. We seem to be on the forefront, there isn't much information anywhere on the web unforunately.

Are you using or to access the Office Web Apps server? I saw this kind of error regularly druing the beta if I forgot to set the SPWopiZone when using http.

See step #4 for configuring a test environment in the article. If you are using I would check to make sure your SSL cert is working correctly. Paul Stork SharePoint Server MVP Principal Solutions Architect: BlueChip Consulting Group Blog: Twitter: Follow Please remember to mark your question as 'answered' if this solves your problem. Hi guys, I'm getting the exact same problem with Office 365. Word Document: 'Sorry, there was a problem and we can't open this document.

If this happens again, try opening the document in Microsoft Word.' Excel Document: 'We couldn't find the file you wanted. It's possible the file was renamed, moved or deleted' PowerPoint: 'Sorry, we ran into a problem. Please try again' I didn't try One Note, but the smart money is on the same error message. Happens on Chrome, Firefox and IE 9. The documents links use http and the site we're using is Thanks to anybody who can help.

Not sure if this will help, but I recently encountered a very similar issue. The following fixed it for me. Found the info here (if you are using https on your SharePoint web applications you should be ready to go. If you are using http for SharePoint you need to set AllowOAuthOverHttp to true. This needs to be done in the SharePoint Management Shell using the following commands: $config = ( Get-SPSecurityTokenServiceConfig) $config.AllowOAuthOverHttp = $true $config.Update() Now I'm stuck on having the web apps server render office doc previews in Exchange 2013 OWA. So convoluted!