PWA fails on edit of project after external update

[Bill E.]

We have a stored procedure that refreshes a selection list for an
enterprise custom field. Basically, this procedure deletes records in
msp_Attribute_Strings for a give proj_id (the ent. global tempate) and
as_id and then reinserts them, pulling the values from another
corporate database. After this, we set the proj_ext_edited flag for
the global enterprise template and the attrib_ext_edited flag in
MSP_FIELD_ATTRIBUTES for the given attrib_field_id and as_id that was
changed.

Everything seems to work fine when opening projects in Project
Professional. However, when we try to edit a project using PWA
(Projects, click on project, Edit) we get the following error:

Request Status: 9121

Looking in the Event Viewer, we see the following error

Component: PDS
Line: 0
Error Number: 0x23a1
Description:
<Description><![CDATA[CDataAccess.ReadUserNamedEnterpriseColumns; 5 :
Invalid procedure call or argument]]></Description>


If we go to Project Professional, open the Global Enterprise Template
and save it, the problem in PWA goes away and we can now edit the
projects. However, I notice that doing this effectively creates a
brand new Global Enterprise Template (a new project in the database).

Is there something that I'm missing in my updates that could be
confusing PWA? Also, as a potential workaround, is there a way that I
can effectively save my Global Enterprise Template but without opening
MS Project Professional?

Bill E.

 

[Rod Gill]

Making any edit directly on the Enterprise Global is very risky. You may
corrupt your entire project setup. Enterprise changes should only be made
manually or via automation. The Ent. Global is a special project and is too
critical to your whole project server setup to mess with!

Absolutely you should have a backup saved before editing it.

 

[Bill E.]

Thanks for the advice, Rod. We were originally making these changes
using PDS but that did not work properly at all. I was then advised by
someone on this forum (Ed Morrison) to modify the tables directly.
After carefully reviewing the pjdb.htm documentation, I was able to
write a couple of stored procedures that did the trick. However,
someone recently spotted this problem with PWA so I had to go back to
see what was happening.

Fortunately, I was able to locate the source of the problem: I'm not
allowed to delete anything from the msp_Attribute_Strings table--I can
only update and insert. Ed warned me about this but I had forgotten.
I went back to my stored procedures and changed them to synchronize the
lists without deleting. This is now working and the problem in PWA has
gone away.

Bill

Making any edit directly on the Enterprise Global is very risky. You may
corrupt your entire project setup. Enterprise changes should only be made
manually or via automation. The Ent. Global is a special project and is too
critical to your whole project server setup to mess with!

Absolutely you should have a backup saved before editing it.

--

Rod Gill
Project MVP
Visit www.msproject-systems.com for Project Companion Tools and more

We have a stored procedure that refreshes a selection list for an
enterprise custom field. Basically, this procedure deletes records in
msp_Attribute_Strings for a give proj_id (the ent. global tempate) and
as_id and then reinserts them, pulling the values from another
corporate database. After this, we set the proj_ext_edited flag for
the global enterprise template and the attrib_ext_edited flag in
MSP_FIELD_ATTRIBUTES for the given attrib_field_id and as_id that was
changed.

Everything seems to work fine when opening projects in Project
Professional. However, when we try to edit a project using PWA
(Projects, click on project, Edit) we get the following error:

Request Status: 9121

Looking in the Event Viewer, we see the following error

Component: PDS
Line: 0
Error Number: 0x23a1
Description:
<Description><![CDATA[CDataAccess.ReadUserNamedEnterpriseColumns; 5 :
Invalid procedure call or argument]]></Description>


If we go to Project Professional, open the Global Enterprise Template
and save it, the problem in PWA goes away and we can now edit the
projects. However, I notice that doing this effectively creates a
brand new Global Enterprise Template (a new project in the database).

Is there something that I'm missing in my updates that could be
confusing PWA? Also, as a potential workaround, is there a way that I
can effectively save my Global Enterprise Template but without opening
MS Project Professional?

Bill E.