CCM client error (Can not connect to database server)

[cuneyt2020]

Hi, 3 of CCM clients getting same error two days ago. Actually i uninstalled th CCM client and reinstalled it but still gives the same error (Cannot connect to Database server, No ccm server is available) and after this message it's closed.

What can be the reason for this?

Note:Other 40 clients are working properly
I checked the error message on client machine and saw this error

[08.11.2005 - 17:00:57]
From: IM
SQL1:"[ConnectSrv]"
SQL2:" [dblogin] [OK] [dbopen]"
dbproc=00D02D70; severity=9;
dberr=10040; dberrstr=Db-library network communciations layer not loaded.
oserr=-1; oserrstr=null

[08.11.2005 - 17:01:00]
From: IM
SQL1:"[ConnectSrv]"
SQL2:" [dblogin] [OK] [dbopen]"
dbproc=00D03A78; severity=9;
dberr=10040; dberrstr=Db-library network communciations layer not loaded.
oserr=-1; oserrstr=null

[08.11.2005 - 17:03:31]
From: IM
SQL1:"[ConnectSrv]"
SQL2:" [dblogin] [OK] [dbopen]"
dbproc=00D02F80; severity=9;
dberr=10040; dberrstr=Db-library network communciations layer not loaded.
oserr=-1; oserrstr=null

[08.11.2005 - 17:03:36]
From: IM
SQL1:"[ConnectSrv]"
SQL2:" [dblogin] [OK] [dbopen]"
dbproc=00D03C88; severity=9;
dberr=10040; dberrstr=Db-library network communciations layer not loaded.
oserr=-1; oserrstr=null

[08.11.2005 - 17:07:47]
From: IM
SQL1:"[ConnectSrv]"
SQL2:" [dblogin] [OK] [dbopen]"
dbproc=00D02D70; severity=9;
dberr=10040; dberrstr=Db-library network communciations layer not loaded.
oserr=-1; oserrstr=null

[08.11.2005 - 17:07:49]
From: IM
SQL1:"[ConnectSrv]"
SQL2:" [dblogin] [OK] [dbopen]"
dbproc=00D03A78; severity=9;
dberr=10040; dberrstr=Db-library network communciations layer not loaded.
oserr=-1; oserrstr=null

Is this the right way for solution? or any other ideas?
Greetings.

 

[slash50]

Have you added any microsoft hotfixes to those clients? and changes to the ODBC drivers? any conflicting software that might have been loaded?

Can you test the ODBC connection?

 

[cuneyt2020]

Actually i don't know if there is any conflicting software done but, on win2000 , i checked the odbc connection part on Administrative tools menu...
And saw that there is no related user or system dsn on odbc connections.In fact i'm not sure if there will be one.
So i added a connection to system DSN, named CCM and with Sa user, and test it and it was a successful connection to SQL DB of CCM.
But again i tested the Information Manager still same database connection error.
So will there be a connection on ODBC connections?

 

[slash50]

So you've got the SQL ODBC driver loaded, have you checked the version on the bad PC's with the version on the good PC's? Have a look at that and see if they differ.

Also take a look in the File DSN's, is there anything that mentions Oliver or Local DNA Server?

 

[ICFUC]

Is IFOR working ?
Is CCM Client installed on Server ?
Does it run there?

The connection between CCM Client and isn't ODBC-DSN
It's a registry value with a host-name to server.
When it stopped working, wht changes had been done in your net, and DNS.

 

[slash50]

I always thought the registry value was just a pointer to the server, it still uses ODBC to query the database.

I had a problem with this a few years ago on a DNA system. We were using SQL 6.5 but somebody loaded the SQL 7 server tools onto one of the clients. This updated the SQL driver in ODBC and caused the OWS to stop accessing the Database.

 

[ICFUC]

Yes it uses ODBC, but not a local DSN
It's the IFOR-conf. on a CCM-client that tells us what IP-adress to make a ODBC-con to.
Im not sure but I think I've reinstalled the IFOR-package on a client when it didn't work, similar errors.

And yes you are right the D.N.A works in a differnent way.

 

[slash50]

Cool, thanks for the explanation )