JSLL: Failure sending data to vortex: error https://preview.support.microsoft.com/bundles/application?v=430VEiAdr2R9QZ6VIhVUVChZ0G-dokW6yMWjvkTW1Ew1:1 in tJSLL: Failure sending data to vortex: error https://preview.support.microsoft.com/bundles/application?v=430VEiAdr2R9QZ6VIhVUVChZ0G-dokW6yMWjvkTW1Ew1:1 in t The enterprise outline code lookup tables are incorrect after you install Project Server 2003 Service Pack 2

The enterprise outline code lookup tables are incorrect after you install Project Server 2003 Service Pack 2

This article has been archived. It is offered "as is" and will no longer be updated.
Symptoms
When you use Microsoft Office Project Server 2003, you check out and then save the enterprise global template file. Then, you notice that the lookup tables that are associated with enterprise outline codes are incorrect. For example, the lookup tables have missing nodes. Alternatively, items in the list are disordered.

For example, suppose that you have an outline lookup table structure that looks similar to the following example before you install Project Server 2003 Service Pack 2 (SP2):
A B  DCE
After you install Project Server 2003 SP2, the outline lookup table structure may look similar to the following example:
A BC E
Additionally, you may not be able to expand or collapse the nodes of the outline lookup table structure.
Cause
This problem occurs after you install Project Server 2003 SP2.
Resolution
To resolve this issue, download and install Project Server 2003 SP2a.

For more information about how to obtain Project Server 2003 SP2a, click the following article number to view the article in the Microsoft Knowledge Base:
873458 How to obtain the latest service pack for Project Server 2003
Note Project Server 2003 SP2 was released on September 27, 2005. Project Server 2003 SP2a was released on December 13, 2005. Project Server 2003 SP2a resolves the issue that is mentioned in the "Symptoms" section.

After you install Project Server 2003 SP2a, follow these steps:
  1. Run the following SQL query against the project database that experiences this issue:
    UPDATE MSP_PROJECTSSET PROJ_EXT_EDITED = 0WHERE PROJ_TYPE = 2
  2. Open the enterprise global template file by using Microsoft Office Project Professional 2003.

    To do this, follow these steps:
    1. Connect to Project Server 2003 by using Project Professional 2003.
    2. In Project Professional 2003, click Tools, point to Enterprise Options, and then click Open Enterprise Global.
  3. Verify that the enterprise outline code lookup tables are displayed the way that you expect. If they are not displayed the way that you expect, collapse the outline by clicking the minus sign (-) and then re-expanding the outline.

    To re-expand the outline, follow these steps:
    1. Click Tools, point to Customize, and then click Enterprise Fields.
    2. Click the Custom Outline Codes tab in the Customize Enterprise Fields dialog box, select the field that you want to view, and then click View Lookup Table.
  4. On the File menu, click Save. Then, click Close to close the enterprise global template file.
Note If you did not try to fix the original problem by trying to add back nodes that were missing or by re-ordering nodes that were disordered, you should only have to run the script.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Microsoft is researching this problem and will post more information in this article when the information becomes available.
projectserver2003 projectserver2k3 prjsvr2003 prjsvr2k3
Properties

Article ID: 909947 - Last Review: 01/15/2015 14:59:33 - Revision: 6.0

  • Microsoft Office Project Server 2003
  • kbnosurvey kbarchive kbupdateissue kbtshoot kbprb KB909947
Feedback