06-29-2007 06:13 AM - edited 07-03-2021 02:16 PM
1. WiSM code 4.1.171. When a user login using a wrong password and failed, WiSM still counts it as a login session. So when the same user try to login from another computer, he may get the error about too many login sessions. I think if the login fails, the WiSM should not count it as a login session.
2. Just upgraded to WCS 4.1.83 on Windows 2003 server. Once log out from the console, the WCS stops. Anyone sees this problem?
Zhenning
08-02-2007 08:53 PM
RE #2. In case you haven't figured this one out yet, it's a bug. Seems WCS gets started as an app instead of service regardless of config. You'll sometime notice when you exit the console (or term svc console) that you briefly see a black dos box screen & then it closes. Then wcs is no longer running. Fixed in later versions supposedly.
08-09-2007 07:13 AM
One of our customers was experiencing the same problem. After upgrading to WCS 4.1.91, the problem appears to be fixed.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: