locked
Issue with reports on server RRS feed

  • Question

  • User-515277660 posted

    Hi,

    I have a report which works locally. Launching it using the VS server or IIS runs it properly. But the moment I move the report on to the production server, it gives the error 'The report you requested requires further information.'

    It populates all the fields with the corresponding details except for the password.

    Here's the snippet related to what I use:

            CrystalReportViewer1.LogOnInfo[0].ConnectionInfo.ServerName = @"xxxxx";
            CrystalReportViewer1.LogOnInfo[0].ConnectionInfo.UserID = "xxxxx";
            CrystalReportViewer1.LogOnInfo[0].ConnectionInfo.Password = "xxx";
            CrystalReportViewer1.LogOnInfo[0].ConnectionInfo.DatabaseName = "xxx";
            CrystalReportViewer1.LogOnInfo[0].ConnectionInfo.Type = ConnectionInfoType.SQL;

    If I use this, it ends up saying that the login fails. Any help would be appreciated..

      CrystalReportViewer1.EnableDatabaseLogonPrompt = false;
    Thursday, September 29, 2011 3:39 PM

Answers

  • User-515277660 posted

    The issue was because of configuring the DB to use a specific port. That had to be included in the connectioninfo along with the other parameters

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Wednesday, October 5, 2011 12:57 PM

All replies

  • User1196771204 posted

    hi headbuz,

    please refer to the following article:

    - http://stackoverflow.com/questions/1186048/crystal-reports-the-report-you-requested-requires-further-information
    - http://forums.asp.net/t/1026635.aspx/1

    Please mark this response as an "answer" if it helps you. Thank you!

    :-) 

    Thursday, September 29, 2011 11:07 PM
  • User-102500655 posted

    try this

      ConnectionInfo connectionInfo = new ConnectionInfo();

                    SqlConnectionStringBuilder conStr = new SqlConnectionStringBuilder(ConfigurationManager.ConnectionStrings["DBConnString"].ConnectionString);
                    rpt.SetDatabaseLogon(conStr.UserID, conStr.Password, conStr.DataSource, conStr.InitialCatalog, false);
                    rpt.DataSourceConnections[0].SetConnection(conStr.DataSource, conStr.InitialCatalog, false);
                    rpt.DataSourceConnections[0].SetLogon(conStr.UserID, conStr.Password);
              
    here ["DBConnString"] Is from webconfig

    store in web config like this if you dont want to hard code

         <add name="DBConnString" connectionString="Data Source="nameof datasource";Initial Catalog=datadasename;User ID=techdev; Password=dev; Integrated Security=False"


    Tuesday, October 4, 2011 3:30 AM
  • User-515277660 posted

    try this

      ConnectionInfo connectionInfo = new ConnectionInfo();

                    SqlConnectionStringBuilder conStr = new SqlConnectionStringBuilder(ConfigurationManager.ConnectionStrings["DBConnString"].ConnectionString);
                    rpt.SetDatabaseLogon(conStr.UserID, conStr.Password, conStr.DataSource, conStr.InitialCatalog, false);
                    rpt.DataSourceConnections[0].SetConnection(conStr.DataSource, conStr.InitialCatalog, false);
                    rpt.DataSourceConnections[0].SetLogon(conStr.UserID, conStr.Password);
              
    here ["DBConnString"] Is from webconfig

    store in web config like this if you dont want to hard code

         <add name="DBConnString" connectionString="Data Source="nameof datasource";Initial Catalog=datadasename;User ID=techdev; Password=dev; Integrated Security=False"


    This has the same issue. It works fine on the local development machine but not on the server.

    Tuesday, October 4, 2011 10:23 AM
  • User1196771204 posted

    hi headbuzz,

    how do you host your crystal report? Is that on a shared server? Have you contacted your host with regards to this issue? 

    Tuesday, October 4, 2011 9:51 PM
  • User-515277660 posted

    It's just a part of our application-not on a shared server. We recently moved from an old server to 2008 R2. Since then we are having this issue.

    We tried installing CR 10.2 ( the version it's built on with .Net 2.0). Still no luck!

    Tuesday, October 4, 2011 10:20 PM
  • User-515277660 posted

    The issue was because of configuring the DB to use a specific port. That had to be included in the connectioninfo along with the other parameters

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Wednesday, October 5, 2011 12:57 PM