INFO

Eventlog Messages (Overview 1) (kb3051)

Le informazioni contenute nel presente articolo riguardano i seguenti prodotti:

  • SwyxWare v6.20

[ Riepilogo | Informazioni ]


Riepilogo

This article contains an overview of all eventlog entries generated by SwyxWare.

This article (part 1) lists eventlog messages generated from the following sources:

  • ConferenceMgrMsg.dll
  • IpPbxGateMsg.dll
  • HwDSrvMsg.dll
  • IpPbxIMAP4Msg.dll
  • IpPbxSrvMsg.dll

Eventlog messages generated from the following files are listed in an additional article (part 2):

Eventlog messages (Overview 2) (kb3904)

  • IpPbxTTSConnectorMsg.dll
  • LinkMgrMsg.dll
  • PhoneMgrMsg.dll
  • IpPbxCDSServiceMsg.dll
  • IpPbxMemMsg.dll
  • FaxSrvMsg.dll

Informazioni

Source: ConferenceMgrMsg.dll

ID

Text

256

A required parameter (%1) could not be read from the registry. This may be caused by an installation problem.

Reinstall the software.

257

ConferenceMgr service could not register a service request handler. This may be caused by an installation problem. Reinstall the software.

258

ConferenceMgr service could not initialize security.

Service will not start.

259

No SwyxServer is available.
Either the SwyxServer services are down or network problems prevent communication with the SwyxServers.

260

The activation of the service failed.

4096

A registry parameter (%1) contains an invalid value.

A default value is used.

4097

ConferenceMgr service received an unknown service request. The request is ignored.

4098

Registration of ConferenceMgr at SwyxServer (%1) with name (%2) failed.

4099

Lost connection to the active SwyxServer %1.
Either the SwyxServer service is down or network problems prevent communication with the SwyxServer.

4100

Lost connection to the passive SwyxServer %1.
Either the SwyxServer service is down or network problems prevent communication with the SwyxServer.

8192

Process memory dump generated. Process: %1 Dumpfile: %2 DumpType: %3

For further information consult the documentation or have a look at Eventlog Message: "Process memory dump generated" (kb2499)

8704

ConferenceMgr started successfully.

8705

ConferenceMgr stopped successfully.

8706

ConferenceMgr registered at SwyxServer (%1) in with name (%2).

8707

ConferenceMgr unregistered.

8708

ConferenceMgr has lost its registration.

8709

Connected to SwyxServer %1 (%2).

8710

The service is using the Standby Option Pack.

8711

The service is now ACTIVE.

8712

The service is now PASSIVE.

8713

The active SwyxServer is %1.

 

Source: IpPbxGateMsg.dll

ID

Text

11

SwyxGate service could not contact SwyxServer '%1' to read configuration.
The SwyxServer service is not running.

12

SwyxGate service could not contact SwyxServer service to read configuration.
Please check if the SwyxGate service is using a logon account with approbiate rights to access the SwyxWare server.

13

SwyxGate service could not contact SwyxServer '%1' to read configuration.

Error code: %1: %2

14

SwyxGate service could not register line %1 with SwyxServer service.
Check at SwyxServer if there are enough voice channel licenses available for the configured number of channels.

15

SwyxGate service configuration data is invalid.
Check SwyxGate and line configuration data at SwyxWare server '%1'

16

No SwyxServer is available.
Either the SwyxServer services are down or network problems prevent communication with the SwyxServers.

4096

A registry entry (%1) contains an invalid value. A default value is used.

4097

SwyxGate service received an unknown service request. The request is ignored.

4098

The SwyxGate connection for line %1 to SwyxServer was interrupted. SwyxGate tries to reestablish the connection. Please check if SwyxServer is running and the network connection is available.

4099

SwyxGate could NOT reestablish the connection to SwyxWare server %1 SwyxGate tries to contact alternative SwyxWare server %2.

4100

Lost connection to the active SwyxServer %1.
Either the SwyxServer service is down or network problems prevent communication with the SwyxServer.

4101

Lost connection to the passive SwyxServer %1. Either the SwyxServer service is down or network problems prevent communication with the SwyxServer.

8192

Process memory dump generated. Process: %1 Dumpfile: %2 DumpType: %3 For further information consult the documentation or have a look at Eventlog Message: "Process memory dump generated" (kb2499)

8704

SwyxGate started successfully.

8705

SwyxGate stopped successfully.

8706

SwyxGate has established the connection for line %1 to SwyxServer.

8707

Connected to SwyxServer %1 (%2).

8708

The service is using the Standby Option Pack.

8709

The service is now ACTIVE.

8710

The service is now PASSIVE.

8711

The active SwyxServer is %1.

8712

SwyxGate has established the connection for line %1 to alternative SwyxWare server '%2'

 

Source: HwDSrvMsg.dll

ID

Text

256

Process %1 hung and has been terminated. For further information consult the documentation or have a look at Eventlog Message: "Process %1 hung and has been terminated" (kb2265)

512

Error dumping process %1

513

SwyxHelper service could not initialize the security settings. Service will not start.

4096

A registry entry (%1) contains an invalid value. A default value is used.

4097

Process %1 (%2) hangs. Trying to generate a process memory dump and terminating the process after that. For further information consult the documentation or have a look at Eventlog Message: "Process %1 (%2) hangs. Trying to generate a process memory dump and terminating the process after that." (kb2266)

4098

Process %1 (%2) hangs. Trying to terminate it.

8192

Process memory dump generated. Process: %1 Dumpfile: %2 DumpType: %3 For further information consult the documentation or have a look at Eventlog Message: "Process memory dump generated" (kb2499)

8704

HwdSrv started successfully.

8705

HwdSrv stopped successfully.

8706

Logon with Windows account %1 to SwyxHelper failed. The account has no administrative rights. Check the administrator access rights with the SwyxWare Administration.

Source: IpPbxIMAP4Msg.dll

ID

Text

11

The required functions for SSL support could not be imported from the DLL '%1'.

Source: IpPbxSrvMsg.dll

ID

Text

256

Process %1 hung and has been terminated.

512

A required parameter (%1) could not be read from the registry. This may be caused by an installation problem. Reinstall the software.

513

SwyxServer database could not be accessed. Server name: %2 Database name: %1 Database user: %3 Error message: %4 Check the SwyxServer database configuration. For further information consult the documentation or have a look at Eventlog Message: "SwyxServer database could not be accessed..." (kb2283)

514

SwyxServer service could not register a service request handler. This may be caused by an invalid installation. Reinstall the software.

515

SwyxServer could not be started. This program requires Windows 2000 or higher.

516

SwyxServer service could not initialize the H.323 protocol. A common reason may be another application using the well-known H.323 ports (UDP 1719, TCP 1720). For further information consult the documentation or have a look at Eventlog Message: "SwyxServer service could not initialize the H.323 protocol." (kb2361)

517

SwyxServer service could not initialize the security settings. Service will not start.

518

SwyxServer service could not initialize the gatekeeper. Service will not start. Error message: %1

Check the SwyxServer database configuration.

519

SwyxServer service could not initialize the accounting module. Service will not start. Check the SwyxServer configuration.

520

SwyxServer could not send Voicemail. SMTP Server: %1 Recipient: %2 Subject: %3 Check the SwyxServer Voicemail configuration and the SMTP server. For further information consult the documentation or have a look at Eventlog Message: "SwyxServer could not send Voicemail" (kb2372)

521

SwyxServer service could not initialize Visual Basic Scripting. Service will not start.

522

SwyxServer service could not deliver a Voicemail. Recipient: %1 SMTP server message: %2 The E-mail has been saved in %3. For further information consult the documentation or have a look at Eventlog Message: "SwyxServer service could not deliver a Voicemail" (kb2360)

523

SwyxServer service could not save a Voicemail for %1 as file %2.

524

SwyxServer service could not initialize licensing. Service will not start. Check the SwyxServer configuration.

525

SwyxServer service could not start. The following DLL could not be located: %1.

526

SwyxServer service could not verify a script's digital signature. Script cannot be used. Script: %1

527

SwyxServer service could not compress voicemail attachment. Error occured executing: Application: %1 Arguments: %2 ErrorCode: %3 Check the compression codec configuration.

528

SwyxServer service could not decompress audio file. Error occured executing: Application: %1 Arguments: %2 ErrorCode: %3 Check the compression codec configuration.

529

SwyxServer service could not initialize the session initiation protocol (SIP). A common reason may be another application using the well-known SIP ports (TCP/UDP 5060, TCP 5061).

530

Master and Standby SwyxServer have different versions. Master: %1. Standby: %2.

531

Stopping Standby handling because of an error.l

532

Opening the TCP listening port %1 failed with %2

533

No standby server is configured. The server will run in standalone mode.

534

No standby option pack license available. The server will run in standalone mode

4096

A registry parameter (%1) contains an invalid value. A default value is used.

4097

SwyxServer service received an unknown service request. The request is ignored.

4098

SwyxServer could not initialize Music on Hold Manager. Music on hold is not available. For further information consult the documentation or have a look at Eventlog Message: "SwyxServer could not initialize Music on Hold Manager." (kb2367)

4099

One or more phone devices were still registered while SwyxServer was stopping. These devices were probably not running, but didn't log off.

4100

Could not initialize Least Cost Routing module. Least Cost Routing (LCR) will not be available. Please ignore this message, if you've not installed LCR. Otherwise check if the appropriate files are present and have the correct version. Error message: %1. For further information consult the documentation or have a look at Eventlog Message: "Could not initialize Least Cost Routing." (kb2362)

4101

Voicemail will not send any messages because of a missing mail server and/or originating address. Current parameters: SMTP Server:%1 Originating address:%2 Check the SwyxServer Voicemail configuration. For further information consult the documentation or have a look at Eventlog Message: "Voicemail will not send any messages because of a missing mail server and/or originating address" (kb2363)

4102

Could not read file '%1' which is needed for Voicemail to work correctly. Voicemail will probably not work. Check the SwyxServer Voicemail configuration.

4103

SwyxServer does not have a valid user license. No user login allowed. Use the SwyxWare Administration to add a valid SwyxServer license key or SwyxServer user upgrade key. For further information consult the documentation or have a look at Eventlog Message: "SwyxServer does not have a valid user license." (kb2364)

4104

SwyxServer does not have a valid server license but one or more user upgrade licenses. No user login allowed. Use the SwyxWare Administration to add a valid SwyxServer license key. For further information consult the documentation or have a look at Eventlog Message: "SwyxServer does not have a valid server license but one or more user upgrade licenses." (kb2365)

4105

SwyxServer does not have a valid channel license. No SwyxGate login will be allowed. Use the SwyxWare Administration to add a valid channel license key. For further information consult the documentation or have a look at Eventlog Message: "SwyxServer does not have a valid SwyxGate license." (kb2366)

4106

SwyxServer could not add the following license Product: %1 Serial: %2 Count: %3 Error: %4

4107

SwyxServer service could not initialize MAPI. Error: %1 %2 Access to Outlook calendar from Call Routing Manager is not available. Check the SwyxServer configuration and Outlook profile for SwyxServer service account. For further information consult the documentation or have a look at Eventlog Message: "SwyxServer service could not initialize MAPI." (kb2359)

4108

SwyxServer service could not verify a script's digital signature. Default script is used instead. Script: %1 Error: %2 For further information consult the documentation or have a look at Eventlog Message: "SwyxServer service could not verify a script's digital signature." (kb2371)

4109

An unsigned script tried to create an arbitrary COM object. Script has been aborted. Script: %1 Object: %2

4110

The users '%1' script didn't stop as requested and was forced to terminate.

4111

The users '%1' script looped or exceeded CPU time and was forced to terminate.

4112

The users '%1' script hung and was cancled manually.

4113

Could not accessing CDR database. Error: %1 Check the database connection settings in SwyxWare Administration and your database configuration. The CDR text file settings specified in SwyxWare Administration will be used instead.

4114

SwyxServer could not load a script. It contains a serial number restriction and the serial number does not match this server's number. Script: %1

4115

Calender of user '%1' could not be accessed.

4116

TCP port 135 on client with IP-address '%1' could not be accessed. Check if client has a desktop firewall or similar software running. If so, ensure that the port can be accessed from SwyxServer and that SwyxIt! has unlimited network access.

4117

A callrouting script has been terminated or could not be executed due to a script error. Script: %1 Error: %2

4118

SwyxServer could not read the SwyxPhone whitelist. File: %1 Error: %2 Check if the file is present and if SwyxServer service account has read permissions on that file.

4119

SwyxServer could not read SIP provider profiles. File: %1 Error: %2 Check if the file is present and if SwyxServer service account has read permissions on that file.

4120

XML file parsing failed: File: %1 Error: %2 Ensure that the file contents comply to the file's XML schema.

4121

Lost connection to the remote SwyxServer. Either the remote SwyxServer service is down or network problems prevent communication between the SwyxServers.

4122

The remote SwyxServer did not respond in time. Either the SwyxServer or the network is malfunctioning.l

4123

SwyxServer could not select trunk '%1' for a call because there are not enough channel licenses. For further information consult the documentation or have a look at Eventlog message: "SwyxServer could not select trunk..." (kb3834).

8192

Process memory dump generated. Process: %1 Dumpfile: %2 DumpType: %3 For further information consult the documentation or have a look at Eventlog Message: "Process memory dump generated" (kb2499)

8704

SwyxServer started successfully.

8705

SwyxServer stopped successfully.

8706

SwyxServer found dialnumber replacement definition file. %1 replacements loaded. Dialnumber replacement active.

8707

E-mail successfully sent. From: %1 To: %2 Subject: %3 SwyxServer successfully delivered the mail to the configured SMTP mail server (%4).

8708

Call detail records will be written into a database as specified in SwyxWare Administration.

8709

SwyxServer successfully loaded the SwyxPhone whitelist. File: %1

8710

SwyxServer successfully loaded SIP provider profiles. File: %1

8711

The service is using the Standby Option Pack.

8712

The SwyxServer is now the ACTIVE server.

8713

The SwyxServer is now the PASSIVE server. Either the SwyxWare administrator made this SwyxServer the passive server or the server became passive automatically after a temporary network failure.

8714

The SwyxServer is connected to the remote SwyxServer %1.l

12288

Logon with Windows account '%1', IP-Address '%2' to SwyxServer failed. Error message: %3 Check the SwyxServer user configuration. For further information consult the documentation or have a look at Eventlog Message: "Logon with Windows account ..." (kb2270)

12289

User '%1' with Windows account '%2', IP-Address '%3' could not log on to SwyxServer because he is logged in already. It's possible that the user has not logged of correctly before. The SwyxWare Administrator can logoff the user via the SwyxWare Administration.

12290

Logon with Windows account %1 to SwyxServer failed. The account has no administrative rights. Check the administrator access rights with the SwyxWare Administration.

12291

Logon of SwyxWare user '%1' with Windows account '%2', IP-Address '%3' to SwyxServer failed. Account is disabled. Enable the user via the SwyxWare Administration. For further information consult the documentation or have a look at Eventlog Message: "Logon with Windows account ... Account disabled" (kb2271)

12292

User '%1' with Windows account '%2', IP-Address '%3' could not log on to SwyxServer because there's no license available or all licenses are currently in use. Use the SwyxWare Administration to check licenses. You need one user license per logon. Note that special features may need other licenses, too. For further information consult the documentation or have a look at Eventlog message: User ... could not log on to SwyxServer because there's no license available (kb2553)

12293

Logon of SwyxPhone with MAC address '%1', IP-Address '%2' to SwyxServer failed. Error message: %3 Check the SwyxServer user configuration. For further information consult the documentation or have a look at Eventlog Message: "Logon of SwyxPhone ... to SwyxServer failed." (kb2370)

12294

User '%1' from SwyxPhone with network address '%2', IP-Address '%3' could not log on to SwyxServer because he is logged in already. It's possible that the user has not logged of correctly before. The SwyxWare Administrator can logoff the user via the SwyxWare Administration.

12295

Logon from SwyxPhone with network address '%2', IP-Address '%3' to SwyxServer failed. Account is disabled. Enable the user via the SwyxWare Administration.

12296

User '%1' with network address '%2', IP-Address '%3' could not log on to SwyxServer because there's no license available or all licenses are currently in use. Use the SwyxWare Administration to check licenses. You need one user license per logon and one phone license per phone. Note that special features may need other licenses, too. For further information consult the documentation or have a look at Eventlog message: User ... with network address ... could not log on to SwyxServer because there's no license available (kb2554)

12304

Logon of a client to SwyxServer failed. User name: %1 indows account: %2 IP-Address: %3 MAC-Address: %4 Error message: %5 Check the SwyxServer user configuration. For further information consult the documentation or have a look at Eventlog Message: "Logon failed ..." (kb2904)

12305

Logon of SwyxWare user to SwyxServer failed. User name: %1 Windows account: %2 IP-Address: %3 MAC-Address: %4 The user is already logged with the maximum allowed number of devices. For further information consult the documentation or have a look at Eventlog Message: "Logon failed, too many devices..." (kb2905)

12306

Logon with Windows account %1 to SwyxServer failed. The account has no administrative rights. Check the administrator access rights with the SwyxWare Administration.

12307

Logon of SwyxWare user to SwyxServer failed. User name: %1 Windows account: %2 IP-Address: %3 MAC-Address: %4 Account is disabled. Enable it via the SwyxWare Administration. For further information consult the documentation or have a look at Eventlog Message: "Logon failed, Account disabled" (kb2906)

12308

Logon of SwyxWare user to SwyxServer failed. User name: %1 Windows account: %2 IP-Address: %3 MAC-Address: %4 No license are available or all licenses are currently in use. Use the SwyxWare Administration to check licenses. You need one user license per logon. Note that special features may need other licenses, too. For further information consult the documentation or have a look at Eventlog message: User ... could not log on to SwyxServer because there's no license available (kb2907)

 

 


Commento

L'articolo è stato utile? Lasci un commento all'articolo



Come possiamo contattarLa se dal Suo commento dovessero nascere altri quesiti?

Indirizzo e-mail Adresse (facoltativo)


Nota

Il campo destinato ai commenti non è ammesso per richieste all'assistenza. Per quesiti inerenti l'assistenza rivolgersi esclusivamente al proprio rivenditore di fiducia o al distributore competente.