-4

IT replaced my machine with a more powerful one (same OS Windows 7 64 bit Pro) and I no longer can open any MS Office files from Sharepoint. They provide Office 2010 so no solutions from 2013 apply.

When I click on any Word, Excel or PP document in Sharepoint, the corresponding application starts up, but does not open a document. Instead it throws the following error:

enter image description here

Title: Microsoft Word Security Warning

Message: Certificate Error

Description: The application experienced an internal error loading the SSL libraries.

Button: OK

If instead of opening a file I go to Libraries view and click on Open With Explorer button, another window pops up 3 times regardless of OK or Cancel:

enter image description here

Title: Select Certificate

The list contains a 2-way SSL cert which every developer has to install in order to debug one of our applications, and one of my co-worker's certificate. My certificate is not in the list, and that co-worker never used this machine.

Buttons: OK, Cancel, View Certificate

Finally it asks for my credentials again and pops up this:

enter image description here

The IT is not very confident troubleshooting this problem so I am on my own.

Tried solutions from here but none worked. If I disable any sharepoint and grove add-ons in IE, I can download the file fine, but have no way to upload back. Any non-office file opens fine in IE.

ajeh
  • 99
  • 7
  • How is that that any question about Microsoft products not working gets automatically downvoted? Not enough billion$ for you? – ajeh Jul 18 '17 at 16:44
  • 1
    It's because this is **server**fault, not **workstation**fault. – Jenny D Jul 22 '17 at 09:04
  • Wow, eloquent, are we? Sharepoint runs on a server. And GPO comes from a server. So this question had the server related root cause and solution. Boo. – ajeh Jul 24 '17 at 13:47
  • Yes, and if the persons in charge of the server had asked it, it would have been on topic. In this instance, you're a workstation user, not a server administrator. If you don't have the ability to check and/or change the server config, view the logs, etc, then this site isn't the one you need. (There are a **lot** of Microsoft questions here; the ones that are on-topic and well written according to [How do I ask a good question](//serverfault.com/help/how-to-answer) don't get downvoted. – Jenny D Jul 24 '17 at 14:10
  • Self appointed moderator alert! – ajeh Jul 24 '17 at 18:17
  • 3
    I do beg your pardon; I mistook your first comment for a request for further information. My apologies for wasting your time by explaining things you are clearly uninterested in, such as what this site is actually for. – Jenny D Jul 24 '17 at 18:20
  • This question is very off topic for Compose. Please review our FAQ and refrain from repeat performances. – Wesley Jul 24 '17 at 18:47
  • Thank you folks for taking time out of your busy lives to eradicate sarcasm. It has no place on the Internet, where every statement must be strictly regulated by policies. One day you will get a medal for saving the Internet from another 374 character post, I am sure! Keep up good work. @JennyD I upvoted your comment as it's spot on - completely uninterested in. – ajeh Jul 24 '17 at 18:49
  • You should be contacting your company internal support desk. This is a configuration issue within their network that you should not have the access to change. – Chris Moore Jul 18 '17 at 16:15

1 Answers1

-2

The admin found and altered a GPO which was pushing a wrong TLS setting down. Once the registry key for TLS was altered on the machine, and the change persisted, the issue was fixed.

ajeh
  • 99
  • 7