first, sorry my english..., apears this error during instalattion the =
second instance on Cluster Windows 2003.
The description for Event ID ( 17052 ) in Source ( MSSQL$LASCAR ) cannot =
be found. The local computer may not have the necessary registry =
information or message DLL files to display messages from a remote =
computer. You may be able to use the /AUXSOURCE=3D flag to retrieve this =
description; see Help and Support for details. The following information =
is part of the event: [sqsrvres] checkODBCConnectError: sqlstate =3D =
01000; native error =3D 35; message =3D [Microsoft][ODBC SQL Server =
Driver][DBNETLIB]ConnectionOpen (Connect()).
Tahnk's.
Carlo Sorrel.
"Uttam Parui[MS]" <uttamkp@online.microsoft.com> escribi=F3 en el =
mensaje news:uX597q8AFHA.1680@cpmsftngxa10.phx.gbl...
[quoted text, click to view] > Hello Carlo,
>=20
> Once you have installed the first instance of virtual SQL Server 2000 =
then the steps for installing the second instance of virtual SQL Server =
2000 is exactly the same. The second virtual instance of SQL Server 2000 =
[quoted text, click to view] > will need a seperate shared drive (you cannot use the shared drive =
that you used for the first instance), unique SQL IP Address (again you =
cannot use the one you used for your windows cluster ip or the first sql =
[quoted text, click to view] > server ip) and unique SQL network name. Also, if the first virtual =
instance is a default instance then the second instance can ONLY be a =
named instance. You CANNOT have two default virtual SQL Server 2000=20
[quoted text, click to view] > instance on the same cluster. To have both the instances similar, many =
customers install both instances of virtual SQL Server 2000 as named =
instances.=20
[quoted text, click to view] >=20
> Since you have multiple instances (2 in your case), you will need to =
ensure that all server nodes have the same resources (processor, memory) =
and it is enough to handle the instances that could potentially fail to=20
[quoted text, click to view] > that node. Another important consideration is to cap memory usage of =
the instance of SQL Server 2000 with max server memory. Especially if =
AWE memory is enabled, max server memory must be set in a=20
[quoted text, click to view] > multiple-instance cluster to prevent starving the server node.
>=20
> If you have a Windows Server 2003 EE cluster then you may find the =
following webcast useful
>=20
> TechNet Support WebCast: How to install a Microsoft SQL Server 2000 =
virtual server on a Microsoft Windows Server 2003 cluster
> Discusses how to install Microsoft SQL Server 2000 clustering on =
Microsoft Windows Server 2003 and differences between Microsoft Windows =
2000 Server and Windows Server 2003.
[quoted text, click to view] >
http://support.microsoft.com/default.aspx?scid=3Dkb;en-us;888121 >=20
>=20
> For Win2K Adv Server cluster, you may find the following whitepaper =
useful
>=20
> SQL Server 2000 Failover Clustering=20
> =
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/failclus.m= spx
[quoted text, click to view] >=20
> Review the above and feel free to post any other qs that you may have.
>=20
> Additional Information
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> Here is some other related links that you may find useful
>=20
> INF: Clustered SQL Server Do's, Don'ts, and Basic Warnings=20
>
http://support.microsoft.com/?kbid=3D254321 >=20
> Introduction to Microsoft SQL Server 2000 Clustering=20
> =
http://support.microsoft.com/default.aspx?scid=3D/servicedesks/webcasts/w=
c051001/wcblurb051001.asp
[quoted text, click to view] >=20
> Microsoft SQL Server 2000 Virtual Server: Things You Should Know=20
> =
http://support.microsoft.com/default.aspx?scid=3D/servicedesks/webcasts/w=
c032602/wcblurb032602.asp
[quoted text, click to view] >=20
>=20
> Microsoft SQL Server 2000 Virtual Server Basic Setup, Maintenance, and =
Service Pack =
http://support.microsoft.com/default.aspx?scid=3D/servicedesks/webcasts/w=
cd061002/wcdblurb061002.asp
[quoted text, click to view] >=20
> Microsoft SQL Server 2000 Failover Clustering Disaster Recovery =
Procedures=20
> =
http://support.microsoft.com/default.aspx?scid=3D/servicedesks/webcasts/w=
cd101802/wcdblurb101802.asp
[quoted text, click to view] >=20
> Troubleshooting SQL 2000 Virtual Server and Service Pack Setups for =
Failover Clustering=20
>=20
> =
http://support.microsoft.com/default.aspx?scid=3D/servicedesks/webcasts/w=
cd020703/wcdblurb020703.asp
[quoted text, click to view] >=20
>=20
> HTH,
>=20
> Best Regards,
>=20
> Uttam Parui
> Microsoft Corporation
>=20
> This posting is provided "AS IS" with no warranties, and confers no =
rights.
>=20
> Are you secure? For information about the Strategic Technology =
Protection Program and to order your FREE Security Tool Kit, please =
visit
http://www.microsoft.com/security. [quoted text, click to view] >=20
> Microsoft highly recommends that users with Internet access update =
their Microsoft software to better protect against viruses and security =
vulnerabilities. The easiest way to do this is to visit the following =
websites:=20
[quoted text, click to view]