Troubleshooting

What problem are you having?

Cannot modify a namespace.

Cause: You are trying to modify a read-only namespace.

Solution: Five of the standard namespaces that are included with Microsoft Provisioning Framework (MPF) are read-only. These namespaces cannot be modified or deleted because they provide critical support for core provisioning functions. Modifying them will cause errors. If you need additional functionality, create a new namespace to provide the required functionality.

MPF stops working when administrator passwords expire or change.

Cause: Passwords are not synchronized.

Solution: Manually reset passwords as appropriate.

  • To change the passwords used in a domain installation, log on with domain administrator credentials and change the passwords for the Active Directory accounts as follows:
    1. Click Start, point to Programs, point to Administration Tools, and then select Active Directory Users and Computers.
    2. In the console tree, click Users.
    3. In the details pane, right-click MPFClientAcct, and then select Reset Password.
    4. In the Reset Password dialog box, specify the password, and then click OK.
    5. In the details pane, right-click MPFServiceAcct, and then select Reset Password.
    6. In the Reset Password dialog box, specify the password, and then click OK.
  • To change the passwords used in a local installation, log on with administrator credentials and change the passwords for the local computer accounts as follows:
    1. Right-click My Computer, and then click Manage.
    2. In the console tree, expand Local Users and Groups, and then select Users.
    3. In the details pane, right-click MPFClientAcct, and then select Set Password.
    4. In the Reset Password dialog box, specify the password, and then click OK.
    5. In the details pane, right-click MPFServiceAcct, and then select Set Password.
    6. In the Reset Password dialog box, specify the password, and then click OK.
  • To change the password for the individual component, change it in Component Services as follows:
    1. Click Start, point to Programs, point to Administration Tools, expand Component Services, and then expand Computers.
    2. Expand COM+ Applications, right-click Provisioning Engine, and then click Properties.
    3. On the Identity tab, right-click Provisioning Engine, and then click Properties.
    4. On the Identity tab, specify the password, and then click OK.
  • To change the password for MPF services, change it in the Services and Applications folder as follows:
    1. Right-click My Computer, and then click Manage.
    2. In the console tree, expand Services and Applications, and then click Services.
    3. In the details pane, right-click Provisioning Auditing and Recovery Service, and then click Properties.
    4. On the Log On tab, specify the password, and then click OK.
    5. In the details pane, right-click Provisioning Queue Manager Service, and then click Properties.
    6. On the Log On tab, specify the password, and then click OK.
  • To change the password for Internet Information Services, change it in the Services and Applications folder as follows:
    1. Right-click My Computer, and then click Manage.
    2. In the console tree, expand Services and Applications, and then expand Internet Information Services
    3. In the details pane, right-click MPF, and then click Properties.
    4. On the Directory Security tab, click Edit in the Anonymous Access and Authentication Control box.
    5. If Anonymous Access is selected, click Edit and specify the password.
    6. Note

      • If Anonymous Access is not selected, no action is required.

See also: Managing security.

Cannot find the performance-monitoring counters for namespaces.

Cause: Performance counters for a namespace are not accessible in the monitoring tool until the namespace has been invoked.

Solution: Submit an MPF request that invokes the namespace.

See also: Microsoft Provisioning Framework SDK documentation.

Event log contains event ID 4609.

Cause: A transaction log database is not available.

Solution: Make sure that at least one transaction log database is active.

See also: To activate or deactivate a transaction log.