Sharepoint Error Event Id 27745
Solved Windows Sharepoint Services 3 event ID 27745 Posted on 2011-09-06 MS SharePoint SBS 1 Verified Solution 9 Comments 2,129 Views Last Modified: 2012-08-13 The Sharepoint component of my SBS 2008 Error: 17806, Severity: 20, State: 2. Check the database connection information and make sure that the database server is running.. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. have a peek here
You can install or repair the component on the local computer. #50071: Unable to connect to the database SharePoint_Config_xxx-xxx-xxxx-xxxx-xxxxxxxxxxxx on xxxxxx\Microsoft##SSEE. Get 1:1 Help Now Advertise Here Enjoyed your answer? Post navigation « Previous Post 5 Responses to Event ID 27745 Dave says: May 25, 2011 at 2:26 pm on what server do you set the spn? It seems my SharePoint install was corrupt BUT I had an additional problem in that when running cliconfg TCP/IP was enabled. https://social.technet.microsoft.com/Forums/office/en-US/7e4520ea-883f-4a3b-942b-961cfea35eba/moss-bug-event-id-27745-fault-while-connecting-to-config-db?forum=sharepointadminlegacy
- Thank you!
- Join Now During routine log maintenance on our Sharepoint server (WS2K3 w/WSS 3.0, upgraded from 2.0) our Event Viewer Application log became flooded with the below errors from Windows Sharepoint Services:
- The following information was included with the event: #50071: Unable to connect to the database SharePoint_Config_29c26fca-17b8-48c1-9704-b869932abcb6 on ANTHEMSERVER\Microsoft##SSEE.
- If I try using Firefox I am prompted for a user and password and then get: HTTP/1.1 200 OK Server: Microsoft-IIS/7.0 Date: Thu, 09 Jun 2011 11:02:41 GMT Connection: close In
- I'm running Small Business Server 2008 Premium with the default install of IIS etc.
- You can connect to it by using the following as the instace name to connect to in Management Studio: \\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query Go to Solution 9 Comments LVL 5 Overall: Level 5
- First Name Please enter a first name Last Name Please enter a last name Email We will never share this with anyone.
TechCenter Sign in United States (English) Brasil (Português)Česká republika (Čeština)Deutschland (Deutsch)España (Español)France (Français)Indonesia (Bahasa)Italia (Italiano)România (Română)Türkiye (Türkçe)Россия (Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) Home20132010Other VersionsLibraryForumsGallery Ask Check the database connection information and make sure that the database server is running. 06/20/2011 22:57:15.52 OWSTIMER.EXE (0x2C1C) 0x57C8 Windows SharePoint Join & Write a Comment Already a member? http://www.jeremythake.com/2008/04/the-description-for-event-id-27745-in-source-windows-sharepoint-services-3-cannot-be-found/ Exchange How to Monitor Bandwidth using SNMP or WMI using PRTG Network Monitor Video by: Kimberley This video gives you a great overview about bandwidth monitoring with SNMP and WMI with
Another Stock Crunch: Intel Second Generation Core... https://www.experts-exchange.com/questions/27293779/Windows-Sharepoint-Services-3-event-ID-27745.html thanks! As such the majority of these customers utilize some version of Small Business Server. Hyper-V Hanging at Shutting Down Cluster Service …...
It doesn't give the detailed solution but hopefully it may provide someone else with pointers in the future. http://dualathlonserver.com/sharepoint-error/sharepoint-error-event-id-5000.php Ran PSconfig and it failed again. ¿ Removed the WSS search database and content db from Sql Studio. ¿ Removed sharepoint again. ¿ Ran Procmon while installing the sharepoint. ¿ We If it's on a separate server it could be a network related issue. 0 Message Author Comment by:DesertDawg2011-09-06 Thanks. Check the database connection information and make sure that the database server is running.
I'll check that out. 0 Message Author Comment by:DesertDawg2011-09-06 Where is "SharePoint_Config_29c26fca-17b8-48c1-9704-b869932abcb6" located? 0 LVL 38 Overall: Level 38 SBS 8 MS SharePoint 2 Message Active today Expert Comment New computers are added to the network with the understanding that they will be taken care of by the admins. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. Check This Out After digging more and more I found these errors in the SQL servers’ logs: The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL
You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. Practice CS (Creative Solutions) 2011.2.3 Update A... From accounting app support through to highly available solutions for accounting firms we've got it covered.
Either the component that raises this event is not installed on your local computer or the installation is corrupted.
Philip Elder MPECS Inc. Log Name: Application Source: Windows SharePoint Services 3 Date: 9/6/2011 4:35:33 AM Event ID: 27745 Task Category: General Level: Subscribe to our monthly newsletter for tech news and trends Membership How it Works Gigs Live Careers Plans and Pricing For Business Become an Expert Resource Center About Us Who We Lots covered from Greenfield to Migration.
Reply go4zero says: May 25, 2011 at 2:56 pm On any server it doesn't matter but you should login with domain admin account to set this permission Reply Dave says: May More details are available in article 912344. After this my SharePoint sites were back up but the next day there were search errors in the logs again and MS did the following. ¿ Checked if network service is this contact form The following information is part of the event: #50071: Unable to connect to the database SharePoint_Config on DATABASESERVERNAME\SQL01.
That does not mean there isn't anything broken, it just means we have not seen anything. Proposed as answer by Sandeep Lad Monday, October 12, 2009 11:48 AM Unproposed as answer by Mike Walsh FIN Thursday, February 24, 2011 8:48 AM Thursday, September 18, 2008 11:10 AM This is an informational message.