Known issues with SPDiag
Applies To: Office SharePoint Server 2007
This Office product will reach end of support on October 10, 2017. To stay supported, you will need to upgrade. For more information, see , Resources to help you upgrade your Office 2007 servers and clients.
Topic Last Modified: 2016-11-14
Read this section for information about known issues in SPDiag.
Error when importing a project to a machine with a different language (SPDiag v2)
When you import a project containing IIS or ULS log files that were generated on a computer with a different language setting than the computer running SPDiag, SPDiag experiences an unhandled exception due to an ASCII page code mismatch.
Workaround: Before you import the project, on the computer running SPDiag, change the locale in Windows Server Regional and Language Options to match the language of the computer on which the log files were generated. After the project has been imported, you can change the locale back to the original setting. However, if you import additional log files in the future, you will need to change the locale again before you import them into the project.
This issue only applies to SPDiag v2, as you cannot import projects in SPDiag v1.
Unhandled exception in SPDiag when Named Pipes SQL connection is used (SPDiag v1)
When you create a new project in SPDiag, and you try to create the project database on a SQL Server computer that has been configured to use named pipes instead of TCP/IP, SPDiag experiences an unhandled exception. We recommend that you configure the computer running SQL Server and hosting the project database to use TCP/IP connections.
If you must use named pipes, you can work around this issue by adding the prefix np: to the pipe name in the format np:hostname.
This issue has been resolved in SPDiag v2.
Database column in custom reports reads “NOT AVAILABLE”
If SPDiag is run in offline mode, the database column in custom reports will read NOT AVAILABLE. This is by design. When SPDiag is not connected to a SharePoint farm, this information is unavailable. If this condition is unexpected, check to be sure the farm is operational.
Installed physical memory value in Snapshot is incorrect for virtualized SharePoint servers
When you examine the “Installed physical memory” field in the Snapshot pane for a SharePoint server running in a virtual machine, the value is incorrect. There is no workaround at this time.
Unicode characters in URLs are logged by IIS as question marks
When Unicode characters are used in SharePoint URLs, IIS logging will convert the characters to questions marks unless UTF-8 logging is enabled in IIS, and the relevant language packs are installed on the computer running SharePoint Products and Technologies.
For more information on UTF-8 logging in IIS, see Enabling UTF-8 Format for Non-English Languages and Security (http://go.microsoft.com/fwlink/?LinkId=141340).
For more information about installing Windows SharePoint Services 3.0 language packs, see Deploy language packs (Windows SharePoint Services) (http://go.microsoft.com/fwlink/?LinkId=141341).
Farm calculated performance counters are not displayed
In order for SPDiag to calculate and display farm performance counters (such as number of requests across the farm, or request response time), you must first upload the IIS logs for the desired time range by selecting them in the Consolidated Logs pane. If data from the IIS logs have not been uploaded to the project database, SPDiag cannot calculate the data, and no results will be displayed for these counters.
Data is missing for some or all of the farm servers
If an SPDiag project is missing data even though SPDiag has been configured correctly, the user account you are using to run SPDiag might not have sufficient permissions to access WMI data, or to copy log files from the target servers. Make sure the user account has administrative rights on all farm servers, and has been granted administrator rights using SharePoint Products and Technologies account administration.