Timeline for Could not find stored procedure DataRefresh.GetSchedule error when managing SharePoint 2016 PowerPivot data refresh schedules
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 28, 2018 at 16:39 | comment | added | KevinRF | After about two weeks with numerous remote sessions with Microsoft, the problem still persists. We have given up hope on a resolution. I suspect its a bug in the SharePoint UI+service and unlikely this will be put on anyone's priority list to fix. | |
| Nov 12, 2018 at 22:45 | comment | added | KevinRF | So far the techs are all focused on the warning (the red text in the first screenshot) and not the ULS logs or any of the other data points I've provided. I'm not inspired with confidence right now. | |
| Nov 12, 2018 at 21:37 | comment | added | Mohamed El-Qassas MVP♦ | Actually, it's a strange issue, in the documentation, Microsoft said the stored procedures already removed! I am looking forward to hearing from you after Microsoft reply! | |
| Nov 12, 2018 at 20:13 | comment | added | KevinRF | Ran a SQL Server trace and the SharePoint PowerPivot service is executing the GetSchedule stored procedure, but right after is executing the GetRefreshSchedule stored proc. No errors and if I run the command in SSMS, the data is returned, I assume, as expected. Some sort of bug...oops..undocumented feature in the service/UI? Opened a ticket with Microsoft. | |
| Nov 12, 2018 at 15:15 | comment | added | KevinRF | Thank you for the response. Yes, I've read the article and this is a new SharePoint 2016+PowerPivot environment and able to reproduce the problem with a new Excel document. Our DBAs will not allow a SQL Server 2012 patch on SQL Server 2016 and those stored procedures listed do not exist on the old SharePoint+SQL server backend. I assume the hotfix has already been applied since SharePoint 2013 is working fine. | |
| Nov 9, 2018 at 7:44 | history | answered | Mohamed El-Qassas MVP♦ | CC BY-SA 4.0 |