Our organization is a user of MS Project Server 2002. We too have experienced
a consistent failure with respect to linking Issues to documents. We have no
trouble linking issues to tasks. What I have discovered:
1). I ran a script debugger and found that the error in our case was
associated with the script iterating over a table of document attributes and
running into a null instance of the title field. After further debugging
efforts I determined that the number of title instances was fewer than other
document attributes. I attempted to correct this through going back through
the project libraries and adding titles to those documents that had
previsiously been added/uploaded and not assigned a title. Although the
number of title instances did indeed change when running the script again I
was never able to get the number of title instances to reconcile with the
attribute that was used to set the iterator control (can't recall the
attribute which the script used). What I finally wound up doing after having
exhausted this newsgroup resource, along with searches for service via
Microsoft support was to edit the script, and use the Title(length) attribute
to set the number of documents, which in turn was used to set the value of
the iterator control. This finally resulted in the script running to
completion without error and I was able to link issues to documents.
unfortunately there is still something askew in the execution of the script,
such that documents are not always assocaited with the correct library.
2). What I have concluded from this experience is the following:
I suspect the problem is owed to the fact that the default view for a
document library documents does not demand that the title field be populated.
I in turn after having created project libraries and having a set of
documents loaded to the project library alter the view to make the entry of a
title mandatory. What has happened is the underlying SQL database is now
corrupt with varying instances of the varioius document attributes.
I believe that I have seen MS Support issues on this problem in the past,
but I can't find any trace of this now. I had applied Project Server 2002 SP1
in hopes that this would correct the problem, and it did not. I am of the
opinion that both Project Server 2002 and 2003 have some fundamental flaws in
their management of the database information, however it would appear that
you will not find your answers via this community newsgroup, as my own pleas
for assistance have gone unanswered on several occasions. If you search for
link, documents or issues you will find several variants of problems related
to this information, without resolutions or answers.
