Kbase 18722: RTB - Error 138 During Partner-Site Load, Things To Check
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
8/21/2003 |
|
Status: Technically Reviewed
FACT(s) (Environment):
Roundtable
SYMPTOM(s):
** <file-name> record not on file. (138)
FIX:
Things to check when you get the 138 error:
1) Make sure that you are naming the workspace the same in the "load" repository as the name of the workspace you dumped. If you use a different name, the outcome can be unpredictable.
2) A workspace that you load into a partner site is an exact copy of the one that was dumped. RTB gives you the ability to create incremental deployments from the master site to keep the partner site up to date.
If there is an incremental deployment missing or you are trying to load a deployment as the first load that is not the first deployment to the site, you get 138 errors when you try to load.
Since it is read-only and an exact copy of the master site's workspace, you can recover easily. You delete the workspace from the partner site, create a new partner site deployment from the master site that is a full/initial deployment (it is the first deployment in the list of deployments for the site). When you
load it into the partner site as a new workspace, you are completely recovered.