In OI 3.5, we have deployed a runtime with access to ORMAIN (report builder) We initially had problems and Andrew McAauley suggested we had somkehow failed to deploy the SYSENV record ORMAIN_RESOURCES. This turned out to be true, and when this was done, it solved most problems….completely on one deployment (standalone) but on another on a network, we get the message "Failure to read resource record" when we Open an existing report definition. We click OK and go on and have anomolies regarding save as, save, etc. The ORMAIN_RESOURCE record is loaded, and in fact the error messages contained it that record are displayed when appropriate.

Would like to resolve the "Failure to ……" thinking that may also solve the save as problems. Does anyone know the source of this error message and how to eliminate the cause?

Thanks,

Paxton-

I haven't come across this problem before. Is the ORMAIN_RESOURCE record the same as in the working system?

-Tracy Revelation

The cause of this most likely is that you have some corrupt report keys in the SYSREPOSREPORTS table - created as a result of the previous problem. Delete these records and problem solved. (Hence why one site OK and others not)

To solve look in the SYSREPOSREPORTS table for record keys that look strange ie

"MYAPP*REPORTBUILDER*record error!"

or similar (I found such records)

THEN delete records ie

RUN DELETE_ROW "SYSREPOSREPORTS","MYAPP*REPORTBUILDER*record error!"

and hopefully problem solved (unless you have to also delete an entity reference)

Richard Bright

BrightIdeas New Zealand

[email protected]

I've looked and can't find a difference. I could try copying the record I guess. I didn't think that was the problem since it uses messages from that record????

thanks, Paxton

Thanks for your excellant suggestion. Gave me something to try, and I found one record "MYAPP*RBLAYOUT*record!" and deleted it, but the symptoms did not change.

To refreash, when report builder opens, ok when we click on open, before we get a list of existing reports, we get "Can not open resource record", OK After clicking OK, can work, but can not save changes.

I don't know of any entity references I might have, you have any other suggestions?

Best regards,

[email protected]

[url=http://www.wws.net/arcs/]ARCS, Inc.

Did you kill off the matching entity pointer in the SYSREPOS table ie

APPNAME*OIREPORT*RDEVELOPER*Bad_record!

(I think that is the format). From memory I killed it off by straight delete but may have done it through the repository delete entity.

Richard Bright

BrightIdeas New Zealand

MANY BIG HEART-OF-AMERICA THANKS! Problem solved and now can proceed with customer installation!!!!

Many cyber points to you!

Hope we can help someone soon!

–paxton

View this thread on the Works forum...