We had a SP2010 application running in classic authentication. After upgrading it to SP2013 in claims mode, an infopath form stopped working. The infopath has a data connection, which submits the data to a sharepoint list using lists.asms web service.

After upgrade it throws error "An error occured while trying to connect to a web service". After analyzing the error we came to to know that using a web service in infopath in claims based model in not supported directly, we need to use the Secure store service application. (Please correct me if I am wrong)

We have configured the Secure store service application, created a passphrase, created an app in service appllication and set the credentials. After using the app id in UDCX connection file it throws another error: "Unable to obtain the master key"

Below are the error logs



07/15/2015 17:38:09.29 w3wp.exe (0x19D4) 0x1130 Secure Store Service Secure Store efw3 Medium SecretKey is not initialized. a8481a9d-0f3e-6062-5ce9-e28d697accf2

07/15/2015 17:38:09.29 w3wp.exe (0x19D4) 0x1130 Secure Store Service Secure Store fl5i High ValidateMasterkey - Refreshing the master key. a8481a9d-0f3e-6062-5ce9-e28d697accf2

07/15/2015 17:38:09.29 w3wp.exe (0x19D4) 0x1130 Secure Store Service Secure Store eft2 High RefreshMasterKey - Refreshing the master key. a8481a9d-0f3e-6062-5ce9-e28d697accf2

07/15/2015 17:38:09.29 w3wp.exe (0x19D4) 0x1130 Secure Store Service Secure Store fr5q Medium Calling Tick on the tracker. a8481a9d-0f3e-6062-5ce9-e28d697accf2

07/15/2015 17:38:09.29 w3wp.exe (0x19D4) 0x1130 Secure Store Service Secure Store efw3 Medium SecretKey is not initialized. a8481a9d-0f3e-6062-5ce9-e28d697accf2

07/15/2015 17:38:09.29 w3wp.exe (0x19D4) 0x1130 Secure Store Service Secure Store f7vr Medium IsMasterKeyFresh for '51f95266-a5c4-4340-bd79-6f44d0d15e1b' : False a8481a9d-0f3e-6062-5ce9-e28d697accf2

07/15/2015 17:38:09.29 w3wp.exe (0x19D4) 0x1130 Secure Store Service Secure Store f6ji Unexpected SyncMasterKey - No passphrase found in memory. a8481a9d-0f3e-6062-5ce9-e28d697accf2

07/15/2015 17:38:09.29 w3wp.exe (0x19D4) 0x1130 Secure Store Service Secure Store eft3 Unexpected RefreshMasterKey - Master key refreshed failed. a8481a9d-0f3e-6062-5ce9-e28d697accf2

07/15/2015 17:38:09.29 w3wp.exe (0x19D4) 0x1130 Secure Store Service Secure Store 7535 Critical The Microsoft Secure Store Service application InfoPath Web Service failed to retrieve the master secret key. The error returned was: 'Unable to obtain master key.'. For more information, see the Microsoft SharePoint Products and Technologies Software Development Kit (SDK). a8481a9d-0f3e-6062-5ce9-e28d697accf2

07/15/2015 17:38:09.29 w3wp.exe (0x19D4) 0x1130 Secure Store Service Secure Store 7541 Critical The Microsoft Secure Store Service application InfoPath Web Service failed to retrieve enterprise application definition information. The error returned was: 'Unable to obtain master key.'. For more information, see the Microsoft SharePoint Products and Technologies Software Development Kit (SDK). a8481a9d-0f3e-6062-5ce9-e28d697accf2

07/15/2015 17:38:09.29 w3wp.exe (0x19D4) 0x1130 Secure Store Service Secure Store efl2 High GetApplication failed with the following exception: System.ServiceModel.FaultException`1[Microsoft.Office.SecureStoreService.Server.SecureStoreServiceFault]: Unable to obtain master key. (Fault Detail is equal to Microsoft.Office.SecureStoreService.Server.SecureStoreServiceFault). a8481a9d-0f3e-6062-5ce9-e28d697accf2

07/15/2015 17:38:09.29 w3wp.exe (0x19D4) 0x1130 SharePoint Foundation Micro Trace uls4 Medium Micro Trace

Hi Apun,

The reason for not being able to refresh the Secure Store service key to get into the service is because there is a passphrase that is created when you first setup the Secure Store Service. If you haven't created the passphrase, please create it with the steps here:

https://technet.microsoft.com/en-us/library/ee924660(v=office.14).aspx

Whenever you create a new instance of Secure Store Service, you should refresh the master encryption key with the passphrase, otherwise, the credentials stored in the secure store will be unusable.

Add another article for the original issue which you may have read:

http://www.tfsconsulting.com.au/sharepoint-2013-infopath-getuserprofileserviceasmx-error/

Thanks,
Reken Liu