Package builds in CRP

[frown]
Hi everybody,
Since a few weeks we're experiencing a rather strange problem: full package builds fail with a memory violation error, but only for the CRP environment, error is:

ERROR: Could not add record to GBRSPEC. Record: evseq: 10, esevsk: 5ef16905..................................."

Package builds for other environments complete successfully.

I've refreshed the specs on the enterprise server (AS/400) but this didn't solve the problem. Planner specs should be ok on the deployment server (Windows NT) as the package builds for DEV en PRD are OK.

Anyone has a clue what could be the problem here?
thanx!!

Kurt
B7332 SP 15.1
AS/400-HP UNIX(JAS) - WTS 2000

Kurt :

Link the CRPB733.F98740 and F98741 tables by using the EVSK field,

SELECT * FROM F98740 INNER JOIN F98741 ON F98740.**EVSK = F98741.**EVSK AND
F98741.**EVSK='5ef16905...'

It will tell you which CRP object went corrupt.
You have to transfer that object from a 'healthy' environment, such as
PRODB733 into CRPB733 and build a full CRPB733 package.

Sebastian

----------------------------------------------------------------------------
Strictly Personal and Confidential.
This email may contain confidential and proprietary material for the sole
use of the intended recipient. Any review or distribution by others is
strictly prohibited. If you are not the intended recipient please contact
the sender and delete all copies.Thanks.
.
Este mensaje es confidencial.
Puede contener informacion amparada por el secreto profesional. Si usted ha
recibido este e-mail por error, por favor comuniquenoslo inmediatamente via
e-mail y tenga la amabilidad de eliminarlo de su sistema; no debera copiar
el mensaje ni divulgar su contenido a ninguna persona. Muchas gracias.
----------------------------------------------------------------------------

I´ve had this problem for a lot of records in my table some months ago.
The way jde told me to solve that is on this document that is available on KG: OTM-01-0021, the document says that is for World, but I used in OW.
Just one more thing, I´ve lost 3 weeks fixing the GBRSPEC, cause anytime I fixed an error, i´ve built the package again and got another error.
I sugest you don´t begin a new package after fixing the error and resubmit the old one, it´ll save you a lot of time.
Robson

I already applied the steps from OTM-01-0021 a couple of times, each time for a different record (after a build resubmit). Was afraid that is was a never-ending process, but apparently you just have to be plucky and keep on trying :-((
Again, thank you for your help…