Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
8 years ago
Solved

0x80040e4 error on refresh

Hi all,

 

since yesterday I've got an issue when I'm refreshing my report.

 

Previously it was working fine and without any problems.

It looks to me that the issue is caused on the database side, the generated error message is pointing towards an ticket number.

This ticket is just updated on the moment of the refresh.

 

Does someone have an clue how to solve this?

 

Many thanks!

  • Hi Jorismo, 

     

    The table SLA Violations used to have a unique value for each Ticket Number. For some reason (this could be in the source database) the ticket number in the table SLA Violations is not unique anymore. There are duplicate values. This is a problem in the one side of a one-to-many relationship. Basically it links by the ticket number from a table where ticket number exists multiple times, to the SLA Violation table where it tries to look up the Ticket number and finds more than one row. 

     

    You should look at the source (in edit query or your source system) , figure out why you have a duplicate value, and try to solve it for the future. 

     

    Hope this helps. 

     

3 Replies

  • waltheed's avatar
    waltheed
    Impactful Individual

    Hi Jorismo, 

     

    The table SLA Violations used to have a unique value for each Ticket Number. For some reason (this could be in the source database) the ticket number in the table SLA Violations is not unique anymore. There are duplicate values. This is a problem in the one side of a one-to-many relationship. Basically it links by the ticket number from a table where ticket number exists multiple times, to the SLA Violation table where it tries to look up the Ticket number and finds more than one row. 

     

    You should look at the source (in edit query or your source system) , figure out why you have a duplicate value, and try to solve it for the future. 

     

    Hope this helps. 

     

    • Anonymous's avatar
      Anonymous
      Not applicable

      Ok, I made an adjustment in my query.

       

      Now the ticketnumber is received from the original Ticket_number table.

       

      Problem solved, thanks for your help!

      • waltheed's avatar
        waltheed
        Impactful Individual

        You're welcome. Glad I could help.