After migration to sharepoint 2010 search result error Cannot find ContentPlaceHolder 'SPNavigation' - sharepoint

I am migrating MOSS 2007 portal to sahrepoint 2010. I am not doing visual uplgrade. to check search setting i typed a keyword and pressed enter anfd it threw me below error. please let me know what to do as I am completely new in this.
Do I need to add the "SPNavigaation" placeholder in my master page. I dont know what custom.master page it is refering.
Error:
Server Error in '/' Application.
Cannot find ContentPlaceHolder 'SPNavigation' in the master page '~masterurl/custom.master', verify content control's ContentPlaceHolderID attribute in the content page.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Web.HttpException: Cannot find ContentPlaceHolder 'SPNavigation' in the master page '~masterurl/custom.master', verify content control's ContentPlaceHolderID attribute in the content page.

Dear all I solved the issue by adding "
<asp:ContentPlaceHolder ID="SPNavigation" runat="server"></asp:ContentPlaceHolder>
"in my master page

Related

NotesXspDocument.save() not allowed to access or modify file "/local/notesdata/xsppers"

We have this error message in our xpages application when saving a ticket with an attachment.
It is basically, fileUpload1 bound to a document field (document1) and Button with document1.save();
Error while executing JavaScript action expression
Script interpreter error, line=1, col=11: [TypeError] Exception occurred calling method NotesXspDocument.save() not allowed to access or modify file: /local/notesdata/xsppers/166/08CABEF7AE5340E0DF9C8D46CF56B3B917EA65C6
not allowed to access or modify file: /local/notesdata/xsppers/166/08CABEF7AE5340E0DF9C8D46CF56B3B917EA65C6
The error says not allowed to access or modify the file within /local/notesdata/xsppers.
My question is how to get access to that folder in the server? What to change or do in the security settings on the server for the /xsppers/ folder.
Or a workaround for this issue. By the way I do not have access to the server. Please help thank you
I saw a related question/issue but I am unable to put a comment as I am new - that is why I posted a new question.. Sorry for that

www.server.com/*.aspx returns server error rather than custom error

I have updated my customerr folder to have a common error page which will be displayed for any sort of error.
www.server.com/wrongone
takes to me to the custom error page. -> Working fine
www.server.com/correctone/wrongone.aspx -> This is handled at application level, so I have no problem with this.
But when I hit www.server.com/wrongone.aspx,
It displays Server error. -> I dont want to display server error
What should I do ( at IIS Level) to redirect this to custom error page?
It depend on what status did you get. To set custom error page for .aspx file, you should set .NET error page <customError> instead of error page.
You could find it in IIS manager->site node->.NET error page and you need to add rule for your status code/error page. When you hit the error status code, the page will be redirected to your custom error page. If your status code is 500, then custom page would fail in some case.
https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012/hh831398(v%3Dws.11)

Error while creating SharePoint publishing page - "The file does not exist"

While creating the page (manually) I am getting "file not found error" for the page I am trying to create. When I am checking the log the error is like -
A critical error occurred while creating a PublishingPage through PublishingWeb.AddPublishingPage(string, PageLayout, SPFolder). System.IO.FileNotFoundException: The file http://win-k3ov869t32r:31141/sites/Demo7/Pages/testpage.aspx does not exist.
Here testpage is the name of the page I want to create.
I would advise going to the ULS logs to get further information.
I would suggest looking to see if the page layout you are creating the page against exists. If you can't find the layout thats your problem.
This could be in the hive or in the page layouts list.
Hope this helps
Many Thanks

405 POST Method Not Allowed using asp for Crystal report file

We are moving a project from IIS6, Windows Server 2003 to Windows 7, IIS7, VS2012 now. Part of this project uses old asp files to open crystal report files. It was working fine on our old server. After I moved them to the new server. It throws me an error message: "HTTP Error 405.0 - Method Not Allowed."
We have a Report.asp file. It uses a form post method to display a crystal report file. Here is the code:
(form method="POST" action="/Reports/InfoNetOverDueDate1.rpt" target="_blank" id=frmOpenReport name=frmOpenReport>
I checked the Headers info. It only Allows GET, HEAD, OPTIONS, TRACE.
Here is what I tried. In IIS, under my Handler Mappings --> Add a Module Mapping. Request Path: .rpt; Module: ProtocolSupportModule; Verbs: GET, POST.
It doesn't throw me any error message, but it doesn't show anything either.
Anybody there can help me with this? Thanks a lot in advance.

can't display error messages with customErrors=Off in SharePoint 2010

I changed the following web.config:
1- VirtualDirectory\80\web.config
2- 14\TEMPLATE\LAYOUTS\web.config
3- 14\TEMPLATE\ADMIN\web.config
4- 14\CONFIG\web.config
CallStack="True", Debug="True" and customErrors="Off"
on all the 4 web.config files but still I can't display the detailed error message
I only get this:
server error in "/" application runtime error
and some instruction on how to display the detailed error message.
I need your help.
According to this link Sharepoint 2010 Server Error '/' in Application , you have to change the web.config of central administration too , then iisreset , please let me know if it works .
This post help me out on SharePoint 2013. It explains step by step how to enable custom errors Enable Debugging and set custom errors off in SharePoint.
Three key areas that the post mention are:
Turn on the call stack (CallStack="true")
Disable custom errors ()
Enable debugging ()
on the locations given on the article.

Resources