
This situation is analogous to what happens when an HTML page referenced by a URL has been deleted, moved, or renamed. If 1993 is no longer accessible, then the hard-coded path to 1993 is no longer valid and the error occurs. For example, if the report was saved while it was expanded down to the year 1993, the report's XML might include the following line. The inaccessible path might have been hard-coded into the report's XML when the report was saved in a filtered, drilled, or expanded state.


For example, the previous error message might appear if the year 1993 has been removed from the cube. If you see this error after the underlying cube is updated, then the report's XML likely contains a hard-coded path to a value that is no longer accessible to you. Formula error - An invalid member name was encountered in the MDX statement - near: "."
