From the Event viewer, the following is an error that get's thrown 10 times every 60 seconds when PPS polls:

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\ppsservice', error code 0x5.

The service identity account is on the same domain as PPS is installed to, and we even elevated the rights of the account to admin on the server. Has anyone seen this before? I've had issues with PPS identity account before, but have not seen this in 20+ installations.

Bottom line, when you create a cycle and assign a form, the services never run. I have to manually start the cycle and assigment. Then, I can get the writeback form in excel, but after submitting, it just hangs up and never moves from pending to partial status.

Please help.. any help is greatly appreciated. Thank you, Kevin

What's the domain name for ppsservice? It seems from the error message that this domain was not set properly. Can you reconfigure the pps server and set the proper domain name for the service identity and try it out?

Mark, thanks for the quick response. Actually, I've reconfigured already- before the problems- here are my configuration settings. Maybe you can find something in the settings:

Planning Server

SQL Analysis Server: VPC-BISUITE

Planning Server databases

SQL Server: VPC-BISUITE
Database configuration: Create
Global Administrator domain: DOMAINNAME
Global Administrator user name: kjobe

Planning Process Service

Service identity domain: domainname
Service identity user name: ppsservice
SQL Server: VPC-BISUITE
Log location: C:\Microsoft Office PerformancePoint Server\
Enable auditing: True
Enable trace logging: True

Planning Web Service

SSL required: False
TCP port: 46787
Service identity domain: domainname
Service identity user name: ppsservice
SQL Server: VPC-BISUITE

Planning Administration Console

SSL required: False

TCP port: 46788
Service identity domain: domainname
Service identity user name: ppsservice

Only thing I notice is the domain is caps under global admin and lower case for the rest.. Again, thanks for any help here.. Kevin

In addition to the initially referenced Event View Error,

An exception occurred while enqueueing a message in the target queue. Error: 15404, State: 19. Could not obtain information about Windows NT group/user 'DOMAINNAME\ppsservice', error code 0x5.

there is an Informational entry as follows:

The activated proc [dbo].[bsp_TimerHandler] running on queue EADP_AppDB.dbo.TimerOriginatorQueue output the following: 'Could not obtain information about Windows NT group/user 'DOMAINNAME\ppsservice', error code 0x5.'

Hi Kevin,

What account is SQL Server running with (the serverwhere theApplication DB is installed)?

One possible source of Error 15404 is that the SQL Server account does not have access to Active Directory.

Randy, Thanks for the response. It does seem the service broker can't communicate with AD. The SQL Server (with AppDB)was running under the local system account. Upon changingSQL Server to run undera domain account, the error continutes to appear.

In addition, from the Event Viewer, there issecurity "failure audit" that occurs on the system userevery 5 seconds:

Logon Failure:
Reason:Unknown user name or bad password
User Name:
Domain:
Logon Type:3
Logon Process:Authz
Authentication Package:Kerberos
Workstation Name:VPC-BISUITE
Caller User Name:sqlsvc
Caller Domain:DOMAINNAME
Caller Logon ID:(0x0,0x664C0C)
Caller Process ID:5744
Transited Services:-
Source Network Address:-
Source Port:-

This seems to be related to my issue as it goes away whenever I either remove the application or simply take the AppDB offline. When I bring it back online, the messages begin. Also, if I delete the application, the errors stop. When I rebuild the app, they do not begin until I create a cycle and assignment, and input data via an excel form.

After uninstalling all PPS Planning components, rebooting the server, reinstalling PPS and building a new application, the error continues to happen.

An exception occurred while enqueueing a message in the target queue. Error: 15404, State: 19. Could not obtain information about Windows NT group/user DOMAINNAME\ppsservice', error code 0x5.

However, I've noticed this error is initially preceded by a PerformancePoint warning from the event viewer:

Failed to perform incremental deployment due to error in retrieving the prior deployment's metadata.

App Domain: /LM/W3SVC/1006647707/Root-1-128504051886364092
Culture: en-US
Host: domainnam.com\VPC-BISUITE
Identity: DOMAINNAME\kjobe
Message Id: PerformancePoint_1050200274
Process: 6072
Severity: Warning
Source: PerformancePoint Mal
Thread: 3316
Time: 2008-03-19T09:31:25.82-04:00
UI Culture: en-US
Data: (empty)

Does this sound like something is left in the registry from previous deployments? Still stumped.. Thanks again for any assistance here!

The message about failing to perform an incremental deployment is just a warning and not really an error. It is just indicating that there is no information about a previous deployment to AS so it will proceed with a full redeployment.

This is expected for a new install. The same warning would occur after changing the AS server in AdminConsole and redeploying.

I'm also stumped regarding your Service Broker error (sorry).

Have you tried not using Kerberos in this case?

Thanks Randy. I'm certainly willing to attempt not using Kerberos, but am not sure how to change this. Could you help with that?

Well, it certainly has something to do with domain communication. I unistalled, reinstalled using only a server specific account for the global admin and service identity account, and the application is working properly. Obviuosly, this is not the recommended solution, but definitely narrows the problem to a domain/trust issue between SQL Server and the domain.

I had this problem with a system here was the root cause:

1) Multiple support personnel have access to the database

2) Ran out of drive space on one of the drives so support person moved the databases to proper drives, H and O.

3) This support personell left the company so his user ID no longer valid, no longer admin on the box, and no longer SA access to this database.

4) Once this account was deleted we received 400,000 in one day to the logs.

5) Here were the errors, often times written to the SQL log 7-9 times a second flooding the log.

Date5/5/2008 11:07:17 AM
LogSQL Server (Archive #1 - 5/5/2008 11:46:00 AM)

Sourcespid17s

Message
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\useraliashere', error code 0x2.

Root Cause:

When support Personnel moved the logs and Database files SQL made this user the owner of the database. You can view this by right clicking properties on SQL Server DB, clicking on Files and view owner. I changed the owner to an SA user of the Database and this has fixed the issue.

Im sorry to bring back to life an almost 5 year old post, but this is pretty much the same problem im having, so i thought i'd post underneath...

i have the same issues, flooding of the following error:

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\spuser', error code 0x5.

Error: 28005, Severity:16, State:2.

'spuser' is a sharepoint service account, the account is still active and can authenticate in various places in the domain. I've seen the advice in this post and in others (http://social.msdn.microsoft.com/Forums/en-US/sqlreplication/thread/db71f793-3f28-4d38-a353-b58e5ed88a8b/ and http://social.msdn.microsoft.com/forums/en-US/sqlservicebroker/thread/28699c94-4d1b-43f2-bcfb-a95152ca226b/).

Im hoping someone can assist in helping me with the 'change to sa' user - im not sure how to do this, what it really means, and further, which SQL DB to apply the change to (my sharepoint install has many databases due to the various applications i've enabled within it) and what the knock-on effects might be to my SharePoint setup if i change databases to this 'sa' user.

can anyone help me? 

Daniel