This issue could be due to the page is referring a content that is required in a folder path one level up from the current page path. i.e there could be some mess with the ./../content . There is a discussion about this issue and the suggested solution in the link below.
http://forums.asp.net/t/980453.aspx[
^]
You could try if that works for you.
If not, definitely you may need to provide more information with code to get in detailed about the issue.