Forum Discussion
Solved
Problem searching new pages within SPO SP141856 - Can we get an update from the SharePoint team here
I think it would be appropriate to hear from the SharePoint team on the cause and status of this long running advisory. I haven't seen SharePoint News page updates since the 13th. A broad description of all the current effects of this problem would be useful given the broader end user impact. How about it Mark-Kashman Andy Haon and others.
I hear you John. I will take that feedback back to the team working on the issue and the communications on it.
- Andy Haon
Microsoft
Hi all,
The team is actively working on deploying the fix to this issue. Communications updates are being posted at: https://lynx.office.net/#/incidents/o365/SP141856/identity
Estimated time to resolve: Based on the new deployment progress timescale, we expect this problem to be resolved within 48 hours.
Next update by: Thursday, June 21, 2018, at 11:00 AM UTC
Dear Andy,
The link you gave is not opened to standard user, as you can see in my case I have directly an error message
So that is confirming, we can't use that as it is.
It's only available for the O365 Admin which are in many case restricted set of users.
Anyway, thanks for your message, I'm waiting the fix deployment.
Fab
- Andy Haon
I made a mistake with the link I posted. That is for internal to Microsoft updates for the team who is working the issue.
Updates on communications for this issue will be posted in your message center and the next update is planned to be communicated by Thursday, June 21, 2018 at 11AM UTC.
- Hi Andy, I appreciate the reply and I have been following progress on the Message Center. I still think the severity of this problem warranted an Incident rather than Advisory. The impact has been widely felt. This has been particularly long running too. I realise such incidents are not marketing friendly but if someone (not having a go at you personally) came and explained here what is happening that would be great comms. Disappointed this time.
- Andy Haon
I hear you John. I will take that feedback back to the team working on the issue and the communications on it.
I have an a ticket open for one month because files are not getting found in many site collections in one of my customers tenants. They have fixed the problem in 2 sites, but not in all.
I recently had to open another support ticket because the search results on the People Card were not rendering properly in multiple browsers
It appears to me that there are numerous problems with search in SPO.
I don't need new features, I need features that work!
- Dean_Gross I think we are paying for both new features and existing ones to work! Given customers here have Tier 1 support I hope the message is escalating. The underlying issues here need flushing out. Superficially it appears that insufficient regression testing is a problem. So the team needs to look at QA resources alongside break / fix solutions. We all know in on premises deployments great pressure would be on us to fix a problem of this duration. Outages of this kind put pressure on service management teams which they cannot address directly. I’ve no doubt this will be fixed but I want to see an improvement in customer communication when these longer outages occur and an upgrade to incident.
Dear all,
From my point of view, the delivery and deployment process is a mess since the start of Office 365.
When no issue appears and deployment done successfully, we as IT have to:
- Discover and Understand the new features (Office Group Site, Modern site, …)
- Fight with the users to help them in that new features (Teams)
- Give a positioning of that features which is clear enough for anyone(Stream vs Video Portal)
- Explain the difference between the tools (ToDo vs Planner)
- Support the potential issue or limitation not documented (see Planner)
- ...
But now, when the issue appears into the deployment, we are entering into the second mess with the classical message:
- Why that feature I'm using since a while is not working anymore ? (observed with the search today)
- Why this action is not doing the same process then before (PDF file opening in Word Online not anymore possible)
- ...
Each time that happen, we are quite alone receiving the complains totally blind.
I asked MS each time I can to have a clear view about the deployment process done in the customer tenants, without any positive feedback.
I hope that situation will help MS to improve the QA and delivery/deployment management, because we are all going to the wall with that process.
Fab
PS1: I don't understand why all the customer tenants are touched by this update, our included because we are last release in Europe Tenant and generally the "first release" in US are receiving the update first (like test customer).
PS2: I'm not blaming anyone about where we are today, because MS and the Office 365 teams are fighting between create and deliver new fancy features (Teams, modern pages/sites, …) and maintaining the old one with old fashion model (Publishing site, search engine, user profiles, …). But because at the end, we are in the same boat and the end users will fight with us (as internal IT), we will have to fight with MS (as supplier). So with a real clear communication way, we will give a better solution at the end. To illustrate that, our Global Intranet is not updated anymore because all the system is based on page using page result. The content manager are now complaining to us and user are viewing news with more than 1 week freshness.
We created also a MS Support premier case for this issue, because the impact is touching our Global intranet site.
We are waiting the fix end of this week (given by Support team).
Fab
This is a huge problem. I'm amazed on how silent it is both from MS and customers.
"Scope of impact: Impact is specific to a subset users attempting to query a subset of *.aspx pages that were recently created."
Don't you mean all users and all .aspx pages created after the 13th?
- I have come to value the SharePoint team’s transparency in this community. Often they go above and beyond to keep us posted on developments. This is why I cannot understand when long running issues occur there is silence. This is beyond Message Center updates and I would say if not service impacting it really is now an ‘incident’. When can we expect normal service to resume? So much goodwill has been built up: Microsoft don’t let us down!
