Wierd ODBC Connection to SQL Server 2000

[andysk]

Hi, We bought a new server (couple weeks ago) that we installed Windows 2003 SP2 and SQL Server 2000 SP3a on it. and we had moved our data from old server (Win NT and SQL Server 7.0) to this server.

After we move to this server we encountered :
- Mostly all clients can connect to new server without any big problem
- On Some Clients, after computer startup, will have a error messagebox (with title Microsoft SQL Server Login, and have "!" sign, and no description, and OK Button only), follow by SQL Server Login dialog box, whenever executing application that using ODBC (MDAC) to connect to new sql server for the first time attempt only. For Second time attempt and the rest, everything works fine as usual. I have tried it to test using ODBC directly (for the first time after computer startup) and found out that new sql server always rejected for the first time connection attempt by those client).
- New SQL server also refused connection from 1 of my XP Home client around 60-80% of connection attempts, i have tried to reformat and reinstall Windows XP Home on this client, still problem remained. For the information, this client never encounter any problem whenever connect to old server.
- New SQL Server also refused 100% connection attempts from 1 one my XP Pro client. while this client also never encounter any problem whenever connect to old server

What might happened? and how to solve it ? Thanks in advance

 

[arrow483]

Check that the MDAC level on the clients is compatabile with the new SQL server. I think you need MDAC 2.8

 

[onpnt]

Agree to validate the MDAC versions across the board.

You can use the MDAC utility.

Is it possible to test an OLE DB connection from these clients?

[sub]____________ signature below ______________
The worst mistake you'll ever make is to do something simply the way you know how while ignoring the way it should be done[/sub]

 

[andysk]

Sorry for late reply, after i apply SP4 and turn on AWE:
- Problem No. 1 has reduced to everytime computer first time started on very morning.
- Problem no. 2 still resided. But now effects to most XP PCs, i upgrade MDAC (come with SP4), but the problem still resided.
- Problem no. 3 is already gone.

What might be the problem now? Now I am using processor license, i will test it using concurrent licenses.

 

[andysk]

After i downgraded Windows 2003 R2 to Windows 2000 Advanced Server, all my problem are solved.

Windows 2003 R2 detected Dual-Core processor as 4 processors, While Windows 2000 Advanced Server detected as 2 processors. Something wrong with Windows 2003 R2?

Thanks a lot for all of your help.

Andy

 

[onpnt]

Nothing wrong with Win 2003 R2 unless it was configured poorly. There are many differences in administration between 2000 and 2003 servers.

[sub]____________ signature below ______________
You are a amateur developer until you realize all your code sucks.
Jeff Atwood[/sub]

 

[andysk]

Hi onpnt, i don't change default installation of Windows 2003, it's automatically detected and installed. Now, may you share how to configure it to right condition?