INFO

Eventlog messages (Overview 2) (kb3904)

The information in this article applies to:

  • SwyxWare v6.20

[ Summary | Information ]


Summary

Here you can find an overview of all event log entries generated by SwyxWare. This article (part 2) lists eventlog messages generated from the following sources:

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

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

Eventlog Messages (Overview 1) (kb3051)

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

Information


Source: IpPbxTTSConnectorMsg.dll

ID

Text

256

Process %1 hung and has been terminated.

512

To use TTS (Text To Speech) at least one TTS channel license is required.

513

The selected Text To Speech engine (%1) could not be loaded.

4096

The TTS (Text To Speech) request was discared because all available TTS channels (%1) are in use.

 

Source: LinkMgrMsg.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

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

514

Service could not initialize the H323 protocol (remote site) using the TCP well known port %1. Check whether this TCP port is already used by another application.

515

Service could not initialize the H323 protocol (local site) using the TCP well known port %1. Check whether this TCP port is already used by another application.

516

Service could not initialize the SIP protocol (remote site) using the TCP/UDP well known ports %1. Check whether these ports are already used by another application.

517

The required well known TCP port (%1) is occupied by another process. Check which process could it be and terminate it.

518

LinkMgr service could not initialize security. Service will not start.

519

LinkMgr service could not read its configuration from PBX server. Service will not start.

520

LinkMgr service could not establish link '%1'.

Check at SwyxServer if there are enough voice channel licenses available for the configured number of channels.

521

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

4096

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

4097

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

4098

Link %1 has been disabled because of an unsupported NAT type (%2).

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

LinkMgr started successfully.

8705

LinkMgr stopped successfully.

8706

Link is established. Link name: %1 Local server: %2 Remote server: %3

8707

Link has been disconnected by local server. Link name: %1 Local server: %2 Remote server: %3 Reason: %4

8708

Link has been disconnected by remote server. Link name: %1 Local server: %2 Remote server: %3 Reason: %4

8709

Link could not register at proxy. Link name: %1 Local server: %2 Remote server: %3 Reason: %4

8710

LinkManager found NAT type %1 using STUN server %2.

8711

Connected to SwyxServer %1 (%2).

8712

The service is using the Standby Option Pack.

8713

The service is now ACTIVE.

8714

The service is now PASSIVE.

8715

The active SwyxServer is %1.

 

Source: PhoneMgrMsg.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

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

258

A required file (%1) could not be found. This looks like an installation problem. Reinstall the software.

259

The required well known TCP port (%1) is occupied by another process.

Check which process could it be and terminate it.

260

PhoneMgr service could not initialize security. Service will not start.

261

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

262

The activation of the service failed.

263

PhoneMgr service found that the administrator configured a firmware update with a firmware version number smaller than the least required one. PhoneType: %1 Least required firmware: %2 The firmware update was skipped.

4096

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

4097

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

4098

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

4099

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

8192

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

8193

PhoneMgr stopped successfully.

8194

Connected to SwyxServer %1 (%2).

8195

The service is using the Standby Option Pack.

8196

The service is now ACTIVE.

8197

The service is now PASSIVEl.

8198

The active SwyxServer is %1.

 

Source: IpPbxCDSServiceMsg.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

Version of the database is incorrect: %1.

258

An error occured during reading profile files. %1.

259

Unspecified error occured: %1.

260

Hosted SwyxWare (%1) could not be registered at the Report and Licensing Service.

261

Accounting of the Hosted SwyxWare (%1) failed.

262

Hosted SwyxWare License is missing.

263

Difference of SwyxServer SystemTime and SQLServer SystemTime exceeds maximum.

264

Sending report to %1 failed.

265

Generation of report for %1 failed.

266

Hosted SwyxWare (%1) could not be registered at the Report and Licensing Service because the database is already used by an active HSW Client registration. Check the database configuration of this Hosted SwyxWare or deactivate the old registration at the Report and License Service.

267

Hosted SwyxWare (%1) could not be registered at the Report and Licensing Service because SwyxWare has been deactivated.

268

The ConfigDataStore was not able to read licenses from server. The error is: %1.

4096

Warning message: %1.

4097

HSWClient "%1" registration failed beacause of missing license.

4098

The database size is reaching the limit of the MS SQL Server Edition.

4099

The time zone setting of the location %1 has been reseted to the current system time zone.

8192

Service started successfully.

8193

Service stopped successfully.

8194

Hosted SwyxWare (%1) has been registered at the Report and Licensing Service.

8195

Hosted SwyxWare (%1) has been accounted successfully.

8196

Registration manager has been initialized.

8197

Accounting has been enabled.

8198

Accounting has been disabled.

8199

Server runs in %1 mode.

8200

Sent report to %1.

8201

HSW Client %1 has been deactivated, because deactivation time has been reached.

8202

HSW Client %1 has been deactivated by Administrator.

8203

Info Message: %1.

12288

Authentication of user '%1' failed.

 

Source: IpPbxMemMsg.dll

ID

Text

11

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

12

The activation of the service failed.

13

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

14

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

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)

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)

 

Source: FaxSrvMsg.dll

ID

Text

21

This copy of SwyxFax has expired. It expired on %1. Some or all of its features have been disabled. %2 Please see the accompanying documentation for information about purchasing SwyxFax.

22

This copy of SwyxFax expires in %1 days on %2, after which it some or all of its features may be disabled. Please see the accompanying documentation for information about purchasing SwyxFax.

23

This copy of SwyxFax has a built-in expiration date. It expires in %1 days on %2, after which it some or all of its features may be disabled. Please see the accompanying documentation for information about purchasing SwyxFax.

24

SwyxFax failed to load the SMTP email delivery component. Therefore fax messages will not be delivered by SMTP email.

25

SwyxFax failed to access the SwyxServer %1 in order to check for installed licenses! The SwyxFax Server service and the SwyxServer service must run under the same (domain) account!.

26

SwyxFax failed to access the SwyxServer %1 in order to check for installed licenses! The SwyxFax Server service and the SwyxServer service must run under the same (domain) account!

27

No SwyxFax licenses have been found on SwyxServer %1 ! Please add your SwyxFax licenses via the SwyxWare Administration.

28

Error reading the PBX attributes from SwyxServer %1.

29

The number of SwyxFax channel licenses found on SwyxServer %1 have been exceeded ! Please add your SwyxFax channel licenses via the SwyxWare Administration.

30

The number of SwyxFax user licenses found on SwyxServer %1 have been exceeded ! Please add your SwyxFax user licenses via the SwyxWare Administration.

31

Unable to open FaxH323.dll ! Please check if you have configured SwyxWare fax user correctly.

32

SwyxFax Server failed to log on to the configured SwyxServer %1, but succeeded to log on to the fallback SwyxServer %2.

33

SwyxFax Server was not able to log on to the configured SwyxServer %1 or fallback SwyxServer %2 within 3 minutes. SwyxFax Server keeps trying to log on to the SwyxServer %1 or fallback SwyxServer %2.

34

The configured SwyxServer %1 rejected SwyxFax Server's logon attempt. This may be caused by missing SwyxFax user/channel licenses.

35

The configured fallback SwyxServer %1 rejected SwyxFax Server's logon attempt. This may be caused by missing SwyxFax user/channel licenses.

36

SwyxFax Server successfully logged on to SwyxServer %1.

37

SwyxFax Server successfully logged on to fallback SwyxServer %1.

38

The configured SwyxServer %1 is of wrong version. You must use SwyxServer of version 6.0 or higher.

39

The configured fallback SwyxServer %1 is of wrong version. You must use SwyxServer of version 6.0 or higher.

104

Telcom Server encountered the error: "%1" while attempting to start the spooler.

105

Error starting the device pool - %1.

106

Error starting the listener thread - %1.

107

Device error - %1 Device: %2.

108

Device error - %1 Device: %2.

256

Unspecified error.

257

Invalid paramater.

258

Insufficient buffer.

259

Error creating temp file.

260

Error deleting temp file.

261

Not enough memory to complete the operation.

262

Error creating or opening a file.

263

Error creating or opening a file.

264

Error creating or opening a file.

512

Invalid job ID.

513

Unknown job ID.

514

Invalid job type..

515

Error getting a new job id.

516

Error creating job.

517

Error adding job to queue.

518

No matching messages.

519

The phone number is empty.

520

The phone number is invalid.

521

There are no pages in this message.

522

Error composing cover page.

523

Error adding attachment.

524

Error deleting attachment.

525

Error scanning the attachments.

526

Error counting pages.

527

The message is not of the type specified.

528

The try limit exceeds the maximum allowed try limit.

768

Invalid device.

769

Unknown device.

1024

Invalid queue.


Comment

Comment on this article



If we have any follow-up questions, where can we contact you?

E-Mail Address (optional)


Note

This feedback form can't be used for support requests. Those requests must be directed to your Swyx reseller or distributor.