Could not find the report with id 93254. - error when exporting

Jared Holtgrewe ●

Hi Mpumi,

Thanks for reaching out with this.

If we have a reportID that we are looking for we can use it to reference the ReportHeader Table within the configuration database. This table holds report information and will give us the name of the report causing the error. A query similar to this should give you the name of the report.

Select * From ReportHeader where reportid= 93254;

With the information I have on the issue (not much) I wouldn't recommend deleting the report via querying the configuration database and should note here that when running any queries directly against the Yellowfin Configuration Database it's possible to cause irrevocable data loss. This process isn't directly supported nor recommended unless otherwise advised to do so. Before running any queries against your Yellowfin Configuration Database, please make sure you have full, up-to-date backups of both your Yellowfin Configuration Database and your Yellowfin Installation folder. This way, if something goes wrong you can revert back to your current state.

Please let me know if this information helps.

Thanks,

Jared

Hi Mpumi,

Thanks for reaching out with this.

If we have a reportID that we are looking for we can use it to reference the ReportHeader Table within the configuration database. This table holds report information and will give us the name of the report causing the error. A query similar to this should give you the name of the report.

Select * From ReportHeader where reportid= 93254;

With the information I have on the issue (not much) I wouldn't recommend deleting the report via querying the configuration database and should note here that when running any queries directly against the Yellowfin Configuration Database it's possible to cause irrevocable data loss. This process isn't directly supported nor recommended unless otherwise advised to do so. Before running any queries against your Yellowfin Configuration Database, please make sure you have full, up-to-date backups of both your Yellowfin Configuration Database and your Yellowfin Installation folder. This way, if something goes wrong you can revert back to your current state.

Please let me know if this information helps.

Thanks,

Jared

1

Jared Holtgrewe ● ●

Hi Mpumi,

Thanks for reaching out with this.

If we have a reportID that we are looking for we can use it to reference the ReportHeader Table within the configuration database. This table holds report information and will give us the name of the report causing the error. A query similar to this should give you the name of the report.

Select * From ReportHeader where reportid= 93254;

With the information I have on the issue (not much) I wouldn't recommend deleting the report via querying the configuration database and should note here that when running any queries directly against the Yellowfin Configuration Database it's possible to cause irrevocable data loss. This process isn't directly supported nor recommended unless otherwise advised to do so. Before running any queries against your Yellowfin Configuration Database, please make sure you have full, up-to-date backups of both your Yellowfin Configuration Database and your Yellowfin Installation folder. This way, if something goes wrong you can revert back to your current state.

Please let me know if this information helps.

Thanks,

Jared

Hi Mpumi,

Thanks for reaching out with this.

If we have a reportID that we are looking for we can use it to reference the ReportHeader Table within the configuration database. This table holds report information and will give us the name of the report causing the error. A query similar to this should give you the name of the report.

Select * From ReportHeader where reportid= 93254;

With the information I have on the issue (not much) I wouldn't recommend deleting the report via querying the configuration database and should note here that when running any queries directly against the Yellowfin Configuration Database it's possible to cause irrevocable data loss. This process isn't directly supported nor recommended unless otherwise advised to do so. Before running any queries against your Yellowfin Configuration Database, please make sure you have full, up-to-date backups of both your Yellowfin Configuration Database and your Yellowfin Installation folder. This way, if something goes wrong you can revert back to your current state.

Please let me know if this information helps.

Thanks,

Jared

Reply URL

1

Mpumelelo Tsabedze ●

Thanks - certainly helped....

URL

1

Jared Holtgrewe ●

Hi Mpumi,

Glad to hear the information was helpful.

Please let me know if you have any other questions regarding this or if you feel its alright to mark this question as answered.

Regards,

Jared

URL

1

Mpumelelo Tsabedze ●

Hi Jared,

Please proceed to mark as answered

Thanks again

Regards,

URL

Could not find the report with id 93254. - error when exporting

Replies (1)