J
J Baird
The Project Server 2002 Projdb.htm (database schema) file states the
following:
MSP_PROJ_SECURITY
This table enforces security in the MSP_PROJECTS table and is maintained by
the Project Data Service (PDS), which enforces either read-only or
read/write access on this table. This table should only have data in it
during a read or write operation from the Microsoft Project Professional
client, therefore, this table should normally appear empty.
The table isn't empty. I have a schedule file (PROJ_ID=109) that has an old
(1+ weeks) record hanging out in this MSP_PROJ_SECURITY table. The user
currently gets all kinds of access errors whenever they open and save the
file. When they're publishing it, Proj_ID#109 has TWO records in the
MSP_Security_Table. The record that won't delete, is from last week. Does
anyone know what causes this problem, and how to fix it?
The old record is as follows:
Proj_ID sec_spid sec_spiddatestamp Sec_readcount
Sec_writecount
109 76 8/19/2004 1:16:04 PM 1
0
BTW: sec_spid: SPID 76 is a SQL "CursorImplicitConversion" Event class
Obviously, the Sec_writecount set to 0 is odd, since this user is the only
one that ever publishes this schedule.
The record duplicates, with different write values when they publish the
file (when they're actually able to publish the file!!!)
following:
MSP_PROJ_SECURITY
This table enforces security in the MSP_PROJECTS table and is maintained by
the Project Data Service (PDS), which enforces either read-only or
read/write access on this table. This table should only have data in it
during a read or write operation from the Microsoft Project Professional
client, therefore, this table should normally appear empty.
The table isn't empty. I have a schedule file (PROJ_ID=109) that has an old
(1+ weeks) record hanging out in this MSP_PROJ_SECURITY table. The user
currently gets all kinds of access errors whenever they open and save the
file. When they're publishing it, Proj_ID#109 has TWO records in the
MSP_Security_Table. The record that won't delete, is from last week. Does
anyone know what causes this problem, and how to fix it?
The old record is as follows:
Proj_ID sec_spid sec_spiddatestamp Sec_readcount
Sec_writecount
109 76 8/19/2004 1:16:04 PM 1
0
BTW: sec_spid: SPID 76 is a SQL "CursorImplicitConversion" Event class
Obviously, the Sec_writecount set to 0 is odd, since this user is the only
one that ever publishes this schedule.
The record duplicates, with different write values when they publish the
file (when they're actually able to publish the file!!!)