After searching a while, we have found several solutions:
- Stop Planning Service and IIS and and do an ALTER application database enabling broker.
- Configure Service Broker.
- Set up Planning Service to use another domain account.
"An exception occurred while enqueueing a message in the target queue. Error: 15404, State: 19. Could not obtain information about Windows NT group/user 'domain\user_name', error code 0x5."
where domain\user_name is a domain account under which SQL Server is working. Actually, this problem is not an issue of PPS but of SQL Server. We set up SQL Server to run under Network Service account. If any SQL Server entity needs to access Active Directory domain controller (e.g. from stored procedure or via Service Broker like PPS does), SQL Server must be run under domain account! So we changed SQL Server to run under domain account and everything went fine.
This is was very interesting for me, since I've tried to follow all recommendations from Deployment Guide and this topic wasn't mentioned.
No comments:
Post a Comment