Forum Discussion
SharePoint Invalid/missing Credentials
No, I have deliberately avoid simultaneous refreshes - and we are a small office, and with refreshes middle of the night - shouldn't be running in conflict with other users. Is there a refresh time limit on sharepoint - possibly a timeout issue - but returning a bogus error message. I should be able to reduce the data download volume, consequently reducing refresh time. Will get back to you tomorrow.
Thank you for responding!
Hey Dellis81 ,
There definitely are SharePoint issues - throttling, time outs and other things and the error message (particularly in the service) always is something a little nebulous that doesn't usually really indicate the problem. Let us know how the test tonight goes!
Hello!
Well, I reduced the data import volume (reduced the initial import dataflow into multiple dataflows) - and after 2 days - appears the reduced workload has helped. The query with unstable refreshes was approximately 1:15 minutes (when working) in duration. Reducing dataflow workload, has reduced the refresh process to around 40 minutes.I have tested refreshing multiple dataflows at the same time - and that also seems to be working. But, I also know in the past - I've had successes for a few weeks- and then something happens.
I am working with 32 bit Access mdb files - and have been told the Service PQ doesn't handle 32 bit files very well. At one time I had the ODBC connector working and it was 2-3x faster. But back on July 12th - that started failing. I need to reengage MS support and see if I can go back to ODBC. Do you have thoughts on best method of connecting to mdb files? I sense working with files on Sharepoint/OneDrive works much better than attempting to pull off a local server w/Gateway.
I appreciate your comments regarding limitations of Sharepoint.thank you!