Last post May 09, 2012 04:25 PM by rfreedlund
May 08, 2012 05:44 PM|rfreedlund|LINK
I created a web app that has been working just fine for a year now when accessing a SQL Server 2005 install on Windows Server 2003. The app was created with Visual Studio 2008.
We want to retire the older server so I transferred the database to a SQL Server 2008 install on Windows Server 2008.
I updated the code to point to the new server and locally it works just fine and I have verified that I am accessing the new server. However, when I transfer the updated code to the IIS server, I get
the infamous The report you requested requires further information problem. I used to receive this error on my original app, but resolved it by passing the database info in through code (accompanying below).
I also rebuilt the reports used to have them point to the new server. Once again, this works fine locally.
Any suggestions as to why it works fine pointing to SQL Server 2005 on Windows Server 2003, but won't let me continue with SQL Server 2008 on Windows Server 2008? Even if I enter the username and password at the prompt that comes up requiring more information,
the app won't continue.
The code that I use to pass the Crystal report it's information follows here:
protected void Page_Load(object sender, EventArgs e)
ReportDocument crystalReport = new ReportDocument();
crystalReport.SetDatabaseLogon("asiireader", "readasii", @"SQL", "ASIIBAKSQL1");
CrystalReportViewer1.ReportSource = crystalReport;
ParameterDiscreteValue parameterDiscreteValue = new ParameterDiscreteValue();
parameterDiscreteValue.Value = (string)Session["Student_N"];
ParameterValues currentParameterValues = new ParameterValues();
ParameterField parameterField = new ParameterField();
parameterField.Name = "StudentNumber";
parameterField.CurrentValues = currentParameterValues;
ParameterFields parameterFields = new ParameterFields();
CrystalReportViewer1.ParameterFieldInfo = parameterFields;
May 09, 2012 02:55 AM|necro_mancer|LINK
please kindly refer to the article at
Please mark this response as an "answer" if it helps you. Thanks heaps!
May 09, 2012 04:25 PM|rfreedlund|LINK
Thanks, however, I have seen this code before, but my current code uses neither the dataset or dataset table, it just passes the login information to the Crystal Report. This is how I got around the additional login problems to begin with connecting to a
SQL Server 2005 box. I do continue to look into ways that I can fix this in code, but I will have to admit some ignorance as to how my Crystal Report does get its data once I've passed it the login info and the input parameters I pass to the report.
My main issue continues to be, why does it work connecting to one SQL Server (2005) when it doesn't work connecting to a different SQL Server (2008)? Locally I have no problems with the new connection to the 2008 server box.
If it's any help, my local machine is a Windows 7 computer. The IIS Server my app runs on is still Windows Server 2003. I did setup IIS on a Windows Server 2008 box to test to see if this was a reason for the problem, but the results were the same.