שלום חברים ,
היום אני נתקלתי בשגיאה קריטית ב- Event Log :
השגיאה שראיתי:
"The Execute method of job definition Microsoft.SharePoint.Diagnostics.SPDatabaseServerDiagnosticsPerformanceCounterProvider (ID…..) Threw an exception. More information is included below.
'Alias Name': The network path was not found.
Please ensure that the database server is available and that the SharePoint Timer service account is a member of the Performance Monitor Users group on the database server."
'Alias Name': The network path was not found.
Please ensure that the database server is available and that the SharePoint Timer service account is a member of the Performance Monitor Users group on the database server."
כאשר משתמשים ב-SQL Alias ומתקינים SPDiagמSharePoint AdminToolkit , צריך להבטיח ש- Alias מנותב לכתובת ה-IP של השרת Cluster / DB.
מה שקורה הוא שה-Timer Job ,שהיישום SPDiag יוצר בSharePoint- מבצע פניית RPC כדי לדגום את הביצועים על SQL Server, אולם בשרתי SQL שלא מותקנים על שרת SharePoint אלא על שרת ייעודי או Clusters של SQL הדגימה נעשית לפי שם DNS.
Alias SQL מבלבל את ה- SPDiag בכך שיש לך בחווה שרת ייעודי (נפרד), שרת מסד נתונים עם Alias Name .
כדי לתקן את הבעיה: הסר את ההתקנה של SharePoint Admin Toolkit או להגדיר ערכים ב- DNS או קובץ Host.
בהצלחה !
רון נס.
============================================================================================================================================================================================================================================================
Hello Friends,
Today I encountered in Critical error in the Event Log:
The errors I saw were:
"The Execute method of job definition Microsoft.SharePoint.Diagnostics.SPDatabaseServerDiagnosticsPerformanceCounterProvider (ID…..) Threw an exception. More information is included below.
'Alias Name': The network path was not found.
Please ensure that the database server is available and that the SharePoint Timer service account is a member of the Performance Monitor Users group on the database server."
'Alias Name': The network path was not found.
Please ensure that the database server is available and that the SharePoint Timer service account is a member of the Performance Monitor Users group on the database server."
When you use SQL Aliases and you have installed SPDiag from the SharePoint Administrator Toolkit, you also need to ensure the Alias name resolves to the IP Address of the cluster / DB Server.
What happens is that the timer jobs that the SPDiag application creates in SharePoint make an RPC call to start up a Performance on the SQL Server, however while local SQL Servers, Remote SQL Servers and SQL Clusters addressed by their DNS name and instance work fine, SQL Aliases confuse SPDiag into thinking that you have a Database Server out there somewhere with the Alias name.
Event 6398 of severity ‘Critical’ occurred every minute in the event log.
To fix the Problem: Uninstall the Admin toolkit or set up entries in your DNS system or Host File.
Good Luck :)
Ron Ness.
