Project Server 2003 err saving "Invalid Column name'ASSN_ENTSUMPRO

[Paul Harker|PMP]

I am getting a strange error saving some projects on my Project Server 2003.

I get the following error: "Invalid Column name'ASSN_ENTSUMPROJID.

Of course, the field is in the table and valid. I have cleared my cache and
deleted my project configuration files, global template, etc.

It does not seem to impact the projects, and everything works except for the
Project Modeler.

Q: If this is a project corruption issue, it seems that a lot of project
files are easily corrupted, and this is a concern as I am only in a POC for
~30 days, and am already seeing that this is a significant issue.

Thanks!

 

[Chak]

I am getting a strange error saving some projects on my Project Server 2003.

I get the following error: "Invalid Column name'ASSN_ENTSUMPROJID.

Of course, the field is in the table and valid. I have cleared my cache and
deleted my project configuration files, global template, etc.

It does not seem to impact the projects, and everything works except for the
Project Modeler.

Q: If this is a project corruption issue, it seems that a lot of project
files are easily corrupted, and this is a concern as I am only in a POC for
~30 days, and am already seeing that this is a significant issue.

Thanks!

Hi Paul,

Which MS project version you are using? By any chance MS Project 2000?
It made me to remember those old days, I used to hear about this
error.

As I know the technical reason beyond this error, starting from MS
Project Server 2002, Microsoft introduced the new column
ASSN_ENTSUMPROJID in MSP_Assignments table. It means Project Server
2003 also have this column.

So, if you trying to attempt to save MS Project 2000 version file in
MS Project 2002 or 2003, and your 2000 version file consists resource
assignments, so obviously original file not have this new column. When
system is saving assignments data into 2002/2003, system unable to
find the ASSN_ENTSUMPROJID column from 2000 file.

I am not sure what's your scenario here, but first thing on my mind,
it seems to be those few projects may be originated from MS Project
2000.


Useful links:

1) About Error message:

http://support.microsoft.com/kb/840702


2) You can see the 2002 documentation here about new column on
MSP_Assignments table. Almost the schema is same for Project Server
2003. (MS Project Server 2007 schema is totally different offcourse.)

http://www.esm.vt.edu/~jlesko/Project/DOCS/1033/PROJDB.HTM


Thanks
Chak
http://www.epmcentral.com

 

[Paul Harker|PMP]

Chak,

All projects are 2003 versions, although some may have originally started as
2000 versions. This is not consistent though. I have created projects from
scratch on ProJ Pro 2003, and am getting the same error, though it is
normally after a few saves to the server.

It sounds more like a corruption issue, so I will start down that path. But
can anyone tell me, why is this issue so common in these threads? It seems
that Proj Server 2003 has a corruption problem!

Thanks.

Paul

 

[Paul Harker|PMP]

FYI, I exported the project as XML, deleted the project off the server (and
site as this is in a POC environment), imported as a new project, and got
exactly the same error. I verified Proj Serv & client 2003 SP3, and verified
the SQL update scripts were run.

Any more ideas?