How to troubleshoot Office Solution Accelerator for Six Sigma installation issues (896044)


The information in this article applies to:

  • Microsoft Office Project Server 2003
  • Microsoft Office Solution Accelerator for Six Sigma

SUMMARY

This article contains information about how to troubleshoot issues that may occur when you install Microsoft Office Solution Accelerator for Six Sigma. This article lists common installation issues, discusses the causes of the issues, and contains information about how to resolve the issues.

INTRODUCTION

This article lists common Office Solution Accelerator for Six Sigma installation issues and contains information about how to troubleshoot the issues. This article assumes that all the following conditions are true:
  • The original release version of Microsoft Office Project Server 2003 is installed successfully on the server and uses a clean database.
  • The connection between Project Server 2003 and Microsoft Windows SharePoint Services works correctly.
  • The Office Solution Accelerator for Six Sigma client is not installed on the server that is running Project Server 2003 and Office Solution Accelerator for Six Sigma.
  • No Project Server 2003 hotfixes or Project Server 2003 service packs are installed on the server.

Office Solution Accelerator for Six Sigma installation issues

This section outlines the Office Solution Accelerator for Six Sigma installation issues, and their solutions.

You receive an error message when you run the CustomActionInstall.cmd script

When you run the CustomActionInstall.cmd script, you receive one or both of the following error messages:

Error message 1
The remote server returned an error: (415).
Error message 2
The remote server returned an error: (404) Not found.
This issue occurs when Project Server 2003 cannot complete the requests within the time-out period. The requests that cannot be completed are contained within the Customactioninstall.cmd script. This issue may be caused by several conditions. Typically, the cause is related to user load and resources. Resources include processor speed, memory, and the number of processes that are running on the server.

The resolution for this issue depends on the variable that causes the heavy loads. We recommend that you install Project Server 2003 and Solution Accelerator for Six Sigma on a dedicated server that has sufficient resources to handle the expected user load. If you cannot use this configuration in your environment, reevaluate the applications and processes that are running on the server, and then make the appropriate changes to improve performance. Typically, if you relocate the resource-intensive applications, you can help improve performance.

You receive an error message when you run the CustomActionInstall.cmd script

When you run the CustomActionInstall.cmd script, you receive the following error message:
Value cannot be null.
Parameter name: format
This issue occurs if the Windows user account that you use to run the CustomActionInstall.cmd script is not a member of the Administrators group in Microsoft Office Project Web Access 2003.

To resolve this issue, add the Windows user account that you use to run the CustomActionInstall.cmd script to Project Web Access 2003. Then, add the Windows user account to the Administrators group in Project Web Access 2003. To do this, follow these steps:
  1. Log on to Project Web Access 2003.
  2. Click Admin, and then under Actions, click Manage users and groups.
  3. Click Add User on the Users page.
  4. Specify the Windows user account that you want to add on the Add User page. In the Groups area, click Administrators, and then click Add.
  5. Click Save Changes.

You receive an error message in the Six Sigma Project Guide when you use in Microsoft Office Project Professional 2003

When you use Project Professional 2003, you receive the following error message in the Six Sigma Project Guide:
The root element is missing
This issue may occur if one of the following conditions is true:
  • Microsoft .NET Framework 1.1 Service Pack 1 (SP1) for Microsoft Windows Server 2003 is not installed on the server.
  • The user account that is configured as the identity for the SixSigma MSA PDA Caller COM+ application is not a member of the Administrators group in Project Web Access 2003.
To resolve this issue, use one of the following methods, depending on your situation:

Method 1

Install the .NET Framework 1.1 SP1 for Windows Server 2003 on the server. You can install the .NET Framework 1.1 SP1 for Windows Server 2003 from the Microsoft Windows Update Web site. The .NET Framework 1.1 SP1 for Windows Server 2003 is a critical update that is listed under Critical Updates and Service Packs in the left pane of the Windows Update Web site.

Additionally, you can download .NET Framework 1.1 SP1 for Windows Server 2003 from the Microsoft Download Center. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

885055 How to obtain Microsoft .NET Framework 1.1 Service Pack 1


Method 2

Add the user account that is configured as the identity for the SixSigma MSA PDA Caller COM+ application to the Administrators group in Project Web Access 2003. To do this, follow these steps:
  1. Log on to Project Web Access 2003.
  2. Click Admin, and then under Actions, click Manage users and groups.
  3. Click the user account that is configured as the identity for the SixSigma MSA PDA Caller COM+ application, and then click Modify User.
  4. In the Groups area, click Administrators, and then click Add.
  5. Click Save Changes.

REFERENCES

For more information about solutions for Six Sigma management using the Microsoft Office System, visit the following Microsoft Web site:

http://www.microsoft.com/office/solutions/accelerators/sixsigma/default.mspx

Modification Type:MinorLast Reviewed:7/28/2006
Keywords:kbsetup kbprb kbtshoot kberrmsg KB896044 kbAudITPRO kbAudDeveloper
©2004 Microsoft Corporation. All rights reserved.