Manual Refresh/Refresh Tests:

  • Following a Karmak Update or something similar, you will need to refresh every report. It is quite a tedious process but necessary to ensure there are as few problems as possible come Monday morning.
  • After opening the Apps Home, select Workspaces and start with the first one listed Workspace.


  • You will need to work your way down the list and refresh each of the datasets by clicking the refresh button that pops up when you hover over one of the datasets. You do not need to refresh the reports, just the datasets.

  • After you have refreshed all of the datasets within a workspace, click back on Workspaces and repeat this process for each one. This is an extremely tedious process and if you do not have enough time to do all of them, then focus on Branch Service Premium and both of the Sales workspaces.



Refresh Failures:

  • There are countless reasons as to why a refresh might fail. I will be laying out each of those reasons below but take note that every report will have a refresh fail from time to time, but when you are notified of multiple refresh failures by either different reports or the same report it will be important to know what to look for.


       Reasons for Refresh Failure Listed Most to Least Common

  1. Query Time Out
  2. Karmak Update Recently
  3. Gateway Issue
  4. Query Clogging
  5. Other


            1. Query Time Out

  • This will usually be listed as an "Internal Service Error" if the report this report fails its next refresh, then there is likely a bigger problem related to the query or the gateway. The best way to test this is to go into Power BI and refresh the dataset manually to ensure it does not fail. If it does not fail then there should not be much to worry about, if it does fail then you should look to #3 Gateway Issue to ensure the gateway is set up.


           2. Karmak Update Recently

  • Following Karmak Updates or anything that makes changes to DB02, you could see an uptick in refresh failures for a couple days. This might not be a problem so long as the reports are still able to refresh successfully when doing a manual refresh.


            3. Gateway Issue

  • This is one of the more difficult problems to assess but fortunately it does not come up often. 
    • Step 1: Open the Settings for a Workspace
    • Step 2: Click on the Datasets option
    • Step 3: Expand the Gateway Connection settings and see if there is a connection to GW01 by looking for two green checkmarks circled below.
  • Step 4: If the Maps To section is blank or does not say ProfitMaster, click on the drop down and select Profitmaster. Click apply after that and then retry the refresh.



            4. Query Clogging

  • In SQL, you can use a pre-programmed query to pull active queries that might be clogging the system. Kern Dodds is familiar with this problem and you can refer to him if you think this might be the case.


            5. Other

  • There are countless reasons as to why a refresh failure can happen and covering every single one would not be possible. Before assuming it is another issue check to make sure it is not one of the above issues. If you confirm it is not any of the above, ask Mark Griswold who you can talk to about this problem.