7

I am trying to install/configure the Tridion Powershell Module for coreservice API calls to our CMA running Tridion 2013 SP1 -- environment is configured and working correctly end to end including Content Porter-- I have successfully imported and installed the Tridion-CoreService module into Powershell. I am able to successfully connect to the CMA server from my client and use 3 of the supplied commands with no issues: (Get-TridionCoreServiceClient, Get-TridionCoreServiceSettings, and Set-TridionCoreServiceSettings)

However, when attempting to use the other provided commands(Get-TridionItem, Get-TridionUser, etc.) I receive the following error. 

PS C:\Program Files\WindowsPowerShell\Modules\Installation> Get-TridionUser
Exception calling "GetCurrentUser" with "0" argument(s): "Access is denied for the user <domain\username>."

Windows Event Viewer throws the error:

Access is denied for the user <domain\username>.


Component: Tridion.ContentManager.CoreService
Errorcode: 770
User: NT AUTHORITY\NETWORK SERVICE

StackTrace Information Details:
at Tridion.ContentManager.Security.AuthorizationManager.LoadAccessToken(String userName, IEnumerable`1 mappedGroupUris, IEnumerable`1 claimSets)
at Tridion.ContentManager.Session..ctor(IEnumerable`1 claimSets)
at Tridion.ContentManager.CoreService.CoreServiceBase.get_CurrentSession()
at Tridion.ContentManager.CoreService.CoreServiceBase.IsExistingObject(String id)
at SyncInvokeIsExistingObject(Object , Object[] , Object[] )
at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)
at Tridion.ContentManager.CoreService.CoreServiceInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)
at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)

I am confused as to why I can connect and create a valid session (deduced from my successful attempts to use the commands I mentioned above), but I am denied access by the other commands.

Any help / suggestions is greatly appreciated!

Improve this question
2
  • Could you list which version of the module that you are using? You can find that by typing: (Get-Module Tridion-CoreService).Version.ToString()
    – Peter Kjaer
    Commented Apr 16, 2015 at 14:50
  • @ Peter Kjaer -- Version # is 2.0.2.0
    – johngalt343
    Commented Apr 16, 2015 at 15:18

1 Answer 1

Reset to default
6

Being able to create a client and connect is not the same as trying to perform an action that requires permissions. The message you are seeing is coming from Tridion: it's telling you that it does not recognise your user as a 'trustee'. I see that you have chosen to say <domain\username> rather than giving the actual value, but is the real value an account that you expect to have Tridion access? You should be able to go in to the Administration section in the Tridion GUI and see the list of users. Can you find this identity listed there? If so, does it have right/permissions to access anything? Answering these questions should solve your problem.

Improve this answer
7
  • Thanks @Dominic Cronin for your response. I am a "Trustee" in Tridion, with Admin rights. The account I am using is the same for Content Explorer, Content Porter, IIS (which has this user as an Impersonation User), and CMA server. Get-TridionCoreServiceSettings returns a "UserName" identical to the user stored in Tridion. I am incorrect assuming cmd 'Set-TridionCoreServiceSettings' requires permissions? If I modify from default, then 'Get' cmd verifies settings were indeed updated.
    – johngalt343
    Commented Apr 15, 2015 at 20:21
  • 1
    But does the access denied message reference the same account?
    – Dominic Cronin
    Commented Apr 15, 2015 at 20:48
  • 1
    Dominic is correct in saying that those working commands don't actually contact Tridion. They just configure the module. So you can't deduce much from them working, except that the module is apparently installed correctly.
    – Peter Kjaer
    Commented Apr 16, 2015 at 13:11
  • 2
    A workaround would be to add yourself as a second trustee, with just the username
    – Dominic Cronin
    Commented Apr 17, 2015 at 11:04
  • 1
    Are you using LDAP or a Single Sign-On solution? Or just Windows Authentication?
    – Peter Kjaer
    Commented Apr 17, 2015 at 13:59

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.