Versions Compared

Old Version 5

changes.mady.by.user Damian Rozmiarkowski

Saved on

compared with

New Version 6

changes.mady.by.user Damian Rozmiarkowski

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Issue description & Solution

There is a timeout in the browser

The activation of large projects can take a while and can usually 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 Cloud stores archived projects on a separate, secure server. This method of preservation was introduced in April 2018, and any project that was created before this implementation is only available for restoration by the XTM International Support team.

...

Note

IMPORTANT!

Due to the nature of the method described above, the specified projects will be available after 6 to 12 hours.

A subcontracted project cannot be activated by an LSP

Solution: If you have received a project from a contractor, and it has been archived for whatever reason, contact your contractor and ask them to activate the project. If they activated it but the project is still inactive on your side, create a suitable ticket for the XTM International Support team and provide all the necessary details (as specified in the previous case).

A project cannot be activated after a migration or XTM Cloud upgrade

A project cannot be activated after a migration or XTM Cloud upgrade. While our standard tests usually eliminate such issues, you can sometimes encounter this problem after your standalone server has either migrated or been upgraded.

...