I am moving an existing ASP.NET (c#) application developed on the .NET Framework 1.0 that uses SQL Server as the DB and Crystal Reports 9 as the reporting component to a new production environment. The old application environment consisted of a web and reporting server called XC and a DB server called EXCHANGE. The decision was recently made to upgrade the hardware and increase the number of servers; two new servers were purchased and XC was taken off the network. In its place, a new web server (WEB01) was setup to mirror XC. WEB01, the new web server, is running the same .NET Framework and Crystal Reports Engine as XC and all necessary project files have been migrated to this box. EXCHANGE currently used as an email server, while a new DB server (SQL01) was built to be the SQL Server for the application. Over the past few days, I have worked hard to test the application. The only aspect of the application left unfinished is the crystal reports. The error I am currently getting when running from the new web and reports server (WEB01) has the following stack trace:
[LogOnException: Error in File C:\CrystalReports\Magi\Final\2004\SupportTicketsBillingByMonthByBillingCode_v1.8_02.20.04_production.rpt: Unable to connect: incorrect log on parameters.]
CrystalDecisions.ReportSource.ProxyReportSource.ThrowExceptionIfError(ResponseContext response) +160
CrystalDecisions.ReportSource.ProxyReportSource.GetPage(PageRequestContext pageReqContext) +41
CrystalDecisions.Web.ReportAgent.{(Boolean C) +214
CrystalDecisions.Web.CrystalReportViewer.OnPreRender(EventArgs e) +143
System.Web.UI.Control.PreRenderRecursiveInternal() +62
System.Web.UI.Control.PreRenderRecursiveInternal() +125
System.Web.UI.Control.PreRenderRecursiveInternal() +125
System.Web.UI.Page.ProcessRequestMain() +1470
After using the debugger in VS.NET 2002, I was able to locate the problem, however, as of yet, I have not resolved the problem. The issue is this:
Production Settings
oTableLogOnInfo.ConnectionInfo.DatabaseName = "Magi";
oTableLogOnInfo.ConnectionInfo.ServerName = "SQL01";
oTableLogOnInfo.ConnectionInfo.UserID = "Magi";
oTableLogOnInfo.ConnectionInfo.Password = "magi";
Though the server name is explicitly set to “SQL01” before being passed as the connection string, the Output – viewed in the Output tab during the debugging process – generated by stepping through the debugger always reads “EXCHANGE.” I have performed and extensive search and not found any hard coded occurrences of the server name “EXCHANGE” in the code, nor can I find any SQL that is performing a lookup on a DB table for the server name.
The only aspect of the puzzle I have left out is if I activate SQL Server on the EXCHANGE box, I can get the reports to run, however, they are running on old data. The new data resides on SQL01 and all other aspects of the application works flawlessly in the new environment.
If any anyone out there has any idea or advice as to how I might go about resolving this issue, I would appreciate it. Thanks and I look forward to learning from all of you out there. If I have not explained something and you need more info, please let me know. The internet and these discussion boards provide such a rich interface for improved problem solving capabilities.
-richie
[LogOnException: Error in File C:\CrystalReports\Magi\Final\2004\SupportTicketsBillingByMonthByBillingCode_v1.8_02.20.04_production.rpt: Unable to connect: incorrect log on parameters.]
CrystalDecisions.ReportSource.ProxyReportSource.ThrowExceptionIfError(ResponseContext response) +160
CrystalDecisions.ReportSource.ProxyReportSource.GetPage(PageRequestContext pageReqContext) +41
CrystalDecisions.Web.ReportAgent.{(Boolean C) +214
CrystalDecisions.Web.CrystalReportViewer.OnPreRender(EventArgs e) +143
System.Web.UI.Control.PreRenderRecursiveInternal() +62
System.Web.UI.Control.PreRenderRecursiveInternal() +125
System.Web.UI.Control.PreRenderRecursiveInternal() +125
System.Web.UI.Page.ProcessRequestMain() +1470
After using the debugger in VS.NET 2002, I was able to locate the problem, however, as of yet, I have not resolved the problem. The issue is this:
Production Settings
oTableLogOnInfo.ConnectionInfo.DatabaseName = "Magi";
oTableLogOnInfo.ConnectionInfo.ServerName = "SQL01";
oTableLogOnInfo.ConnectionInfo.UserID = "Magi";
oTableLogOnInfo.ConnectionInfo.Password = "magi";
Though the server name is explicitly set to “SQL01” before being passed as the connection string, the Output – viewed in the Output tab during the debugging process – generated by stepping through the debugger always reads “EXCHANGE.” I have performed and extensive search and not found any hard coded occurrences of the server name “EXCHANGE” in the code, nor can I find any SQL that is performing a lookup on a DB table for the server name.
The only aspect of the puzzle I have left out is if I activate SQL Server on the EXCHANGE box, I can get the reports to run, however, they are running on old data. The new data resides on SQL01 and all other aspects of the application works flawlessly in the new environment.
If any anyone out there has any idea or advice as to how I might go about resolving this issue, I would appreciate it. Thanks and I look forward to learning from all of you out there. If I have not explained something and you need more info, please let me know. The internet and these discussion boards provide such a rich interface for improved problem solving capabilities.
-richie