MSPS 2007 - Asking for help to debug a Reporting (Project Publish)

[Tim Mccoy]

I am publishing a project schedule and the Job Type = Reporting (Project
Publish) keeps failing with a 'Failed But Not Blocking Correlation' error. I
assume I need to figure out what the error means and how to fix it even
though my schedule still shows up in PWA.

Does anybody have any information I can use to debug?

Thank you.

 

[Stephen C. Sanderlin]

First off, I would check the SQL Server to see if there are any usable
errors there. I would then turn the Diagnostic Logging levels all the
way up, republish a project, and then go through the Application and
ULS Logs on the server(s) to see if there is anything relevant.

There have been reports of the Reporting database sync failing due to
corruption, causing this type of error, but I wouldn't jump to this
conclusion without some harder evidence of such.

--
Stephen C. Sanderlin
Owner/Founder - EPMFAQ
http://www.epmfaq.com/
http://forums.epmfaq.com/

Principal Consultant - BT INS
http://bt.ins.com/

This electronic message, along with any information, advice, and
opinions it contains, are mine alone and are not representative of my
employer. All information is provided in "GOOD FAITH" and on an "AS IS"
basis only. I provide no presentations or warranties, express or
implied, including implied warranties of fitness for a particular
purpose, merchantability, title, and noninfringement. I strongly advise
you to extensively test any changes, workarounds, or techniques
described herein on a development system prior to implementation in a
production environment, and you are hereby notified that I bear no
responsibility whatsoever for any loss, harm, or otherwise negative
outcomes resulting from your actions, whether or not said actions were
a result of this electronic message, directly or indirectly.

 

[Paul Conroy]

There should be some elementary logging available in the Queue. Scroll the
Queue dialogue so you can see the right most column. There should be a link
to an error.

As Stephen mentioned, increased the logging of the Project Queue to Verbose
and re-publish your plan. This will give you as much information as the
system can provide.

Don't leave verbose logging turned on indefinately as the size of your log
files will gro expotentially.

 

[WimVDB]

Hello everybody,

I have the same problem. Did anyone find a solution already?
Using verbose mode for event logging didn't help. In fact, there is nothing
like 'ERROR' in the log file. The reporting database doesn't seem to be
corrupt either (but rather empty )

Wim