none
Can't Delete Encrypted Content: Microsoft.ReportingServices.WmiProvider.WMIProviderException: Value cannot be null. RRS feed

  • Question

  • I'm having servere issues with our SSRS. We decided today to change our Admin password over the weekend, this has have the effect of locking me out of our SSRS. Unfortunately we don't have a backup of the Encryption keys either.....

    So i'm resigned to deleting all encrypted content. however that isn't working either, i get the following message whatever i try to do.

    Microsoft.ReportingServices.WmiProvider.WMIProviderException: Value cannot be null.
    Parameter name: key
       at Microsoft.ReportingServices.WmiProvider.RSWmiAdmin.ThrowOnError(ManagementBaseObject mo)
       at Microsoft.ReportingServices.WmiProvider.RSWmiAdmin.DeleteEncryptedInformation()
       at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.DeleteEncryptedInformation()

    I have tried the fixes in the following thread, none of these have worked. I have also deleted the key directly from the ReportServer database following this thread that didn't work either. I really don't want to create a new ReportServer instance, however i fear i'm heading that way.

    Anyone have anything else i could try?

    Many Thanks

    Scotty.

    Monday, March 18, 2013 2:20 PM

Answers

  • Hi Scotty,

    To delete the keys from the catalog database, please use the following script instead:

    use ReportServer
    go
    --- run below query to get the instance name for your report server
    select InstanceName from Keys
    go
    --- replace the instance_name to the one you get from above query
    delete from keys where InstanceName='INSTANCE_NAME'
    go 

    If it doesn't work, are you able to change the password of the Reporting Services Service Account back to the previous one? If so, you can resolve the issue easily by using the following steps:

    1. Reset the password of the service account to be the previous one.
    2. In the services snap-in, reset the log on account of the SQL Server Reporting Services service using the modified password. Restart the Reporting Services service.
    3. Open the Reporting Services Configuration Manager, verify that the report server works well.
    4. Reset the password of the service account to be expected one.
    5. Open the Reporting Services Configuration Manager, and update the password.
    6. Back up the Encryption Keys.

    Hope this helps.

    Regards,
    Mike Yin

    If you have any feedback on our support, please click here


    Mike Yin
    TechNet Community Support

    • Marked as answer by scotty_uk Tuesday, March 19, 2013 11:16 AM
    Tuesday, March 19, 2013 10:14 AM
    Moderator

All replies

  •   Sorry to bump this thread, things are getting desperate.

    I really want to avoid creating a new instance and starting from scratch.

    Any help would be greatly appreciated!

    Scotty

    Tuesday, March 19, 2013 9:46 AM
  • Hi Scotty,

    To delete the keys from the catalog database, please use the following script instead:

    use ReportServer
    go
    --- run below query to get the instance name for your report server
    select InstanceName from Keys
    go
    --- replace the instance_name to the one you get from above query
    delete from keys where InstanceName='INSTANCE_NAME'
    go 

    If it doesn't work, are you able to change the password of the Reporting Services Service Account back to the previous one? If so, you can resolve the issue easily by using the following steps:

    1. Reset the password of the service account to be the previous one.
    2. In the services snap-in, reset the log on account of the SQL Server Reporting Services service using the modified password. Restart the Reporting Services service.
    3. Open the Reporting Services Configuration Manager, verify that the report server works well.
    4. Reset the password of the service account to be expected one.
    5. Open the Reporting Services Configuration Manager, and update the password.
    6. Back up the Encryption Keys.

    Hope this helps.

    Regards,
    Mike Yin

    If you have any feedback on our support, please click here


    Mike Yin
    TechNet Community Support

    • Marked as answer by scotty_uk Tuesday, March 19, 2013 11:16 AM
    Tuesday, March 19, 2013 10:14 AM
    Moderator
  • Thanks Mike, that seems to have done the trick.

    I've had to delete my datasources from SSRS and then re-deploy them, and then attach my reports again but that's better than starting from scratch.

    Lesson learned....."Back up the Encription Keys!"

    Thanks Again.

    Scotty.

    Tuesday, March 19, 2013 10:48 AM
  • Thanks very much. After going through so many help sites at last this worked.

    Regards,

    Sudhir

    Friday, March 6, 2015 8:14 AM
  • Thanks for the above solution...It really Works like a charm :)

    Friday, January 5, 2018 10:36 PM
  • It is work for me

    Thank you!

    Wednesday, April 3, 2019 3:55 PM