从Project Server 2010迁移到Project Server 2013后出现许多错误 [英] Many error after Migration from Project Server 2010 to Project Server 2013
问题描述
Hello Guys，在Project server 2010之后 - > 2013年迁移，我在Projeft服务器队列中发现很多错误。
环境：
发件人：
SharePoint 2010农场
- 1个WFE，Aplication Server，SQL Server，Team Foundation Server
to：
SharePoint 2013 Farm（无团队基础）
- 1 WFE，APP服务器
- 1 SQL Server
我发现的错误是：
1。当我要发布项目以修复风险和问题列表时（因为此TechNet发布了
http://technet.microsoft.com/EN-US/library/ff686780.aspx ），Project Professional收到以下错误： "发布失败，错误
23000"。在Project Server队列中，我找到了以下信息：
一般
•Microsoft.Office.Project.Server.BusinessLayer.Queue.Message：
$ b $b◦ProjectPublishFailure（23000）。详细信息：id ='23000'name ='ProjectPublishFailure'uid ='6f6a637d-8720-e311-93fe-00505683566a'projectuid ='2c8c09b8-b5d1-4fbe-8286-47b0f271ce58'messorytype ='Microsoft.Office.Project.Server.BusinessLayer .QueueMsg.FixupLinksFieldMessage'
messageID ='40'stage =''blocking ='DontBlock'。
•队列：
$ b $b◦GeneralQueueJobFailed（26000） - ProjectPublish.FixupLinksFieldMessage。详情：id ='26000'name ='GeneralQueueJobFailed'uid ='706a637d-8720-e311-93fe-00505683566a'JobUID ='9e430f53-8620-e311-be76-e02a8248ba06'ComputerName ='5cb42698-f709-4727-9b66-336647d7eb73 '
GroupType ='ProjectPublish'MessageType ='FixupLinksFieldMessage'MessageId ='40'Stage =''CorrelationUID ='1544449c-ace7-c072-7eb7-3e0a9c5b8c67'。有关更多详细信息，请查看机器5cb42698-f709-4727-9b66-336647d7eb73上的ULS日志，以获取具有JobUID 9e430f53-8620-e311-be76-e02a8248ba06的条目。
在ULS查看器中，我发现以下条目的相关ID为"1544449c-ace7-" c072-7eb7-3e0a9c5b8c67'
E1。 创建字段失败：字段类型PwaLinkCustomField未正确安装。转到列表设置页面以删除此字段。
E2。 错误是：ProjectPublishFailure。详细信息：Microsoft.Office.Project.Server.BusinessLayer.Queue.Message属性： 2c8c09b8-b5d1-4fbe-8286-47b0f271ce58  Microsoft.Office.Project.Server.BusinessLayer.QueueMsg.FixupLinksFieldMessage 
40 DontBlock  。标准信息：PSI入口点： 项目用户：i：0＃.w | ddcinternal\spproject相关ID：5af22152-8620-e311-93fe-00505683566a PWA网站网址：
http：// hivedev：8030 / SWAT SA名称：Project Server服务应用程序PSError：ProjectPublishFailure（23000），LogLevelManager Warning-ulsID：0x37677870没有明确指定实体。
E3 。 "标准信息：PSI入口点：< unknown> 项目用户：< unknown> 相关ID：< unknown> PWA网站网址： SA名称：< unknown> PSError：< unknown>队列作业有
失败。这是每次作业失败时Project Server队列记录的一般错误 - 有效的故障排除使用此错误消息和其他更具体的错误消息（如果有），操作指南（记录有关排队的
作业的更多详细信息）和跟踪日志（可以提供更详细的上下文）。有关失败作业的更多信息如下。失败作业的GUID：9e430f53-8620-e311-be76-e02a8248ba06。处理此作业的计算机的名称：5cb42698-f709-4727-9b66-336647d7eb73
（要进一步调试，您需要查看此计算机的跟踪日志）。作业类型失败：ProjectPublish。失败的子作业类型：FixupLinksFieldMessage。子作业ID失败：40。子作业失败的阶段： （当一个子作业的逻辑处理阶段超过
时，这非常有用）。"
E4。 错误是：GeneralQueueJobFailed。详细信息：队列属性： 9e430f53-8620-E311-be76-e02a8248ba06&NBSP; 5cb42698-f709-4727-9b66-336647d7eb73&NBSP; ProjectPublish&NBSP; FixupLinksFieldMessage&NBSP; 40&NBSP;&NBSP;&NBSP; 1544449c-ace7-c072-7eb7-3e0a9c5b8c67&NBSP;
。标准信息：，LogLevelManager警告-ulsID：0x000DD158没有明确指定实体。
E5。 PWA :, ServiceApp：未知，用户：未知，PSI：UnknownUnknown [QUEUE] noop BeginMessageGroup 64afb96d-8620-e311-93fe-00505683566a type = PreparePSProjectPermissionSynchronization priority = StandardPriority，LogLevelManager Warning-ulsID：0x6230726B
没有明确指定实体。 />
E6。 PWA：，ServiceApp：未知，用户：未知，PSI：UnknownUnknown [QUEUE] noop BeginMessageGroup fcedfb8a- 8720-e311-93fe-00505683566a type = PSPermissionSynchronizePWASite priority = StandardPriority，LogLevelManager Warning-ulsID：0x6230726B
没有明确指定实体。
E7。 < nativehr> 0x81020054< / nativehr>< nativestack>< / nativestack>用户"i：0＃.w | ddcinternal\baserver"不存在，无法添加。在"i：0＃.w | ddcinternal\baserver"之后指定的所有用户
也没有添加。报告的错误与代码= 0x81070000和消息之间可能不匹配："用户"i：0＃.w | ddcinternal\baserver"不存在，无法添加。在"i：0＃.w | ddcinternal\baserver"之后指定的所有用户还没有添加
。"代码为0x81020054的返回错误。
E8。 < nativehr> 0x81020054< / nativehr>< nativestack> < / nativestack>用户"i：0＃.w | adario@desertdevco.com"不存在，无法添加。在"i：0＃.w | adario@desertdevco.com""之后指定的所有用户
也没有添加。报告的错误与代码= 0x81070000和消息之间可能不匹配："用户"i：0＃.w | adario@desertdevco.com"不存在，无法添加。在"i：0＃.w | adario@desertdevco.com""之后指定的所有用户还没有添加
。"以及代码为0x81020054的返回错误。
2 。当我尝试将Active Directory用户组与Project Server同步时，出现以下错误：
常规
•队列：
$ b $b◦GeneralQueueJobFailed（26000） - AdSyncERP.AdSyncERPMessage。详细信息：id ='26000'name ='GeneralQueueJobFailed'uid = '84bc9ff7-8520-e311-93fe-00505683566a'JobUID ='570ecef4-8520-e311-93fe-00505683566a'ComputerName ='5cb42698-f709-4727-9b66-336647d7eb73 'GroupType ='AdSyncERP'
MessageType ='AdSyncERPMessage'MessageId ='1'Stage =''CorrelationUID ='ee43449c-9c91-c072-7eb7-306325643883'。有关更多详细信息，请查看机器5cb42698-f709-4727-9b66-336647d7eb73上的ULS日志，以获取具有JobUID 570ecef4-8520-e311-93fe-00505683566a的条目。
在ULS查看器中，我找到了关联ID为"ee43449c-9c91-c072-7eb7-306325643883"的以下条目：
E1。标准信息：PSI入口点：< unknown> 项目用户：< unknown> 相关ID：< unknown> PWA网站网址： SA名称：< unknown> PSError：< unknown>队列作业失败。
这是每次作业失败时Project Server队列记录的一般错误 - 有效的故障排除使用此错误消息以及其他更具体的错误消息（如果有），操作指南（记录有关排队作业的更多详细信息）
和跟踪日志（可以提供更详细的上下文）。有关失败作业的更多信息如下。失败作业的GUID：570ecef4-8520-e311-93fe-00505683566a。处理此作业的计算机的名称：5cb42698-f709-4727-9b66-336647d7eb73（对于
进一步调试，您需要查看此计算机的跟踪日志）。失败的工作类型：AdSyncERP。失败的子作业类型：AdSyncERPMessage。子作业ID失败：1。子作业失败的阶段： （当一个子作业有多个逻辑处理
阶段时，这很有用。）
错误是：GeneralQueueJobFailed。详细信息：队列属性： 570ecef4-8520-e311-93fe-00505683566a&NBSP; 5cb42698-f709-4727-9b66-336647d7eb73&NBSP; AdSyncERP&NBSP; AdSyncERPMessage&NBSP; 1&NBSP;&NBSP;&NBSP; ee43449c-9c91-c072-7eb7-306325643883&NBSP; 。标准
信息：，LogLevelManager警告-ulsID：0x000DD158没有明确指定实体。
如果有人知道这个错误正在发生，我将
非常感激。
PD： 我可以在发生错误时发送日志文件。只是让我知道电子邮件。
问候，
Andres Rojas
波哥大 - 哥伦比亚
Ing。 Andres Rojas | MVP SharePoint Server | MCITP，MCPD，MCTS | http://arojaspa.blogspot.com | twitter：arojaspa
Hello Guys, after a Project server 2010 -> 2013 migration, I'm found many error in the Projeft Server Queue.
Environments:
From:
SharePoint 2010 Farm
- 1 WFE, Aplication Server, SQL Server, Team Foundation Server
to:
SharePoint 2013 Farm (no team foundation)
- 1 WFE, APP server
- 1 SQL Server
The errors that I found are:
1. When I going to publish a Project to fix the Risk and Issue List (as this TechNet post
http://technet.microsoft.com/EN-US/library/ff686780.aspx), Project Professional get the following error: "publish failed with error
23000". In the Project Server Queue I found the following information:
General
•Microsoft.Office.Project.Server.BusinessLayer.Queue.Message:
◦ProjectPublishFailure (23000). Details: id='23000' name='ProjectPublishFailure' uid='6f6a637d-8720-e311-93fe-00505683566a' projectuid='2c8c09b8-b5d1-4fbe-8286-47b0f271ce58' messagetype='Microsoft.Office.Project.Server.BusinessLayer.QueueMsg.FixupLinksFieldMessage'
messageID='40' stage='' blocking='DontBlock'.
•Queue:
◦GeneralQueueJobFailed (26000) - ProjectPublish.FixupLinksFieldMessage. Details: id='26000' name='GeneralQueueJobFailed' uid='706a637d-8720-e311-93fe-00505683566a' JobUID='9e430f53-8620-e311-be76-e02a8248ba06' ComputerName='5cb42698-f709-4727-9b66-336647d7eb73'
GroupType='ProjectPublish' MessageType='FixupLinksFieldMessage' MessageId='40' Stage='' CorrelationUID='1544449c-ace7-c072-7eb7-3e0a9c5b8c67'. For more details, check the ULS logs on machine 5cb42698-f709-4727-9b66-336647d7eb73 for entries with JobUID 9e430f53-8620-e311-be76-e02a8248ba06.
In the ULS viewer I found the following entries with the correlation ID '1544449c-ace7-c072-7eb7-3e0a9c5b8c67'
E1. Failed to create field: Field type PwaLinkCustomField is not installed properly. Go to the list settings page to delete this field.
E2. Error is: ProjectPublishFailure. Details: Microsoft.Office.Project.Server.BusinessLayer.Queue.Message Attributes: 2c8c09b8-b5d1-4fbe-8286-47b0f271ce58 Microsoft.Office.Project.Server.BusinessLayer.QueueMsg.FixupLinksFieldMessage
40 DontBlock . Standard Information: PSI Entry Point: Project User: i:0#.w|ddcinternal\spproject Correlation Id: 5af22152-8620-e311-93fe-00505683566a PWA Site URL:
http://hivedev:8030/SWAT SA Name: Project Server Service Application PSError: ProjectPublishFailure (23000), LogLevelManager Warning-ulsID:0x37677870 has no entities explicitly specified.
E3. "Standard Information:PSI Entry Point: <unknown> Project User: <unknown> Correlation Id: <unknown> PWA Site URL: SA Name: <unknown> PSError: <unknown> A queue job has
failed. This is a general error logged by the Project Server Queue everytime a job fails - for effective troubleshooting use this error message with other more specific error messages (if any), the Operations guide (which documents more details about queued
jobs) and the trace log (which could provide more detailed context). More information about the failed job follows. GUID of the failed job: 9e430f53-8620-e311-be76-e02a8248ba06. Name of the computer that processed this job: 5cb42698-f709-4727-9b66-336647d7eb73
(to debug further, you need to look at the trace log from this computer). Failed job type: ProjectPublish. Failed sub-job type: FixupLinksFieldMessage. Failed sub-job ID: 40. Stage where sub-job failed: (this is useful when one sub-job has more than
one logical processing stages)."
E4. Error is: GeneralQueueJobFailed. Details: Queue Attributes: 9e430f53-8620-e311-be76-e02a8248ba06 5cb42698-f709-4727-9b66-336647d7eb73 ProjectPublish FixupLinksFieldMessage 40 1544449c-ace7-c072-7eb7-3e0a9c5b8c67
. Standard Information: , LogLevelManager Warning-ulsID:0x000DD158 has no entities explicitly specified.
E5. PWA:, ServiceApp:Unknown, User:Unknown, PSI: UnknownUnknown[QUEUE] noop BeginMessageGroup 64afb96d-8620-e311-93fe-00505683566a type = PreparePSProjectPermissionSynchronization priority = StandardPriority, LogLevelManager Warning-ulsID:0x6230726B
has no entities explicitly specified.
E6. PWA:, ServiceApp:Unknown, User:Unknown, PSI: UnknownUnknown[QUEUE] noop BeginMessageGroup fcedfb8a-8720-e311-93fe-00505683566a type = PSPermissionSynchronizePWASite priority = StandardPriority, LogLevelManager Warning-ulsID:0x6230726B
has no entities explicitly specified.
E7. <nativehr>0x81020054</nativehr><nativestack></nativestack>The user "i:0#.w|ddcinternal\baserver" does not exist and could not be added. All users specified after "i:0#.w|ddcinternal\baserver"
were also not added. Possible mismatch between the reported error with code = 0x81070000 and message: "The user "i:0#.w|ddcinternal\baserver" does not exist and could not be added. All users specified after "i:0#.w|ddcinternal\baserver"
were also not added." and the returned error with code 0x81020054.
E8. <nativehr>0x81020054</nativehr><nativestack></nativestack>The user "i:0#.w|adario@desertdevco.com" does not exist and could not be added. All users specified after "i:0#.w|adario@desertdevco.com"
were also not added. Possible mismatch between the reported error with code = 0x81070000 and message: "The user "i:0#.w|adario@desertdevco.com" does not exist and could not be added. All users specified after "i:0#.w|adario@desertdevco.com"
were also not added." and the returned error with code 0x81020054.
2. When I try to synchronize the Active Directory User Group with Project Server, I get the following error:
General
•Queue:
◦GeneralQueueJobFailed (26000) - AdSyncERP.AdSyncERPMessage. Details: id='26000' name='GeneralQueueJobFailed' uid='84bc9ff7-8520-e311-93fe-00505683566a' JobUID='570ecef4-8520-e311-93fe-00505683566a' ComputerName='5cb42698-f709-4727-9b66-336647d7eb73' GroupType='AdSyncERP'
MessageType='AdSyncERPMessage' MessageId='1' Stage='' CorrelationUID='ee43449c-9c91-c072-7eb7-306325643883'. For more details, check the ULS logs on machine 5cb42698-f709-4727-9b66-336647d7eb73 for entries with JobUID 570ecef4-8520-e311-93fe-00505683566a.
In the ULS viewer I found the followign entries with Correlation ID 'ee43449c-9c91-c072-7eb7-306325643883':
E1. Standard Information:PSI Entry Point: <unknown> Project User: <unknown> Correlation Id: <unknown> PWA Site URL: SA Name: <unknown> PSError: <unknown> A queue job has failed.
This is a general error logged by the Project Server Queue everytime a job fails - for effective troubleshooting use this error message with other more specific error messages (if any), the Operations guide (which documents more details about queued jobs)
and the trace log (which could provide more detailed context). More information about the failed job follows. GUID of the failed job: 570ecef4-8520-e311-93fe-00505683566a. Name of the computer that processed this job: 5cb42698-f709-4727-9b66-336647d7eb73 (to
debug further, you need to look at the trace log from this computer). Failed job type: AdSyncERP. Failed sub-job type: AdSyncERPMessage. Failed sub-job ID: 1. Stage where sub-job failed: (this is useful when one sub-job has more than one logical processing
stages).
Error is: GeneralQueueJobFailed. Details: Queue Attributes: 570ecef4-8520-e311-93fe-00505683566a 5cb42698-f709-4727-9b66-336647d7eb73 AdSyncERP AdSyncERPMessage 1 ee43449c-9c91-c072-7eb7-306325643883 . Standard
Information: , LogLevelManager Warning-ulsID:0x000DD158 has no entities explicitly specified.
If somebody knows waht is happening with this errors, I will be
very grateful.
PD: I can send the Log file when errors occurred. Just let me know the email.
Regards,
Andres Rojas
Bogotá - Colombia
Ing. Andres Rojas | MVP SharePoint Server | MCITP, MCPD, MCTS | http://arojaspa.blogspot.com | twitter: arojaspa
推荐答案
是db 2010年至2013年的谈话是否成功？
Was db conversation from 2010 to 2013 was successful?
这篇关于从Project Server 2010迁移到Project Server 2013后出现许多错误的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
