Downloads
Product availability Matrix (PAM)
Downloads of this patch are available from the
Rocket Customer Support Portal.
Further explanation can be found
here.
Fixes
| UNI-34236 | A call to a ProcScript function from within some ProcScript function sometimes fails with a <uprocerr_function> error.</uprocerr_function> |
| UNI-34067 | Uninstalling RMS 10 from a Windows system may leave a key in the registry |
| UNI-34010 | License error 'License File: 210133 - Fail to acquire resource lock' not handled properly |
UNI-34236 - A call to a ProcScript function from within some ProcScript function sometimes fails with a <uprocerr_function> error.</uprocerr_function>
Solution available in patch(es): 10.4.02-029
Description:
When an entity-level operation calls a ProcScript function which calls another function, the second function call can fail with a <UPROCERR_FUNCTION> error.
As an example, consider the following code in the Collection Script container of some entity:
partner operation oper1
throws
call func1()
end
function func1
throws
call func2()
end
function func2
throws
message "Function func2 is being called"
end
In a situation where collection operation oper1 is activated, the call to func2 fails with <UPROCERR_FUNCTION>.
Environment:
+ Uniface version 10.4.02.016 and higher
+ Platform: ALL
Workaround:
None.
Notes:
This problem is solved.
UNI-34067 - Uninstalling RMS 10 from a Windows system may leave a key in the registry
Solution available in patch(es): 10.4.02-029
Description:
When uninstalling the RMS 10 server from a Windows system is successful there may still be a key for it left under Uninstall. This causes Windows to think it is still installed and display it as an installed program, even though it is no longer on the system.
Environment:
+RMS 10.0
+Operating System: Windows
Workaround:
Remove the registry key under uninstall manually.
Notes:
The uninstallrms.ps1 script that takes care of returning cloud leased licenses and then uninstall RMS has been updated to also remove this registry key if the uninstallation was successful.
UNI-34010 - License error 'License File: 210133 - Fail to acquire resource lock' not handled properly
Solution available in patch(es): 10.4.02-029
Description:
Error 210133 means that Sentinel was unable to acquire a lock on some resource because it is already locked. Such a lock is only temporary, so Uniface should retry the license login and not terminate.
Environment:
+Uniface: Version 10.3.02-061 (and higher), 10.4.01 (and higher)
+Operating System: OS independent
+Database: DBMS independent
+License Configuration: Stand alone, both On-premise and CLoud leased.
Workaround:
You can try to have fewer Uniface processes trying to use the license file at the same time. Other than that there is no workaround for this problem.
Notes:
Uniface will retry log-in to the license system immediately after receiving this error. If that fails again, Uniface will wait for half a second and then retry. If that fails again it will wait for one second and retry, and again for two seconds and retry. If after that time log-in to the license system still fails, Uniface will stop trying.