ProjectOptCurrencyCodeNot3Chars = 1045 The optional currency code is not three characters. ArchiveSystemSettingsFailure = 25022 Cannot read the system settings archive. We had to replicate some of the changes as the ‘good' DB backup copy was slightly older. OptimizerCannotCreateAnalysis = 29603 Cannot create the portfolio analysis. useful reference
Issue with both default and custom templates. CalendarRecurrenceMonthShouldNotBeNull = 13004 The recurrence month should not be null. Always, if I assign in the Project Prof Client a resource (a user created from AD) to a task and then publish the project to the server, I get the following CBSGetDefaultOlapDatabase = 17026 Error in getting the default OLAP database. https://msdn.microsoft.com/en-us/library/office/ms508961.aspx
I am getting same error as mentiond in below URL. ProjectHasNoReadLock = 1032 Project does not have a read lock. ProjectTypeInvalidForCreate = 1003 The project type for the create operation is not valid. PlannerInvalidProjectDuration = 28202 The project duration is not valid.
ProjectUpdateDuplicateUpdateSequenceNumber = 1152 Duplicate sequence number in the project update. SRAInvalidVersion = 27300 SRA invalid version. LookupTableLanguageParameterInvalidWithXmlFilter = 11080 A language parameter is not valid with a lookup table xmlFilter parameter. AdminInvalidCompatibilityMode = 28030 The compatibility mode is not valid.
CustomFieldRolldownInvalidOnFormulaFields = 11717 A roll down cannot occur on a formula custom field. OptimizerInvalidRange = 29200 The date range for the optimizer is not valid. CustomFieldCannotModifyDepartmentUidOnBuiltinFields = 11732 The department GUID cannot be modified on built-in custom fields. Below steps helps you to enable the Microsoft SharePoint Foundation Workflow Timer Service in Central Administrator: 1.
CalendarFilterInvalid = 13043 The filter is not valid for a calendar. LookupTableMaskHasGaps = 11002 The lookup table code mask has gaps. GeneralSecurityAccessDenied = 20010 Access is denied because of security permissions. CICOAlreadyCheckedOutToYou = 10101 Already checked out to you.
What I Encountered - My Findings The site creation failed with project creation and manual process. https://badalratra.wordpress.com/category/project-server-2010/issues/ Cause: The time taken to popluate the large value set exceeds the time available to update the lookup table resulting in a time out error when a save is attempted on Project Server 2010 Error Codes CBSErrorReadingCubeDepartments = 17033 Error reading departments in the OLAP cube. Project Server 2013 Rest Api ProjectCheckedout = 1007 Project checked out.
To process more than 1000 items, use multiple calls, for example, to QueueUpdateProject. see here CBSOlapDatabaseReadSettingListFailed = 17021 Failed to read the OLAP database list of settings. This topic lists the error codes in tables that are arranged by the PSI class or functional area and by the error identifier (ID) number. OptimizerCannotCreateDependency = 29008 The dependency cannot be created.
For a way to get more information, see CheckOutResources. OptimizerCannotEditAnalysis = 29614 Cannot edit the portfolio analysis. PlannerInvalidTimeScale = 28007 The time scale is not valid. this page OptimizerInvalidPlannerData = 29615 The Planner data is not valid for the Optimizer.
GeneralStartDateGTorEQFinishDate = 26 The specified date range is not valid. AdminInvalidDatabaseTimeoutType = 28027 Timeout due to a database type that is not valid. I am also a Microsoft Business Value Planning Services (BVPS) Consultant helping organisations streamline their business processes using Microsoft Office System solutions.
Use a database in DataStoreEnum. Can anyone identify the city in this photo? When i changed to the old name it doesn't work. Mathematics tenure-track committees: Mathjobs question Can we feed external data to xDB?
Posted by PJ Mistry at 20:42 Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest Labels: Knowledge Base, Known Issues No comments: Post a Comment Please include your email address with comments. Admin web service error codes Admin error code Description AdminViewNameAlreadyExists = 16600 The view name already exists. Restore previous ‘good' backup of the SQL databases Restore from previous SharePoint farm backup I went for Option (2) above and everything started working fine. Get More Info This is a general error code that could result from many different causes.