locked
Azure RMS connector install error RRS feed

  • Question

  • I am setting up a hybrid RMS configuration for Exchange to use Azure rms to encrypt emails.  I have made a service account in Office 365 that is a global admin.  When the connector get to the step of installing the files on a server on prem I get an error 0x80070643.
    Thursday, March 9, 2017 2:48 PM

Answers

  • I actually fixed/got around this problem by installing it on a different server.  The only major difference is that the server is DID work on was not already using IIS.  I think since I already had a site on port 80/443 on the server it wasnt working on that was conflicting.
    • Marked as answer by tdecurtins Tuesday, March 28, 2017 1:05 PM
    Tuesday, March 28, 2017 1:04 PM

All replies

  • What version of Windows Server and does the account you're using to run RMSConnectorSetup.exe  have local admin permissions?
    Thursday, March 9, 2017 7:05 PM
  • Server 2012 R2.  Im using a different domain admin account to run the installer.  Domain admin group is in the local administrator group.
    Thursday, March 9, 2017 7:06 PM
  • Then I'm out of ideas and can only suggest you open a Support ticket to help with this.  There must be a setup log that might have more information but I don't know where it is - I've not heard of this installation failing before so I've never looked.
    Friday, March 10, 2017 2:39 AM
  • i have the similar problem, when i install RMSconnector it return this error in tab credential:

    " An undefined server error was encountered. Error code = InternalFailure. The correlation ID for this event is c6d6eb98-1e14-4e77-b1fe-2e1f90109184."

    i've test with different account but the problem not disapper. All account used are Global Administrator.

    • Marked as answer by tdecurtins Tuesday, March 28, 2017 1:05 PM
    • Unmarked as answer by tdecurtins Tuesday, March 28, 2017 1:05 PM
    Tuesday, March 28, 2017 11:35 AM
  • I actually fixed/got around this problem by installing it on a different server.  The only major difference is that the server is DID work on was not already using IIS.  I think since I already had a site on port 80/443 on the server it wasnt working on that was conflicting.
    • Marked as answer by tdecurtins Tuesday, March 28, 2017 1:05 PM
    Tuesday, March 28, 2017 1:04 PM