Table 3: General error codes, except 20003 is in Table 6: Admin web service Table 23: Security, except 19011, 19012, and 19032 are security-related codes in Table 6: Admin web service Table 31: WssInterop and Object Link Provider (SharePoint integration) Table 18: Projects, except 9131 is in Table 3: General error codes Table 3: General error codes, except 77 is in Table 9: Calendar Error code table by number range Error code range Table 31: WSSInterop and ObjectLinkProvider (SharePoint integration)ġ6400 - 16499: SharePoint integration and project workspaces 18000 - 18099: Object Link Provider and SharePoint project import Table 16: Optimizer (project portfolio analysis) However, tables in this article include all Project Server error codes for completeness. For example, because the ExchangeSync and PWA web services are not supported for third-party development, you are not likely to see error codes from methods in those areas, such as the Rules and StatusReports methods. Many of the error codes are used only internally.For more information, see SQL Server Profiler. Use the Microsoft SQL Server Profiler to help catch or monitor database errors.To help find or watch for specific issues in ULS data, use the ULS Viewer.For more information about using ULS logs, see the Project Support blog article Project Server 2010: What to Expect when you get the Unexpected, and search the blog for "reading ULS logs.".For an explanation, see the Checking Errors section in Getting Started with Development for Project 2010. Use the Unified Logging Service (ULS) trace logs.Use the application event log on the Project Server computer.
For WCF-based applications, you can use to get a PSClientError object and also to get additional error information.For ASMX-based applications, use .SoapException with the PSClientError object to show a list or hierarchy of errors in a PSI method call.For more information about errors, you can do the following: Many of the error codes are general and can have multiple possible causes.
0 kommentar(er)
