Does anyone have a list of the sites that the Sharepoint Connector accesses during the connection with Sharepoint? I've been struggling with this for over a month and have been on several calls with Alteryx support and my IT group. At this point, both sides are pointing at each other for next steps.
Here's the stats of what I have:
IT has lifted the following sites in trying to determine where the block is:
Since these look like generic sites, I thought I'd see if anyone else has a list of sites that caused them trouble. Or was there anything else that you did to get it to work?
Hi, I'm in a similar situation as yours except that I'm using 2023.1 Designer and SharePoint connector 2.4.2. I performed all the steps mentioned in your post except the below.
Also, I'm unable to trace the HTTPs traffic trace using Fiddler as my organization needs it to be run as admin to capture the traffic so I'm stuck in a step before Fiddler.
1. Did you find the above step in any documentation? Would you mind sharing the link or steps?
2. Is your issue resolved and are you able to run a workflow successfully by connecting to SharePoint through input or output connectors?
I'm stuck on this issue for few months now and any inputs from your would be of great help. Appreciate in advance.
First, no this is not resolved. I've since submitted a support case with Alteryx. We've been working on it for a while and I don't see a solution in sight.
Many of the steps I mentioned I found in the comments of the SharePoint connector site in community. Some of them were while I was on a call with my IT and Alteryx Support. It *currently* looks like it might be related to how it works with our proxy. Many of the trouble shooting steps, including the Fiddler trace, I've had an IT admin on the phone while performing.
The only work around we've been able to use, is syncing the sharepoint site with OneDrive and accessing it through there. It will only work for files though and not lists.
Some additional steps we've tried:
1. I've tried using the Admin version and non-admin version of Alteryx.
2. Manually setting the proxy address.
3. Using a test proxy.
4. Explicitly disabling WPAD on your machine and see if that forces us to fall back on the PAC script? Instructions for this can be found here:
5. Running designer as administrator
Did you get anywhere with this? I am having the same challenges. There seems to be multiple posts around this but none have a answer and alot refer to server (I am trying first to even just get it to run in designer then will face the server when we get this working)
Any help is much appreciated as am also having back and forth with IT and Alteryx support.
It's now working when I use the latest connector. Alteryx changed the way they connected to SharePoint in the 2.4 version which works better. I haven't attempted to roll this out onto server though.