Unable to create a new AD Endpoint after CP2

[Daniele Panichi]

Hi guys,

after install CP2 we are unable to create a new AD Endpoint via etautil or provisioning manager for this error:

"eTADSMaxConnectionsInPool not found in attribute registry"

eTADSMaxConnectionsInPool is a new prov dir attribute added by CP2. 
Anyone with the same behaviour?

Thanks

[Bill Patton]

This is for 14.3 CP2 yes?

@Kenneth Verrastro have you seen this yet?

Bill Patton​

------------------------------
And, as always Perhaps there are others in the communities who have experience in doing this and we invite them to comment here also.

Another option may be to reach out to our partner HCL Technologies to see in what way they can assist further. The Enterprise Studio team of HCL can be reached at [e-mail]. https://www.hcltech.com/enterprise-studio
------------------------------

[Daniele Panichi]

Yep, 14.3 CP2

[Kenneth Verrastro]

Was the CP2 only applied to the IM and Provisioning Server?

Be sure that all of the JCS/CCS have been updated with the CP2 and that the Provisioning Repository was also updated with CP2.

Based on the error it sounds like the JCS/CCS were not updated.

[Rashi Parham]

Kenny,

Was this the only thing you did? 
I have reapplied the patches and still getting this error when trying to acquire AD endpoint

[Daniele Panichi]

Hi Rashi,

there is a cache in prov server to clear but I don't remember where.
In the CP2 installation guide this step is described.

[Rashi Parham]

Interesting,,, I don't see any reference to a cache clearing for the provisioning server in the documentation

[Kenneth Verrastro]

I am not aware of what cache is being referred to. Applying the CP2 on the vApp node and also downloading the updated External Windows Connector Server after that and using it to update the Windows machine should be enough. I see you just opened a support case for this and we can review further via that case.

[Rinat Matityahu]

Hi Daniele
Were you able to resolve this error by reapplying CP2?
Thank you
Rinat

[ACCUTECH SA]

I get the same error, trying to create an AD Endpoint. The version is 14.3 CP2, all hotfixes applied and external CS is 14.3. Also I restarted the services and provisioning server and jcs but still the issue persists

Regards
Gerasimos

[Rinat Matityahu]

Hi
Can you please consult https://ca-broadcomcsm.wolkenservicedesk.com/wolken/esd/knowledgebase_search?articleId=202209 and confirm you are seeing the attribute in question (eTADSMaxConnectionsInPool ) for the endpoint?
Thank you
Rinat

[Rinat Matityahu]

My advice would be then to
1. Reapply JCS 14.3 CP2 patch
2. Clear JCS cache (follow resolution notes from https://knowledge.broadcom.com/external/article?articleId=187593)
3. Start JCS and try again

[Rashi Parham]

To fix this you have to re download the External Connector server from the VApp UI after applying the patch. 
Once you download that and re-install, it will fix your issue.

[ACCUTECH SA]

Hi Rashi 

You were right. Downloading and installing the Connector Server after the CP2 patch fixed the issue!
Thank you 
Gerasimos

[Scott Owens]

URL returns 404 error.  See corrected URL below along with solution

https://knowledge.broadcom.com/external/article?articleId=187593

Resolution

- Stop JCS Service
- Delete the following folders
..\Connector Server\Data\activemq
..\Connector Server\data\cache
..\Connector Server\data\derby
..\Connector Server\data\port
..\Connector Server\jcs\data\jdbm\etasa
..\Connector Server\jcs\data\jdbm\SA Configuration
- Start JCS Service

------------------------------
Best regards,

Scott Owens
Sr Support Engineer

------------------------------
And, as always Perhaps there are others in the communities who have experience in doing this and we invite them to comment here also.

Another option may be to reach out to our partner HCL Technologies to see in what way they can assist further. The Enterprise Studio team of HCL can be reached at [e-mail]. https://www.hcltech.com/enterprise-studio
------------------------------
------------------------------

[ACCUTECH SA]

Hi Rinat
I consulted the article and I don't see that attribute for the endpoint!

Regards
Gerasimos