SOLVED: An issue with WorkPoint's Web API caused WorkPoint Express to fail
UPDATE: 16:04, 24/06-2020
The issue with WorkPoint's Web API has been solved by Microsoft and users should no longer experience issues with WorkPoint Express.
The issue was due to maintenance work by Microsoft but has now been fully solved. Both WorkPoint and Microsoft continues to monitor the WorkPoint Web API to secure that no further issues should arise.
SOLVED: Many customers are currently experiencing 503 errors
UPDATE: 16/04-2020 20.50
The capacity on SharePoint is now back to normal levels and all customers may now resume full regular use of their WorkPoint solutions.
UPDATE: 3/4-2020 10.30
We've received reports from customers that they receive 503 - Server Unavailable errors.
This is SharePoint Online responding that the service isn't available. This can’t be fixed in WorkPoint, therefore we encourage all customers to report this directly to Microsoft from your own Office365 tenant.
WorkPoint has also contacted Microsoft to get the service restored. We'll provide an update as soon as we have new information to share.
UPDATE: 27/03-2020 15.00
With the latest corrections from Microsoft, we are now happy to inform You, that all customers can now resume using WorkPoint Express and our WorkPoint Office add-ins. We no longer expect our customers to experience the SharePoint servers being unavailable, thus users should only exceptionally experience related error messages.
Some customers may still occasional reduced system performance, especially with regards to creating site collections, due to the generally reduced capacity on SharePoint.
The following blog is now available with some additional information about these temporary changes: Awareness of temporary adjustments in SharePoint OnlineWe also advise you to take a look at SharePoint Incident SP207374 in your Microsoft 365 Admin Center.
UPDATE: 25/03-2020 16.00
We've been monitoring all customer solutions during the day and have only seen very few throttling issues (503 errors), however we are currently maintaining our previously announced recommendations to minimize traffic against SharePoint.
UPDATE: 25/03-2020 08.00
Microsoft have found some unexpected throttling (503 errors) and have addressed the issue during the night. We're monitoring all customer solutions to confirm if the change is working as expected.
UPDATE: 25/03-2020 22.00
The SharePoint Engineering Team at Microsoft is investigating possible solutions
UPDATE: 23/03-2020 22.30
Our Microsoft case has now reached the SharePoint Product Group.
Tomorrow we expect a public announcement from Microsoft regarding the issue.
WorkPoint will also provide some guidelines/actions to minimize traffic against SharePoint.
UPDATE: 23/03-2020 12.00
Microsoft is still having issues with their service.
Unfortunately we haven't been provided with a time frame for a solution.
It is primarily the APIs to SharePoint that is affected, so as a workaround customers can use the browser to access WorkPoint/SharePoint.
UPDATE: 20/03-2020 12.00
We're working with Microsoft and some customers to collect trace logs.
The issue has also been escalated within Microsoft.
SOLVED: Unexpected error in wizards
Updated 11:01, March 13th, 2020
The previously identified issue which resulted in unexpected errors when trying to launch wizards from WorkPoint 365 has now been fully solved.
SOLVED: An issue has been identified which prevents users from creating new site collections.
Updated 09:26, February 26th, 2020
The previously identified issue which prevented WorkPoint users from creating site collections has now been fully solved.
SOLVED: WorkPoint Express issues with latest update to Microsoft Windows
The latest update to Windows (May 2019 - version 1903) seems to cause issues for WorkPoint Express.
The update breaks the input fields in the program making it impossible to enter text in WorkPoint Express. Thereby, users can not navigate, search, create entities or update properties among other things.
We are investigating the issue and will be working on a hotfix, but meanwhile, we will suggest that you postpone the Microsoft update for now.
If you have experienced any issues or have any questions regarding this, please contact firstname.lastname@example.org and The WorkPoint Team will assist you.
SOLVED 20.03.2019: Breaking change on field ordering of content type fields
This Week, Microsoft accidentally introduced a bug in their server-side SharePoint API's. The bug affects the ordering of fields on content types.
The consequence of the bug is that SharePoint returns an error each time a client requests a new order of fields on a content type. WorkPoint 365 does this in various features. The following features may be affected by the bug:
- Site Creation
- Master Site Synchronization
- Site Collection Provisioning
- Site Collection Synchronization
Microsoft has acknowledged the bug and a fix is planned to get fully applied to production worldwide within the next 36 hours.
If you have experienced any issues with this, please contact email@example.com and The WorkPoint Team will assist you.
We are working on getting further information from Microsoft and we will provide an update, when we have more information or the issue has been resolved.
If you have questions regarding this, please contact firstname.lastname@example.org