Microsoft Knowledge Base Email Alertz

(843088) - Describes an issue in Microsoft Project Server where you receive the 0X8C040017 error message when you publish a project. This issue may occur if the Project Managers group does not have the correct permissions to create resource accounts.

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 843088 - Last Review: September 18, 2011 - Revision: 3.0

"0X8C040017" error message when you publish a project to Project Server 2003 or to Microsoft Project Server 2002

SYMPTOMS

When you publish a project that contains new resources to Microsoft Office Project Server 2003 or to Microsoft Project Server 2002, you may find that a flashing red exclamation mark appears next to the Microsoft Office Project Server Spooler icon (in Project Server 2003) or next to the Microsoft Project Server Spooler icon (in Microsoft Project Server 2002) in the notification area, at the far right of the taskbar. When you double-click the icon, you receive the following error message in the Error column:
The manager cannot create the resource account (0X8C040017)
Additionally, event error messages that are similar to the following may be logged in the application event log:

Type: Error
Source: Microsoft Project Server Tracing Eventlog Provider
Category: None
Event ID: 2
User: NT AUTHORITY\LOCAL SERVICE
Description:
The description for Event ID (2) in Source (Microsoft Project Server Tracing Eventlog Provider) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details.
Component: PjMsgHlr
File: PathAndNameOfFile
Line: 516
Error Number: 0x8c040017

Description: <Description><![CDATA[Assert Detected. The error code was also included.]]></Description>

Type: Error
Source: Microsoft Project Server Tracing Eventlog Provider Event
Category: None
Event ID: 2
User: NT AUTHORITY\LOCAL SERVICE
Description:
The description for Event ID (2) in Source (Microsoft Project Server Tracing Eventlog Provider) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details.
Component: PjMsgHlr
File: PathAndNameOfFile
Line: 587
Error Number: 0x8c040017
Description: <Description><![CDATA[Assert Detected. The error code was also included.]]></Description>

Although you receive the error messages, the project is published to Microsoft Project Server.

CAUSE

This issue may occur if the Project Managers group is not configured with the correct permissions to create resource accounts.

RESOLUTION

To resolve this issue, make sure that the Project Managers group is assigned the "Create Accounts from Microsoft Project" permission. To do this:
  1. Log on to Microsoft Project Web Access by using a user account that has administrator credentials.
  2. Verify that the Project Managers group is assigned the "Create Accounts from Microsoft Project" permission. To do this:
    1. Click Admin, click Manage users and groups.
    2. In the left pane, under Add, modify, and delete, click Groups.
    3. In the Group Name column of the table that appears on the Group page, click Project Managers, and then click Modify Group.
    4. Under Global permissions: Set global permissions for the members of this group on the Modify Group page, use one of the following methods, depending on the version of Microsoft Project Server that you are running:
      • If you are running Project Server 2003, make sure that the Allow check box is selected. The Allow check box is located next to the Create Accounts from Microsoft Office Project permission.
      • If you are running Microsoft Project Server 2002, make sure that the Allow check box is selected. The Allow check box is located next to the Create Accounts from Microsoft Project permission.
    5. If the Allow check box is not selected, click to select the Allow check box, and then click Save Changes.
  3. Verify that the Project Managers group is assigned the "Create Accounts from Microsoft Project" permission at the site level. To do this:
    1. Use one of the following methods, depending on the version of Microsoft Project Server that you are running:
      • If you are running Project Server 2003, click Admin, and then click Server configuration.

        In the left pane, under Configuration options, click Features (if it is not already selected).
      • If you are running Microsoft Project Server 2002, click Admin, and then click Manage organization.

        In the left pane, under Organization options, click Features (if it is not already selected).
    2. In the Account Creation column of the table that appears on the Features page, use one of the following methods, depending on the version of Microsoft Project Server that you are running:
      • If you are running Project Server 2003, make sure that the Allow check box is selected. The Allow check box appears next to Create Accounts from Microsoft Office Project.
      • If you are running Microsoft Project Server 2002, make sure that the Allow check box is selected. The Allow check box appears next to Create Accounts from Microsoft Project.
    3. If the Allow check box is not selected, click to select the Allow check box, and then click Save Changes.

MORE INFORMATION

For more information about how to configure and about how to administer Project Server 2003, see the Project Server 2003 Administrator's Guide. To obtain the Project Server 2003 Administrator's Guide, visit the following Microsoft Web site:
http://www.microsoft.com/downloads/details.aspx?FamilyID=2f446940-147b-447a-b0d3-6088673a53a4&amp;DisplayLang=en (http://www.microsoft.com/downloads/details.aspx?FamilyID=2f446940-147b-447a-b0d3-6088673a53a4&DisplayLang=en)
For more information about how to configure and about how to administer Microsoft Project Server 2002, see the Microsoft Project Server 2002 Web Administrator's Guide. To obtain the Microsoft Project Server 2002 Web Administrator's Guide, visit the following Microsoft Web site:
http://www.microsoft.com/technet/prodtechnol/project/project2002/reskit/prk_tadminguide_3571.mspx (http://www.microsoft.com/technet/prodtechnol/project/project2002/reskit/prk_tadminguide_3571.mspx)

APPLIES TO
  • Microsoft Office Project Server 2003
  • Microsoft Project Server 2002
Keywords: 
kberrmsg kbprb kbtshoot KB843088
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate

ITG_MIke Reported as Irrelevant  
Written: 7/12/2004 10:58 AM
This KB article seems to suggest that I solve this "problem" by allowing PM's to create resource accounts after they have (inappropriately) created a local resource in MSP. We don't use local resources and I don't want PM's creating global resource accounts - I will manage the Global Resource Pool myself. Am I missing something here? Is this solving some other, more subtle, problem? I assume that companies that use a glabol pool would not want to implement the change suggested here. Is this correct? Mike

James Hayes - james.hayesATanalog.com Reported as Irrelevant  
Written: 9/23/2004 5:40 PM
I was thinking the same thing Mike, it seems like we'd be giving the PM's a lot more priveledges than necessary, specifically, I'd also like to prevent them from using resources that aren't in the global pool...

Steve Moore - stmoore NOSPAM-AT-NOSPAM salliemae.com Reported as Irrelevant  
Written: 1/27/2005 4:19 PM
Again, I was thinking the same thing. We are getting the error code on one plan - we may have 5 updates (tasks) to accept. Some hours may come over during time approvals, while others may not. It seems the solution is a mis-match of resources ... so we just allow them to create the resource. I wonder if this can be done once, then turned off. Might be worth a shot.

Lionel Goulet - http://www.CompHelpCo.com Reported as Irrelevant  
Written: 8/16/2005 12:35 PM
Dudes, you ROCK. The info in this article solved my users' problem. And thanks for the links to MS Project Server documentation.