CCR Printer Discovery Service Stopped

[daveyboy1977]

We have an issue with a customer running CCR 9.0.0.189, all was going well for about 30 days and then the Printer Discovery Service decided to stop, all scheduled tasks still exist, but when you click to modify them, or complete the setup, the page times out to a message that the error should be reported to an administrator, and that the error has been logged.

When I look in the diagnostics page, no errors are reported, but when I look in the Windows event viewer I see an event 2016 and an event 4001, both seem to imply username / password issue, but no passwords have been changed.

We have tried running the Printer Discovery Service as a local admin account, as it was originally a Domain account. The customer has no resorted to rebooting the server every night as none of the scheduled task's work, so this is the way they have found to reset wallboard stats short term. Every time the server is reboot the same events appear as the service tries again.

I have looked through quite a few of the posts that seem to be similar to our issue, but so far I have not found a solution.

Has anyone come across this issue? Any help would be gratefully accepted.

Keep up the good work guys, I have always found a lot of useful info on this site, do occasionally try to give a bit back, juts not as frequent as I should

Cheers Dave.

 

[daveyboy1977]

Sorry forgot to include in the above, we have it installed on W2k8 SP2 64 bit.

 

[Okkie26]

Did you installed it via the 'run as administrator' option?

If not then reinstal even is you're logged in as administrator.

 

[daveyboy1977]

Good question Okkie26, I can't recall Did the install before Christmas, lots of booze, food and sleeping was in between install and problem I will look into that, thanks for the pointer.

 

[bob10752000]

Try the below:

Printer Discovery Service Password Change
During IP Office Customer Call Reporter software installation an administrator name and password is requested for use by the IP Office Customer Call Reporter's printer discovery service. If the password for that account is changed, the printer discovery service will not operate. The following process can be used to change the password used by the printer discovery service.



1. On the server computer, open the folder <CCR Installation Directory>\CCRWebClient\CCRPrinterDiscoveryService.
2. Locate and double-click SBCCResetServicePassword.exe.
The SBCC Printer Discovery Password Reset window opens up.
3. Enter the new password that matches the one being used by the administrator account, and click Reset.
4. Click OK.
5. Log in to IP Office Customer Call Reporter as administrator, and restart the Avaya IPOCCR Printer Discovery Service.
6. Log out of IP Office Customer Call Reporter and then log in again.


ACSS (SME)
APSS (SME)

 

[daveyboy1977]

Thanks for the response bob10752000, sorry forgot to mention in my original post I had tried this as I had seen similar posts, the weird thing is with that is that it gets killed as soon as I have tried to run it, also running as Administrator doesn't work for the password reset, beginning to wonder if the whole install needs flattening!

 

[kradangel]

Hi,

I've been having the same problem from CCR version 8 to IP Office Customer Call Reporter 9.0.2.0 Build 1. I always get error "Communications Faulted in Printer Discovery Service".

OS: Windows Server 2008 R2
CCR: IP Office Customer Call Reporter 9.0.2.0 Build 1

Tried below but still not fix.
1. Reinstall CCR using Administrator through Run As Administrator (Many Times, even upgraded CCR version)
2. Change Account to local Administrator of Avaya IPOCCR Printer Discovery and Task Scheduler via Services
3. One thing I can't do as of this time is to run SBCCResetServicePassword.exe to its folder path. I'm getting error
Faulting application name: SBCCResetServicePassword.exe, version: 9.0.2.1, time stamp: 0x529c2ec9
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18229, time stamp: 0x51fb1677
Exception code: 0xe0434f4d
Fault offset: 0x000000000000940d
Faulting process id: 0x%9
Faulting application start time: 0x%10
Faulting application path: %11
Faulting module path: %12
Report Id: %13

I hope somebody could have solution for this. Thanks in advance.

 

[IPGuru]

We have an outstanding bug for Avaya for this
They have a patched version of V9.0.1
we are still waiting for them to implement this in the 9.0.2 release.

A Maintenance contract is essential, not a Luxury.
Do things on the cheap & it will cost you dear

 

[Bas1234]

Is IPv6 disabled?
Clear Evemnt viewer.

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged (Avaya Search tool

http://tinyurl.com/bas1234

)
______________________________________

 

[kradangel]

I hope that they can release those patch ASAP.

 

[robboardman]

I fixed this by adding a localhost entry to the hosts file normally located c:\windows\system\etc
Robb

 

[kradangel]

Hi Robb, Did you put localhost as loopback?

 

[robboardman]

yes its remmed out I think

localhost 127.0.0.1

Robb

 

[IPGuru]

We were provided with V9.0.2.7 last week & so far it seems good
Be aware that dispute this issue being present form at least V9.1 it is still present in the V9.0.3 release



A Maintenance contract is essential, not a Luxury.
Do things on the cheap & it will cost you dear