Conrad Agramont's WebLog

Moved to: http://agramont.net/

MPS: Provisioning Client Event Log Errors (4608)

During normal MPS/MPF operations, you may see the following Entry in the Event Log:

Event ID: 4608
Source: Provisioning Client

A failure occurred while connecting to the configuration database. Previously cached configuration settings will be used.

Connection String = 'server='sql01';database='MPFConfig''.

SQL server reported errors:
Login failed for user 'MYCOMPANY\IIS01$'.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

This is a very common issue.  There is no need to worry or take action on this error.

The MPF Client gets information on available MPF Engines and setting by connecting to the MPFConfig Database (this is stored in a registry key).  Peridodically (not sure of what the time frame is), the MPF Client will try to refesh the data in it's registry (this is a duplicate of what's in the MPFConfig database) with the data in the MPFConfig Database.  If the user submitting the request doesn't have the appropriate rights to connect to the MPFConfig database, then this error will be written to the Event Log and the request will continue to be processed based on the data already in the Registry (which includes information on MPF Engines).

So in the above Event Log error example, the Active Directory Object "IIS01$", which is a Machine Account" was trying to access the MPFConfig database but failed because it doesn't have access.

So how DO you refresh the database table?  Well, you'd have to submit a request (any request will do) to MPF with a user account that has access to the MPFConfig database.

Posted: Jan 25 2005, 03:18 PM by Conrad | with no comments
Filed under:

Comments

No Comments

Leave a Comment

(required) 

(required) 

(optional)

(required)