ReadProjectEntities causes a GeneralUnhandledException

[Tiffy Huxtable]

Hi

when I call ReadProjectEntities(Guid, 266,
PSI_PROJECT.DataStoreEnum.PublishedStore) I get a
GeneralUnhandledException from the WebService. I want to read Tasks,
Assignments and Assignment Custom Fields.

The Guid is valid, the project is checked-in, nobody else but me is
using Project Server.
Any suggestions what causes this exception?

Thanks and good bye
Tiffy

 

[Stephen Sanderlin]

Try setting the ProjectEntityType value to: (2 | 8 | 256) instead of
266.

--

Stephen Sanderlin

Principal Consultant

MSProjectExperts



For Project Server Consulting: http://www.msprojectexperts.com

For Project Server Training: http://www.projectservertraining.com



Read my blog at: http://www.projectserverhelp.com/

Join the community at: http://forums.epmfaq.com

 

[Tiffy Huxtable]

Try setting the ProjectEntityType value to: (2 | 8 | 256) instead of
266.

Ty for your answer. To be honest I don't see any difference, and the
GeneralUnhandledException does still occur. Can it be that the results
are too big? If yes then a split into three separate calls could help.

I have more data now: when the user is member of administrator group
then it works, for all other users it does not and this exception
occurs. Is a really tricky issue but I have to solve it.

Good bye, Tiffy

 

[Stephen Sanderlin]

There really isn't any difference at the binary level with the values
Microsoft has chosen for that enumeration. 10 + 1000 + 100000000 =
100001010 == 10 | 1000 | 100000000 = 100001010. however, I just wanted
to have you check and make sure since the SDK explicitly says to do a
bitwise OR rather than an ADD. It's usually best to eliminate the
obvious (albeit unlikely) issues first.



ReadProjectEntities requires LogOnToProjectServerFromProjectProfessional
and OpenProject. Since you're saying that this works fine for
Administrators, it sounds like Administrators have the OpenProject
permission via a category for all projects, whereas whatever account you
are executing the call as does not. Can you confirm?



If the call works for Administrators but for nobody else, I would not
expect this to be a capacity issue. More likely, it is a permissions
issue. I would be inclined to believe that when the PSI encounters a
project that the user you are running the operation as does not have
permission to, it throws the error (though I would personally expect it
to throw error 20010 instead of error 42, but that's just me). Let's
check the permissions and see if that is the issue.



--

Stephen Sanderlin

Principal Consultant

MSProjectExperts



For Project Server Consulting: http://www.msprojectexperts.com

For Project Server Training: http://www.projectservertraining.com



Read my blog at: http://www.projectserverhelp.com/

Join the community at: http://forums.epmfaq.com

 

[Tiffy Huxtable]

Ok, I did the following, because I read three elements from PSI at one
time (tasks, assignments, assn custom fields) maybe the results are
just too big. I split them into three single webservice calls, one for
tasks, one for assignments and one for assn custom fields, and get
three ProjectDataSets. I am still waiting for the results so I don't
have any more information at this time.

Can it be that ReadProjectEntities can cause such a big ProjectDataSet
that either the call or the SOAP crashes with a
'GeneralUnhandledException'?
Or can it be that the webservice call uses so much RAM on the web
server that is crashes at this point, like 'out of memory' ? I
remember a setting in the IIS web service where you can define a
certain amount of RAM for every web server call.

Greetings, Tiffy

 

[Stephen Sanderlin]

To be entirely honest, I'm not sure. The SDK states that updates are
limited to 1000 rows, but makes no mention of any similar restriction
for ReadProjectEntities.



However, it is a possibility. One way to check would be to turn up the
verbosity of the Diagnostic Logging on the server and try to reproduce
the issue to see if any errors arise in the ULS, Event, or IIS logs.



An interesting test would be to see if ReadProject() gives the same
error. if not, then perhaps this is an idiosyncrasy of the
ReadProjectEntities method we should make note of. Can any of the
Microsoft people on the board provide any insights?



When receiving the three datasets, you may want to take advantage of the
Merge() method of the ProjectDataSet to get one big dataset if you would
prefer.


--

Stephen Sanderlin

Principal Consultant

MSProjectExperts



For Project Server Consulting: http://www.msprojectexperts.com

For Project Server Training: http://www.projectservertraining.com



Read my blog at: http://www.projectserverhelp.com/

Join the community at: http://forums.epmfaq.com