No item exists at http://SERVER/SITE/mypage.aspx?ID=1. It may have been deleted or renamed by another user
RAPID PUBLISHING
RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.
Symptom
Consider the following scenario:
We have custom pages using the Data Form Web Part to display information. The main information is stored in a SharePoint custom list and a SharePoint custom document library. All of the data and the pages exist in the same sub-site.
The query string is defined as follows:
- On the details page:
- The details page is displayed with details.aspx?ID=xx.
- In the datasource listing:
- <ParameterBinding Name="CustomItem" Location="QueryString(ID)" DefaultValue="1"/>
- In the xslt:
- <xsl:param name="CustomItem">1</xsl:param>
<xsl:variable name="Rows" select="/dsQueryResponse/Custom_Listings/Rows/Row[@ID = $CustomItem]" />
- <xsl:param name="CustomItem">1</xsl:param>
In this scenario, we receive the following error message:
w3wp.exe (0x1104) 0x1670 CMS Publishing 8vzh
Unexpected PortalSiteMapProvider was unable to fetch current node, request URL:
/example/path/here/custom/pages/opportunitydetails.aspx, message: No item exists at http://SERVER/example/path/here/custom/pages/opportunitydetails.aspx?ID=20. It may have been deleted or renamed by another user., stack trace: at Microsoft.SharePoint.SPContext.get_Item() at Microsoft.SharePoint.SPContext.get_ListItem() at Microsoft.SharePoint.Publishing.Navigation.PortalSiteMapProvider.get_CurrentNode()
Cause
When we try passing the Query Parameter Name as ID to the .aspx Page (which itself is the record in the document library) Sharepoint loses track of what ID is used for. Sharepoint no longer knows if ID is the document in the document library or the ID of the listItem which we need to update using this .aspx page. This problem happens because Sharepoint has its own variable named ID which it uses to identify documents/pages on the server. Our solution should not be using a variable named ID.
Resolution
Change the query string parameter from ID to CustomID. Then change the details page from QueryString(ID) to QueryString(CustomID). Once this is done the page will display with no errors.
More Information
DISCLAIMER
MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, RELIABILITY OR ACCURACY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE (THE “MATERIALS”) FOR ANY PURPOSE. THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE.
TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.
Article ID: 972225 - Last Review: 06/08/2009 10:25:42 - Revision: 1.0
- Microsoft Office SharePoint Server 2007
- Microsoft Windows SharePoint Services 3.0
- kbrapidpub kbnomt KB972225