We have a number of PowerPivots scheduled to refresh every Monday morning at 8am. While in isolation these files will refresh successfully, and in testing even when scheduled together they will typically refresh successfully they are failing regularly on their actual schedule with the following messages:

08/15/2011 08:00:43

08/15/2011 08:00:44

00:00:00

Failed

The data refresh job failed because it did not run within the time period allotted for running this schedule.

The schedule continues to reinstantiate itself and will keep trying to refresh the files until stopped. They will continue to give this error message.

However immediately once we configure a new schedule and tick the "Also refresh as soon as possible" all the files refresh successfully.

Apart from the timer interval (which does not seem relevant) I cannot find any timeout settings that could apply. These files typically refresh in less than a minute when they run successfully.

Any assistance would be appreciated.

Hi Keiran,

 

 

Can you show us the ULS logs for the failures? Also, you are using "Earliest start time" option when  scheduling, right?

 

Thanks,

Mariano

Thanks for getting back to me. I will post the ULS logs soon (most likely early next week). Just need to resolve a small issue with the as well.

Yes - we are using the Earliest Start Time option to schedule.

Thanks

Keiran

 

I am also running into this issue and can't seem to find any resources online to resolve.  Were you able to fix this and how did you do it?

Not yet. Was hoping to post log detail today. Unfortunately once again our logs stopped running over the weekend for no apparent reason. As I find it difficult to reproduce this problem once it is corrected (I tried today but they kept running successfully) I have to wait for tomorrow morning before I have any log detail to look at.

Not yet. I wanted to post the ULS log info today but we are having some issues with the logs as well and once again our logs stopped running over the weekend (for no apparent reason).

I cannot reproduce this issue very easily for some reason. So after trying a couple of times today (in every case they ran successfully) I have rescheduled the refresh for tomorrow morning 8am and have made sure the logs are running. Hopefully I will be able to post the detail at that point.

So its really strange. The schedule ran perfectly again this morning. The problems I have with replicating this issue leads me to believe that the issue is actually related to the time period between refreshes. Generally what happens is they fail on Monday morning. I investigate and try to replicate the problem and cannot. They continue to refresh perfectly after the first time. I eventually give up and leave the files until the following Monday morning when once again they fail. It probably means I can work around the problem by simply refreshing the file on a daily basis.

I will try one more time next week to get the log files.

 

Thanks for the follow up.  I'm moving my scheduled job to run on Mondays as opposed to Sundays at noon.  Hopefully we have some luck.

These seem to be the only relevant lines in the logs. Not much more useful than the error message displayed:

 

09/06/2011 08:00:00.57  w3wp.exe (0x2B88)                        0x6984 SSAS Mid-Tier Service          Data Refresh                   42 Verbose  Found a datarefresh job to run and acquired all the required locks. Examining data sources.. 0082b90c-2ec5-406f-93a2-46efbd42c2cc

09/06/2011 08:00:00.57  w3wp.exe (0x2B88)                        0x6984 SSAS Mid-Tier Service          Data Refresh                   42 Verbose  Job Description: Run Id - 1807, Item - POC TREND EDGARS V5.xlsx, User Identity -   0082b90c-2ec5-406f-93a2-46efbd42c2cc

09/06/2011 08:00:00.57  w3wp.exe (0x2B88)                        0x6984 SSAS Mid-Tier Service          Data Refresh                   99 High     EXCEPTION: Microsoft.AnalysisServices.SharePoint.Integration.DataRefreshException: The data refresh job failed because it did not run within the time period allotted for running this schedule. 0082b90c-2ec5-406f-93a2-46efbd42c2cc

09/06/2011 08:00:00.57  w3wp.exe (0x2B88)                        0x6984 SSAS Mid-Tier Service          Data Refresh                   99 High     EXCEPTION: Microsoft.AnalysisServices.SharePoint.Integration.DataRefreshException: The data refresh job failed because it did not run within the time period allotted for running this schedule.     at Microsoft.AnalysisServices.SharePoint.Integration.DataRefreshService.Execute() 0082b90c-2ec5-406f-93a2-46efbd42c2cc

09/06/2011 08:00:00.57  w3wp.exe (0x2B88)                        0x6984 SSAS Mid-Tier Service          Data Refresh                   42 Verbose  Sending mail on failure to 'EDCON\tacgn1,EDCON\tackra' 0082b90c-2ec5-406f-93a2-46efbd42c2cc

Unfortunately re-scheduling the job didn't fix the issue for me.  Anyone monitoring this thread have a solution?

Hello Keiran_R,

 

Can you confirm the schedule that was used? Was it a run once, or a periodic refresh? If periodic, was it daily, weekly, etc? Did you also mark it to "also refresh as soon as possible"? What was the Credentials used to set its schedule? Does this workbook has many datasources? Please be as specific as possible. It may help us identify the issue faster!

 

Best,

Mariano

Hi Mariano,

Thanks for the help.

The workbooks are scheduled to refresh on a weekly basis every Monday morning at 8am. There are 3 workbooks. They do have 2 or 3 datasources.

When they fail on a Monday morning they continue to retry as long as I allow them to but continue to fail with the same message. To resolve the problem I go into the schedule, check "Also Refresh as Soon as Possible", resave the schedule and then it refreshes successfully.

In a test SITE on the same SERVER I have played with alternate schedules e.g. Daily and I do not have this issue. Even on the same production site if I make the schedule daily or hourly I dont seem able to replicate the issue. It seems to be specific to the weekly option. Obviously I might be able to use a daily schedule to work around the issue although I have not left the refresh running on a daily schedule long enough to be 100% certain the issue wont resurface. I would still like to resolve the problem if anyone has any idea what might be causing it.

We use AD credentials configured as an unattended PowerPivot account for the refreshes but we are very certain this issue is not permissions related. If it were it would not be so specific to the weekly schedule and it would obviously not work at any point.

• Edited by Keiran_R Thursday, September 08, 2011 6:43 AM

We are having the same issue on one specific workbook.  It only has one datasource, a SharePoint list.

Instead of selecting Weekly, select Daily and select a day, e.g. Monday to make it run weekly. Hopefully will solve the problem. Don't ask the reason, obviously something with the service.