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.
Related
I'm trying to read data from Share Point online. I'm using KingwaySoft SharePoint Drivers on SSIS.
I'm getting below error even though with provided credentials
what could be the reason?
do I have to change the URL pattern?
Resolved
I have added /_vti_bin/listdata.svc/ at the end of the site URL.
like :
https://company0.sharepoint.com/sites/sfinfo/IT_team/_vti_bin/listdata.svc/
Thanks
The ideal service URL that you would need to provide should include the base site and subsite, if necessary, and no other details.
Give it a try and if the error persists, please reach out to our support team with the screenshot of the SharePoint connection manager configuration.
I have an Azure logic app, inside that i am creating FTP (when file is added or modified) but after creation of FTP connection, i am unable to see the folder name inside the folder box with the error "The gateway did not receive a response from 'Microsoft.Web' within the specified time period".
Did you follow the steps in the doc create the FTP connector?
I think the problem is you didn't open the passive mode, the mode is a prerequisite asked in the doc. Due to environmental constraints, I couldn't open the passive mode, you could try it. And you need make sure you server is accessible from the internet.
If you still have questions, please let me know.
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.
I deployed an application on Azure. Now, I setup my MvcWebRole project to publish directly to my role instance through web deploy. (refering link : http://www.wadewegner.com/2010/12/using-web-deploy-with-windows-azure-for-rapid-development/ )
However, whenever I am trying to publish an application, it is giving an error like:
Error 1 Web deployment task failed.(Remote agent (URL http://mywebsvr/MSDEPLOYAGENTSERVICE) could not be contacted.
Make sure the remote agent service is installed and started on the target computer.)
The requested resource does not exist, or the requested URL is incorrect.
Error details:
Remote agent (URL http://mywebsvr/MSDEPLOYAGENTSERVICE) could not be contacted. Make sure the remote agent service is installed and started on the target computer.
An unsupported response was received. The response header 'MSDeploy.Response' was '' but 'v1' was expected.
The remote server returned an error: (404) Not Found. 0 0 CPE Tracking System
I read some articles and most of them advise to make sure the remote agent service is already started by issuing the command "net start msdepsvc". But I don't know why issuing this command will return the error "The service name is invalid".
How come the server can't understand the parameter msdepsvc?
Would anybody please help!
Thanks,
TAdhav
I would try to use the new SDK 1.4 Refresh. That includes an officially supported WebDeploy tooling now and is much more likely to work without hiccups.
More information and link to download here:
http://blogs.msdn.com/b/windowsazure/archive/2011/04/15/now-available-windows-azure-sdk-1-4-refresh-with-webdeploy-integration.aspx
Thanks for your reply. Problem is resolved now. The user trying to deploy an application didn't have permission on machine.
Reference link: http://forums.iis.net/p/1176267/1974277.aspx
Link Used for setting up permission on server is: http://learn.iis.net/page.aspx/155/an-overview-of-feature-delegation-in-iis-70/
Thanks,
TA
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.