strider
Member
I have a Windows 2008 R2 Terminal Server issue with Crystal reports dlls.
I am implementing the terminal server configuration for 3rd party software that we use to access a SQL server DB.
I am using Win server 2008 R2 on the terminal server. All of the workstations connecting to the TS are running Win XP.
Many of the new reports supplied by the vendor present a window with drop downs for variable and sort selections, which is great, but this is the cause of my problem.
Many of my users cant run the new reports and are presented with blank drop down menus when the new report is run. However, other users dont have any problems with the reports. For users that get the blank drop downs, they cant run the report or even exit the drop down window.
This is a very random problem, but always the same for each user. Any user that cannot see the drop downs on their own workstation, can log onto any other workstation and still not see the drop downs. So, the problem follows the user to every workstation.
Its not a security configuration problem as all users are in the same network security group.
I know I can downgrade the terminal server to Win server 2003 and most likely the problem will go away (experiments with another 2003 TS have proven this), but I need a solution for the Win server 2008 R2.
The 3rd party software vendor doesn't have a clue what is going on. He runs the same win 2008 r2 setup without problems.
The SAP Crystal Reports forum hasn't yielded any info other than CR uses java to write the dlls and that might be the cause.
Further info
The same users can attach to the SQL DB through ODBC with the 3rd party software installed on their workstation and the reports work fine.
If I remove the 2010 report window with the drop downs (requiring entering parameters or selecting a sort order), the reports works fine for every user.
The new reports with the parameters are great and using a 2008r2 Terminal Sever is the right solution, but I need to find a fix for this incompatibility problem.
The maddening thing is that it works for some users and not others in the same network security group.
Anyone have any idea what is causing this very random problem?
Thanks for your help,
I am implementing the terminal server configuration for 3rd party software that we use to access a SQL server DB.
I am using Win server 2008 R2 on the terminal server. All of the workstations connecting to the TS are running Win XP.
Many of the new reports supplied by the vendor present a window with drop downs for variable and sort selections, which is great, but this is the cause of my problem.
Many of my users cant run the new reports and are presented with blank drop down menus when the new report is run. However, other users dont have any problems with the reports. For users that get the blank drop downs, they cant run the report or even exit the drop down window.
This is a very random problem, but always the same for each user. Any user that cannot see the drop downs on their own workstation, can log onto any other workstation and still not see the drop downs. So, the problem follows the user to every workstation.
Its not a security configuration problem as all users are in the same network security group.
I know I can downgrade the terminal server to Win server 2003 and most likely the problem will go away (experiments with another 2003 TS have proven this), but I need a solution for the Win server 2008 R2.
The 3rd party software vendor doesn't have a clue what is going on. He runs the same win 2008 r2 setup without problems.
The SAP Crystal Reports forum hasn't yielded any info other than CR uses java to write the dlls and that might be the cause.
Further info
The same users can attach to the SQL DB through ODBC with the 3rd party software installed on their workstation and the reports work fine.
If I remove the 2010 report window with the drop downs (requiring entering parameters or selecting a sort order), the reports works fine for every user.
The new reports with the parameters are great and using a 2008r2 Terminal Sever is the right solution, but I need to find a fix for this incompatibility problem.
The maddening thing is that it works for some users and not others in the same network security group.
Anyone have any idea what is causing this very random problem?
Thanks for your help,