Anonymous Calendar Sharing URL in Exchange is not working between Exchange 2016/2019 coexistence

%3CLINGO-SUB%20id%3D%22lingo-sub-2818656%22%20slang%3D%22en-US%22%3EAnonymous%20Calendar%20Sharing%20URL%20in%20Exchange%20is%20not%20working%20between%20Exchange%202016%2F2019%20coexistence%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2818656%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20guys%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3E(Scenery)%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%204%20Exchange%20Servers%202016%20CU22%20Frontend%3B%20%3CSTRONG%3E%3CU%3E%3CEM%3EOnly%20CAS%20Function%20%7C%20CAS%20Role%3C%2FEM%3E%3C%2FU%3E%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%3EI%20have%206%26nbsp%3BExchange%20Servers%202019%20CU9%20Backend%3B%26nbsp%3B%3CSTRONG%3E%3CEM%3E%3CU%3EOnly%20MBX%20Function%20%7C%20MBX%20Role%3C%2FU%3E%3C%2FEM%3E%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSTRONG%3E(Flow)%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EInternet%3C%2FSTRONG%3E%26nbsp%3B%3D%3D%26gt%3B%20%3CSTRONG%3EHLB%20(Hardware%20Load%20Balancer)%3C%2FSTRONG%3E%20%3D%3D%26gt%3B%20%3CSTRONG%3ECAS%3C%2FSTRONG%3E%26nbsp%3B%3D%3D%26gt%3B%20%3CSTRONG%3EMBX%3CBR%20%2F%3E%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EPS%3A%20%3C%2FSTRONG%3EExchange%20Server%202016%20CU22%20is%20kept%20as%20CAS%20Role%20to%20maintain%20compatibility%20with%20older%20email%20clients.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAll%20users%20when%20accessing%20shared%20calendar%20settings%20get%20this%20error%20%26lt%3B%3CSTRONG%3EHTTP%20ERROR%20500%3C%2FSTRONG%3E%26gt%3B%20below%20using%20Exchange%20Server%202016%20CU22%20with%20proxy%20function.%3CBR%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22HTTP%20ERROR%20500.PNG%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F315655iC4E4996F5C83322D%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22HTTP%20ERROR%20500.PNG%22%20alt%3D%22HTTP%20ERROR%20500.PNG%22%20%2F%3E%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSTRONG%3E%3CBR%20%2F%3E%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3EBut.%20if%20i%26nbsp%3Baccess%20directly%20through%20an%26nbsp%3BExchange%20Server%202019%20CU9%2C%20the%20feature%20works%20perfectly.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22HTTP%20ERROR%20500_OK.PNG%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F315661i719FE4A63C20AE08%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22HTTP%20ERROR%20500_OK.PNG%22%20alt%3D%22HTTP%20ERROR%20500_OK.PNG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFollow%20the%20configuration%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Capturar.PNG%22%20style%3D%22width%3A%20714px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F315659iBE10C33E86485EDE%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22Capturar.PNG%22%20alt%3D%22Capturar.PNG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Capturar.PNG%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F315660i3FCEF66954E13416%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22Capturar.PNG%22%20alt%3D%22Capturar.PNG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20ideas%20guys%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ET%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2818656%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Ecalendar%20sharing%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
New Contributor

Hi guys,

 

(Scenery)

 

I have 4 Exchange Servers 2016 CU22 Frontend; Only CAS Function | CAS Role

I have 6 Exchange Servers 2019 CU9 Backend; Only MBX Function | MBX Role

(Flow)

 

Internet ==> HLB (Hardware Load Balancer) ==> CAS ==> MBX

 

PS: Exchange Server 2016 CU22 is kept as CAS Role to maintain compatibility with older email clients.

 

All users when accessing shared calendar settings get this error <HTTP ERROR 500> below using Exchange Server 2016 CU22 with proxy function.
HTTP ERROR 500.PNG

But. if i access directly through an Exchange Server 2019 CU9, the feature works perfectly.

 

HTTP ERROR 500_OK.PNG

 

Follow the configuration:

 

Capturar.PNG

 

Capturar.PNG

 

Any ideas guys?

 

T

0 Replies