N
Nikita Goverdovskiy
Guest
Hello.
My question is: we'v got exchange 2013.
Suddenly nearly all of the buttons in OWA became unusable: you press em and nothing happens.
If you look up in owa page code you'll see:
Application Cache Error event: Manifest fetch failed (440) Outlook
What was all ready done: clear cache, clear canary data (ad).
Now we'v installed exchange 2019 and migrating to it.
OWA is not pointed to old CAS server: only to new exchange server.
In that case OWA version should be:
https://owa.domain.com/owa/prem/15.2.494
But in code i can still see owa 2013 version.
https://owa.domain.com/owa/prem/15.0.1497.2
But none of the clients pointed to 2013!
Same thing with ouutlook anywhere (rpc): none of the cliens are pointed to 2013 but tries to connect to some 15.0.1497.2 service and fails.
RPC itself was broken (for any users outside our local network), but after installing exchange 2019 and pointing all connections to new cas server RPC connection became normal with version 15.2.494.
2 days later it broke again and trying to connect to old version 15.0.1497.2.
Old 2013 cas server is still online but none of the connections pointed to it.
It turned off in load balancer.
So there a 2 main questions: why and how owa is stil in old version (and rpc) and how to force em to use new 15.2 version ?
Sorry for my poor english, and thanks in advance )
Continue reading...
My question is: we'v got exchange 2013.
Suddenly nearly all of the buttons in OWA became unusable: you press em and nothing happens.
If you look up in owa page code you'll see:
Application Cache Error event: Manifest fetch failed (440) Outlook
What was all ready done: clear cache, clear canary data (ad).
Now we'v installed exchange 2019 and migrating to it.
OWA is not pointed to old CAS server: only to new exchange server.
In that case OWA version should be:
https://owa.domain.com/owa/prem/15.2.494
But in code i can still see owa 2013 version.
https://owa.domain.com/owa/prem/15.0.1497.2
But none of the clients pointed to 2013!
Same thing with ouutlook anywhere (rpc): none of the cliens are pointed to 2013 but tries to connect to some 15.0.1497.2 service and fails.
RPC itself was broken (for any users outside our local network), but after installing exchange 2019 and pointing all connections to new cas server RPC connection became normal with version 15.2.494.
2 days later it broke again and trying to connect to old version 15.0.1497.2.
Old 2013 cas server is still online but none of the connections pointed to it.
It turned off in load balancer.
So there a 2 main questions: why and how owa is stil in old version (and rpc) and how to force em to use new 15.2 version ?
Sorry for my poor english, and thanks in advance )
Continue reading...