Eventlog Message: "Logon failed ..." (kb2904)
Le informazioni contenute nel presente articolo riguardano i seguenti prodotti:
- SwyxWare v4.40
This article contains additional information about event log entry:
Failure Audit Source:
12288 (0x3000) Text:
Logon of a client to SwyxServer failed.
User name: %1
Windows account: %2
Error message: %5
Check the SwyxServer user configuration.
If a SwyxIt! user logs on, SwyxServer searches its user database to find a SwyxWare-User If this fails, the above event log message is written. To identify a client SwyxServer uses different mechanisms depending on the client type. For SwyxIt! the windows user account is used, the SwyxWare user must have that user account assigned. For SwyxPhones the PIN or, in case of automatic logon, the MAC address is used.
Depending on the client type some parameter in the event log entry remain empty, e.g. the MAC address is available for SwyxPhone Logons only. The IP-Address is available in all cases.
Check with SwyxWare Administration if there's a SwyxWare user configured and if he has the correct authentication parameters. The following parameter must be configured for the different client types:
|Client||Necessary authentication parameter|
|SwyxPhone||PIN or MAC address (for automatic logon)|
|H.323 Client||H.323 Alias|
|SIP Client||SIP User ID and, if authentication is enabled, the SIP user name and password|
If this eventlog entry is written regularly in short intervals and the windows account is the Swyx service account, it's caused by SwyxConferenceManager which cannot log on. A special SwyxWare account named "Conference" (changeable during installation) is created during installation which has the SwyxWare service account assigned. SwyxConferenceManager logs into SwyxServer with this user. Login fails and produces this event log entry if that user was accidently deleted or has another windows account assigned. SwyxConferenceManager continuously retries to log in. Solution for this case:
- If you don't need Conferencing, stop the SwyxConference Manager service and set it's start type to "Manual"
- If you need Conferencing, check if the SwyxWare Conference-User (named "Conference" per default) is present and has the Swyx Service account assigned. If the account is missing you can recreate it by starting SwyxWare Configuration Wizard (configwiz.exe in SwyxWare program folder). Note: Configuration Wizard will restart all SwyxWare services .