Terminal Server, ODBC, SQL, Crystal Report Viewer

Jay

Jay

Jay

Associate
Joined
18 Oct 2002
Posts
1,650
Location
North West
Hi Guys, got a bit of a strange problem here and hope maybe someone has experienced it before.

There is a terminal server.

A domain user can logon from PC1 to the terminal server using their domain account. They can login to the software and run a report (opens in crystal report viewer)

The same domain user, logs onto the same terminal server from PC2, opens the software, runs the report and gets a "ODBC Error, logon failed bla bla bla"


This is the exact same domain account, logging onto the exact same terminal server, just from 2 different PC's


The only difference:

PC1 is a computer that is attached to the DOMAIN.
PC2 is NOT attached to the domain.

Was working fine on both machines up until today.

Any idea's because i'm baffled.
:)
 
Just to Add, this is the error seen:

Logon failed Details: 01000:[Microsoft][ODBC Driver Message]The driver doesn't support the version of the ODBS behavior that the application requested (see SQLSetEnvAttr)
 
Are both machines patched to the same level? I saw this once when a machine didn't have the correct .NET f/w. If the application isn't .NET based, this may be unlikely.

Could it be something to do with DSNs? I don't have experience with TS, so not sure how these things work... is it set locally?
 
Hi mate.

DSN is set on the Terminal Server. Its a strange one, because the user is logging onto the terminal server with the exact same domain account. From one machine the report runs fine, from the other it fails.

You would think it shouldnt matter where your logging onto the terminal server from (PC1, PC2, mobile phone, laptop), as long as your logging onto the Terminal Server successfully everything else is done from the terminal server session, surely?
 
Only difference i can see is PC1 has version 6 RDP client, and PC2 has version 5.1 RDP client.
 
Jay said:
Only difference i can see is PC1 has version 6 RDP client, and PC2 has version 5.1 RDP client.
Click to expand...

You know what needs to be done then

I've had issues with the CR viewer on citrix/rdp environments before, normally down to it seemingly trying to save to the local device
 
Cool, thanks iaind.

btw: local drives in local resources on the RDP client is disabled. But the setting on the terminal server is set to allow local drives, and not "use client settings". Will this override the local RDP client setting? I wouldn't have thought it would?
 
It shouldn't, no.

I never did figure out exactly what was going on with it, but it has always seemed to be related to local resources
 
You must log in or register to reply here.
Back
Top Bottom