salesforce add in for outlook not working

#Salesforce add in for outlook not working code#

Customer Relationship Management (CRM) and email application, meantime as they are separate, sales rep have needed to move between them. But there seems to be the problem faced by Sales rep daily while sending and replying Email. Note: when I opened my Outlook client after the change - Outlook could not open mailbox (and I thought I screwed the pooch), but close and open and all is well.Īgain thank you for your suggestions, and thank you Doe.Effective Time Management is important to achieve success during the Sales process. JSON token gets delivered correctly now to Salesforce calls and Outlook Plugin is working. Set-AuthConfig -NewCertificateThumbprint (your thumbprint) -NewCertificateEffectiveDate $aĭelete previous maybe invalid cert from Auth Config: I assigned our public valid OWA certificate to the Exchange Auth Configuration: The cause was a missing / invalid Exchange Auth Certificate. I followed the steps (repeated here for others if necessary) Per Mica (and thank you!): As the thread is archived, and the individual who posted only had one post to his 'name' I can not thank the individual directly.Īlthough all the exchange certs were active and valid (checked that pretty early in the process) the Authconfig did not reflect a current thumbprint (which apparently does not matter for 'vanilla' Exchange functionality as everything else from Autodiscover etc was working fine). But I have to say, after going through some 110 various urls - MS - SF - Reddit - other 3rd party add-ons that discuss EWS - I found one article today that resolved it. I had hit I most of them prior to my posting (which was not as exhaustive (or exhausting) of all the work that was done to date). Hi, first thank you again for the comments and suggestions. It blows my mind that this is hard to locate any practical information. I'd appreciate any general guidance or suggestions.

So anyone have any practical guidance to clarify any of the above? If we have to make a specific endpoint for this app, is it really more involved than a few PS commands, or is it as involved as these MS documents that seem aimed at developers make it out to be? So I am wondering if the whitelist is specifically for the endpoint (ie configured with Exchange).

I have focused on a firewall rule, which is completely open for the time being from the range, and there still are issues. SF also has list of IPs which needs to be whitelisted. So I am assuming that a end-point needs to be configured. ' An Exchange metadata endpoint that allows unauthenticated HTTP access must be available' There is no genuine response.īut I keep coming back to this comment in document: So I basically asked SF, other than downloading the app, is ther anything else we need to configure on Exchange. (On a client and OWA) the debug tools reflect blanks in client, and in OWA the debug will not load.) SF gathered some additional data, but said, it looks good.

#Salesforce add in for outlook not working code#

All looks good, except there is a HTTP code of 401. When SF ran some internal tools against the EWS they showed green: meaning the url was fine the SSL cert is fine the level of authentication is solid for their add-on. When I use Remote Connectivity Analyzer to test via autodiscover and/or Exchange Web Services URL they both are successful (related to impersonation). When one enters the url both internally/externally one is prompted for creds and one logs in and is presented with 'you have created a service.to test service svcutil.exe It's internal and external urls are the same: Hopefully someone can fill in the missing pieces for us.Ĭurrent state: EWS is running, and has been. Same for SF documentation/videos.Īs mentioned in SF calls, is basically throw us a bone as to what to look for, and frankly the MS articles forwarded our way are, IMO, too much of a deep dive and seem to be focused on development of apps. Most SF VARs don't have much to share in the implementation with on-prem. I have to admit, within our customer base, EWS end-points are not commonly 'enabled'. SF's support can be summarized as the quoted following: 'Enabling an EWS end-point is a common practice.but if you have questions open an MS support'. Finally have the add-in installed on EAC. Decided to have the Add-on be deployed centrally. Customer wants to integrate SalesForce Add-on. On-Prem - single server Exchange 2016 CU 18 install.