Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
5 years ago

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

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

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

9 Replies

  • Anonymous's avatar
    Anonymous
    Not applicable
    5 years ago

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

     

    Thanks !

  • Anonymous's avatar
    Anonymous
    Not applicable
    5 years ago

     

    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

      • Anonymous's avatar
        Anonymous
        Not applicable
        5 years ago

        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 !

  • Anonymous's avatar
    Anonymous
    Not applicable
    5 years ago

    Hi @  ,

    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 !

  • Anonymous's avatar
    Anonymous
    Not applicable
    5 years ago

    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 !

      • Anonymous's avatar
        Anonymous
        Not applicable
        5 years ago

        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 !