sark3k
February 24th, 2006, 01:05 PM
Ok, I have been banging my head for a couple of days on this, and cannot seem to get anywhere.
I have developed an application for an insurance company to keep track of policies and claims, and am using VB.Net 2002, Crystal Reports 9, and SQL Server 2000. Aside form the occasional buggy-boo (who knew that TRUE is so different from FALSE!?!?!), the application performs very well. I have it deployed on 7 workstations, all WinXPSp2 with .NET Framework 1.1, and have a few crystal hotfixes installed to fix some random oddities with crystal rendering.
It is a pretty complex database layout, because they deal in international currencies, and write some VERY complicated policies that span the globe, but I have standardized a lot of things to make my crystal development pretty easy. I have designed over 20 reports that give the users various ways of examinign thier production, and forecasting, etc, and these also work well.
Now to the problem. I have several international users that connect into the system over a terminal server, to use the exchange email system, and access the application to check on policies, and claims, etc. The application works fine, except for the Crystal Reports portion. Every time I attempt to view a report, you will be prompted for any parameters that are on the report, but then you get an ODBC Logon Screen, prompting for Server, Database, Username and password. If you type in the info that should connect you, you get a failure.
Now, I got this early on in my development, on the individual workstations, but have since fixed that. My problem was sending the logon info through the code for each subreport table, so I designed a DLL that loads the reports, assigns the database logon info for each table in the report and subreports, and then displays it. So it works perfectly on all the workstations, just not on the terminal server sessions, even logged in as the Domain Administrator. It seems to be an SQL access/security issue, but I am at a loss.
My network configuration is 1 PDC/AD Controller, which is also my SQL Server, and the Terminal Server, which is dedicated to that function, but is a member of the domain. Both are Win2003 Servers with SP1 applied. 7 workstations, winXPSp2. Wireless Access Points used for workstations, servers are hardwired using gigabit ENet. T1 access brings in remote Terminal Service users over VPN.
So the summarized question is: how do I get my reports to function properly without a logon screen in my Terminal Server sessions, as they do on normal workstations?
Thanks for any help you may offer!
ScottJ
I have developed an application for an insurance company to keep track of policies and claims, and am using VB.Net 2002, Crystal Reports 9, and SQL Server 2000. Aside form the occasional buggy-boo (who knew that TRUE is so different from FALSE!?!?!), the application performs very well. I have it deployed on 7 workstations, all WinXPSp2 with .NET Framework 1.1, and have a few crystal hotfixes installed to fix some random oddities with crystal rendering.
It is a pretty complex database layout, because they deal in international currencies, and write some VERY complicated policies that span the globe, but I have standardized a lot of things to make my crystal development pretty easy. I have designed over 20 reports that give the users various ways of examinign thier production, and forecasting, etc, and these also work well.
Now to the problem. I have several international users that connect into the system over a terminal server, to use the exchange email system, and access the application to check on policies, and claims, etc. The application works fine, except for the Crystal Reports portion. Every time I attempt to view a report, you will be prompted for any parameters that are on the report, but then you get an ODBC Logon Screen, prompting for Server, Database, Username and password. If you type in the info that should connect you, you get a failure.
Now, I got this early on in my development, on the individual workstations, but have since fixed that. My problem was sending the logon info through the code for each subreport table, so I designed a DLL that loads the reports, assigns the database logon info for each table in the report and subreports, and then displays it. So it works perfectly on all the workstations, just not on the terminal server sessions, even logged in as the Domain Administrator. It seems to be an SQL access/security issue, but I am at a loss.
My network configuration is 1 PDC/AD Controller, which is also my SQL Server, and the Terminal Server, which is dedicated to that function, but is a member of the domain. Both are Win2003 Servers with SP1 applied. 7 workstations, winXPSp2. Wireless Access Points used for workstations, servers are hardwired using gigabit ENet. T1 access brings in remote Terminal Service users over VPN.
So the summarized question is: how do I get my reports to function properly without a logon screen in my Terminal Server sessions, as they do on normal workstations?
Thanks for any help you may offer!
ScottJ