Error while create a new connection (office 365 Sharepoint Metadata)

[balajibc64]

Hi I'm trying to create a connection from Qlik Sense to access the Sharepoint URL. When I tried to create I'm facing the issue, 

Status: Awaiting authentication...

Error retrieving the URL to authenticate: ENCRYPTION_KEY_MISSING - you must manually set an encryption key before creating new connections.

I checked this error and tried to run the below command ? 

cd C:\Program Files\Common Files\Qlik\Custom Data\QvWebStorageProviderConnectorPackage

(when I tried to run this command in the path C:\Users\QvService\AppData\Roaming\Qlik\QwcKeys\ nothing changes)

Even File modified date showing older date. 

Please suggest. 

[steeefan]

I am not a Sharepoint / O365 / Azure admin at my company and therefore have no access to the admin backend of things. There is unfortunately nothing else I can do for you regarding this request.

[balajibc64]

Hi @steeefan Thanks. I will check 

@Sonja_Bauernfeind  Tagging you . If you have any idea pls suggest. @Albert_Candelario 

[balajibc64]

Hi @steeefan At-last  I found the email is going to AZURE GLOBAL ADMINISTRATOR for approval. I will check with them for the approval request. Once done I will do further steps. If anything I will get back to you. As of now I closed this conversation and marked as done. Thanks for your support. 

[balajibc64]

Hi @steeefan  Hope you are doing well.  I would like to refresh few things about the Qlik Sense connectivity with Office 365 Share point. 

Based on your earlier comments, I have done the changes in our Qlik Sense test environment and its working fine. But I need to replicate the same things once again. The reason is to verify the steps and implement in the production environment. 

While doing this steps, I'm struck on the below step. 

1. I can able to get the encryption key. 

2. After that, I'm trying to run this code "runas /user:{sense service user} cmd. For example:runas /user:MYCOMPANY\senseserver". But unfortunately not able to find the exact command.

Could you help me on this? 

[steeefan]

Please provide a screenshot of what you're trying to do and what the result is.

What I can tell you right away however is that you cannot execute the command runas /user:MYCOMPANY\senseserver just as it is. You must replace MYCOMPANY\senseserver with the actual name of your user, not just some random placeholder shown here as an example.

[balajibc64]

Hi @steeefan  I got it. Below is the command I follow. 

1. runas /user:MYCompanyname\qlikuatadmin cmd (Then it will ask pwd for that user qlikuatadmin).

2. Once I gave then it will take to another cmd window like qlikuatadmin as user. 

3. From there, I can able to run the exe command. 

[balajibc64]

Hi @steeefan  Moreover, I'm having few queries. Could you please check the below link. 

https://community.qlik.com/t5/Integration-Extension-APIs/Qlik-Sense-Connecting-to-MS-Office-365-Shar...

[balajibc64]

Hi @steeefan  Can you guide me on this. 

1. I need to create the Encryption key and executed the command

"C:\Program Files\Common Files\Qlik\Custom Data\QvWebStorageProviderConnectorPackage". QvWebStorageProviderConnectorPackage.exe /key {key}

During this process, a key is generated, but it was indicated that it would be stored at C:\Users\QvService\AppData\Roaming\Qlik\QwcKeys\, whereas the key is actually being stored at C:\Users\QvService\AppData\Roaming\Qlik\Keys\. 

So, In which folder the key needs to be store ? 

2. On my production server, I have checked both of the following folders, and the key folder is present: C:\Users\QvService\AppData\Roaming\Qlik\QwcKeys\                            C:\Users\QvService\AppData\Roaming\Qlik\Keys\ Is this the default location?

If I execute these commands, will it affect the existing setup in any way? 

3. After completing the above steps, should I restart any services?

[steeefan]

This whole thread is only about connecting to SharePoint 365. Please read it from the beginning and execute all the necessary steps listed here in great detail. You will then have a working integration. I have no interest in writing it all over again. If you run into problems, contact Qlik support.