SharePoint 2013 报错 "Server Error in '/' Application"

霖雨 SharePoint 开发  2014-07-15 04:46:23
环境描述
Windows 2012 r2 + SharePoint 2013,sql、SharePoint、ad分开装的;

访问报错如下
Server Error in '/' Application.
--------------------------------------------------------------------------------
Runtime Error
Description: An exception occurred while processing your request. Additionally, another exception occurred while executing the custom error page for the first exception. The request has been terminated.

操作
管理服务器的部门,打了补丁,具体补丁如下:
KB2929961
KB2930275
KB2596672
KB2925418
KB972222
KB2251487
KB2669970
KB2919355

其他错误信息
1、The Forefront Identity Manager Synchronization Service service terminated with the following service-specific error:
Unspecified error

2、The AppFabric Caching Service service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.

3、The event logging service encountered an error (5) while enabling publisher {0bf2fb94-7b60-4b4d-9766-e82f658df540} to channel Microsoft-Windows-Kernel-ShimEngine/Operational. This does not affect channel operation, but does affect the ability of the publisher to raise events to the channel. One common reason for this error is that the Provider is using ETW Provider Security and has not granted enable permissions to the Event Log service identity.

4、Application 'C:\Windows\System32\inetsrv\w3wp.exe' (pid 6444) cannot be restarted - Application SID does not match Conductor SID..

5、There was an internal error invoking the timer job '{15766937-724B-4109-9E34-DA2327370F99}' for service '{724A167C-2E68-4AEF-BCBC-908EBF81CCC4}'.

6、Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (809d193a-c197-4a34-893c-e8d914bcb76b).

7、SQL Database 'SharePoint_Config' on SQL Server instance 'MySQLServer' not found. Additional error information from SQL Server is included below.

Cannot open database "SharePoint_Config" requested by the login. The login failed.
Login failed for user 'domain\user'.

8、Event 5586 (SharePoint Foundation) of severity 'Error' occurred 345 more time(s) and was suppressed in the event log

TimerJob报错
error1:
Unknown SQL Exception 64 occurred. Additional error information from SQL Server is included below. A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The specified network name is no longer available.)

error2:
Can not connect to configuration database: System.Data.SqlClient.SqlException (0x80131904): A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The specified network name is no longer available.) ---> System.ComponentModel.Win32Exception (0x80004005): The specified network name is no longer available
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
at System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj, UInt32 error)
at System.Data.SqlClient.TdsParserStateObject.ReadSniSyncOverAsync()
at System.Data.SqlClient.TdsParserStateObject.TryReadNetworkPacket()
at System.Data.SqlClient.TdsParserStateObject.TryPrepareBuffer()
at System.Data.SqlClient.TdsParserStateObject.TryReadByte(Byte& value)
at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData()
at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior)
at Microsoft.SharePoint.Utilities.SqlSession.ExecuteReader(SqlCommand command, CommandBehavior behavior, SqlQueryData monitoringData, Boolean retryForDeadLock)
at Microsoft.SharePoint.Utilities.SqlSession.ExecuteReader(SqlCommand command, CommandBehavior behavior)
at Microsoft.SharePoint.Administration.SPConfigurationDatabase.FetchObject(Guid id)
at Microsoft.SharePoint.Administration.SPConfigurationDatabase.GetObject(Guid id, Boolean checkInMemoryCache, Boolean checkFileSystemCache)
at Microsoft.SharePoint.Administration.SPConfigurationDatabase.Initialize(SqlConnectionStringBuilder connectionString, Boolean enableCaching, Boolean checkCompatibility, Boolean bindRequestGuid)
at Microsoft.SharePoint.Administration.SPConfigurationDatabase.Initialize(SqlConnectionStringBuilder connectionString, Boolean enableCaching, Boolean checkCompatibility)
at Microsoft.SharePoint.Administration.SPConfigurationDatabase.get_Local() ClientConnectionId:50754574-0652-4bdb-aea0-bbf61c77b1ef

特别的,通过对SharePoint Logs的观察,报错是从0点开始的。以上是错误的详细描述,希望碰碰运气,有遇到过的给我个回信儿。
...全文
645 点赞 收藏 17
写回复
17 条回复
Justin-Liu 2014年07月22日
引用 16 楼 linyustar 的回复:
[quote=引用 14 楼 FoxDave 的回复:] 坐等答案~
没答案了,重新装了,微软一起追踪了一礼拜,没解决; 我是来结贴的,哈哈哈~~应该是某一个补丁引起的,但是不知道是哪个;[/quote] 微软太差了 他们给你用windebug调试了吗?
回复 点赞
Justin-Liu 2014年07月21日
坐等答案~
回复 点赞
霖雨 2014年07月21日
算了,吐槽无意义,还是解决问题吧~~
回复 点赞
霖雨 2014年07月21日
引用 14 楼 FoxDave 的回复:
坐等答案~
没答案了,重新装了,微软一起追踪了一礼拜,没解决; 我是来结贴的,哈哈哈~~应该是某一个补丁引起的,但是不知道是哪个;
回复 点赞
jikai2008 2014年07月21日
adminsitrator的domain user是否过期了?
回复 点赞
CreateSiteCollection 2014年07月18日
如果所有报错是从0点开始的 那麼你要問你的同事0點到底發生了什麼事 怎看都想像不到Workflow會把SQL斷掉, 應該是Infrastructure的同事搞死的, 例如樓上所述殺毒軟件所害
回复 点赞
Crazygolf 2014年07月18日
引用 11 楼 legendgod 的回复:
[quote=引用 10 楼 linyustar 的回复:] [quote=引用 9 楼 legendgod 的回复:] 如果所有报错是从0点开始的 那麼你要問你的同事0點到底發生了什麼事 怎看都想像不到Workflow會把SQL斷掉, 應該是Infrastructure的同事搞死的, 例如樓上所述殺毒軟件所害
现在基本上20点-21点挂一次,重启了;早上6-7点挂一次; 是因为补丁造成的,具体哪个补丁还不清楚,怎么解决还在查; 开了微软的case,如果有结果了,我回来这里回复的,呵呵~[/quote] 所以麻.... 我認為, 除非有功能需求, 否則投產了的系統絕對不要打補丁 (微軟不只一次害慘我了)[/quote] 打补丁真的要谨慎
回复 点赞
CreateSiteCollection 2014年07月18日
引用 10 楼 linyustar 的回复:
[quote=引用 9 楼 legendgod 的回复:] 如果所有报错是从0点开始的 那麼你要問你的同事0點到底發生了什麼事 怎看都想像不到Workflow會把SQL斷掉, 應該是Infrastructure的同事搞死的, 例如樓上所述殺毒軟件所害
现在基本上20点-21点挂一次,重启了;早上6-7点挂一次; 是因为补丁造成的,具体哪个补丁还不清楚,怎么解决还在查; 开了微软的case,如果有结果了,我回来这里回复的,呵呵~[/quote] 所以麻.... 我認為, 除非有功能需求, 否則投產了的系統絕對不要打補丁 (微軟不只一次害慘我了)
回复 点赞
霖雨 2014年07月18日
引用 9 楼 legendgod 的回复:
如果所有报错是从0点开始的 那麼你要問你的同事0點到底發生了什麼事 怎看都想像不到Workflow會把SQL斷掉, 應該是Infrastructure的同事搞死的, 例如樓上所述殺毒軟件所害
现在基本上20点-21点挂一次,重启了;早上6-7点挂一次; 是因为补丁造成的,具体哪个补丁还不清楚,怎么解决还在查; 开了微软的case,如果有结果了,我回来这里回复的,呵呵~
回复 点赞
wl19861202 2014年07月16日
半夜是不是有杀毒软件在跑???
回复 点赞
霖雨 2014年07月16日
补充一下,所有TimerJob的错误 Work Management Synchronize with Exchange A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The semaphore timeout period has expired.) 7/16/2014 8:01 AM Health Statistics Updating A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The semaphore timeout period has expired.) 7/16/2014 8:00 AM User Profile Service Application - Feed Cache Repopulation Job Unexpected exception in FeedCacheService.IsRepopulationNeeded: Connection to the server terminated,check if the cache host(s) is running . 7/16/2014 8:00 AM Microsoft SharePoint Foundation Usage Data Import A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The semaphore timeout period has expired.) 7/16/2014 7:16 AM Health Statistics Updating A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The semaphore timeout period has expired.) 7/16/2014 7:02 AM Search Custom Dictionaries Update Failed to run flow Microsoft.CustomDictionaryDeployment. Correlation Id: 0be8a49c-8590-f0fd-e016-2b3b628d66df. 7/16/2014 7:20 AM Health Analysis Job (Hourly, Security Token Service, All Servers) Health Analysis Job (Hourly, Word Automation Services, Any Server) Health Analysis Job (Hourly, Microsoft SharePoint Foundation Timer, Any Server) Health Analysis Job (Hourly, Microsoft SharePoint Foundation Timer, All Servers) Health Analysis Job (Hourly, User Profile Service, Any Server) Health Analysis Job (Hourly, Distributed Cache, All Servers) 7/16/2014 7:00 AM My Site Instantiation Interactive Request Queue Document Set fields synchronization job Workflow Failover Workflow My Site Instantiation Non-Interactive Request Queue Translation Export Job Definition User Profile Service Application - Feed Cache Repopulation Job pause 7/16/2014 6:00 AM Product Version Job(Checks the install state of the machine and puts that data into the database.) Collection was modified; enumeration operation may not execute. 7/16/2014 12:51 AM 这些错误,基本都是重启以后就不出现了,出现时间就是每天0点 - 重启之前。
回复 点赞
Justin-Liu 2014年07月16日
不好整啊这样的 拿windebug跑
回复 点赞
霖雨 2014年07月16日
引用 3 楼 jason_dct 的回复:
霖雨, 你确认你的防火墙、策略做好了。 ok看到了 Job 错误了,去管理中心看一下你的 所有timer 或者JOB 或者正在运行的程序。 找到 报错之后 被终止的job --------------查找它需要访问的页面或其他事件。 肯定有被关闭的。
我昨天就已经把所有的job看了一遍,居然没发现有报错的;日志里提到报错的job,状态居然是successed,而且即使SharePoint挂了,所有的job依然正常运行;今天早上又宕机了,想早点过来看看服务器宕机时的状态,结果被抢先重启了,哎。 我怀疑因为打了补丁,然后某些job运行,造成了内存或者sql执行中断,使SharePoint不能正常运行了,但是现在没有信息能证明我的想法,愁。 继续谷歌吧...
回复 点赞
Crazygolf 2014年07月15日
报错这么多。。。
回复 点赞
段传涛 2014年07月15日
霖雨, 你确认你的防火墙、策略做好了。 ok看到了 Job 错误了,去管理中心看一下你的 所有timer 或者JOB 或者正在运行的程序。 找到 报错之后 被终止的job --------------查找它需要访问的页面或其他事件。 肯定有被关闭的。
回复 点赞
霖雨 2014年07月15日
引用 1 楼 legendgod 的回复:
[quote=引用 楼主 linyustar 的回复:] SQL Database 'SharePoint_Config' on SQL Server instance 'MySQLServer' not found. Additional error information from SQL Server is included below. Cannot open database "SharePoint_Config" requested by the login. The login failed. Login failed for user 'domain\user'.
我想所有錯誤都由於這個, 只能建議你詳細的檢查SQL的連接有沒有錯誤, 或是SQL的用戶權限有變, 或是路由器, 防火牆之類 我以前遇過一個狀況, 我的SP原本指向一個叫SPDB的名, 由於負責DNS的人, 把SPDB指向另一台SQL SERVER, 但那台SQL SERVER當然沒有SharePoint_Config, 所以測試老半天連接是通的, 但Sharepoint卻一直出SQL exception error.[/quote] sql指向没问题,登陆上去也能打开,都没问题;两台服务器,分别重启,就好了,转天继续报错,纠结~
回复 点赞
CreateSiteCollection 2014年07月15日
引用 楼主 linyustar 的回复:
SQL Database 'SharePoint_Config' on SQL Server instance 'MySQLServer' not found. Additional error information from SQL Server is included below. Cannot open database "SharePoint_Config" requested by the login. The login failed. Login failed for user 'domain\user'.
我想所有錯誤都由於這個, 只能建議你詳細的檢查SQL的連接有沒有錯誤, 或是SQL的用戶權限有變, 或是路由器, 防火牆之類 我以前遇過一個狀況, 我的SP原本指向一個叫SPDB的名, 由於負責DNS的人, 把SPDB指向另一台SQL SERVER, 但那台SQL SERVER當然沒有SharePoint_Config, 所以測試老半天連接是通的, 但Sharepoint卻一直出SQL exception error.
回复 点赞
发动态
发帖子
SharePoint
创建于2007-12-13

3027

社区成员

4593

社区内容

企业开发 SharePoint
社区公告
暂无公告