ICD Problem

[adignan]

I am having problems with ICD starting correctly. When I boot the server (which has CallManager,IPIVR, and ICD on it). The IPIVR subsystems are "in service". If I stop and start the engine, it just says unavailable. When I go to the event viewer I get a ton of DC Directory errors that say "An LDAP client has issued a request specifying acontrol which is not supported" I am at a loss. Thanks

[rokibbe]

Check to ensure that the JTAPI plugin is installed, and that the credentials setup for your JTAPI user are correct.

[adignan]

Yes, JTAPI plugin is installed, and the credentials for the JTAPI users is correct. I just get this stupid error on the callmanager ""An LDAP client has issued a request specifying a control which is not supported" I am still at a loss. Thanks

[tmckeon]

Here's a suggestion from an engineer knowledgeable with IP ICD:

"Sounds like there is probably a port contention problem with the RMI Port

number on the Admin Engine Configure page. The default is 1099,

have them try changing it to 1098 then restart the Apps engine."

If this doesn't work contact me.

[csteyn]

Good Day all

We have the exact same problem and can not seem to solve this .We have tried changing the RMI port but then the Application engine stays unavailable any other suggestions .

I include the error as it appears in the eventlog .DSA DSA LDAP(43) Proc 1540, Sev 12)

An LDAP client has issued a request specifying a control which is

not supported.

From remote address: 10.7.242.221

On Connection ID: 142

Name of control: 2.16.840.1.113730.3.4.2

Was control critical: False

DN of client: 2.16.840.1.113730.3.4.2

[adignan]

Could make sense because we do have 2 app engines running (one for conferencing) so changing that might help, i will change that. I really appreciate the help, this is getting frustrating.

[adignan]

Tried chaning the RMI port number, but it didn't work here is some trace and event viewer info that might help?

Event Viewer message on call manager:

Event Type: Information

Event Source: DCDirectory

Event Category: Software Error

Event ID: 7419

Date: 2/27/2002

Time: 4:24:57 PM

User: N/A

Computer: CMIPCCDEMO2

Description:

(DSA DSA LDAP(48) Proc 1540, Sev 12)

An LDAP client has issued a request specifying a

control which is

not supported.

From remote address: 192.168.99.82

On Connection ID: 127

Name of control: 2.16.840.1.113730.3.4.2

Was control critical: False

DN of client: 2.16.840.1.113730.3.4.2

App Engine Event Viewer Output:

Event Type: Information

Event Source: Cisco Application Engine

Event Category: None

Event ID: 0

Date: 2/27/2002

Time: 4:35:44 PM

User: N/A

Computer: EBC_DEMO2

Description:

The description for Event ID ( 0 ) in Source ( Cisco Application Engine ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: Service started.

Event Type: Information

Event Source: Cisco Application Engine

Event Category: None

Event ID: 0

Date: 2/27/2002

Time: 4:35:43 PM

User: N/A

Computer: EBC_DEMO2

Description:

The description for Event ID ( 0 ) in Source ( Cisco Application Engine ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: RegQueryValueEx failed: Overlapped I/O operation is in progress.

App Engine Trace File:

0: Feb 27 16:30:18.625 PST %MIVR-ENG-6-UNK:Cisco Application Engine Service starting...

1: Feb 27 16:30:18.640 PST %MIVR-ENG-6-UNK:Cisco Application Engine Service started

2: Feb 27 16:30:18.640 PST %MIVR-ENG-6-UNK:Cisco Application Engine Domain: Cisco Workflow CCN Domain

3: Feb 27 16:30:18.656 PST %MIVR-ENG-6-UNK:Workflow RT Container set

4: Feb 27 16:30:18.671 PST %MIVR-ENG-6-UNK:Workflow Manager initialized

5: Feb 27 16:30:18.750 PST %MIVR-ENG-6-UNK:RMI Manager initialized

6: Feb 27 16:30:18.781 PST %MIVR-ENG-6-UNK:Realtime Data Manager started

7: Feb 27 16:30:18.781 PST %MIVR-ENG-6-UNK:Historical Reporting Manager initialized

8: Feb 27 16:30:18.812 PST %MIVR-SS_DB-6-UNK: Initializing EDBS Subsystem

9: Feb 27 16:30:18.812 PST %MIVR-SS_DB-6-UNK:Microsoft JDBC Driver Open Success

10: Feb 27 16:30:19.109 PST %MIVR-SS_DB-5-UNK: No DSNs configured

11: Feb 27 16:30:19.250 PST %MIVR-SS_TEL-6-UNK:JTAPI Login Str: 192.168.99.81;login=jtapiuser2;passwd=cisco

12: Feb 27 16:30:19.390 PST %MIVR-SS_TEL-6-UNK:Starting CTI Port recovery thread...

13: Feb 27 16:30:20.093 PST %MIVR-SS_RMCM-6-UNK:rmcm initializing

14: Feb 27 16:30:20.531 PST %MIVR-SS_RM-6-UNK:RM Jtapi Login Str: 192.168.99.81;login=icduser;passwd=cisco

15: Feb 27 16:30:20.531 PST %MIVR-ENG-6-UNK:Subsystems started

16: Feb 27 16:30:20.531 PST %MIVR-ENG-6-UNK:Cisco Application Engine ready

17: Feb 27 16:30:21.218 PST %MIVR-SS_TEL-4-UNK:JTAPI Exception while trying to initialize JTAPI provider: javax.telephony.PlatformException: java.net.ConnectException: Connection refused

18: Feb 27 16:30:21.546 PST %MIVR-SS_RM-4-UNK:JTAPI Exception while trying to initialize JTAPI provider: javax.telephony.PlatformException: java.net.ConnectException: Connection refused

[rkiamil]

Dear A,

Could u mail me rif.kiamil@jjfastfood.com