Timeline for Because SDL Web could not connect to the notification system, it cannot receive push notifications
Current License: CC BY-SA 3.0
12 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Aug 27, 2017 at 0:14 | vote | accept | Sudhakar Rao | ||
Aug 25, 2017 at 23:47 | answer | added | Velmurugan♦ | timeline score: 3 | |
Jul 7, 2017 at 3:29 | comment | added | Sudhakar Rao | Issue resolved and working perfectly now. | |
Jul 6, 2017 at 3:18 | comment | added | Chris Summers | @Sudhakar - Did you ever solve this, I am having a similar issue when I enable our SSO modules for the CME | |
Mar 17, 2017 at 9:43 | comment | added | Peter Kjaer | It's indeed possible that Site Minder is interfering and returning a different response. You should be able to see that using a network monitoring tool such as Wireshark. | |
Mar 17, 2017 at 6:05 | history | tweeted | twitter.com/StackTridion/status/842617746118643714 | ||
Mar 16, 2017 at 22:15 | comment | added | Warner Soditus | you should mention this is a server with Site Minder protection and none of the other servers have it :) | |
Mar 16, 2017 at 17:35 | history | edited | Sudhakar Rao | CC BY-SA 3.0 |
added 2418 characters in body
|
Mar 16, 2017 at 17:34 | comment | added | Sudhakar Rao | When I open CME got this error: | |
Mar 16, 2017 at 7:33 | comment | added | Sudhakar Rao | it`s working fine in three development server and one SIT server. I check tomorrow morning once second again!!! | |
Mar 16, 2017 at 0:59 | comment | added | Nickoli Roussakov | My guess is that you have a firewall policy that is blocking the port on the which the notifications are communicated. | |
Mar 15, 2017 at 23:14 | history | asked | Sudhakar Rao | CC BY-SA 3.0 |