XML in Viewdrop

[AI]

Hi All:

In our instance of Project Server, XML queue grew to 120 XML files over 3
days. The View notify process was running fine. There was a problem with one
of the project (say Project A) with the oldest XML that caused the queue to
grow. We moved the problematic (Project A) XML file to a temp folder as
Microsoft suggests. The processing of the remaining 119 files resumed and
finished in Viewdrop folder.

When I bring this "Project A" XML file back to viewdrop, what should I take
care of. I am afraid that because the PM may have accepted updates later on
this Project A, another newer XML for this project A may have gotten
processed. If I push this old XML to Viewdrop does it affect my project
adversely in any way?

Please advise. Your suggestions are appreciated.

Thanks,
AI

 

[Johnnie Rotten]

Sorry to piggy back off of your question but we have some "similar" problems
to your situation.

We're periodically experiencing "stuck" files in our VIEWDROP folder. When
we remove the offending file OR restart the views & scheduler services the
files are processed, or removed from the folder. I say removed because
there is no log or event log entry saying that the xml is processed
successfully.

Errors in the application log do indicate a problem with the xml file's
CDATA - Description parameter. The error codes correspond with spooler
errors outlined in the Admin Guide. Once the view & scheduler service is
restarted why does the the "stuck" files become processed?

Thanks!!!!!

-John R. (Rust never sleeps --> Neil Young)

 

[Gary L. Chefetz [MVP]]

AI:

The XML package is an instruction to process, and doesn't contain the data
to be processed. That survives in the database regardless of whether it gets
published or not. So, restoring the XML package after another containing the
same instructions has run for a project, this only restarts the publish
process. If underlying data corruption or permissions issues are the root
cause, theoretically the next XML instruction set will fail in the same way.

--


Gary L. Chefetz, MVP
"We wrote the books on Project Server"
http://www.msprojectexperts.com

For Project Server FAQs visit
http://www.projectserverexperts.com

For Project FAQs visit
http://www.mvps.org/project

 

[AI]

Gary:

Thanks for the insightful information.

What I find bizzarre is that these XML files execute fine when submitted at
a later point in time. That makes me wonder what was corrupt about them in
the DB or what permissions were missing. Could it be temporary network
problems that causes the permissions to be verified.

When you say it reatsrts publishe process, do you mean that it publishes New
and Changed assignment when triggered by XML.

Thanks.
AI

 

[Gary L. Chefetz [MVP]]

Yes: it causes the publishing process to run again.

--


Gary L. Chefetz, MVP
"We wrote the books on Project Server"
http://www.msprojectexperts.com

For Project Server FAQs visit
http://www.projectserverexperts.com

For Project FAQs visit
http://www.mvps.org/project