PM87378: [WI 261599] - Invalid UUID [] error when importing MS Project XML

APAR status

• Closed as program error.

Error description

• Problem description
  When importing a Microsoft Project file to a plan an error is
  thrown in Step 4 when the dialog Assign Users shows up.
  
  Error message and stack trace:
  ?Invalid UUID []?
  
  'errorClass': 'java.lang.IllegalArgumentException',
      'errorCode': 400,
      'errorTraceMarshall': [
      {
     'errorTraceFileName': 'UUID.java',
          'errorTraceClassName':
  'com.ibm.team.repository.common.UUID',
          'errorTraceMethodName': 'valueOf',
          'errorTraceLineNumber': 76
      },
      ..
      ..
  
  How to reproduce:
  
  
  It happens with all supported Browsers and versions.
  There is an Proxy Server with default content type setting as
  text/plain.
  
  The problme occurs because there is no content type in the
  response for a request during this import and takes the default
  content type from the Proxy Server but it should be 'text/xml'
  as the response is in xml format.
  
  For further information see Work Item:
  https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.Wo
  rkItem/261599
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The problem is that we are not setting the content type in
  the response for a request to UploadImportFileService.
  Due to this the IHS can set the content type based on the
  configuration. In some cases the response will be set as
  "text/plain", in these cases dojo will not parse the XML and
  hence all further calls will fail.
  

Problem conclusion

• The problem is that we are not setting the content type in
  the response for a request to UploadImportFileService.
  Due to this the IHS can set the content type based on the
  configuration. In some cases the response will be set as
  "text/plain", in these cases dojo will not parse the XML and
  hence all further calls will fail.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  RATL TEAM CONCE

• Fixed component ID

  5724V0400

Applicable component levels

• R401 PSN

     UP