topic Re: Attempted to read or write protected memory.This is often an indication that other memory is corrupt in Report Server

Attempted to read or write protected memory.This is often an indication that other memory is corrupt

Anonymous — Fri, 20 Nov 2020 11:31:43 GMT

Hello ,

Can anyone please check this report's schedule refresh error occured on PBI Report server and let me know your suggestions / solutions to fix this.

We're using On premise Report server ( May'2020 version ) , to match this we're using May'2020 version PBI desktop tool. Thanks !

Regards,

Gopi Krishna J

Re: Attempted to read or write protected memory.This is often an indication that other memory is corrupt

Anonymous — Fri, 20 Nov 2020 11:37:04 GMT

And when we do refresh on PBI desktop tool, it's working fine, but it's getting failed on report server 😞

Thanks !

Re: Attempted to read or write protected memory.This is often an indication that other memory is corrupt

Anonymous — Sun, 22 Nov 2020 15:24:31 GMT

Hi @Petebro ,

I believe, you can help me on this issue. Can you please take a look on my issue once and let me know your suggestions/solution.

Thanks !

-Gopi Krishna J

Re: Attempted to read or write protected memory.This is often an indication that other memory is corrupt

v-xuding-msft — Tue, 24 Nov 2020 06:50:18 GMT

Hi Anonymous ,

Power BI Report Server October 2020 has been released. Please install it and check if it works fine.

Microsoft Power BI Report Server- October 2020

Re: Attempted to read or write protected memory.This is often an indication that other memory is corrupt

Anonymous — Tue, 24 Nov 2020 07:30:07 GMT

Hi @ v-xuding-msft ,

Thank you very much for looking my issue. Sure, we'll plan to upgrade to Oct'20 release and let you know whether this fix my issue or not.

Thanks again !

Re: Attempted to read or write protected memory.This is often an indication that other memory is corrupt

Anonymous — Sun, 17 Jan 2021 12:11:38 GMT

Hi ,

We've upgraded our PBI Reprort server from May'20 version to the latest version (i.e. Oct'20).

And we tried to refresh the same report - Now, we're seeing a different error as shown below :

To fix the above error, we've installed IBM data driver package also, but still issue remains same.

Can you please help us how to overcome this issue.

Thanks !

Re: Attempted to read or write protected memory.This is often an indication that other memory is corrupt

Anonymous — Thu, 04 Feb 2021 14:20:59 GMT

Hi Xue Ding,

Still we're seeing the same error even after PBIRS Oct'20( latest build ) upgrade. I think this is a flaw in in PBIRS.

Can you please help us on this issue.

Thanks !

Re: Attempted to read or write protected memory.This is often an indication that other memory is corrupt

josef78 — Fri, 05 Feb 2021 22:45:56 GMT

Latest October 2020 release is very problematic, related to new Enhanced Metadata Format

Please upgrade to latest January 2021 release (28th January release, not 8th)

https://www.microsoft.com/en-us/download/details.aspx?id=55329

Re: Attempted to read or write protected memory.This is often an indication that other memory is corrupt

Anonymous — Sun, 07 Feb 2021 14:34:07 GMT

Thanks Jose for looking our issue . As you suggested we had upgraded to latest version ( Jan'2020 - 28th), but still the issue remains same.

We've no answer to reply to our users regarding this issue. So, we tried an alternative way to fix this and it worked.

Alternative method is : Actually, this error is occuring only for DB2 data source connected reports.

So, we tried ODBC data source connection instead of DB2 and it worked.

Why it's not working when the report is connected to DB2 even we had installed latest DB2 client drivers.

We request to Microsoft team to look on this and kindly fix it on next release.

Thanks !

Re: Attempted to read or write protected memory.This is often an indication that other memory is corrupt

Anonymous — Wed, 17 Feb 2021 20:56:11 GMT

Hi ,

Can someone please suggest me how to fix this error or is this a bug in power bi report server, please let me know.

Thanks !