Apache OpenOffice (AOO) Bugzilla – Issue 80874
IZ-CRM connection problems
Last modified: 2017-05-20 10:27:48 UTC
New error after adding comment to issue: 500 SSL negotiation failed: at CRMConnector.pm line 58
Also filing issues is *SLOW* right now.
reassign to support, IZ is dead slow in producing that error.
Screenshots of error at http://tmp.janik.cz/OpenOffice.org/80874/ I won't add them here, because it is much faster to add *one* link than *two* screenshots.
We have started investigating on this issue.
Initial investigation points to the CRM - IZ connector .
The IZ is working fine presently. Also left a voice mail informing Martin H the same . This particular error was thrown due to the connection getting dropped between the Salesforce CRM and the IZ. More updates to follow.
Bringing down the priority of the issue .
We have received information that Salesforce has been making some changes/adding some more features in their system as part of an upgrade . We are assuming this could be reasons for the anomalies noticed previously . However we are continuing our investigation on our end to identify the actual reason for the said behavior.
*** Issue 80948 has been marked as a duplicate of this issue. ***
Modifying the Summary based on the actual problem noticed by the users.
*** Issue 80973 has been marked as a duplicate of this issue. ***
Support, can you merely suppress the CRM error message? it's valueless to the community but is distracting. Thanks louis
Louis, As we speak one of our engineers has come with a patch which would suppress these error messages from been show to the users. We would first like to test this patch on the stage box to identify and make sure there are no other regression via this fix.
thanks! louis
.
While testing noticed that the CRM error is not thrown anymore while submitting any content to this issue. However we would be combining the fix to suppress the CRM error message along with the next upcoming patch release to make sure that the community users are put into task. Moving this issue to Resolved Later .
Reopening this issue
The patch has been applied with the above fix . Moving this issue to the Resolved Later queue
Actually marking as Resolved Fixed