'The Internet Address ... Is Not Valid' Error Message Due to Corrupt Ancestor Table
Platform Notice: Data Center - This article applies to Atlassian products on the Data Center platform.
Note that this knowledge base article was created for the Data Center version of the product. Data Center knowledge base articles for non-Data Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Symptoms
Below are some symptoms you may encounter, not necessarily all inclusive:
- When editing an attachment using the Office Connector, you may see an error message like below:
"The Internet Address ... is not valid" - Alternatively, you may see a blank document despite that the attachment is a valid attachment.
- When observing the HTTP traffic (eg. via Fiddler), you may encounter a 404 error. Indicating the path to the attachment file is a wrong path.
Cause
The Office Connector plugin is reading paths from the Confluence Ancestor table, which can get corrupted. The root cause for this corruption is still under investigation: CONF-19753.
Resolution
- Rebuild the Ancestor table to correct the issue. Note that in some instances, this action can take a long time to complete.
- From
Administration >> WebDav Configuration, check the box labeled "Disable strict path check". This is available from WebDav version 2.1 onwards. See related improvement request: WBDV-204
Note that this issue is separate from The URL for this File is Too Long for the Application Due to Path Limitation.
Related Articles
Rebuild Ancestor Table Bug
WebDav JIRA Issue
Rebuilding the Ancestor Table
The URL for this File is Too Long for the Application Due to Path Limitation