Forum Discussion
SharePoint List Errors
Recently I've seen many different users on different sites experience problems with SharePoint lists. They are all getting the same error on different lists which prevents them from accessing them. The error in question says: Something went wrong Invalid Argument: 'headers' missing application ID header
Sometimes reloading fixes it, clearing cookies can fix it, and trying a different link can fix it. This problem keeps coming up though and I'm not sure how to find the root of the issue to prevent this from happening over and over. Any ideas?
- Lalit MohanIron Contributor
Hi Scott180
Users across multiple SharePoint sites are encountering a recurring "Invalid Argument: 'headers' missing application ID header" error when trying to access lists. While temporary solutions like reloading and clearing cookies work, the issue persists. To resolve this:
- Ensure updates and patches are up-to-date.
- Review customizations and code for conflicts.
- Check authentication settings and network configuration.
- Monitor server logs for insights.
- Engage Microsoft Support if needed.
- Communicate transparently with users about progress.
By following these steps, you can pinpoint the cause and implement a lasting solution for the error, enhancing SharePoint list usability.
- Scott180Copper Contributor
Lalit Mohan We are using the online version of SharePoint, so how would I check to make sure it’s updated or go through the code? Can I check the logs for the online version as well? If so, what would I be looking for?
- Lalit response are ChatGPT anwsers and those are usually hit and miss...
As for you error, check what error the user is getting on web browser Console. Usually that will give a hint about the error. Post a screenshot here if possible
Are users getting this on new lists or old lists ?
Are they created from the GUI or Provisioned ?
Any custom to these lists such as Content type that has been provisioned?
If everything is stock, than you probably need to create a case with support as it's a back-end issue.