In my situtation theynoticed that my Project Server databases weren't ugpraded to SP1. Can the post SP1 hotfixresolve the problem? Even from Information Risk Management prospective, sometimes supporting too old version means also keeping old vulnerabilities alive in your new system. The problem was born just after the SP1 installation.Post by WajdiI have the same problem, after I migrated the farm to new servers updated toSP1, the PWA was successful but when useful reference
The limit is NEW_CF_PER_REQUEST_LIMIT in one request.CustomFieldNameIsReservedName = 11722A custom field name cannot be a reserved name.CustomFieldNameInvalidForOlapMeasure = 11723The custom field name is invalid for an OLAP cube measure.CustomFieldNameInvalidForOlapDimension = 11724The it was an iterative process were I deleted all sections of a plan and saved, if saved I added the next section and saved, etc... Project Server error code:42 (too old to reply) Angie 2008-01-15 23:32:00 UTC PermalinkRaw Message I just loaded both the Windows Sharepoint Services 3.0 SP1 and 2007 MS OfficeServers SP1 (Project Server) The value in the database being queried was just fine - 14.1461140000, the same as on a working system I was comparing with.
Can the post SP1 hotfixresolve the problem? Resource plan error codesResource plan error codeDescriptionResourcePlanProjectPublishIncomplete = 30000Did not complete publishing the project for the resource plan.ResourcePlanInvalidResourceType = 30001Invalid resource type in the resource plan.ResourcePlanInactiveResourcesDisallowed = 30002Inactive resources are not The error given is: > > > The following job failed to complete. Project Server error code:42, wildo Re: Job Failed.
Any ideas on what to research on thedatabase side?Please help! Any ideas on what to research on thedatabase side?Please help!- Hide quoted text -- Show quoted text -Don't panic - it's not a database issue - it's definitely apermissions issue. We have gone through the wizard and the plan has no errors, and is ready to be saved to the server, however when trying to save we get the following error; Delete Actual Work Protected 2003 SQL Queries Enterprise Fields Project Fields Resource Fields Sample Queries Admin Tools Re-associate Site Project Archival VBA Administrators -> MS Project Server
These are both clean 2007 installs, using WindowsAuthentication. You can see the version that is passed on to the PWA is not the right one. Is this a permissions issue? Obviously the lower level tasks indented > under this summary tasks were also 0 duration, o work, and 0% complete.
Project Server Error Codes Office 2007 Other Versions Office 2013 and later Office 2010 This content is outdated and is no longer being maintained. Did you find a solution yet?Post by AngieI just loaded both the Windows Sharepoint Services 3.0 SP1 and 2007 MS OfficeServers SP1 (ProjectServer) in my test environment. Lookup table error codesLookup table error codeDescriptionLookupTableMaskNotDefined = 11000The lookup table code mask is not defined.LookupTableMaskHasTooManyValues = 11001The lookup table code mask has too many values.LookupTableMaskHasGaps = 11002The lookup table code Cancel Home Deployment MS Project PWA SharePoint Articles Administrators FAQs Consulting Guest Book Search Site Map Error Messages Project Server 2003 PWA Login DropDown Inactive vs.
good luck. > > > > "Jim Watson" wrote: > > > Hi > > > > Did you ever get the fix for this problem? > > > > I http://www.office-forums.com/threads/cannot-save-project-to-project-server-2007-error-code-42.1591617/ anyone?//MasjfalPost by DulePlease help. We have another installation that works fine, andthis is a new install. Names must be unique.AdminViewInvalidDividerPosition = 16601The divider position is invalid.AdminViewDataWasTampered = 16602The data has been altered.AdminViewMaxDisplayedFieldsNumberExceeded = 16603The display exceeds the maximum number of fields.AdminViewCannotDeleteDefaultView = 16604Cannot delete the default view.AdminViewCannotCopyDefaultView
Did you find a solution yet?Post by AngieI just loaded both the Windows Sharepoint Services 3.0 SP1 and 2007 MS OfficeServers SP1 (Project Server) in my test environment. http://bsdupdates.com/project-server/project-server-2007-error-codes.php PedroJose Guest Hello, I have installed PS2007 and all is working fine. Char 2008-01-23 23:06:01 UTC PermalinkRaw Message Hi Wildo,I'm working on this issue right now with Microsoft. Any otherideas?Post by MHS70Post by wildoI'm having the same problem.
Which MS Project Professional product can connect with which MS Project Server product? Any ideas on what to research on thedatabase side?Please help!- Hide quoted text -- Show quoted text -Don't panic - it's not a database issue - it's definitely apermissions issue. Ms Project Professional versions prior to that number will not be able to connect with MS Project Server. this page Two otherusers, one with only admin and another with PM, have the same problem.Everything is correct in the MSProjectPro side with the account and URL.We're able to connect and operate everything
Try using a backup copy I published the plan to a completely different Project Server 2010 environment, and it seemed to be ok. Could not Load Project. View the newsletter archive.
Won't I lose my data if I createnew databases? For example, in 2013 we don’t recommend the UPDATE_STATISTICS settings because we, like SharePoint in 2010 and 2013, now have a timer job for that purpose. We have tried restoring to a previous data with no luck. See:http://www.projectserverhelp.com/Lists/Posts/Post.aspx?ID=5This could help you get to your answer sooner.--Gary L.
Two otherusers, one with only admin and another with PM, have the same problem.Everything is correct in the MSProjectPro side with the account and URL.We're able to connect and operate everything With that said, first, I would use PWA and go to "Server Settings" and "Manage Users" and make sure that the authentication you have selected is Windows. Project Server error code:, wildo Re: Job Failed. Get More Info Any ideas on what to research on thedatabase side?Please help!
Make sure the URL is correct.I'll be glad to give you further instructions, but it may not benecessary at this stage.- Hide quoted text -- Show quoted text -How soon do Hardware and software requirements for Project Server 2013 https://technet.microsoft.com/en-us/library/ee683978.aspx Plan browser support in SharePoint 2013 https://technet.microsoft.com/en-us/library/cc263526.aspx Thanks Faisal Masood softvative.com Comment by Faisal Masood on 06/01/2016 at 5:07 pm Hi Faisal We have another installation that works fine, andthis is a new install. The second version number is the version number of Microsoft Office.
Thanks.Post by CharHi Wildo,I'm working on this issue right now with Microsoft. They originally created this plan in Project Professional 2010 (I think someone installed the wrong local copies pre server deployment - they only wanted to use 2007) Any other ideas? As our last resort we went to the resource sheet view and deleted the resources, it worked fine with us like magic.Hope it would be applicable for other cases, too.Thanks 18 If the problem persists, > > contact your system administrator. > > The only option is to click ok through this error. > > Then this message appears " Could not
If the problem persists, save the project > > > as an mpp and contact adminsitrator. > > > > > > Also a little red flag is displayed at the