2 Replies Latest reply on Jul 15, 2011 2:13 AM by CCrossfield

    Incident.rpt - running without supplying password

    Rookie

      We have a pretty standard installation of ServiceDesk 7.32 with Crystal Reports, etc.

      The Incident.rpt works fine, but it requires that a password is supplied to run and we don't really want to give the password to the DB out to everyone.

      I've looked throught the articles here but not had any success.

      Is there a way to embed the connection details in the crystal report so that the password is not required?

        • 1. Re: Incident.rpt - running without supplying password
          masterpetz ITSMMVPGroup

          Hi,

           

          as far as I know, you have to create a db user with the dbreader role. This user needs a blank password.

          In your report use this user to connect to the db . If you then add this report with this user in the servicedesk application, you are not asked for a password again.

          Hope that helps.

           

          Cheers

          Christian

          • 2. Re: Incident.rpt - running without supplying password
            SupportEmployee

            Hi John,

             

            A read only account can be created with no password to run the reports under (recommended in the guide below in ADDENDUM 1 – Create a reporting database login in SQL):

             

            http://community.landesk.com/support/docs/DOC-19090

             

            The other way is to specify the password in the reports configuration in the Crystal Report component.

            If the location of your reports is specified at a network location such as \\drive\share the password does not carry across the network the prompt for the password is shown.

             

            However this works better if you map a drive reports (or use an existing one) such as V:\reports and store the reports in that location. All users accessing the report need to be access to the location. Then set the default path for the reports to the mapped network location.

             

            Calvin

            1 of 1 people found this helpful