dbTalk Databases Forums  

Added new Instance for SQL 2000 SP4

microsoft.public.sqlserver.clustering microsoft.public.sqlserver.clustering


Discuss Added new Instance for SQL 2000 SP4 in the microsoft.public.sqlserver.clustering forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
leezy
 
Posts: n/a

Default Added new Instance for SQL 2000 SP4 - 11-06-2008 , 08:10 PM






Dear all,

I have added a new instance for SQL 2000 SP4 on to one of the node in the
clustered server.
after i have add the second server for fail over, i am getting this error in
the other server when trying to fail over to the other side.

the services refuse to start after that on server 2

[sqsrvres] checkODBCConnectError: sqlstate = IM002; native error = 0;
message = [Microsoft][ODBC Driver Manager] Data source name not found and no
default driver specified
[sqsrvres] ODBC sqldriverconnect failed

it keep coming out every second in my application logs and was unable to
start the services from the cluster admin.

when i take offline and bring it back to server 1, it is working fine
without any problem. Could there be any problem with my setup?

regards,
leezy



Reply With Quote
  #2  
Old   
laicalhermes
 
Posts: n/a

Default RE: Added new Instance for SQL 2000 SP4 - 11-25-2008 , 07:16 PM






consider adding a namepipe alias....

"leezy" wrote:

Quote:
Dear all,

I have added a new instance for SQL 2000 SP4 on to one of the node in the
clustered server.
after i have add the second server for fail over, i am getting this error in
the other server when trying to fail over to the other side.

the services refuse to start after that on server 2

[sqsrvres] checkODBCConnectError: sqlstate = IM002; native error = 0;
message = [Microsoft][ODBC Driver Manager] Data source name not found and no
default driver specified
[sqsrvres] ODBC sqldriverconnect failed

it keep coming out every second in my application logs and was unable to
start the services from the cluster admin.

when i take offline and bring it back to server 1, it is working fine
without any problem. Could there be any problem with my setup?

regards,
leezy




Reply With Quote
  #3  
Old   
laicalhermes
 
Posts: n/a

Default RE: Added new Instance for SQL 2000 SP4 - 11-25-2008 , 07:16 PM



consider adding a namepipe alias....

"leezy" wrote:

Quote:
Dear all,

I have added a new instance for SQL 2000 SP4 on to one of the node in the
clustered server.
after i have add the second server for fail over, i am getting this error in
the other server when trying to fail over to the other side.

the services refuse to start after that on server 2

[sqsrvres] checkODBCConnectError: sqlstate = IM002; native error = 0;
message = [Microsoft][ODBC Driver Manager] Data source name not found and no
default driver specified
[sqsrvres] ODBC sqldriverconnect failed

it keep coming out every second in my application logs and was unable to
start the services from the cluster admin.

when i take offline and bring it back to server 1, it is working fine
without any problem. Could there be any problem with my setup?

regards,
leezy




Reply With Quote
  #4  
Old   
laicalhermes
 
Posts: n/a

Default RE: Added new Instance for SQL 2000 SP4 - 11-25-2008 , 07:16 PM



consider adding a namepipe alias....

"leezy" wrote:

Quote:
Dear all,

I have added a new instance for SQL 2000 SP4 on to one of the node in the
clustered server.
after i have add the second server for fail over, i am getting this error in
the other server when trying to fail over to the other side.

the services refuse to start after that on server 2

[sqsrvres] checkODBCConnectError: sqlstate = IM002; native error = 0;
message = [Microsoft][ODBC Driver Manager] Data source name not found and no
default driver specified
[sqsrvres] ODBC sqldriverconnect failed

it keep coming out every second in my application logs and was unable to
start the services from the cluster admin.

when i take offline and bring it back to server 1, it is working fine
without any problem. Could there be any problem with my setup?

regards,
leezy




Reply With Quote
  #5  
Old   
laicalhermes
 
Posts: n/a

Default RE: Added new Instance for SQL 2000 SP4 - 11-25-2008 , 07:16 PM



consider adding a namepipe alias....

"leezy" wrote:

Quote:
Dear all,

I have added a new instance for SQL 2000 SP4 on to one of the node in the
clustered server.
after i have add the second server for fail over, i am getting this error in
the other server when trying to fail over to the other side.

the services refuse to start after that on server 2

[sqsrvres] checkODBCConnectError: sqlstate = IM002; native error = 0;
message = [Microsoft][ODBC Driver Manager] Data source name not found and no
default driver specified
[sqsrvres] ODBC sqldriverconnect failed

it keep coming out every second in my application logs and was unable to
start the services from the cluster admin.

when i take offline and bring it back to server 1, it is working fine
without any problem. Could there be any problem with my setup?

regards,
leezy




Reply With Quote
  #6  
Old   
laicalhermes
 
Posts: n/a

Default RE: Added new Instance for SQL 2000 SP4 - 11-25-2008 , 07:16 PM



consider adding a namepipe alias....

"leezy" wrote:

Quote:
Dear all,

I have added a new instance for SQL 2000 SP4 on to one of the node in the
clustered server.
after i have add the second server for fail over, i am getting this error in
the other server when trying to fail over to the other side.

the services refuse to start after that on server 2

[sqsrvres] checkODBCConnectError: sqlstate = IM002; native error = 0;
message = [Microsoft][ODBC Driver Manager] Data source name not found and no
default driver specified
[sqsrvres] ODBC sqldriverconnect failed

it keep coming out every second in my application logs and was unable to
start the services from the cluster admin.

when i take offline and bring it back to server 1, it is working fine
without any problem. Could there be any problem with my setup?

regards,
leezy




Reply With Quote
  #7  
Old   
laicalhermes
 
Posts: n/a

Default RE: Added new Instance for SQL 2000 SP4 - 11-25-2008 , 07:16 PM



consider adding a namepipe alias....

"leezy" wrote:

Quote:
Dear all,

I have added a new instance for SQL 2000 SP4 on to one of the node in the
clustered server.
after i have add the second server for fail over, i am getting this error in
the other server when trying to fail over to the other side.

the services refuse to start after that on server 2

[sqsrvres] checkODBCConnectError: sqlstate = IM002; native error = 0;
message = [Microsoft][ODBC Driver Manager] Data source name not found and no
default driver specified
[sqsrvres] ODBC sqldriverconnect failed

it keep coming out every second in my application logs and was unable to
start the services from the cluster admin.

when i take offline and bring it back to server 1, it is working fine
without any problem. Could there be any problem with my setup?

regards,
leezy




Reply With Quote
  #8  
Old   
laicalhermes
 
Posts: n/a

Default RE: Added new Instance for SQL 2000 SP4 - 11-25-2008 , 07:16 PM



consider adding a namepipe alias....

"leezy" wrote:

Quote:
Dear all,

I have added a new instance for SQL 2000 SP4 on to one of the node in the
clustered server.
after i have add the second server for fail over, i am getting this error in
the other server when trying to fail over to the other side.

the services refuse to start after that on server 2

[sqsrvres] checkODBCConnectError: sqlstate = IM002; native error = 0;
message = [Microsoft][ODBC Driver Manager] Data source name not found and no
default driver specified
[sqsrvres] ODBC sqldriverconnect failed

it keep coming out every second in my application logs and was unable to
start the services from the cluster admin.

when i take offline and bring it back to server 1, it is working fine
without any problem. Could there be any problem with my setup?

regards,
leezy




Reply With Quote
  #9  
Old   
laicalhermes
 
Posts: n/a

Default RE: Added new Instance for SQL 2000 SP4 - 11-25-2008 , 07:16 PM



consider adding a namepipe alias....

"leezy" wrote:

Quote:
Dear all,

I have added a new instance for SQL 2000 SP4 on to one of the node in the
clustered server.
after i have add the second server for fail over, i am getting this error in
the other server when trying to fail over to the other side.

the services refuse to start after that on server 2

[sqsrvres] checkODBCConnectError: sqlstate = IM002; native error = 0;
message = [Microsoft][ODBC Driver Manager] Data source name not found and no
default driver specified
[sqsrvres] ODBC sqldriverconnect failed

it keep coming out every second in my application logs and was unable to
start the services from the cluster admin.

when i take offline and bring it back to server 1, it is working fine
without any problem. Could there be any problem with my setup?

regards,
leezy




Reply With Quote
  #10  
Old   
laicalhermes
 
Posts: n/a

Default RE: Added new Instance for SQL 2000 SP4 - 11-25-2008 , 07:16 PM



consider adding a namepipe alias....

"leezy" wrote:

Quote:
Dear all,

I have added a new instance for SQL 2000 SP4 on to one of the node in the
clustered server.
after i have add the second server for fail over, i am getting this error in
the other server when trying to fail over to the other side.

the services refuse to start after that on server 2

[sqsrvres] checkODBCConnectError: sqlstate = IM002; native error = 0;
message = [Microsoft][ODBC Driver Manager] Data source name not found and no
default driver specified
[sqsrvres] ODBC sqldriverconnect failed

it keep coming out every second in my application logs and was unable to
start the services from the cluster admin.

when i take offline and bring it back to server 1, it is working fine
without any problem. Could there be any problem with my setup?

regards,
leezy




Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.