Home > Project Server > Project Server 2007 Error 42

Project Server 2007 Error 42

Is this a permissions issue? Statusing Web service error codesStatusing error codeDescriptionStatusingInvalidEntity = 3102Invalid entity for Statusing.StatusingGetDataForTaskFailed = 3103Failed to get data for task status.StatusingGetTaskOrAssnCntrFailed = 3104Failed to get task or Assignment Center for status.StatusingInvalidPIDForProjCntr = Chefetz [MVP] 2008-08-06 20:30:06 UTC PermalinkRaw Message MAS:This could be caused by a number things in Critix. As a Gold Certified Independent Software Vendor (ISV), Solvusoft is able to provide the highest level of customer satisfaction through delivering top-level software and service solutions, which have been subject to useful reference

wildo 2008-01-24 16:17:02 UTC PermalinkRaw Message Thanks for the info. Error code functional areas and related number rangesProject Server functional areaError code number rangesTable 3: General error codes0 - 99; 500 - 999; 9131; 10000 - 10099; 20000 - 20099; 26000 Please Note: If 42 errors still persist after a clean install of Windows, your Runtime Errors problem MUST be hardware related. Regards RobRob Hardy Wednesday, August 24, 2011 1:22 PM Reply | Quote 0 Sign in to vote Hi Rob, What service pack is your Project 2007 client?

If you choose to participate, the online survey will be presented to you when you leave the Technet Web site.Would you like to participate? Enter any administrator passwords (if prompted). MHS70 2008-01-16 19:27:06 UTC PermalinkRaw Message I'm having the same problem.  Did you find a solution yet?Post by AngieI just loaded both the Windows Sharepoint Services 3.0 SP1 and 2007 MS

Can the post SP1 hotfixresolve the problem? 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. That helped in getting rid of the old version completely and then installing the MS Project Professional version again. There seems to be a problem with the database, please contact your server administrator.

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... Solution A trailing space was found at the end of a Global Template. Any otherideas?Post by MHS70Post by wildoI'm having the same problem. https://blogs.msdn.microsoft.com/brismith/2012/11/07/project-server-databasesplease-dont-mess-with-the-default-options/ I can open the PWA siteand all web sites, but I cannot open project from a Project Pro 2007 clientworkstation using my previous project server account setups.I get the following error

If updates are available, click the Install Updates button. Did you find a resolution?Post by wildoIt happens when immediately when trying to connect.I also installed SP1 for MS Project Pro, and still have the same problem.Post by MHS70Post by wildoI Details: Attributes:  . wildo 2008-01-16 16:25:02 UTC PermalinkRaw Message I'm having the same problem.

You'll needto run the select * from versions query to check very version #. http://microsoft.public.project.server.narkive.com/JAuiDnFZ/job-failed-could-not-load-project-project-server-error-code-42 Runtime Errors such as “Error 42” can be caused by a variety of factors, so it is important that you troubleshoot each of the possible causes to prevent it from recurring. For example, if you use Resource.CheckOutResources where one of the resources is already checked out, PSErrorInfo shows the reason for failure for each resource that cannot be checked out, but does That version is dated back to June 2012.

If the problem persists,contact your system administrator.The only option is to click ok through this error.Then this message appears " Could not retrieve enterprise global template.There seems to be a problem http://bsdupdates.com/project-server/project-server-2007-error-codes.php I'm an administrator (actually have given myself allgroups), and have not changed anything in security anywhere. Site does not seem to exist. Privacy & Cookies Terms of Use Trademarks © 2016 Microsoft Sign-in Register Site help Skip to ContentSkip to FooterSolutions Transform to a Hybrid Infrastructure Protect Your Digital Enterprise Empower the Data-Driven

Incorrectly editing your registry can stop your PC from functioning and create irreversible damage to your operating 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 In most cases, the "Temporary Files" category will occupy the most disk space. this page You'll needto run the select * from versions query to check very version #.

Is this a permissions issue? This is agood site that will tell you what RTM and SP1 versions should be.http://blogs.msdn.com/shaden/Looks as though I need to push out SP1 again. wildo 2008-01-23 22:41:02 UTC PermalinkRaw Message No resolution yet, and we have several people looking into it - getting readyto uninstall and reinstall and see what happens.In the meantime, I also

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

Custom field error codesCustom field error codeDescriptionCustomFieldInvalidPropertyType = 11500Invalid property type.CustomFieldInvalidScope = 11503Invalid scope.CustomFieldScopesMustBeIdentical = 11504The scopes must be identical.CustomFieldInvalidEntityUID = 11505Invalid entity GUID.CustomFieldHasInvalidPropertiesForNonLookupTableCF = 11506Invalid properties for a custom field We may need to take this offline for more detailed troubleshooting. I'm an administrator (actually have given myself allgroups), and have not changed anything in security anywhere. Clicking more Info button reveals more details.

Table 1 lists the functional areas for Project Server error codes, with the general number ranges. You'll needto run the select * from versions query to check very version #. These are both clean 2007 installs, using WindowsAuthentication. Get More Info Is this a permissions issue?

Type "command" in the search box... Char 2008-01-23 23:06:01 UTC PermalinkRaw Message Hi Wildo,I'm working on this issue right now with Microsoft. Type "regedit" and hit ENTER. I am getting the same problem.Post by masjfal...and so am I.

Ms Project Professional versions prior to that number will not be able to connect with MS Project Server. Please try after some time. So if these two are related, it's not just a problemin connecting with Project Pro.Post by CharHi,I'm having the exact issue.