cancel
Showing results for 
Search instead for 
Did you mean: 

EMC eRoom doesn't work probably after upgrade from 7.1r5 to 7.1r7

Highlighted
Occasional Contributor

EMC eRoom doesn't work probably after upgrade from 7.1r5 to 7.1r7

I'm going to do the rollback soon to test if the software version is to blame but thought that maybe I should ask here also.
Situation is this -
* Using SSL with Mozilla/IE connecting SA2500 SSL VPN

* Problem is with two different EMC eRoom links (different servers/links/etc)
Both eRooms work so far that they get the /eRoomASP/CookieTest but do not go further (I see it in IVE logs)
On the client in the browser only the blank page is presented.

These HTTPS links through SA where working before and they are the same as before.

No configuration with this profile/resource hasn't been changed.

All other links seem to work ok.
The same client (PC/browser) works ok over Pulse connection - using same HTTPS link as with SSL VPN.

Any pointers what might be the problem or where to look?

BR,

Kalev

4 REPLIES 4
Highlighted
Respected Contributor

Re: EMC eRoom doesn't work probably after upgrade from 7.1r5 to 7.1r7

Are you seeing this still being set to rewrite in your policy trace?

Highlighted
Regular Contributor

Re: EMC eRoom doesn't work probably after upgrade from 7.1r5 to 7.1r7

If no configuration has been changed in the backend or on the SA it would be better to open a support case.

Highlighted
Occasional Contributor

Re: EMC eRoom doesn't work probably after upgrade from 7.1r5 to 7.1r7

Hi, I did the rollback and things started to work.

Concerning opening the case - have to think about it because solving the case takes time and these systems are in production. End users can't wait that long.

And I do not have any test systems...

Any recommendation? Smiley Happy

BR,

Kalev

Highlighted
Respected Contributor

Re: EMC eRoom doesn't work probably after upgrade from 7.1r5 to 7.1r7

unfortunately, there is not much that can be done if there is no test system and alternate solutions cannot be implemented while working with JTAC.

one option, depending on how strict your change control policies are, would be to upgrade as-needed to get logs with JTAC (Rewrite troubleshooting and log collection) and then rollback for production use.