Activation Problem

[Former Member]

Hi,

I have a problem with Activation of some Activities.

Request Protocol tells me the following:

Change request state from PROCESSING to FAILED

ERROR! The following problem(s) occurred during request processing:

ERROR! The following error occurred during request processing:Server error (500 Internal Server Error)

I get that error, if i try to activate a special activity.

If I try to import more than one activity, I get the following error message:

Change request state from PROCESSING to FAILED

ERROR! The following problem(s) occurred during request processing:

ERROR! The following error occurred during request processing:HTTP protocol error (reason: Parsing of the response body failed (reason: </ expected (:main:, row:1, col:114355)))

Anyone an idea?

Otmar

Edited by: Otmar Jatsch on Feb 27, 2008 4:20 PM

[Former Member]

Thanks Pascal,

indeed it was a Problem with the database, which I could extract from the log-files.

And I remember some months ago I had a similar problem.

So perhaps for problems in the future:

If you get an error message that tells you that the http request could not be parsed, it can be a problem with the database, exact problem was a tablespace that could not be extended.

Thanks Pascal for bringing me on the right path.

[Former Member]

Back again.

Restart of Server helped temporarily. I could activate some activities. But after some time the problem was the same. Restart the server again, could activate some activities and problem is back. I dont want to start the server over and over again till I have done all my work.

It seems that the server gets into a inconsistent state.

I again post the error in hope someone got an answer:

ERROR! The following error occurred during request processing:HTTP protocol error (reason: Parsing of the response body failed (reason: </ expected (:main:, row:1, col:10226)))

[Former Member]

Since it seems that the server is having a problem, it might be a good idea to examine the server logs.

[Former Member]

Solved problem!

Restart of Server did it