Kbase 16931: Citrix Winframe Support Policy -- Errors 1124, and 1152 .dbi
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
11/21/2006 |
|
Status: Technically Reviewed
GOAL:
Progress and Citrix Winframe support policy.
FACT(s) (Environment):
Citrix Winframe 1.7
SYMPTOM(s):
SYSTEM ERROR: wrong dbkey in block. Found <dbkey>, should be <dbkey2> (1124)
SYSTEM ERROR: read wrong dbkey at offset <offset> in file <file>
FIX:
Progress tested and supports Citrix 1.7 with Progress version 8.2C or later. This Knowledge Base discusses errors that may result with unsupported combinations of Progress and Citrix Winframe. Sometimes clients won't advise you they are using Winframe, so this KBase also provides TSEs with some of the clues that will help in spotting the Winframe users.
Winframe is a shared windowing environment similar to X-Windows. It allows many clients to use low-powered machines to connect to a single very powerful machine and run their Windows from that server. Basically Winframe is Windows NT 3.51 with some modifications.
Progress announced support for Winframe version 1.7 starting with Progress 8.2C. However, many customers are using earlier versions of Progress on Citrix. Other customers are using Progress on Microsoft's Windows Terminal Server which is based upon Citrix technology. However, Progress only tests and supports Citrix 1.7 and only with Progress version 8.2C or later. Any other combinations are not supported and not recommended by Progress Software Corp.
Here are some things to look for. Frontstep (formerly Symix) did some testing and established certain guidelines for Syteline (their product) on a Winframe Server. A typical Frontstep Winframe server will have 256 Meg of Ram and will likely have two 200 Megahertz Pentium processors. However these are likely figures for a Frontstep system which has 16-20 users. If there are more users, look for 512 or higher Meg of ram.
-- Support for Progress versions prior to 8.2C:
We have made written agreements with Frontstep (and I believe QAD) stipulating that if a client has a problem while they are using Winframe, the client is to try to reproduce the same problem using a TRUE NT 3.51 or NT 4.0 system. If the problem can be reproduced on that TRUE NT system then we will address the issue. If the problem can not be reproduced on the true NT system then the problem is most likely specific to Winframe and that client should speak to the AP
who sold them the package.
-- Support for Progress versions 8.2C and later:
Progress Technical Support will work with the customer to resolve issues directly on Citrix WinFrame 1.7, the customer does not need to duplicate the problem on regular Windows NT. However, the customer must be on Citrix version 1.7, no other versions are supported.
Most of the problems we have seen relating to Winframe seem to involve the temporary files normally created by the client processes.
If you get any of the following errors 137, 1152, 1124, 15 please check the Database log and look for problems with .dbi or .lbi files.
Also if the client does a dbrpr scan of the database and it comes up clean but you are getting 1124 errors, ask the client if they are using Winframe.
References to Written Documentation:
Performance issues are detailed in Progress Knowledge Base Solution 17660, "WinFrame Citrix Support & Installation Notes", and also in the Citrix manuals.
For more detailed information on 1124 errors, please see Progress Knowledge Base Solution 15349, "Debugging the causes of S/E 1124"