Project Server 2013: QueueUpdateProject2 fails with LookupTableItemInvalidLookupTable error

Hi,
We have a strange problem here using the newly introduced QueueUpdateProject2 PSI method in WebSvcProject. The server is running version 15.0.4481.1005 (Project Server 2013, March 2013 PU). Here's the minimum repro code:
projectService.CheckOutProject(projectUid, sessionUid, sessionDescription);
var projectDataSet = projectService.ReadProject(projectUid, DataStoreEnum.WorkingStore);
projectDataSet.Project[0].SetModified(); // Simplest repro
var jobUid = Guid.NewGuid();
projectService.QueueUpdateProject2(jobUid, sessionUid, projectDataSet, false);
Unfortunately the QueueUpdateProject2 queue job always fails with error LookupTableItemInvalidLookupTable for this project. Here's the full error information as shown in PWA:
LookupTableItemInvalidLookupTable for lookup table value b99b7782-924c-e311-9404-00155d027b07:
LookupTableItemInvalidLookupTable (11073). Details: id='11073' name='LookupTableItemInvalidLookupTable' uid='b1c62182-924c-e311-9404-00155d027b07'.
Queue:
GeneralQueueJobFailed (26000) - ProjectUpdate.ProjectUpdate2Message. Details: id='26000' name='GeneralQueueJobFailed' uid='b020bf82-924c-e311-9404-00155d027b07' JobUID='f294b911-f500-45bc-91ec-a493bdf3d07a' ComputerName='1beb2ff2-5dc9-4136-aa24-1c2be86c5768'
GroupType='ProjectUpdate' MessageType='ProjectUpdate2Message' MessageId='2' Stage='' CorrelationUID='ce4e569c-0aa5-70d6-c576-8b3b764d14f1'. For more details, check the ULS logs on machine
1beb2ff2-5dc9-4136-aa24-1c2be86c5768 for entries with JobUID
f294b911-f500-45bc-91ec-a493bdf3d07a.
Here are some corresponding entries from the ULS log:
11/13/2013 19:36:30.82 Microsoft.Office.Project.Server (0x06D0) 0x1E60 Project Server                Active Cache Save
myzo Medium Error is: LookupTableItemInvalidLookupTable. Details: LookupTableItemInvalidLookupTable for lookup table value b99b7782-924c-e311-9404-00155d027b07 . Standard Information: , LogLevelManager Warning-ulsID:0x6D797A6F has no
entities explicitly specified. ce4e569c-0aa5-70d6-c576-8b3b764d14f1
11/13/2013 19:36:30.82 Microsoft.Office.Project.Server (0x06D0) 0x1E60 Project Server                Active Cache Save
4zbp Monitorable PWA:, ServiceApp:Project Server Service Application, User:i:0#.w|my\account, PSI: [TrackingId:fa790381-924c-e311-9404-00155d027b07][ResourceId:3222f5b7-c13b-e311-9404-00155d027b07][SessionGuid:db83645c-50e1-4368-a59f-94df13ff7d5e][SessionDescr:][JobGuid:af20bf82-924c-e311-9404-00155d027b07][ProjectGuid:81a4a757-c446-e311-9404-00155d027b07][PS_AC][400]
Microsoft.Office.Project.Server.BusinessLayer.WinProjUtility.WinProjException: LookupTableItemInvalidLookupTable for lookup table value b99b7782-924c-e311-9404-00155d027b07     at Microsoft.Office.Project.Server.BusinessLayer.WinProjUtility.P12Deserializer.PostReadRow(P12ContainerHeader
cntrHeader, Row row)     at Microsoft.Office.Project.Server.BusinessLayer.WinProj.SaveProjectInternal(Guid projGuid, String projName, Int32 projType, Boolean ... ce4e569c-0aa5-70d6-c576-8b3b764d14f1
11/13/2013 19:36:30.82* Microsoft.Office.Project.Server (0x06D0) 0x1E60 Project Server                Active Cache Save
4zbp Monitorable ...isNewProj, Guid jobGuid, Guid sessionGuid, Guid checkOutByResUid, String sessionDescr, Boolean isFirstPacket, Boolean isLastPacket, String newVersionStamp, Int16 dataFormatVersion, Boolean isDataCompressed, Byte[] projectData,
String winprojBuildNumber, ACProcessorType acProcType), LogLevelManager Warning-ulsID:0x347A6270 has no entities explicitly specified. ce4e569c-0aa5-70d6-c576-8b3b764d14f1
We would be happy to provide more information if needed. Project Professional can open and save the project just fine, so it seems to be unrelated to other forum posts (1, 2).
Has anybody seen this before? Any hints on where to search or what to look for?
Thanks,
Thomas
TPG The Project Group
[1] http://social.technet.microsoft.com/Forums/projectserver/en-US/da3c0d64-1ced-45dd-ace6-ce821fd1c362/what-are-the-lookup-fields-in-the-local-project-cant-publish-project-to-the-server
[2] http://answers.microsoft.com/en-us/office/forum/office_2010-project/error-110730x2b41-importsave-to-project-server/03fd792f-4451-4512-ac0b-ddad946c3e3

Just to clarify, I get these errors in the ULS logs:
06-11-2014 14:15:02.42        w3wp.exe (0x23AC)        0x23E0        Project
Server        Active Cache Save        myzo        Medium        Error is: LookupTableItemInvalidLookupTable.
Details: LookupTableItemInvalidLookupTable for lookup table value 440c1ce7-61f1-e311-944d-00155de84b1a . Standard Information: PSI Entry Point: Project User: i:0#.w|africa\spsetupdev Correlation Id: f6a91701-62f1-e311-944d-00155de84b1a PWA Site URL:
http://epmdev.af.didata.local/PWA SA Name: SharePoint_EPM_Dev_ProjectServerService PSError: LookupTableItemInvalidLookupTable (11073), LogLevelManager Warning-ulsID:0x6D797A6F has no entities explicitly specified.        72d0999c-429e-80e4-4f95-1037e3c788ff
06-11-2014 14:15:02.42        w3wp.exe (0x23AC)        0x23E0        Project
Server        Active Cache Save        4zbp        Monitorable        PWA:http://epmdev.af.didata.local/PWA,
ServiceApp:SharePoint_EPM_Dev_ProjectServerService, User:i:0#.w|africa\spsetupdev, PSI: [TrackingId:f6a91701-62f1-e311-944d-00155de84b1a][ResourceId:f6760993-7a33-47ef-8cea-0c9cc5231ae7][SessionGuid:6c189001-cd9e-e311-9426-00155d879c00][SessionDescr:ZABRYSVEPMD01\Dev
PWA][JobGuid:d3e31201-62f1-e311-944d-00155de84b1a][ProjectGuid:7537ccc0-7692-4456-93dd-fc7adcb5d1c8][PS_AC][807] Microsoft.Office.Project.Server.BusinessLayer.WinProjUtility.WinProjException: LookupTableItemInvalidLookupTable for lookup table value 440c1ce7-61f1-e311-944d-00155de84b1a
at Microsoft.Office.Project.Server.BusinessLayer.WinProjUtility.P12Deserializer.PostReadRow(P12ContainerHeader cntrHeader, Row row)     at Microsoft.Office.Project.Server.BusinessLayer.WinProj.SaveProjectInternal(Guid projGuid, String projName,
Int32 projType, Boolean isNewProj, Guid jobGuid, Guid sessionGuid, Guid checkOutByResUid, String sessionDescr, Boolean isFirstPacket, Boolean isLastPacket, String newVersionStamp, Int16 dataFormatVersion, Boolean isDataCompressed, Byte[] projectData, String
winprojBuildNumber, ACProcessorType acProcType), LogLevelManager Warning-ulsID:0x347A6270 has no entities explicitly specified.        72d0999c-429e-80e4-4f95-1037e3c788ff
And in addition to that, we get the Error 9000 when saving in MSP.
Still downloading the files, but the more and more I look at it I'm hopeful this will solve our problem.
http://blogs.umtsa.co.za/nicoo

Similar Messages

Can't open Project Server 2013 word documents with office 2010 installed

hello forum members,
we having issues opening a word document in a Project Server 2013 . we have Office 2010 on our computers installed.
when I click on a document link, i get a message "The webpage cannot be displayed". the only way to open a document is to right click on link and select "Open".
Does Project Server 2013 require Office 2013 installed? If not, is there a way to open documents in Project Server 2013 without right clicking on links?
tatiana
tatiana

Hi Tatiana,
This is the know issue. I have experienced this issue with one of our client. The cause of issue as below -
Scenario
You have 2007 Microsoft Office installed on a computer.
On the same computer, you also have a Microsoft Office 2013 application installed, such as Microsoft Lync 2013 or Microsoft Word 2013.
SOLUTION
To work around this issue, remove the Microsoft SharePoint Foundation Support program component from the Office 2013
installation on the affected computer or computers. To do this, follow the “Install or remove individual Office program components” section of the following Microsoft Office website:
Install or remove individual Office
programs and components
(http://office.microsoft.com/redir/HA010354261.aspx)
After you complete these steps, repair 2007 Office. For more information about how to repair the installation, click
the following article number to go to the article in the Microsoft Knowledge Base:
924611
(http://support.microsoft.com/kb/924611/ )
How to install the individual 2007 Office features or to repair the installed 2007 Office programs
Note When
you follow these steps, set the Microsoft SharePoint Foundation Support
component within Office Tools to Not Available.
This solution doesn't apply to scenarios in which SharePoint Designer 2013 is installed on the affected computer.
You can find further details here at Microsoft support site -
http://support.microsoft.com/kb/2888015
Hope this helps you.
Cheers, Badal

Office 2013 VL and app-v 5 SP2 on RDS server - package add fails with script error

We have used the MS Office Depolyment Tool for click-to-run to download the latest Office 365 version, and flatten it into an app-v 5 package - not a problem.
When we try to add the package to our client machine (Server 2008R2 running the app-v 5 SP2 client software), it fails with an message that a script has failed and not returned a 0 code. We have not added any scripting to this automatically created
package, so it seems that the app-v client does not like the "official" package. Any hints and tips gratefully accepted, thanks
App-v client has scripting enabled.
The powershell command line we are using is:
PS C:\windows\system32> Set-ExecutionPolicy Unrestricted
PS C:\windows\system32> Add-AppvClientPackage -path file://hostname/app-v/o365-noaccess/ProPlusVolume_en-us_zh-cn_x86.appv -DynamicDeploymentConfiguration \
\hostname\app-v\O365-NoAccess\ProPlusVolume_en-us_zh-cn_x86_DeploymentConfig.xml
with a result of:
Add-AppvClientPackage : Embedded Script process exited with an error code indicating failure (return code other than 0). Please ensure that Embedded
Script process can complete successfully and exits with 0.
Operation attempted: Configure AppV Package.
AppV Error Code: 100000000C.
Please consult AppV Client Event Log for more details.
At line:1 char:1
+ Add-AppvClientPackage -path
file://hostname/app-v/o365-noaccess/ProPlusVolum ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~
    + CategoryInfo          : InvalidResult: (:) [Add-AppvClientPackage], ClientException
    + FullyQualifiedErrorId : ConfigurePackageError,Microsoft.AppV.AppvClientPowerShell.AddAppvPackage
and these are the error messages we see in the debug app-v client logs:
Script Launcher successfully waited for script with command line: '"C:\ProgramData\App-V\D24C3BDD-8FAD-44D3-998C-933F8F053682\CD9725CE-4503-4932-863B-4FCDA3F9551D\Root\..\Scripts\Integrator.exe" /I /Msi /License /AppV PackageGUID=D24C3BDD-8FAD-44d3-998C-933F8F053682
PackageRoot="C:\ProgramData\App-V\D24C3BDD-8FAD-44D3-998C-933F8F053682\CD9725CE-4503-4932-863B-4FCDA3F9551D\Root" MsiName=SPPRedist.msi,SPPRedist64.msi PidKey=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx,xxxxx-xxxxx-xxxxx-xxxxx-xxxxx,xxxxx-xxxxx-xxxxx-xxxxx-xxxxx
PRIDName=ProPlusVolume'.
and...
Package {d24c3bdd-8fad-44d3-998c-933f8f053682} version {cd9725ce-4503-4932-863b-4fcda3f9551d} failed configuration in folder 'C:\ProgramData\App-V\D24C3BDD-8FAD-44D3-998C-933F8F053682\CD9725CE-4503-4932-863B-4FCDA3F9551D' with error 0x79100E10-0xC.
and...
machine script for event AddPackage with command line: '"C:\ProgramData\App-V\D24C3BDD-8FAD-44D3-998C-933F8F053682\CD9725CE-4503-4932-863B-4FCDA3F9551D\Root\..\Scripts\Integrator.exe"'
exited with failure error code: The extended attributes are inconsistent.. Because Rollback is set to true in the script definition, the current AppV Client operation was rolled back.
We believe this last error message is the kicker, but can't debug any further.

Just to validate the problem, I started again.
I have just downloaded the latest ODT from MS, and then downloaded the latest Office 2013 packaged - volume license. Then created the app-v package - all went perfectly, no error messages. Uploaded the package to the app-v 5 server and published
it. I have made NO changes to any of the files.
I have just built a brand new Windows Server 2008R2 Datacentre VM, patched it to the hilt, and installed the RDS role, powershell 3 and appv 5.0 SP2 client for RDS.
I then use powershell as above:
          scripting unrestricted
          app v client scripting enabled
         app v server added
          global and user update enabled
         add-appvclient package "url of office package.appv"
             and received exactly the same error message.
It is not complaining that scripting is not allowed, it is complaining that the script is invalid.
Help!!!!

Project Professional 2013 Installations Fails with Office 2010 installed on Windows 7 x86

When attempting to install Project Professional 2013 Pro (x86) on Windows Professional x86 PC that has Office 2010 ProSp2 installed client getting an error message at the end of the installation "Project 2013 has encountered an error during setup".
I have gotten the installer to work on x64 PC with Office 2010 installed. (Something worth noting that even thought I set the reboot to prompt its automatically reboots without warning but, appears to be working.) I also tried using the OTC, custom XML
file and just running setup.exe and get the error no matter what. When looking in the logs I there are MSI installer error with an error: Product:
Microsoft Project Professional 2013 - Update '{A6FFA77F-C1C1-43D3-A2C7-6A5B68138D9F}' could not be installed. Error code 1603. Windows Installer can create logs to help troubleshoot issues with installing software packages. Use the following link for
instructions on turning on logging support: http://go.microsoft.com/fwlink/?LinkId=23127
Without having to uninstall Office 2010 what do I need to modify in the installer to get it to Project 2013 Pro to install on the x86 machine?
Thanks

Hi,
Your environment will support 32 bit of Project professional 2013 (x86) as you have Windows and Office of (X86).
You try to modify registry then you wont face issue.
The issue when you hit a "1653" is that Windows
Installer "DisableRollback" is set. Office 2013 requires that "rollback" be enabled. If you are getting a "1653"
error in your logs as Ken did then the solution is to delete the "DisableRollback" (or set to '0') at the following registry keys:
HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows\Installer
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer
these are the issues I've seen:
Scheduler service was stopped. At a cmd window typing "net start schedule" resolves the problem.
CMD.exe was customized via the following registry key. Solution was to temporarily disable the customization by changing autorun value to autorun_old.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Command Processor
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Command Processor
Permission issues - seems some custom permissions affected Ingram's install which he explained in his previous post.
Environment variable "ComSpec" had been modified (semicolon added). Fix was to remove the added semicolon (there should be no semicolon).
The way to identify you are hitting this specific issue is if in the %temp%\OfficeSetup.log there is a mention of "Office64MUI.msi" failing to install with return value of 1603
If you want to enable verbose logging via the following key, rerun your failed install, and collect all the setup and MSI* logs that will give more information.
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer]
"logging"= "voicewarmup"
kirtesh

Office 2013 Installer - Fails with No Errors

Hello,
I ran into issues on two different Windows 8 (64-bit) machines today, both with Office 2013 Pro Plus (32-bit) installed. I could not get the installer to come up to add a module (or make any other changes).
On one of the PCs, I tried running the Fixit to remove Office, since the option of the "Online Repair" was not accessible, (installer would not start). Fixit removed Office, but after a reboot, it still would not run the office installer, even
with Office 2013 completely gone.
Things I tried:
- Disabled anti-virus (windows defender)
- Run with elevated privileges (I'm a domain admin and UAC is off, but just to be safe)
- Removed skydrive
- Cleaned out temp directory
- Scanned for registry errors (none)
- Re-downloaded the installer DVD
- Made sure no pending windows update
- Reboots (lots of times, definitely after the uninstall)
- Checked the install log in %temp%, this is what I get:
2013/08/12 13:51:14:263::[2848] PERF: TickCount=1295931 Name=OBootStrapper::Run Description=Begin function
2013/08/12 13:51:14:264::[2848] Operating System version: 6.2.9200 . Platform ID: 2
2013/08/12 13:51:14:264::[2848] Running 32-bit setup on a 64-bit operating system.
2013/08/12 13:51:14:264::[2848] Command line: "F:\SETUP.EXE"
2013/08/12 13:51:14:264::[2848] No command line arguments given
2013/08/12 13:51:14:513::[2848] Verify file signature in "F:\SETUP.EXE"
2013/08/12 13:51:14:562::[2848] F:\SETUP.EXE is trusted.
2013/08/12 13:51:14:562::[2848] Verify file signature in "F:\proplus.ww\OSETUP.DLL"
2013/08/12 13:51:14:598::[2848] F:\proplus.ww\OSETUP.DLL is trusted.
2013/08/12 13:51:14:612::[2848] Using setup controller dll at [F:\proplus.ww\OSETUP.DLL].
2013/08/12 13:51:14:612::[2848] PERF: TickCount=1296274 Name=OBootStrapper::Run Description=Calling RunSetup
This is almost identical to what I see on the other PC, except with different drive letters.
THERE ARE NO ERROR MESSAGES - no popup, no installer dialog - nothing, which makes it really hard to troubleshoot. And it's happening on both Windows 8 machines that have had Office 2013 installed. I am so frustrated right now after wasting half of today
troubleshooting this.
Any thoughts?

Hi
Let’s follow these steps:
Make sure you have end the tasks of setup.exe and integratedoffice.exe.
   1. Press the Ctrl + Alt+ Delete key -> Click on Task Manager to open.
   2. Under Processes tab -> Select setup.exe -> Click on End Process.
    3. Under Processes tab -> Select integratedoffice.exe -> Click on End Process.
  Restart the computer in Clean Boot and install Office 2013. Follow the steps:
       http://support.microsoft.com/kb/929135
   Note: After you have finished troubleshooting in clean boot, ensure you restart the computer in normal mode.
In addition, you can also refer to the following link to try more methods:
http://support.microsoft.com/kb/2822317/en-us
Regards

Approvals on Project Server 2013 - An unknown error has occurred

Migrated Project server 2010 to Project server 2013. All the quick launch pages were working after I completed the migration. Started the process of publishing projects and statusing/timesheets to update project.
Now I see "An Unknown Error has occurred".   Tried all my solutions for Project Server 2010 without success.
Event log looks clean.
Has anybody seen and resolved this issue?
Cheers!
Michael Wharton, MBA, PMP, MCT, MCSD, MCSE+I, MCDBA, MCC 2011, MCC2012
Website http://www.WhartonComputer.com
Blog http://MyProjectExpert.com contains my field notes and SQL queries

We are having the same error with an on-premise install of Project Server 2013. This is the error from the ULS logs.
04/24/2013 06:50:58.90   w3wp.exe (0x18C0)   0x1D0C   Project Server   Task Statusing and Updates   c3bn   High   PWA:https://projects.geocent.com/commsec,
ServiceApp:Project Server Application Service, User:i:0#.w|geocent\john, PSI: System.NullReferenceException: Object reference not set to an instance of an object.     at Microsoft.Office.Project.Server.BusinessLayer.Statusing.StatusApprovalsQueryInfo.AddAllTimesheets(DataTable&
dt, Dictionary`2& timephased, List`1& actualDates)     at Microsoft.Office.Project.Server.BusinessLayer.Statusing.StatusApprovalsQueryInfo.TryLoad(LoadApprovalType method, DataTable& dt, Dictionary`2& timephased, List`1&
actualDates), LogLevelManager Warning-ulsID:0x6333626E has no entities explicitly specified.   c9e7149c-070d-5035-0dca-bda3580b7d07
Not very helpful. Any ideas?

SQL Server Agent job fails with error : The package execution returned DTSER_FAILURE (1).

Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 10:00:01 AM Error: 2014-08-15 10:00:07.20
Code: 0xC0047062 Source: Data Flow Task LEAN [6761]
Description: Teradata.Client.Provider.TdException: [Teradata Database] [3006] Logons are disabled.
at Teradata.Client.Provider.WpMessageManager.CheckForError()
at Teradata.Client.Provider.WpMessageManager.ProcessResponse()
at Teradata.Client.Provider.WpLogonManager.Action()
at Teradata.Client.Provider.WpSession.ManagerAction(WpMessageManager manager, UtlStopwatchWrapper watch, Int32 connectionTimeout)
at Teradata.Client.Provider.WpSession.Open(Int32 connectionTimeout, String password)
at Teradata.Client.Provider.WpSession.Open(Int32 connectionTimeout)
at Teradata.Client.Provider.Connection.Open(UtlConnectionString connectionString, UInt32 timeout)
at Teradata.Client.Provider.ConnectionPool.CreateConnection(UInt32 timeout)
at Teradata.Client.Provider.ConnectionPool.GetConnectionFromPool(Object owningObject)
at Teradata.Client.Provider.ConnectionFactory.GetConnection(Object owningObject, UtlConnectionString connStr)
at Teradata.Client.Provider.TdConnection.Open()
at Microsoft.SqlServer.Dts.Runtime.ManagedHelper.GetManagedConnection(String assemblyQualifiedName, String connStr, Object transaction)
at Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSConnectionManager100.AcquireConnection(Object pTransaction)
at Microsoft.SqlServer.Dts.Pipeline.DataReaderSourceAdapter.AcquireConnections(Object transaction)
at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostAcquireConnections(IDTSManagedComponentWrapper100 wrapper, Object transaction)
End Error Error: 2014-08-15 10:00:07.35 Code: 0xC0047017 Source: Data Flow Task SSIS.Pipeline
Description: component "LEAN" (6761) failed validation and returned error code 0x80004005. End Error Error: 2014-08-15 10:00:07.48
Code: 0xC004700C Source: Data Flow Task SSIS.Pipeline Description: One or more component failed validation.
End Error Error: 2014-08-15 10:00:07.60 Code: 0xC0024107 Source: Data Flow Task
Description: There were errors during task validation. End Error
DTExec: The package execution returned DTSER_FAILURE (1). Started: 10:00:01 AM Finished: 10:00:07 AM
Elapsed: 6.692 seconds. The package execution failed. The step failed.
SQL Server agent job fails with above error, Please let me know process tohandle it.
Thanks,
Vishal.

The error message suggests its the issue with Teradata source database to which SSIS tries to connect within the data flow task. Make sure Teradata database is available and LOGON is enabled.
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

Project Server 2013 - Project Plan crashes frequently

Team,
We are using EPM , and everytime we update the project plan using enterprise project, the plan crashes and it does not allow me to publish the plan on the Project server.
Please suggest solution for the above
We are using Project Server 2013
Regards
Vidhya

Vidhya --
First of all, is your Project Server 2013 system updated with the latest Cumulative Updates and/or with Service Pack 1 (just released yesterday)? If not, I would strongly suggest that you update your system and your copies of Microsoft Project 2013
with Service Pack 1 at the earliest date possible.
Second, regarding this project in particular, I would strongly suspect that this project is corrupted. To resolve the corruption, you will need to use the Save for Sharing feature in Microsoft Project 2013. To do this, right-click anywhere on
a ribbon tab in Microsoft Project 2013, such as the Tasks tab, and then select the Customize Quick Access Toolbar item on the shortcut menu. In upper left corner of the Project Options dialog, click the Choose Commands From pick list and select
the All Commands item. In the list of commands on the left side, select the Save For Sharing item and click the Add button to add it to the list on the right. Click the OK button when finished.
To use the Save for Sharing feature, do the following:
Open the enterprise project in question.
Click the Save for Sharing button in the Quick Access Toolbar.
In the Save dialog, save the MPP file to a location where you can find it easily, such as your computer Desktop, for example.
Close the MPP file.
Reopen the MPP file.
Click File > Save As and then save the project.
When the Save operation is done, try publishing the project.
Please let us know if this helps.
Dale A. Howard [MVP]

"View failed to load" error when I open Resources - Project Server 2013

Hello,
I get the following error when I open the Resources Page (I am using Project Server 2013):
"The view failed to load. Press OK to reload this view with the default settings. Press Cancel to select another view"
Help please.

Hi,
Is your environment up to date with the latest SP/CU?
HAve you tried selecting another view?
See those hotfix :
http://support.microsoft.com/kb/2760261/en-us
http://support.microsoft.com/kb/2863881/en-us
Hope this helps,
Guillaume Rouyre, MBA, MCP, MCTS |

Timesheet Error with custom Line Classifications in Project Server 2013

We implemented Project Server 2013 last year and began using timesheets. We are a billable consulting group. In order manage our billing, we have created three custom line classifications, "Billable Onsite", "Billable Offsite",
and "Non-billable". We do not use "Standard" as a line where time is entered. We are using SEM. We have chosen no prepopulation on timesheets. Our system is updated through the March 2013 update.
The error we get is presented as "__error Loading" with the title bar of the pop-up reading "Message from webpage". This occurs when you attempt to add a new line to a timesheet and choose one of the custom line classifications.
A confusing aspect to this, while we have prepopulation turned off, the timesheet is populated with "Standard" lines for the tasks that are currently assigned to the user. We have come up with a workaround that works sometimes but not all the
time. When the user receives this error, they move away from the timesheet screen and then return. They add all of the applicable lines to the timesheet with "Standard" even if they already exist on the timesheet and save. Then
they add the lines with the appropriate line classification and the time. If they receive the "__error loading" error again, then the timesheet can not be corrected. You must delete the timesheet and recreate. We have been able
to recreate the problem in a vanilla install with a custom line classification added.
Just yesterday, I was able to find a error log entry that may help some of you identify the source:
General Unhandled Exception in _TimeSheet.GetTimesheetForGridJsonFromViewUid_ Attributes: System.ArgumentException: Assignment line already exists for assignment uid: d9afeb60-d589-e311-bd64-08edb9dd8afb     at Microsoft.Office.Project.Server.BusinessLayer.Timesheet.VerifyLineIsUnique(Guid
assignmentUid, Guid taskUid, Guid projectUid, Guid lineClassUid)
at Microsoft.Office.Project.Server.BusinessLayer.Timesheet.CreateAssignmentLine(Guid assignmentUid, Guid taskUid, Guid projectUid, Guid lineClassUid, String taskName, String projectName)     at Microsoft.Office.Project.Server.BusinessLayer.TimesheetSEM.CreateAssignmentLine(Guid
assignmentUid, Guid taskUid, Guid projectUid, Guid lineClassUid, String taskName, String projectName)     at Microsoft.Office.Project.Server.BusinessLayer.Timesheet.AddTimesheetLine(Guid assignmentUid, Guid taskUid, Guid projectUid, Guid
classUid, ValidationType validationType, Guid lineUid, String taskName, String projectName, String comment)     at Microsoft.Office.Project.Server.BusinessLayer.Timesheet.ImportTimesheetLine(NewTask importedLine)
at Microsoft.Office.Project.Server.BusinessLayer.Timesheet.<>c__DisplayClass4c.<AddNewLines>b__49(NewTask line)     at Microsoft.Office.Project.Server.Library.PSUtility.Apply[T](IEnumerable`1 enumerable, Action`1 fn)
at Microsoft.Office.Project.Server.BusinessLayer.Timesheet.AddNewLines(IEnumerable`1 newLines)     at Microsoft.Office.Project.Server.BusinessLayer.TimesheetSEM.AddNewLines(IEnumerable`1 newLines)     at Microsoft.Office.Project.Server.BusinessLayer.TimesheetLoaderForGrid.Load()
at Microsoft.Office.Project.Server.BusinessLayer.TimeSheet.GetTimesheetForGridJsonFromViewUid(JsGridSerializerArguments gridSerializerArgs, Guid tsUid, Guid viewUid, String changesJson, String viewOptionsJson)     at Microsoft.Office.Project.Server.Wcf.Implementation.PWAImpl.<>c__DisplayClass2f5.<TimeSheetGetTimesheetForGridJsonFromViewUid>b__2f4()
at Microsoft.Office.Project.Server.Wcf.Implementation.WcfMethodInvocation.InvokeBusinessObjectMethod(String businessObjectName, String methodName, IEnumerable`1 actions) . Standard Information: PSI Entry Point: Project User: i:0#.w|mayberry\nunderwood
Correlation Id: 91c4ca27-6492-e311-93ff-00155d149902 PWA Site URL: XXX SA Name: Project Services Application PSError: GeneralUnhandledException (42), LogLevelManager Warning-ulsID:0x00101622 has no entities explicitly specified.
We have not been able to find any similar timesheet issues here or on other boards. Our users, as you can imagine, are getting increasingly frustrated. A ny advice?
Thanks,
Nate

More scenario testing today. Tested with both "No Prepopulation" and populate assigned task options! no difference in our instance. We are only updated through March 2013, waiting for IT support. We have previously tried the deactivation/reactivation
of custom classifications. Tried with and without template, no difference. So the new scenario and findings:
1. Create a project with 2 tasks, one assigned and one not. Save and publish.
2. Create a timesheet, do not use an existing timesheet. Here we found, in spite of population option chosen, the timesheet was populated with a Standard line for the assigned task. With no action taken other than creating timesheet, the reporting assignment
table showed the new entry.
3. Add an assignment to the other task in the project, publish.
4. Open the same timesheet period. Now I saw the other task appear on the screen. It did not show in the database. I could not save to make it appear in the database unless I did something else to the screen to make it "dirty". Once I did that,
I could save and the second Standard line appeared In the database.
If I tried to add a custom line class line to the TS when the Standard line was not in the database, I get the error. It doesn't matter if it shows on the screen.
If it shows on the screen but not in the db, and I attempt to add a non-standard line, it will error, unless I manually add the standard line first. The user would not know to do this.
You will not be able to reproduce if you make the assignments and then create the TS. You need to try in reverse order.
It appears as though there are issues with both the timesheet population options and the code that runs when the TS loads after it's initial creation. I'm wondering why on creation the standard line is created and committed to the db, but on reload with
new tasks it doesn't' do the same. Also when No Prepopulation is turned on, why my time sheets are always prepopulated.
Sorry for any typos, working from my ipad keyboard. Thanks for your help!

Error while creating a Timesheet - Project Server 2013

Hi everyone,
One of user of PWA encounters an issue when he tries to create a timesheet. This error only occurs with a timesheet of
a specific period, he can create all the other timesheet.
So, when he creates the timesheet, this error occurs : "The timesheet creation failed, because of problems with Project Web App or with data validations"
After reloaded the list of the timesheets, a link to go to the specific timesheet
is available but if we click on it, we have this error :
"View Failue - The view failed to load"
I think , this error occurs
because the timesheet is not realy existing even if we have a link to it.
In the log (full log at the end), I've got this error :
Exception occured in method 'TimeSheet.CreateTimesheet' System.ArgumentException: These columns don't currently have unique values.
I've found this link with the same kind of problem :
http://social.technet.microsoft.com/Forums/projectserver/en-US/b0a92afc-11fc-40ef-9a44-357d953b31f6/unable-to-open-or-create-timesheets-these-columns-dont-currently-have-unique-values?forum=projectserver2010general but I've checked and published all the
user project but still have the error.
Have you got any idea where are these columns ? How can I found them without checked every project of PWA ?
Thanks,
Patmol
Full logs, for information :
[bucketHash:E3B9DED0] Exception occured in method 'TimeSheet.CreateTimesheet' System.ArgumentException: These columns don't currently have unique values. at System.Data.ConstraintCollection.AddUniqueConstraint(UniqueConstraint constraint) at System.Data.ConstraintCollection.Add(Constraint constraint, Boolean addUniqueWhenAddingForeign) at System.Data.DataTable.set_PrimaryKey(DataColumn[] value) at Microsoft.Office.Project.Server.DataAccessLayer.Generated.TimesheetDalBase.ReadCustomFieldsForAssignments(ISet`1 assignmentUids) at Microsoft.Office.Project.Server.BusinessLayer.Timesheet.ImportCustomFields(HashSet`1 assignmentUids) at Microsoft.Office.Project.Server.BusinessLayer.Timesheet.ImportActualsAndCustomFields(IEnumerable`1 assignmentUids, ISet`1 userImported) at Microsoft.Office.Project.Server.BusinessLayer.TimesheetLoaderForGrid.Load() at Microsoft.Office.Project.Server.BusinessLayer.TimeSheet.CreateTimesheet(TimesheetDataSet dsDelta, PreloadType preloadType) at Microsoft.Office.Project.Server.Wcf.Implementation.TimeSheetImpl.<>c__DisplayClass45.<CreateTimesheet>b__44() at Microsoft.Office.Project.Server.Wcf.Implementation.WcfMethodInvocation.InvokeBusinessObjectMethod(String businessObjectName, String methodName, IEnumerable`1 actions) StackTrace: at Microsoft.Office.Project.Server.Native.dll: (sig=6ea170d1-988e-4153-9f1d-0305c0ea0309|2|microsoft.office.project.server.native.pdb, offset=3C1E) at Microsoft.Office.Project.Server.Native.dll: (offset=1255D)
Watson bucket parameters: Microsoft Project Server 2013, ULSException14, 070f6ea0 "project server", 0f0011db "15.0.4571.0", ea364808 "system.data", 0400766f "4.0.30319.0", 52310bef "thu sep 12 02:33:51 2013", 00000e02 "00000e02", 00000020 "00000020", 44395864 "argumentexception", 00101621 "aeby7"
Error is: GeneralUnhandledException. Details: General Unhandled Exception in _TimeSheet.CreateTimesheet_ Attributes: System.ArgumentException: These columns don't currently have unique values. at System.Data.ConstraintCollection.AddUniqueConstraint(UniqueConstraint constraint) at System.Data.ConstraintCollection.Add(Constraint constraint, Boolean addUniqueWhenAddingForeign) at System.Data.DataTable.set_PrimaryKey(DataColumn[] value) at Microsoft.Office.Project.Server.DataAccessLayer.Generated.TimesheetDalBase.ReadCustomFieldsForAssignments(ISet`1 assignmentUids) at Microsoft.Office.Project.Server.BusinessLayer.Timesheet.ImportCustomFields(HashSet`1 assignmentUids) at Microsoft.Office.Project.Server.BusinessLayer.Timesheet.ImportActualsAndCustomFields(IEnumerable`1 assignmentUids, ISet`1 userImported) at Microsoft.Office.Project.Server.BusinessLayer.TimesheetLoaderForGrid.Load() at Microsoft.Office.Project.Server.BusinessLayer.TimeSheet.CreateTimesheet(TimesheetDataSet dsDelta, PreloadType preloadType) at Microsoft.Office.Project.Server.Wcf.Implementation.TimeSheetImpl.<>c__DisplayClass45.<CreateTimesheet>b__44() at Microsoft.Office.Project.Server.Wcf.Implementation.WcfMethodInvocation.InvokeBusinessObjectMethod(String businessObjectName, String methodName, IEnumerable`1 actions) . Standard Information: PSI Entry Point: Project User: i:0#.w|wavenet\cev Correlation Id: 9709e41b-9a18-e411-941e-00155d029b05 PWA Site URL: http://intranet.wavenet.lan/PWA SA Name: Project Server Application PSError: GeneralUnhandledException (42), LogLeve...

Hi Patmol,
Have you tried to go to the previous or next timesheet and then navigate with the "previous period" or "next period" to the timesheet in question.
Also have you tried to open it using a delegation session?
Hope this helps,
Guillaume Rouyre, MBA, MCP, MCTS |

Project Server 2013 - External Data Refresh Failed

Hi,
I have built new Project Server 2013 in a 3 tier farm, with OWA, configured PWA site everything working fine except, Reports in BI Center, where i am getting - External Data Refresh Failed error
http://Sp2013/PWA/ProjectBICenter/Sample%20Reports/Forms/AllItems.aspx
i have stopped using Excel Web also to use Excel Services, get below error
External Data Refresh Failed
An error occurred while accessing application id ProjectServerApplication from Secure Store Service. The following connections failed to refresh:
Project Server - Issue Data
Project Server - Risk Data
Learn
more about data refresh
Steps Tried:
1.deleted Excel Services - recreated
2.Deleted Secure store - recreated
Built test box without OWA still have the same issue
Any suggestions/ Solutions greatly appreciated.
Thanks
Aleem
Alim

Hi,
If you are still facing the same issue follow the below steps:
1) Access PWA from your server
2) Download any built in report from Reports section (in your case
Project Server - Issue Data Project
Server - Risk Data) to your server.
3) Open report in excel, go to Data->Connections in Workbook Connection dialog open "Project Server - Issue Data" go to properties.
4) Here select tab 'Definition' under connection file remove tick for 'Always use connection file'
5) Tweak your connection string & tick save password option
6) Excel Services: Authentication Settings (suit yourself)
Now, save & publish on PWA, hope it works :)

Project Server 2013 SSRS with Project Site

Hi All,
We are using Project Server 2013. We have developed a SSRS report by accessing Project Site lists. It was working fine for some time, now when we try to access the report it is showing loading. The data source itself is not working, we used http://<servername>/PWA
as URL for the data source . The reports developed without Project Site list are working fine.
After 5 to 10 minutes it is showing the below error.
An error has occurred during report processing. (rsProcessingAborted)
Query execution failed for dataset 'dtRisk'. (rsErrorExecutingCommand)
An error occurred when accessing the specified SharePoint list. The connection string might not be valid. Verify that the connection string is correct. (rsSPDataProviderError)
For more information about this error navigate to the report server on the local server machine, or enable remote errors
When we try to test the datasource connecting string, after 5 minutes showing the below error.
An error occurred when accessing the specified SharePoint list. The connection string might not be valid. Verify that the connection string is correct. (rsSPDataProviderError) Get Online Help For more information about this error navigate to the report server
on the local server machine, or enable remote errors
Below connection setings
Thanks in advance , Taj

Hi Taj,
Your list is in PWA? is a global list?, if not, try to make a connection with http://server/PWA/SiteProject may this can resolve, because when you do some DS with a SPList, your need to stablish that connection directly at site path where you have the list.
I hope this help
Ray

Project Server 2013 OLAP cube build error

When I try to build the OLAP cube I receive the below error:
[2/26/2014 12:36 PM] Failed to build the OLAP cubes. Error: The attempt to build the OLAP database on server SQL_Server_Name failed, the SQL Server Analysis Services Analysis Management Objects (AMO) client software may not be installed on this server, please
install/update the client on this server and retry. The underlying exception was: Could not load file or assembly 'Microsoft.AnalysisServices, Version=10.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot
find the file specified.
I did some search and found that Analysis Management Objects (AMO) client software is not installed on my servers, I downloaded and installed the AMO client software , restarted the Project Server Service application to the 4 Servers. I rebooted the
4 servers, tried to build the cube, but I got the same error. I checked the assembly on the 4 servers and they contain the dll Microsoft.AnalysisServices.
Any help?
I read that AMO client software tools must be installed during the farm setup, after installing the SharePoint Prerequisites and before installing SharePoint. Is that correct?

Hello,
Even with SQL 2012, the 2008 SQL AMO component is required on the Project Server servers. See the post from Brian for more details:
http://blogs.msdn.com/b/brismith/archive/2012/11/12/project-server-2013-requirements-to-build-an-olap-cube.aspx
Paul
Paul Mather | Twitter |
http://pwmather.wordpress.com | CPS

Project Server 2013 Configuration Wizard Error

Hi Everyone,
I have installed SharePoint 2013 over Single Server with built in DB. Server
uses Windows Server 2008 & SQL Server 2008. SharePoint installed correctly and it is running well.
Now,
I need to install Project Server 2013, so I installed its required updated, its prerequisites, then installed it. After installation, Configuration wizard started, but it failed with following error info:-
What
is the reason of that error and how to solve this problem?
Thanks
Wa'el Mohsen

That sounds easy enough. Just two questions though:
1) what is 25774? KB? an update?
2) how do I delete it from IIS?
Thank you,

Project Server 2013: QueueUpdateProject2 fails with LookupTableItemInvalidLookupTable error

Similar Messages

Maybe you are looking for