Kbase P25347: Getting WebSpeed error 6019 and 6383 intermittently with 132 error in the server log file
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
09/09/2008 |
|
Status: Verified
SYMPTOM(s):
Getting WebSpeed error 6019 and 6383 intermittently with 132 error in the server log file
WebSpeed error from messenger process (6019)
Agent did not return an HTML page (6383)
The <broker_name>.Server.log, or server log file contains the following error:
** webSess already exists with sessId <id number> loginId "<userName>". (132)
** <file-name> already exists with <field/value...>. (132)
FACT(s) (Environment):
A dump and load was done on the database, but the sequence is never reset to its previous sequence value
All Supported Operating Systems
Progress/OpenEdge Versions
CHANGE:
Dump and load of the data is performed on the database without resetting the previous sequence value
CAUSE:
The dump and load from one database to another new database causes the sequence value to be different if the sequence value is not reset with the previous database value. Therefore, when a user tries to create a record, the sequence value is created with value of 1. On the other hand, the sequence value 1 is already exist when the data that is loaded on the new database, hence, the error message 132 shows up in the server log file.
FIX:
Reset the sequence value on the new database from the old database by dumping the recent sequence value.