Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents

Introduction

Below you will find the most common causes of issues with project activation in XTM UI.

...

Issue description & Solution

There is a timeout in the browser

Activation of bulky projects can take a while and usually can result in timeouts in the browser.

...

EXAMPLE:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:pm="http://pm.v2.webservice.projectmanagergui.xmlintl.com/">

   <soapenv:Header/>

   <soapenv:Body>

      <pm:updateProjectActivity>

         <loginAPI>

            <client>XYZ</client>

            <password>Password123</password>

            <userId>20</userId>

         </loginAPI>

         <projects>

            <id>3388</id>

         </projects>

         <options>

            <activity>0</activity>

         </options>

      </pm:updateProjectActivity>

   </soapenv:Body>

</soapenv:Envelope>

Project older than April 2018 on XTM Cloud return error

To save disc space XTM stores archived projects on a separate, secure server. This method of preservation has been introduced in April 2018, and any project that was created before this implementation is available for restoration only by the XTM Support team.

...

IMPORTANT!

Due to the nature of the above method, specified projects is available after 6-12 hours.

A subcontracted project cannot be activated by LSP

Solution: If you received a project from a contractor, and it got archived for whatever reason, please, reach out to your contractor and ask them to activate the project. If they activated it, yet the project is still inactive on your side, please, create a proper ticket to the XTM Support team and provide all the necessary details (as specified in the previous case).

A project cannot be activated after a migration or XTM upgrade

While our standard tests usually eliminate such issues before a client has a chance to notice it, sometimes you can encounter this problem after your standalone server was either migrated or upgraded.

...