Genesys CTI User Forum

Genesys CTI User Forum => Genesys CTI Technical Discussion => Topic started by: Reg on November 30, 2007, 01:41:25 PM

Title: CCPulse Error
Post by: Reg on November 30, 2007, 01:41:25 PM
Has anyone else experienced the following error messages returned from CCPulse running locally or via Citrix?  CCpulse is working fine, but throws up this message:
Connection to the specified configuration server (hostxxxx, portxxxx) cannot be established.  Error Type: CFGConnWriteError.  Check the setting and try again.

Acknoweldging this then returns the same connection error, with Error Type: CFGConnReadError.

The config server error logs do not show disconnection.

Can anyone offer any assistance?
Title: Re: CCPulse Error
Post by: catanirex on November 30, 2007, 02:33:15 PM
Hi,

I would guess that indicates that CCP have lost connection to configserver. Which version of CCP are you using? Have you tried to configure an addp connection to confserv application on CCP application object?
Title: Re: CCPulse Error
Post by: exchelente on December 03, 2007, 02:15:21 PM
Oh yeah, I've seen that!  Install CSProxy and have users connect through that instead of connecting straight to Config Svr.
Title: Re: CCPulse Error
Post by: Daimonas on December 04, 2007, 03:41:33 PM
There is a known issue starting with CCPulse 7.01 where when changes are made via CME, CCPulse clients will receive this error. The reason is because the client is reloading all the configuration from config server for every change and when there is several clients, these requests bog down config server, which causes a delay. Likewise, if you have any delay in your network, you will receive this error.

Genesys has been working to correct this issue or better handle it, hotfix 7.5.000.12 for CCPulse fixed it for us.

Title: Re: CCPulse Error
Post by: mark on December 07, 2007, 01:29:18 PM
Stu,

The 7.5 update should solve this as it brings in a constant connection to confserv, I think I have posted about it on here a few months ago but cannot find it! quite a few people were surprised by it not having this already!

Also, need to find time to have a drink :]

Mark

Title: Re: CCPulse Error
Post by: tony on December 07, 2007, 10:06:27 PM
Sorry to put a downer on things guys - just a note to mention that CCPulse+ 7.5.000.11 is a tad buggy... Unless anyone hasn't noticed that they have changed the default time profile type to hh:mm:ss, from mm:ss and some other standard settings have been changed.

We've had a few issues when running it with Thresholds and Actions too... Actions created in an earlier version ran 5 times over, instead of once and we had to reapply/re-import pretty much everything; Views, Templates, Actions and Thresholds....

- Not bad for one version upgrade by the software supplier, huh...? :(

Anyone else noticed these strange little bugs, or are we on our own with this one?

Tony
Title: Re: CCPulse Error
Post by: mark on December 11, 2007, 02:48:51 PM
Not had the pleasure of 7.5 CCPulse, looks like I am not missing anything though!!
Title: Re: CCPulse Error
Post by: Kevin on December 11, 2007, 04:49:40 PM
Here's one for you.

I created a new template in CC Pulse 7.5  and saved it. When a user running 7.1 opened the workspace with the template, the statistics showed negative values that did not change as the statistics values did.

Of course, it showed properly in 7.5

I had to update the template in 7.1 and resave.
Title: Re: CCPulse Error
Post by: cavagnaro on December 11, 2007, 05:30:42 PM
I have read somewhere on Genesys site that templates made for 7.x are not compatible for 7.5, and viceversa.
Don't understand why but I have also a lot of errors trying to read or open 7.X templates on 7.5 CCPulse, shouldn't be as it is still the same major version, and even if not it's ridiculous to remake all your templates again for a software which is supposed to be an upgrade...it looks more like a downgrade.
Title: Re: CCPulse Error
Post by: unfaced on December 12, 2007, 08:07:13 AM
i can confirm this - templates made in 7.5 are not compatible with former versions and viceversa. but we also recognized this after we did changes in production templates  ::)