Tuesday, July 29, 2008

Steps to setup a domain

In these days, I am preparing the env setup  for ClearCase and ClearQuest integration. Since ClearCase need a domain env to begin, I try to setup one domain and here are the brief steps.  All machines run Win2k3 server.

A. assign one machine as active directory server and setup the AD and create one domain on it.
B. on that domain controller, add DNS server role
C. add other machines to this domain. You can do this on the domain controller or the machine itself. After doing this, you can see the new domain in the logon to drop down list when you try to login domain machines.

D. in each domain machine, point to the DNS server to the Domain Controller. Else, you may encounter errors (RPC Server is unavailable) when doing step E

E. in each domain machine, add domain users or domain group into the Remote Desktop Users group. After doing this, granted domain users/groups can login domain machines

Tuesday, July 8, 2008

Solutions for the SQL Server Driver Error in ClearQuest

Here is some cases happened these days caused by the SQL Server Driver for ODBC

1. When import CQ profile using IBM Rational ClearQuest Maintenance Tool, user encountered error message as below,
Unable to login to the database using the following connection information:Driver= {SQL Server};UID=xxx;DataBase=xxx;PWD=xxx;SERVER=XXXVerify that the information used matches the way the database was set up
The error message was: SQLDriverConnect:RETCODE=-1,State=08001,Native Error=52
[Microsoft][ODBC SQL Server Driver][dbnmpntw]ConnectionOpen(CreateFile())
[Microsoft][ODBC SQL Server Driver][dbnmpntw]ConnectionOpen(CreateFile())
[Microsoft][ODBC Driver Manager]Driver's SQLSetConnectAttr failed

2. When users login CQ using CQ native client, below error massage happens,
Unable to logon to the SQL_SERVER database xxx
The vendor error message was:
SQLDriverConnect: RETCODE=-1, State=IM003, Native Error=160
pecified driver could not be loaded due to system error 126 (SQL Server).

Here are the steps to diagnose the cause,
1. Open ODBC Data Source Administrator
2. Enter the Drivers tab to check the version of SQL Server
3. Check your CQ product version and get the supported SQL Server version in CQ release notes
4. In most cases, the version is not the correct one to match the CQ products
5. Login microsoft to download the right MDAC(Microsoft Data Accessing Components) version to install and correct the version.





Best Regards
Oliver Zheng
Tel: 86-756-3398810