Troubleshooting the strangest symptom

  • I've worked with SSRS for many years, but I have a real head scratcher.
    Reports use a shared datasource the datasource happens to be an oracle connection and it depends on an Oracle wallet for SSL certificate. Admins, are able to test data source connections successfully.
    There is an execution account set in RSCM.
    This is where it gets weird.
    The reports will render if and only if the execution account has an active desktop session on the SSRS server.
    So, execution account user logs into the SSRS server to start a desktop session. Then from any other system on the network, any user (who has permission to access SSRS) is able to run the reports and the reports pull data from their Oracle sources as expected.
    Once the execution account's desktop session is terminated, either by it logging out, or being killed, The reports fail with the following error: Network Transport: SSL failure in parsing wallet location.
    The SSRS SPN is properly registered and the service account correct.
    Anyone have any ideas? I'm happy to provide any more info. We've been fighting with this for several weeks now.

  • More info, this is SSRS 2016.

  • Another twist is disabling the execution account, or rather removing it from the configuration, and reports run fine.

  • Yuri Padorin - Thursday, May 17, 2018 12:04 PM

    Another twist is disabling the execution account, or rather removing it from the configuration, and reports run fine.

    That account, by logging off, has got to be doing something to the wallet that otherwise does not occur.   But at least you fixed the problem.  Might not feel real good, but fixed is fixed.

    Steve (aka sgmunson) 🙂 🙂 🙂
    Rent Servers for Income (picks and shovels strategy)

  • Well, not so much fixed, because the account is needed to authenticate to some web service data sources. But the behaviour suggests to me that SSRS is getting it's Oracle provider config. info from the registry. so maybe I can put it in the machine.config instead.

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply