I've just installed Courier from the repository in the package manager on a v7.2.0 site but I'm having trouble authenticating the user.
The site user membership is our AD and we have a specific service account setup to run Umbraco with full access to the file system and db. Our repository config is below. (Same in both environments)
When I try to send a single file from one site to the next I'm getting the below error in the Courier Log file. In the back office it just hangs at the packing your items screen with a message of 'Please wait...'
2015-07-29 09:49:40,779 [13] INFO Umbraco.Courier.Core.TaskManager - [Thread 11] Application is shutting down, waiting for tasks to complete
2015-07-29 09:49:40,779 [13] INFO Umbraco.Courier.Core.BackgroundTaskRunner`1[[Umbraco.Courier.Core.Interfaces.IRevisionTask, Umbraco.Courier.Core, Version=1.2.5010.37710, Culture=neutral, PublicKeyToken=null]] - [Thread 11] AggregateException thrown with the following inner exceptions:
2015-07-29 09:49:40,779 [13] INFO Umbraco.Courier.Core.BackgroundTaskRunner`1[[Umbraco.Courier.Core.Interfaces.IRevisionTask, Umbraco.Courier.Core, Version=1.2.5010.37710, Culture=neutral, PublicKeyToken=null]] - [Thread 11] .Net TaskCanceledException: .Net Task ID 1
2015-07-29 09:49:40,779 [13] INFO Umbraco.Courier.Core.BackgroundTaskRunner`1[[Umbraco.Courier.Core.Interfaces.IRevisionTask, Umbraco.Courier.Core, Version=1.2.5010.37710, Culture=neutral, PublicKeyToken=null]] - [Thread 11] Shutdown
2015-07-29 09:49:40,779 [13] INFO Umbraco.Courier.Core.TaskManager - [Thread 11] Application is shutting down, waiting for tasks to complete
2015-07-29 09:49:40,779 [13] INFO Umbraco.Courier.Core.BackgroundTaskRunner`1[[Umbraco.Courier.Core.Interfaces.IRevisionTask, Umbraco.Courier.Core, Version=1.2.5010.37710, Culture=neutral, PublicKeyToken=null]] - [Thread 11] Shutdown
2015-07-29 09:50:48,968 [3] DEBUG Umbraco.Courier.Core.EventManager - [Thread 15] Unloading (count: 0)
2015-07-29 09:50:50,638 [3] DEBUG Umbraco.Courier.Core.EventManager - [Thread 8] Unloading (count: 0)
2015-07-29 09:50:50,669 [3] DEBUG Umbraco.Courier.Core.EventManager - [Thread 8] Unloading (count: 0)
2015-07-29 09:50:51,433 [3] DEBUG Umbraco.Courier.Persistence.V6.NHibernate.NHibernateSessionManager - [Thread 21] Loading factory
2015-07-29 09:50:54,148 [3] DEBUG Umbraco.Courier.Persistence.V6.NHibernate.NHibernateSessionManager - [Thread 21] Complete (took 2705ms)
2015-07-29 09:50:54,148 [3] DEBUG Umbraco.Courier.Persistence.V6.NHibernate.NHibernateSessionManager - [Thread 21] Loading factory
2015-07-29 09:50:54,351 [3] DEBUG Umbraco.Courier.Persistence.V6.NHibernate.NHibernateSessionManager - [Thread 21] Complete (took 202ms)
2015-07-29 09:50:54,881 [3] DEBUG Umbraco.Courier.Core.EventManager - [Thread 21] Unloading (count: 0)
2015-07-29 09:50:56,550 [3] DEBUG Umbraco.Courier.Core.EventManager - [Thread 17] Unloading (count: 0)
2015-07-29 09:50:59,561 [3] DEBUG Umbraco.Courier.Core.EventManager - [Thread 9] Unloading (count: 0)
2015-07-29 09:51:03,102 [3] DEBUG Umbraco.Courier.Core.EventManager - [Thread 17] Unloading (count: 0)
2015-07-29 09:51:05,755 [3] DEBUG Umbraco.Courier.Core.EventManager - [Thread 15] Unloading (count: 0)
2015-07-29 09:51:05,770 [3] DEBUG Umbraco.Courier.Core.EventManager - [Thread 15] Unloading (count: 0)
2015-07-29 09:51:05,786 [3] INFO Umbraco.Courier.Core.TaskManager - [Thread 15] Added PackagingTask behind queue of : 0
2015-07-29 09:51:05,786 [3] INFO Umbraco.Courier.Core.BackgroundTaskRunner`1[[Umbraco.Courier.Core.Interfaces.IRevisionTask, Umbraco.Courier.Core, Version=1.2.5010.37710, Culture=neutral, PublicKeyToken=null]] - [Thread 15] Task added Umbraco.Courier.Core.Tasks.PackagingTask
2015-07-29 09:51:05,801 [3] INFO Umbraco.Courier.Core.TaskManager - [Thread 7] Starting PackagingTask with id: c563843d-a797-41d8-a7d8-ce2c752d2815
2015-07-29 09:51:05,817 [3] DEBUG Umbraco.Courier.RepositoryProviders.Local - [Thread 7] Opening session: 5073ed9a-2cd8-4798-861d-ae17540e699b
2015-07-29 09:51:05,817 [3] INFO Umbraco.Courier.Core.BackgroundTaskRunner`1[[Umbraco.Courier.Core.Interfaces.IRevisionTask, Umbraco.Courier.Core, Version=1.2.5010.37710, Culture=neutral, PublicKeyToken=null]] - [Thread 15] Starting
2015-07-29 09:51:06,441 [3] DEBUG Umbraco.Courier.Core.EventManager - [Thread 7] Unloading (count: 0)
2015-07-29 09:51:06,441 [3] ERROR Umbraco.Courier.Core.TaskManager - [Thread 7] Error PackagingTask with id: c563843d-a797-41d8-a7d8-ce2c752d2815
2015-07-29 09:51:06,441 [3] ERROR Umbraco.Courier.Core.TaskManager - [Thread 7] An error occurred consuming task
System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> User: ServiceAccountUsername could not be authenticated
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at Umbraco.Courier.RepositoryProviders.CourierWebserviceRepositoryProvider.CloseSession(String sessionKey)
at Umbraco.Courier.RepositoryProviders.CourierWebserviceRepositoryProvider.Dispose(Boolean disposing)
at Umbraco.Courier.RepositoryProviders.CourierWebserviceRepositoryProvider.Dispose()
at Umbraco.Courier.Core.Packaging.RevisionPackaging.Dispose(Boolean disposing)
at Umbraco.Courier.Core.BaseRevisionHandler.Dispose()
at Umbraco.Courier.Core.Tasks.PackagingTask.Run()
at Umbraco.Courier.Core.BackgroundTaskRunner`1.ConsumeTaskInternal(T task)
2015-07-29 09:56:23,178 [3] DEBUG Umbraco.Courier.Core.EventManager - [Thread 11] Unloading (count: 0)
This is the first site we've installed Courier on a v7 site, all our previous v6 sites with the same setup work fine so I've copied the setup from those to this one.
As a side note I've also swapped out the service account details for mine as I have the relevant permissions in the 2 environments but get the same error.
The user must be a valid Umbraco user - i.e. present in the backoffice with rights for courier. I suggest setting the user to the "0" user for testing, then after verifying that works as expected, work on adding in your AD user - which must be a backoffice user as well.
I've swapped the Courier authentication over in the config to user 0 as suggested and thats working fine.
The AD account is present in the back office in each environment and is configured as an Admin with access to Courier with everything in the Courier Security section checked other than the 'Deny x' options so I'm not sure why it doesn't work.
As the user 0 method is working I'll keep that in place for now.
Courier: User could not be authenticated
Hi.
I've just installed Courier from the repository in the package manager on a v7.2.0 site but I'm having trouble authenticating the user.
The site user membership is our AD and we have a specific service account setup to run Umbraco with full access to the file system and db. Our repository config is below. (Same in both environments)
When I try to send a single file from one site to the next I'm getting the below error in the Courier Log file. In the back office it just hangs at the packing your items screen with a message of 'Please wait...'
This is the first site we've installed Courier on a v7 site, all our previous v6 sites with the same setup work fine so I've copied the setup from those to this one.
As a side note I've also swapped out the service account details for mine as I have the relevant permissions in the 2 environments but get the same error.
Any help would be greatly appreciated.
Cheers
Chris
@Chris
The user must be a valid Umbraco user - i.e. present in the backoffice with rights for courier. I suggest setting the user to the "0" user for testing, then after verifying that works as expected, work on adding in your AD user - which must be a backoffice user as well.
Hi Paul.
I've swapped the Courier authentication over in the config to user 0 as suggested and thats working fine.
The AD account is present in the back office in each environment and is configured as an Admin with access to Courier with everything in the Courier Security section checked other than the 'Deny x' options so I'm not sure why it doesn't work.
As the user 0 method is working I'll keep that in place for now.
Thanks for your help.
Cheers
Chris
is working on a reply...