SAS 8 and SecLab are not loading or are timing out
SAS 8 or SecLab hang, fail to load, or time out when started with X-Win32 5.4.3 or lower. This was a bug with X-Win32 5.4.3 and earlier that was fixed in X-Win32 6.0 and later.
SAS makes initial contact with the X-Win32 then disconnects as part of its normal startup process. SAS spawns a few different windows when it starts up correctly. After it’s initial connection and disconnect, X-Win32 resets. X-Win32 only resets after all connections are dropped. During X-Win32’s reset, which takes about a second, SAS is tries to connect again but fails because X-Win32 is not able to accept a connection for.
The work-around for X-Win32 5.4.3 and earlier is to instead start an xterm in your session, then start SAS or SecLab from that xterm. The xterm will remain open during SAS or SecLab’s startup process, which will prevent X-Win32 from resetting, thus allowing these applications to start correctly. Alternatively, you can upgrade to the latest version of X-Win32, which does not have this problem.
Category:Applications -> SAS
Category:Applications -> SecLab
Category:Bugs

Solutions