Unsolved
This post is more than 5 years old
3 Posts
0
546
October 12th, 2006 09:00
Co-Standby Server AAdvanced could not Detect SQL Server Instance
Hello,
I would appreciate if someone can help me with an strange issue with Co-Standyby Server AAdvanced. I'm trying to configure a new SQL cluster, and the Co-StandBy 5.1.2 cannot detect the SQL Server Instance.
My environment:
2 node servers running MS Windows 2003 Server SP1. All Microsoft Update Patches was applied on both servers before starting the Legato Software.
The have installed the AAdvanced in the following order:
5.1 Agent
5.1 Console
5.1.2 Agent Update
5.1.2 Console Update
Fixes
512p1
71040
74900
82044
81839
80000
I have set the replication on both nodes, created IP addresses, node aliases without problems.
Now the issue: I installed MS SQL Server 2000 SP3a Enterprise Edition on Both nodes. I have installed the Program files of SQL Server on C:\Program Files\SQL Server of both machines, and the data were installed on my replicated D:\ drive.
After installation of first node, I deleted the information on D:\ drive, and repeated the installation on second Node, and used the same credentials, TCP/IP settings and SQL instance name. On both nodes, I set the SQL Server and Agent services to start manually.
When I try to use the Wizard to create the cluster, the AA Co-Standby cannot detect these SQL Instance, on any node. I have sure that the data source is attached to correct node, but at moment that the wizzard tries to detect the instance, the field was blank. I made the same steps on both Nodes and the result was the same.
I'm trying to find what's happening here, but any help will be appreciated.
Sorry for the long post text and some english mistakes.
Thanks,
Ricardo Teixeira Leite
I would appreciate if someone can help me with an strange issue with Co-Standyby Server AAdvanced. I'm trying to configure a new SQL cluster, and the Co-StandBy 5.1.2 cannot detect the SQL Server Instance.
My environment:
2 node servers running MS Windows 2003 Server SP1. All Microsoft Update Patches was applied on both servers before starting the Legato Software.
The have installed the AAdvanced in the following order:
5.1 Agent
5.1 Console
5.1.2 Agent Update
5.1.2 Console Update
Fixes
512p1
71040
74900
82044
81839
80000
I have set the replication on both nodes, created IP addresses, node aliases without problems.
Now the issue: I installed MS SQL Server 2000 SP3a Enterprise Edition on Both nodes. I have installed the Program files of SQL Server on C:\Program Files\SQL Server of both machines, and the data were installed on my replicated D:\ drive.
After installation of first node, I deleted the information on D:\ drive, and repeated the installation on second Node, and used the same credentials, TCP/IP settings and SQL instance name. On both nodes, I set the SQL Server and Agent services to start manually.
When I try to use the Wizard to create the cluster, the AA Co-Standby cannot detect these SQL Instance, on any node. I have sure that the data source is attached to correct node, but at moment that the wizzard tries to detect the instance, the field was blank. I made the same steps on both Nodes and the result was the same.
I'm trying to find what's happening here, but any help will be appreciated.
Sorry for the long post text and some english mistakes.
Thanks,
Ricardo Teixeira Leite
yito1
262 Posts
0
October 12th, 2006 18:00
I'm Japanese.
If English can be wrong, I am sorry.
Cannot you detect "SQL Site Name" in the step of "MSSQL Server Configuration"?
Can you offer the following information?
1) Cmd.exe is started.
2) Execute "c:\Program Files\Legato CSBSAA\ \modules\sql2000_2.0\sql2000_up.exe".
3) Execute "SERVERS" command.
4) Describe the content displayed by the command prompt.
Regards,
Yoshinobu Ito
tribicic
157 Posts
0
October 13th, 2006 03:00
rtleite
3 Posts
0
October 13th, 2006 07:00
Thanks for your answer!!
Yes, before starting the SQL Wizard I've attached the Data source manually on first node. I tried to reppeat the procedure on the other node, and the problem is the same.
It's strange, because I used the same SA credentials on SQL installation of both Nodes, same Windows account (administrator) to install the software. The wizard don't detect the instance anyway!!!
Thanks!!!
Ricardo Teixeira Leite.
rtleite
3 Posts
0
October 13th, 2006 07:00
Thanks for your message.
I executed the commands, in the following order:
1 - Start / Run: CMD.EXE
2 - On the command prompt I executed the command "C:\Program Files\Legato CSBSAA\ \modules\Sql2000_2> Sql2000_up.exe servers"
The answer was: NODE01\INFRA
If I repeat the procedure on second server, attaching the same data source to the other node, I receive the answer: NODE02\INFRA
In this case, " INFRA" is my MsSQL 2000 Instance.
On both Nodes I can manually start the SQL Server Service and Agent using the SQL Server Service Manager, or using the services icon on Windows Control Panel, without errors.
Reading the help of Sql2000_up.exe file, I tried to use the option "MSQLSITE" and I received the following message: Command failed: undefined " MSSQLServerSite"
About the English, don't worry, because I'm from Brazil and my English is poor too... ; )
Thanks!!
Ricardo Teixeira Leite.
yito1
262 Posts
0
October 15th, 2006 19:00
It is a question again.
In which step have you stayed when the SQLModule wizard is executed?
Is it a step of "Select the SQL instance to be nonitored"?
Is it a step of "Enter SQL Server database to monitor"?
Moreover, please describe the log of AutoStartSE when the SQLModule wizard is executed.
Some error is sure to be displayed.
*There was the following articles in EMC Knowledge Base.
Please refer.
------------------------------------------------------------------------------------------------------------------
Support Note Information
Subject: Cannot complete SQL Module installation on AAM/COSBS Advanced
Note: Fact: Windows 2003
Fact: Co-StandbyServer Advanced 5.1
Fact: SQL Module for Co-StandbyServer Advanced 5.1
Symptom: Cannot complete SQL Module installation
Symptom: In the Server Site Name window they go to pull down a Server Site Name, but there is nothing in this pulldown menu
Symptom: list for Server Site Name is blank
Cause: The User entered into a previous window for the SQL Login does not have the correct priveledges to run SQL. Since the install GUI cannot login to SQL using the user listed, the list for Server Site Name is blank.
Fix: Enter a user during the install that has Domain wide Administrator priveledges. This user should have Domain priveledges and be able to authenticate to the Domain from both nodes.
---------------------------------------------------------------------------------------------------------------------
Regards,
Yoshinobu Ito