I've been running 5.4.3.2007 in production for about a year. Over 500 TRIOs, all connected to exchange without issue.
In our QA environment, I upgraded 3 TRIOs to 5.4.5.9111 and after less than 10 days, the calendar was blank. A simple hard reboot of the TRIO established the exchange connection and populated the calendar. exchange.reconnectOnError is set to 1.
How can I troubleshoot this? Would setting the application log level to debug help my effort?
Is there a known issue with 5.4.5.9111?
Thanks
Sean
Hello Sean,
I suggest you get this into support straight away and maybe in parallel setup a rolling wireshark trace via a spanned port and enable Syslog.
I would probably try Exchange Logs at debug and maybe PGUI.
In order to raise a support ticket you need to work with your Polycom reseller as they need to do this for you.
If this is some sort of an Internet discounter please post either your phone's MAC address or your Polycom devices serial so I can look up who would be able to support you. This may not be who you purchased the Polycom device from.
Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.
Best Regards
Steffen Baier
Polycom Global Services
If official support is required please check how to phone or open a case here
----------------Thanks as always Steffen.
I set Exchange Client to debug, I didnt see PGUI, is that a module?
I'll open up a ticket with support.
Sean
Hi Sean
Settings > Logging > Module Log Level Limits > Presentation > Debug
Regards
Steffen Baier
If official support is required please check how to phone or open a case here
----------------Same issue here, which has cropped up in the 5.4.5 release. We're running .9188 and have 4 devices with the exact same problem.
I'm in the process of opening a ticket. Here are errors happening on all the devices when the problem happens. Rebooting fixes it immediately.
0613033032|pgui |4|00|'ews' Service CSoapTransaction network error = Operation canceled (5) while requesting URL 'https://owa.xxx.xxx/EWS/Exchange.asmx' 0613033032|pgui |4|00|Network error occured 5 0613033032|pgui |4|00| Retrying the subscription with retryCount 1 0613033047|pgui |4|00|Re-syncing calendar events 0613033302|pgui |4|00|CSoapTransaction error = Connection closed (2) 0613033302|pgui |4|00|'ews' Service CSoapTransaction network error = Connection closed (2) while requesting URL 'https://owa.xxx.xxx/EWS/Exchange.asmx' 0613033302|pgui |4|00|Network error occured 2 0613033302|pgui |4|00| Retrying the subscription with retryCount 3 0613033347|pgui |4|00|Re-syncing calendar events 0613033347|pgui |4|00|CSoapTransaction error = Connection closed (2) 0613033347|pgui |4|00|'ews' Service CSoapTransaction network error = Connection closed
Hello philliplyle,
welcome back to the Polycom Community.
Please go ahead and use the above suggested logging levels i.e.:
Settings > Logging > Global Settings > Global Log Level Limit > Debug
Settings > Logging > Log File Upload > Upload Append Size Limit (Kbytes) > 51200
Settings > Logging > Module Log Level Limits > Exchange Client > Debug
Settings > Logging > Module Log Level Limits > Presentation > Debug
Please also post a ticket number for this new issue and update your old issue => here <= with a ticket reference.
Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.
Best Regards
Steffen Baier
Polycom Global Services
If official support is required please check how to phone or open a case here
----------------Quick update:
The calendar information on the TRIOs seems to disappear roughly after a week of connectivity.
I am working with support and we uploaded a configuration file which basically just set the log levels correctly.
Interesting note:
The Exchange connection status on the TRIOs even when the calendar is blank is listed as "connected". Pressing disconnect from server, then pressing connect to server on the TRIO also fixes the issue.
Seems like something gets hungup after a period of time.
Thanks
Sean
I submitted logs with the device in state today.
Case #1-6294427875
Thank you. I have supplied my logs to support as well.
I'll update this post when I hear back.
Thanks
Sean
FYI, my case is 1-6188938060 and its been open for over a month.
I supplied your case # and they are seeing the same errors, so thank you for providing it.
Hoping for answers tomorrow or Monday.
Sean