SharePoint 2013 search application break after windows update. - search

Problem:
We applied some windows updates to our SharePoint server 2013 WFE. This update caused our search service application to break. It is giving following error from search service application in CA:
The search application 'Search Service Application' on server C....1 did not finish loading. View the event logs on the affected server for more information.
To investigate the root cause of the problem I check Event log and found following error :
The Execute method of job definition Microsoft.Office.Server.Search.Administration.CustomDictionaryDeploymentJobDefinition (ID a006ef86-4d33-4f2d-a77f-4cb2ac909b23) threw an exception. More information is included below.
The search application '102a182f-24fd-4147-8bc4-d22168b3e29e' on server CBRDEVSPS01 did not finish loading. View the event logs on the affected server for more information.
I also checked ULS log and find following error:
11/17/2015 10:23:57.06 OWSTIMER.EXE (0x300C) 0x32A0 SharePoint Server Search Administration dl1x High Unexpected exception caught in GathererProject::EnsureComServer. Exception message: The device is not ready. . 4f4e429d-c15d-5048-e5da-799794211bff
11/17/2015 10:23:57.06 OWSTIMER.EXE (0x300C) 0x32A0 SharePoint Server Search Administration fwi9 Exception search application Search Service Application: synchronization of default content sources failed System.IO.FileNotFoundException: The device is not ready. at Microsoft.Office.Server.Search.Administration.MSSITLB.IGatherApplication2.get_GatherProjects() at Microsoft.Office.Server.Search.Administration.GathererProject.get_ProjectObject() at Microsoft.Office.Server.Search.Administration.GathererProject.EnsureComServer() at Microsoft.Office.Server.Search.Administration.GathererProject.GetContentSource(String strContentSource) at Microsoft.Office.Server.Search.Administration.OSSPrimaryGathererProject.ProvisionContentSources() at Microsoft.Office.Server.Search.Administration.SearchServiceApplication.SynchronizeDefaultContentSources() at Microsoft.Office.Server.Search.Administration.SearchServiceApplication.Synchronize() StackTrace: at Microsoft.Office.Server.Native.dll: (sig=678c0f87-966f-4d99-9c94-b49e788d2672|2|microsoft.office.server.native.pdb, offset=131CE) at Microsoft.Office.Server.Native.dll: (offset=21BE5) 4f4e429d-c15d-5048-e5da-799794211bff
11/17/2015 10:23:57.07 OWSTIMER.EXE (0x300C) 0x32A0 SharePoint Server Search Administration fwj8 Exception failed to synchronize application Search Service Application System.IO.FileNotFoundException: The device is not ready. at Microsoft.Office.Server.Search.Administration.SearchServiceApplication.Synchronize() at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize() StackTrace: at Microsoft.Office.Server.Native.dll: (sig=678c0f87-966f-4d99-9c94-b49e788d2672|2|microsoft.office.server.native.pdb, offset=131CE) at Microsoft.Office.Server.Native.dll: (offset=21BE5) 4f4e429d-c15d-5048-e5da-799794211bff
11/17/2015 10:23:57.12 OWSTIMER.EXE (0x300C) 0x32A0 SharePoint Server Shared Services 6482 Critical Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (64d2ce6d-5c68-4c52-93b8-d0abdaf1dd18). Reason: The device is not ready. Technical Support Details: System.IO.FileNotFoundException: The device is not ready. at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize() at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob) 4f4e429d-c15d-5048-e5da-799794211bff
To Solve it I tried following:
Restart the SharePoint Server Search through PowerShell but could not complete the action.
Clear file system Cashed on all WFE where SharePoint Timer Service is running http://www.social-point.com/sharepoint-2010-event-id-6482-application-server-administration-job-failed-for-service-instance-microsoft-office-server-search-administration-searchserviceinstance
Uninstall all the Windows Update
Tried to reset search index and stop crawling using PowerShell command and failed to do.
Run the SharePoint product configuration wizard
Check the group policy log and find nothing Impacted SharePoint Accounts.
I created a new search Application which is fully functional. Any Advise to fix the current search Application will be highly appreciated.

I think you're right that there are times when the only solution is to recreate the SSA. I'm in a similar situation right now after installing Windows Updates. The current search index is returning results, but new crawls will not complete and just seem to hang. It can take days to crawl all the content on this farm, so to minimize downtime, here is the plan we are about to implement:
Create a temporary web application.
Create a new Search Service Application associated with the new web
app.
Create content sources in the new SSA
Export managed properties from the old SSA using a PowerShell script like the one described here (http://blog.riccardocelesti.it/exportimport-managed-properties-via-powershell/)
Crawl the content with the new SSA
Import managed properties and mappings (again using the script above)
Switch the service app associations so the production web app uses
this new SSA. It should contain all the crawled content and be ready to respond to queries with current data.
I hope this helps someone.

Only option was to re-create search Servcie Application. Can I avoid creating SSA. Any idea guys?

one of the windows update probably installed a part of one of the earlier CUs. see https://blogs.technet.microsoft.com/stefan_gossner/2015/07/15/important-psconfig-is-mandatory-for-july-2015-cu-for-sharepoint-2013/
Have you tried running the product config wizard (or psconfig)? This might fix you search problems.

Related

This webpage is not available

I am newbie in Azure development ,I am migrating an existing asp.net application to be hosted as cloud service ,everything works just fine locally (on dev. AppFabric) but when I publish it on cloud and after I try to singin on my signin.aspx page it keeps giving me "This webpage is not available" error .
after that refreshing the page gives me "HTTP Error 503. The service is unavailable." error
my signin page does a lot of stuff (calling db procedure ,setting user session) before redirecting to default page [I am using the free azure trial account]
what may cause the problem ,how can I debug ,why everything works fine on the emulator ?
Checking the event Viewer I found that the problem was in "Debugger.Break ();" inside a class it seems like that line just freaks the runtime out and causes it to lose control and recycle the Application Pool and stopping the service !!!!
You should set up a remote desktop connection to your web role instance and look at the Event Log for IIS. You will want this for development and testing independent of your current issue.
Links:
http://www.windowsazure.com/en-us/develop/net/common-tasks/remote-desktop/
http://msdn.microsoft.com/en-us/library/windowsazure/gg443832.aspx

Detailed errors in IIS 7

I'm trying to figure out why I'm getting 500 errors in setting up a website in IIS.
So far I've tried the following steps:
Enabled Failed Request Tracing (Doesn't write logs for this site, but
works for other sites)
Enabled detailed error messages. Still Getting the default 500 page
with no additional information.
Give app pool full permission to the project directory.
Made sure app pool was running on classic .NET 2 (old app)
Running the site under a permutation of (Classic/Integrated, .NET
2/4)
Enabled anonymous authentication
So my thinking is, somehow, the site fails before the logging modules are ran.
I suspect this is the case because I see no new entities in Event Viewer, IIS Advanced Logs folder, Or in Failed Request Tracing folder. My only source of information (besides 500 error) is a new entry in the IIS log:
2012-12-04 13:06:05 127.0.0.7 GET / - 80 - 127.0.0.1 Mozilla/5.0+(compatible;.....)
To verify this, is there a way to check which stage of the pipeline a request failed? Is it possible to run the logging modules before the failure occurs?
There is a trace event logger for HTTP.sys. With this you can determine if the request is even making it to the right app pool in IIS. Direction on usage
As a last resort, Microsoft offers a tool called Debug Diagnostic. When you have no other option, use this. It will produce a crash dump of the app pool of your choice. Not easy to go through, but it’s a lead. Direction on usage

Sharepoint Central Administration not running

I am getting the following error when I try to browse either the Central Administration or the Web Application:-
Unable to connect to database.
Check database connection information and make sure the database server
is running
In the event log, I have the following error entry:
The description for Event ID ( 27745 ) in Source ( Windows SharePoint Services 3 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: #50071: Unable to connect to the database SharePoint_AdminContent_a9991124-7852-4cc2-8a15-470a061b7a0d on svrhspuneet. Check the database connection information and make sure that the database server is running..
Please help me resolve this.
Thanks
Hi Puneet try running the sharepoint configuration wizard again. your problem will get resolved.

Any possible reasons, when cannot create web application at sharepoint 2007 from central administration or using extendvs

Pls give me any suggestion.
Now I cannot create new web applicaion at sharepoint 2007 from central administration ... error shows that "unknow error" ... so any possible reasons?? ... that i need to check for this error ...
I also cannot create new web application with extendvs stsadm command ... because my database server is from the another machine .. errors shows that ...
Directory lookup for the file "F:\MSSQL\DATA\WSS_Content_Internet_NewProd.mdf" f
ailed with the operating system error 3(The system cannot find the path specifie
d.).
CREATE DATABASE failed. Some file names listed could not be created. Check relat
ed errors.
CREATE DATABASE failed at stsadm -o extendvs
so ... any things that i need to check ??
I have appropritate permission to use the database from another machine ...
pls give me any suggestion to create new web application using central admin or extendvs
any possible reasons ?
Try to create a database, any database, manually on that SQL server, you will probably get an error as well. This could be a result of misconfiguration on the server or physical errors on disk F.

Debug an Error in a Custom SharePoint Web Service

I have created a custom SharePoint web service that was deployed to, and successfully tested on, a test environment. Unfortunately, the web service has since stopped working, and I am trying to determine what the error is.
The web service now returns the following error in the SOAP response:
SOAP:server
Server was unable to process request. Object reference not set to an instance of an object.
There have been no changes to the deployed web service, so I am assuming that a more recent deployment has altered the SharePoint configuration. My web service .asmx is deployed to the _vti_bin folder, and the assembly is deployed to the GAC. I can see the WSDL file being displayed when I browse to http://servername:port/_vti_bin/MyCustomWebService.asmx. The web methods in the assembly make use of logging (to the Windows Event log), but no logging is occurring when I try and access the web service, which suggests that the call is not getting as far as entering the web method.
Given the above, can anyone offer any suggestions as to debug this issue?
Thanks. MagicAndi.
Update
I have now realised that when I consume the web service from the endpoint http://servername:port/Site/_vti_bin/MyCustomWebService.asmx, it works, but when I use the endpoint http://servername:port/_vti_bin/MyCustomWebService.asmx, the web service fails as described above. I will update further when I diagnose the cause of the issue.
this is a try catch to get more infomraion on the exception. It will give you more information which will help debug your problem
try {
// Do soap call here
}
catch (System.Web.Protocols.SoapException soap_ex)
{
Console.WriteLine(soap_ex.Detail.OuterXML);
}
catch(System.Exception ex)
{
Console.WriteLine(ex.Message);
}
The easiest option is to attach a debugger set to break on exceptions. If your infrastructure rules don't allow that, you'll probably need to add some additional logging to your code on the server. If you are lucky there may be enough information available in the soap message, but in my experience null reference exceptions usually need more information to be found easily.

Resources