This project has moved and is read-only. For the latest updates, please go here.

Unable to obtain the application proxy for the context

Aug 15, 2011 at 8:58 PM


I successfully ran the autoinstaller to setup the Index server (first server in the farm).  However, I noticed the following errors.  What am I missing?  thanks



- Configuring service app settings...

- Setting unattended account credentials...

- Creating Secure Store Target Application e4e1ba59-64b7-40e9-863a-ff8d2506a1e4-ExcelUnattendedAccount...

- Creating Secure Store Application...

New-SPSecureStoreApplication : Unable to obtain the application proxy for the c


At D:\SharedFiles\MOSS\SP2010\SP2010AutoInstaller\AutoSPInstaller\AutoSPInstall

erFunctions.ps1:3055 char:53

+ $secureStoreApp = New-SPSecureStoreApplication <<<<

-ServiceContext $context `

+ CategoryInfo : InvalidData: (Microsoft.Offic...toreApplication:

SPNewSPNewSPSecureStoreApplication) [New-SPSecureStoreApplication], Secure


+ FullyQualifiedErrorId : Microsoft.Office.SecureStoreService.PowerShellCm



- Updating Secure Store Group Credential Mapping...

Update-SPSecureStoreGroupCredentialMapping : Cannot validate argument on parame

ter 'Identity'. The argument is null. Supply a non-null argument and try the co

mmand again.

At D:\SharedFiles\MOSS\SP2010\SP2010AutoInstaller\AutoSPInstaller\AutoSPInstall

erFunctions.ps1:3063 char:58

+ Update-SPSecureStoreGroupCredentialMapping -Identity <<<<

$secureStoreApp -Values $credentialValues

+ CategoryInfo : InvalidData: (:) [Update-SPSecure...edentialMapp

ing], ParameterBindingValidationException

+ FullyQualifiedErrorId : ParameterArgumentValidationError,Microsoft.Offic





Aug 15, 2011 at 11:58 PM

(I'm surprised it worked at all with your path structure - the scripts are buried deeper than I've ever seen...)

With regard to the error, have you created a Secure Store service app before trying to configure Excel Services unattended account?


Aug 16, 2011 at 1:53 AM

Hi Brian,

Thanks for the response.  The only thing I have that is related to secure store are below:

        <SecureStoreService Provision="true"
                            Name="Secure Store Service"
                            ProxyName="Secure Store Service">

Other than that, I am not sure what else need to be done.  Any suggestions?  One other questions, for a WFE server, how should the input script be modified?


Dec 17, 2011 at 5:15 PM

The script input file actually no longer needs to be modified for a WFE (or APP) server - we can now specify server names within parts of the script like service applications to define on which servers specific services/service apps will be provisioned. As a result I now mainly use the very same XML input file for each server in the farm.


Dec 20, 2011 at 3:13 PM

I got the same issue.

Sep 20, 2012 at 4:31 PM

A workaround is to manually generate a key for the secure store and then running the script again.

Navigate to your service applications in Central Admin and select the secure store > Manage >Generate new key