Trimble MEP incident

MEPcontent for Fabrication (ITM) v1.2

Notice Resolved View vendor source →

Trimble MEP experienced a notice incident on June 7, 2021 affecting MEP content for Fabrication (ITM), lasting 1d 18h. The incident has been resolved; the full update timeline is below.

Started
Jun 07, 2021, 11:43 PM UTC
Resolved
Jun 09, 2021, 05:49 PM UTC
Duration
1d 18h
Detected by Pingoru
Jun 07, 2021, 11:43 PM UTC

Affected components

MEP content for Fabrication (ITM)

Update timeline

  1. investigating Jun 07, 2021, 11:43 PM UTC

    Some users may be experiencing issues accessing MEPcontent for Fabrication (ITM). Our engineering team is working hard to resolve the issue. Please monitor https://www.trimblemep.cloud/ for updates on availability. We apologize for the inconvenience. We will send an additional updates in the future. Thank You, MEP SupportOps

  2. identified Jun 08, 2021, 01:05 PM UTC

    Some users may be experiencing issues accessing MEPcontent for Fabrication (ITM). Our engineering team has identified the issue and is working hard to create a patch that will be available soon. Please monitor https://www.trimblemep.cloud/ for updates on availability. We apologize for the inconvenience. We will send an additional updates in the future. Thank You, MEP SupportOps

  3. identified Jun 08, 2021, 06:37 PM UTC

    We are continuing to work on a fix for this issue.

  4. monitoring Jun 09, 2021, 01:35 AM UTC

    Our engineering team has implemented a fix for our customers using v1.2 of MEPcontent for Fabrication (ITM). This patch can be downloaded from the link here: https://s3.amazonaws.com/mepdownloads-na.trimble.com/client-downloads/ITM/MEPcontent+for+Fabrication+V1.2/Trimble+Content+Installer.exe Before installing the new version, please clear your cache. Click the link to download the new installer for v1.2 of MEPcontent for Fabrication (ITM). Please monitor https://www.trimblemep.cloud/ We sincerely apologize for the inconvenience. Thank You, MEP SupportOps

  5. resolved Jun 09, 2021, 05:49 PM UTC

    This incident has been resolved.