A
aSoundMind
Hi there,
I recieved this error when trying to delete any risk or issue. My
system is
Project Server 2003, SQL Server 2000 and WSS 2.0 all running in one
server
'record count' is null or not an object
An error occured in updating the project server database with the
uploaded
document. log on to project server again, and link this document to a
task in
your tasks page'
I have checked the sharepoint database and I found out these facts:
1. A new issue is never stored in database. But it's displayed in PWA
and
can be edited.
2. A new risk in other hand is stored in database. can be found in
userData
table
3. Although I have assigned affected task to the risk, the
wobj_task_id is
NULL which I assume that it inditactes there's no tasks related to
the
particular issue. But the fact those tasks are.
I am wondering if there's some sort of error in the database which
makes me
can't view the issues and affected tasks. How to resolve the error I
mentioned above. Hope after resolving the risks and issues are stored
and can
be viewed normally in the wss and project server database.
//Jack
I recieved this error when trying to delete any risk or issue. My
system is
Project Server 2003, SQL Server 2000 and WSS 2.0 all running in one
server
'record count' is null or not an object
An error occured in updating the project server database with the
uploaded
document. log on to project server again, and link this document to a
task in
your tasks page'
I have checked the sharepoint database and I found out these facts:
1. A new issue is never stored in database. But it's displayed in PWA
and
can be edited.
2. A new risk in other hand is stored in database. can be found in
userData
table
3. Although I have assigned affected task to the risk, the
wobj_task_id is
NULL which I assume that it inditactes there's no tasks related to
the
particular issue. But the fact those tasks are.
I am wondering if there's some sort of error in the database which
makes me
can't view the issues and affected tasks. How to resolve the error I
mentioned above. Hope after resolving the risks and issues are stored
and can
be viewed normally in the wss and project server database.
//Jack