Kbase P105460: Security Range code raises error 132 on the appserver
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
25/03/2010 |
|
Status: Unverified
SYMPTOM(s):
When a container with Security Ranges code implemented is run multiple time against the AppServer, error 132 is written to the AppServer log file and expected data may not be displayed
** <file-name> already exists with <field/value...>. (132)
** ttRangeSecurityCheck already exists with "<range>" "<object>" "<module>". (132)
Application works fine in Client/Server mode
FACT(s) (Environment):
Dynamics
CAUSE:
Bug# OE00117064
FIX:
Clear the content of the ttRangeSecurityCheck temp-table in the rangeSecurityCheck internal procedure of af\app\afsecmngrp.i and recompile both the client (af\sup2\afsecclntp.p) and the server (af\app\afsecsrvrp.p) parts of the security manager. The easiest solution is to add "EMPTY TEMP-TABLE ttRangeSecurityCheck." statement after the &ELSE line:
&ELSE
...
DEFINE BUFFER b2ryc_smartobject FOR ryc_smartobject.
EMPTY TEMP-TABLE ttRangeSecurityCheck.
/* If security is disabled or the security object is not passed in then "" is
returned for both values indicating full access is permitted.
...
Although the solution is simple, it effectively disables server side security caching for ranges.