Showing posts with label windows. Show all posts
Showing posts with label windows. Show all posts

Thursday, March 29, 2012

Change IP in SQL Cluster

Hi all,
We need to change the IP address of server SQL.
We use SQL 2000 Enterprise, Windows 2000 Advanced Server, Cluster Service
with two nodes.
What must we do?
Thanks a lot,
Ednaldo
Please check the following articles
Changing the IP Address of Network Adapters in Cluster Server
http://support.microsoft.com/default...b;en-us;230356
Changing the IP Address of a Cluster Adapter May Result in Failover
http://support.microsoft.com/kb/241828/EN-US/
How to change the network IP addresses of SQL Server virtual servers
http://support.microsoft.com/kb/244980
"Ednaldo" wrote:

> Hi all,
> We need to change the IP address of server SQL.
> We use SQL 2000 Enterprise, Windows 2000 Advanced Server, Cluster Service
> with two nodes.
> What must we do?
> Thanks a lot,
> Ednaldo

Change IP in SQL Cluster

Hi all,
We need to change the IP address of server SQL.
We use SQL 2000 Enterprise, Windows 2000 Advanced Server, Cluster Service
with two nodes.
What must we do?
Thanks a lot,
EdnaldoPlease check the following articles
Changing the IP Address of Network Adapters in Cluster Server
http://support.microsoft.com/defaul...kb;en-us;230356
Changing the IP Address of a Cluster Adapter May Result in Failover
http://support.microsoft.com/kb/241828/EN-US/
How to change the network IP addresses of SQL Server virtual servers
http://support.microsoft.com/kb/244980
"Ednaldo" wrote:

> Hi all,
> We need to change the IP address of server SQL.
> We use SQL 2000 Enterprise, Windows 2000 Advanced Server, Cluster Service
> with two nodes.
> What must we do?
> Thanks a lot,
> Ednaldo

Change IP in SQL Cluster

Hi all,
We need to change the IP address of server SQL.
We use SQL 2000 Enterprise, Windows 2000 Advanced Server, Cluster Service
with two nodes.
What must we do?
Thanks a lot,
EdnaldoPlease check the following articles
Changing the IP Address of Network Adapters in Cluster Server
http://support.microsoft.com/default.aspx?scid=kb;en-us;230356
Changing the IP Address of a Cluster Adapter May Result in Failover
http://support.microsoft.com/kb/241828/EN-US/
How to change the network IP addresses of SQL Server virtual servers
http://support.microsoft.com/kb/244980
"Ednaldo" wrote:
> Hi all,
> We need to change the IP address of server SQL.
> We use SQL 2000 Enterprise, Windows 2000 Advanced Server, Cluster Service
> with two nodes.
> What must we do?
> Thanks a lot,
> Ednaldo

Tuesday, March 27, 2012

Change IP address and subnet of Cluster nodes

I have two node SQL 2005 Cluster on Windows 2003 SP1. Now, I have to change
both IP address and subnet Windows Cluster servers.
is it possible? or What can I do step-by-step?
thanks
"TUFAN ODUNCU" <TUFANODUNCU@.discussions.microsoft.com> wrote in message
news:AF919426-25AC-4D68-AE1D-214729F868EE@.microsoft.com...
>I have two node SQL 2005 Cluster on Windows 2003 SP1. Now, I have to change
> both IP address and subnet Windows Cluster servers.
> is it possible? or What can I do step-by-step?
> thanks
Per Ryan in the other cluster newsgroup...
Changing the IP address of network adapters in cluster server
http://support.microsoft.com/kb/230356
How to change the network IP addresses of SQL Server failover cluster
instances
http://support.microsoft.com/kb/244980
Russ Kaufmann
MVP - Windows Server - Clustering
ClusterHelp.com, a Microsoft Certified Gold Partner
Web http://www.clusterhelp.com
Blog http://msmvps.com/clusterhelp
The next ClusterHelp classes are:
July 10-13 in Denver
July 16-19 in New York
Sep 3 - 6 in Copenhagen

Change in windows platform from XP to NT

hello... my SQL database is being not able to be accessed by application when i run through VS2005 . I created the database in XP sys now brought to a NT systeem..what shd i do ..? pls help Sad

Hi,

Could you show us the error message so that we can solve the problem more quickly. In your case, I think there's no relationship with Windows platform.Maybe you haven't attached your database into your current SQLServer properly.You may backup your database from your old SQLServer and restore the backup file into the new one. Thanks.

Change from Active\Active to Active\Passive Cluster

I have a SQL Server 2000 Cluster with Windows 2000 Server.
The Cluster was set up as a Active\Active and I would like to change it to
Active\Passive.
What do I need to change go from Active\Active to Active\Passive?
Thanks,
Hi
Active/Active vs Active/Passive in SQL server tems is not correct.
Active/Active = 2 SQL Server instances, one running on each node.
Active/Passive = 1 SQL Server instance, running on a Node, with the other
node doing nothing but waiting for a failover.
Uninstall one SQL server instance and you have what you want. Any reason you
want to do this?
Regards
Mike
"Joe K." wrote:

> I have a SQL Server 2000 Cluster with Windows 2000 Server.
> The Cluster was set up as a Active\Active and I would like to change it to
> Active\Passive.
> What do I need to change go from Active\Active to Active\Passive?
> Thanks,
|||Mike - Are you recommending not to run an active/passive cluster config?
"Mike Epprecht (SQL MVP)" wrote:
[vbcol=seagreen]
> Hi
> Active/Active vs Active/Passive in SQL server tems is not correct.
> Active/Active = 2 SQL Server instances, one running on each node.
> Active/Passive = 1 SQL Server instance, running on a Node, with the other
> node doing nothing but waiting for a failover.
> Uninstall one SQL server instance and you have what you want. Any reason you
> want to do this?
> Regards
> Mike
> "Joe K." wrote:
|||Hi
No, but the decision must be based on business requirements.
If you need 2 instances of SQL Server, run them.
At work, we use put 4-6 instances per node on a SQL Cluster (= 8-12 per 2
node cluster). Our perspective is that having one machine do nothing is a
waste of space and energy.
Single Instance (Active/Passive), from a licensing perspective is cheaper,
you only need to license the single node as the other node is DR and is not
active.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Todd" <Todd@.discussions.microsoft.com> wrote in message
news:90355A4B-87CE-4B14-8C2C-AC0D909D1981@.microsoft.com...[vbcol=seagreen]
> Mike - Are you recommending not to run an active/passive cluster config?
> "Mike Epprecht (SQL MVP)" wrote:
other[vbcol=seagreen]
you[vbcol=seagreen]
it to[vbcol=seagreen]
|||I agree Mike. At work we use all active/passive clusters (4 total clusters
with 2 nodes in each) and run only a single instance on each active node. We
are doing a mass db consolidation project now and will likely go the path of
a multinode cluster as that will best suit our business needs.
Do you run different coalition settings on your 4-6 instances per node?
Thanks,
Todd
"Mike Epprecht (SQL MVP)" wrote:

> Hi
> No, but the decision must be based on business requirements.
> If you need 2 instances of SQL Server, run them.
> At work, we use put 4-6 instances per node on a SQL Cluster (= 8-12 per 2
> node cluster). Our perspective is that having one machine do nothing is a
> waste of space and energy.
> Single Instance (Active/Passive), from a licensing perspective is cheaper,
> you only need to license the single node as the other node is DR and is not
> active.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Todd" <Todd@.discussions.microsoft.com> wrote in message
> news:90355A4B-87CE-4B14-8C2C-AC0D909D1981@.microsoft.com...
> other
> you
> it to
>
>
|||Hi
No, Same collation. For us, multi-instances are there for security (bank),
to keep everyone away from each other.
It also makes it easier to add more nodes if we need to, so we then move the
instances around.
Once you start to have more than 2 busy instances, you better have a decent
SAN (EMC, biiiig EMC's) that can sustain the throughput. Multi fiber cards,
multi paths etc.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Todd" <Todd@.discussions.microsoft.com> wrote in message
news:23520408-C115-496C-9D33-A5313C3424C2@.microsoft.com...
> I agree Mike. At work we use all active/passive clusters (4 total
clusters
> with 2 nodes in each) and run only a single instance on each active node.
We
> are doing a mass db consolidation project now and will likely go the path
of[vbcol=seagreen]
> a multinode cluster as that will best suit our business needs.
> Do you run different coalition settings on your 4-6 instances per node?
> Thanks,
> Todd
> "Mike Epprecht (SQL MVP)" wrote:
2[vbcol=seagreen]
a[vbcol=seagreen]
cheaper,[vbcol=seagreen]
not[vbcol=seagreen]
config?[vbcol=seagreen]
reason[vbcol=seagreen]
change[vbcol=seagreen]
|||I agree 100% with Mike. I run a large N-1 cluster (N Nodes, N-1 Instances)
so I have one stand-by node for three active instances. I have scripts to
change the cluster failover order depending on what maintenance is
happening. I also can change memory settings and collapse the cluster on a
single node during low activity times for host node maintenance. It takes a
few extra steps to manage a large, multi-instance cluster, but the same
principles apply.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:Ok8qLjeGFHA.3472@.TK2MSFTNGP09.phx.gbl...
> Hi
> No, Same collation. For us, multi-instances are there for security (bank),
> to keep everyone away from each other.
> It also makes it easier to add more nodes if we need to, so we then move
the
> instances around.
> Once you start to have more than 2 busy instances, you better have a
decent
> SAN (EMC, biiiig EMC's) that can sustain the throughput. Multi fiber
cards,[vbcol=seagreen]
> multi paths etc.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Todd" <Todd@.discussions.microsoft.com> wrote in message
> news:23520408-C115-496C-9D33-A5313C3424C2@.microsoft.com...
> clusters
node.[vbcol=seagreen]
> We
path[vbcol=seagreen]
> of
per[vbcol=seagreen]
> 2
is[vbcol=seagreen]
> a
> cheaper,
is[vbcol=seagreen]
> not
> config?
the[vbcol=seagreen]
> reason
> change
Active\Passive?
>
sql

Sunday, March 11, 2012

Change computer name while running SQL Server

I need to change the computer name on my Windows Server 2003. I am currently
running SQl Server, and I am trying to find out if changing the name will
affect the SQL server or not. Is there a process for doing this, or if I
change the name and reboot, will the name automatically change in the SQL
Server Services Manager?
Thanks,
JOE
"Joe Michl" <JoeMichl@.discussions.microsoft.com> wrote in message
news:094A1C97-34EE-49F2-B374-1BC7DF62A712@.microsoft.com...
> I need to change the computer name on my Windows Server 2003. I am
currently
> running SQl Server, and I am trying to find out if changing the name will
> affect the SQL server or not. Is there a process for doing this, or if I
> change the name and reboot, will the name automatically change in the SQL
> Server Services Manager?
As long as there are no applications coded for your specific server name you
should be OK. After changing the server name and rebooting, use the commands
in the following article:
http://support.microsoft.com/default...&Product=sql2k
Steve

Thursday, March 8, 2012

Change Cluster Disk Owner

I have an Active/Active cluster with Windows 2003 with SQL Server 2000. I
am trying to move the cluster disk T: owner to my other group.
I keep receiving the following error:
An error occurred attempting to change the group of the
Disk T: to 'Other Resource' Group. The cluster node is not the owner of the
group. Error ID:5016
I checked all cluster groups and they have both owners. I also checked and
there is no dependency on Disk T:
Please help me with moving Disk T: to the Other Resource Group.
Thanks,
You can only change ownership of a resource from the node that currently
both resource groups.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Joe K." <JoeK@.discussions.microsoft.com> wrote in message
news:BAFDEF6E-33BF-4C6B-9066-8CD9F5347325@.microsoft.com...
> I have an Active/Active cluster with Windows 2003 with SQL Server 2000. I
> am trying to move the cluster disk T: owner to my other group.
> I keep receiving the following error:
> An error occurred attempting to change the group of the
> Disk T: to 'Other Resource' Group. The cluster node is not the owner of
the
> group. Error ID:5016
> I checked all cluster groups and they have both owners. I also checked
and
> there is no dependency on Disk T:
> Please help me with moving Disk T: to the Other Resource Group.
>
> Thanks,
|||And the SOLUTION would be to create a new resource group ("FOO") with no resources in it. Move it to the same node as the group that owns the resource you want to move. Now you can move the resource into the FOO resource group.
Move the FOO resource group to the node that owns the group to which you'd like to move the resource. Now you can move the resource to its destination.
Remove the FOO group and you are done.
This, of course, is only necessary if you can't move both resources to the same node for some reason.
HTH
jg

Quote:

Originally posted by Geoff N. Hiten
You can only change ownership of a resource from the node that currently
both resource groups.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
> I have an Active/Active cluster with Windows 2003 with SQL Server 2000. I
> am trying to move the cluster disk T: owner to my other group.
> I keep receiving the following error:
> An error occurred attempting to change the group of the
> Disk T: to 'Other Resource' Group. The cluster node is not the owner of[/vbcol]
the
> group. Error ID:5016
> I checked all cluster groups and they have both owners. I also checked
and
> there is no dependency on Disk T:
> Please help me with moving Disk T: to the Other Resource Group.
>
> Thanks,

|||Joe,
Geoff is correct.
Make sure you both groups are on the same node.
Then from that node, move the T: drive into the other resource group.
You will of course need to make sure T: is not a dependency of any other
resources prior to moving it.
Hope that helps!
Donna Lambert
Microsoft PSS
SQL Server Support

Change authentication modes

Can someone tell me how to change authentication modes from Windows
integrated to mixed mode after installation has taken place ?
I really dont want to reinstall if I can avoid it.
TIAEM, Right-click your server, properties, security tab.
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Poppy" <paul.diamond@.NOSPAMthemedialounge.com> wrote in message
news:%23OYP%23HRpDHA.3732@.tk2msftngp13.phx.gbl...
> Can someone tell me how to change authentication modes from Windows
> integrated to mixed mode after installation has taken place ?
> I really dont want to reinstall if I can avoid it.
> TIA
>|||Paul
Right click on your server in Enterprise Manager and
choose properties. On the security tab, you can change it
there.
Regards
John|||go to EM in that tools menu click on sql server configuration and click on
the security tab.
--
Shaju Thomas
e-Cosmos Technologies Ltd.,
Mail: shaju@.e-cosmostech.com
Phone(Off) : 51217037/38 Extn: 132
Mobile: +91 98455 21794
"Poppy" <paul.diamond@.NOSPAMthemedialounge.com> wrote in message
news:#OYP#HRpDHA.3732@.tk2msftngp13.phx.gbl...
> Can someone tell me how to change authentication modes from Windows
> integrated to mixed mode after installation has taken place ?
> I really dont want to reinstall if I can avoid it.
> TIA
>

Change Authentication

SQL Server has been installed using Windows Authentication.
I want to change one of my databases to mixed mode.
Can someone tell me if this is possible and how to go about it ?
TIAthe authentication is done at the server level so I don't think you can do
this at DB level.
anyone?
"Poppy" <paul.diamond@.NOSPAMthemedialounge.com> wrote in message
news:ucmjj36pDHA.2772@.TK2MSFTNGP12.phx.gbl...
> SQL Server has been installed using Windows Authentication.
> I want to change one of my databases to mixed mode.
> Can someone tell me if this is possible and how to go about it ?
> TIA
>|||Authentication modes apply to the server and can't be set
differently for individual databases.
-Sue
On Mon, 10 Nov 2003 17:13:00 -0000, "Poppy"
<paul.diamond@.NOSPAMthemedialounge.com> wrote:
>SQL Server has been installed using Windows Authentication.
>I want to change one of my databases to mixed mode.
>Can someone tell me if this is possible and how to go about it ?
>TIA
>

Wednesday, March 7, 2012

Change

Currently have a 2 node windows 2000 cluster, active/passive, with sql 2000
running a data vault that's controlled by node a. Would like to upgrade to
windows 2003, but run active/active with sql running on node b. To do this,
do I have to reinstall sql server? I'm at a loss and all help and any white
papers would be appreciated.
Thanks in advance.
Hi
Don't think of "active/passive" or "active/active", rather think of it as 2
nodes, with either one or 2 (or 3 or 4 etc) virtual servers.
Currently, you have 2 nodes, with one virtual server and you want to have 2
nodes with 2 virtual servers. Between the 2 nodes, there is a shared quorum
drive.
The virtual server you currently have has a name, an IP address and disk
groups associated with it. If you want an additional virtual server, you
need the same again, another name, another IP address and another set of
disk groups.
Only one node can own a disk group at a time, so it you have allocated all
the space on the SAN to one disk group, you do not have space to make more
virtual disks for the other node. You might need to buy higher capacity
drives, add drives or add another SAN, or reduce the size allocated to the
disk group that currently exists.
I have a strict policy. No OS Upgrades to clusters. Re-Installs only.
Especially if you have to re-do the disk groups, it gives you a chance to
re-do the cluster.
So, backup your databases to a safe place, off the SAN, wipe it, setup your
disks and then re-do the whole cluster.
Get to know the content on
http://www.microsoft.com/windowsserv...g/default.mspx
On the pages, there is a step by step on how to setup a SQL cluster:
http://www.microsoft.com/technet/pro.../failclus.mspx
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Scott" <Scott@.discussions.microsoft.com> wrote in message
news:B2FC1873-54BB-40F8-B0BD-CA25597A35E9@.microsoft.com...
> Currently have a 2 node windows 2000 cluster, active/passive, with sql
2000
> running a data vault that's controlled by node a. Would like to upgrade
to
> windows 2003, but run active/active with sql running on node b. To do
this,
> do I have to reinstall sql server? I'm at a loss and all help and any
white
> papers would be appreciated.
> Thanks in advance.
|||I have a slightly different approach. I will allow an OS node upgrade,
mainly to find out compatibility issues, then I go back and rebuild each
node from scratch.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:OIoWPIzLFHA.2492@.TK2MSFTNGP14.phx.gbl...
> Hi
> Don't think of "active/passive" or "active/active", rather think of it as
> 2
> nodes, with either one or 2 (or 3 or 4 etc) virtual servers.
> Currently, you have 2 nodes, with one virtual server and you want to have
> 2
> nodes with 2 virtual servers. Between the 2 nodes, there is a shared
> quorum
> drive.
> The virtual server you currently have has a name, an IP address and disk
> groups associated with it. If you want an additional virtual server, you
> need the same again, another name, another IP address and another set of
> disk groups.
> Only one node can own a disk group at a time, so it you have allocated all
> the space on the SAN to one disk group, you do not have space to make more
> virtual disks for the other node. You might need to buy higher capacity
> drives, add drives or add another SAN, or reduce the size allocated to the
> disk group that currently exists.
> I have a strict policy. No OS Upgrades to clusters. Re-Installs only.
> Especially if you have to re-do the disk groups, it gives you a chance to
> re-do the cluster.
> So, backup your databases to a safe place, off the SAN, wipe it, setup
> your
> disks and then re-do the whole cluster.
> Get to know the content on
> http://www.microsoft.com/windowsserv...g/default.mspx
> On the pages, there is a step by step on how to setup a SQL cluster:
> http://www.microsoft.com/technet/pro.../failclus.mspx
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Scott" <Scott@.discussions.microsoft.com> wrote in message
> news:B2FC1873-54BB-40F8-B0BD-CA25597A35E9@.microsoft.com...
> 2000
> to
> this,
> white
>
|||Thanks Mike and Geoff!!!!
It's pretty much what I figured, but was hoping not.
Again, THANKS!!!!
"Geoff N. Hiten" wrote:

> I have a slightly different approach. I will allow an OS node upgrade,
> mainly to find out compatibility issues, then I go back and rebuild each
> node from scratch.
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
>
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:OIoWPIzLFHA.2492@.TK2MSFTNGP14.phx.gbl...
>
>

Saturday, February 25, 2012

Certificate not recognized by SQL 2005 - Encryption Problem

Hi,

We recently upgraded from SQL 2K to SQL 2005 on WINDOWS 2003 Server. The entire upgrade process has run pretty smoothly aside from encryption.

We have ASP.NET 1.x apps that connect to an internal server but fail when encrypted. We have tried all of the steps available on the MS KB and still have not resolved the issue.

On http://msdn2.microsoft.com/en-us/library/ms191192.aspx, we find the following:
To configure the server to accept encrypted connections

1. In SQL Server Configuration Manager, expand SQL Server 2005 Network Configuration, right-click Protocols for <server instance>, and then selectProperties.
2. In the Protocols for<instance name> Properties dialog box, on the Certificate tab, select the desired certificate from the drop down for the Certificate box, and then click OK.
3. On the Flags tab, in the ForceEncryption box, select Yes, and then click OK to close the dialog box.
4. Restart the SQL Server service.

The problem is when we get to step 2, there are NO certificates available in the dropdown box.

This problem is solely the result of installing SQL Server 2005. The apps were successfully encrypting data connections prior to the install. All internal and non-encrypted connections work correctly and no other changes were made to the box aside from the SQL 2005 upgrade.

This issue has remained unresolved for almost two weeks now.... We have tried the KB articles many times over, none of which have made a difference. We have also created certificates many times over, checking Server Authentication in the EKU section and making sure the cert has a private key. The expiration date on the certs we create are in 2009 and are named using the FQDN. Clearly, I'm no certificate expert, but there has got to be something we're missing with the certificates since every other app connection works like it should

What can I do to get certificates to appear in the Certificate tab of the Properties dialog box? What else would you recommend?

Many thanks.

-Matt

Orcabbelle,

To help you troubleshoot this issue, I need you to share some more info,

(1) ERRORLOG of the SQL Server,

You should be able to find it under place similar to

'C:\Program Files\Microsoft SQL Server\MSSQL.XX\MSSQL\LOG\ERRORLOG''

Extract specific lines that show certificate if any.

(2) Run certutil.exe as

certutil.exe -v -store my.

pasted the output w.r.t the cert that you have just installed here.

Generally, there is also way to modify the registry value to force server encryption. But it is not recommended because it is errorprone. Let me know if you want to do that to get you problem solved faster.

|||Nan,

There is only one relevant line I can find in the errorlog:
2006-04-04 11:11:03.59 Server A self-generated certificate was successfully loaded for encryption.

Not sure what this means or where I can find the self-generated cert. Is it the cert in with the data files?

As for #2, we ran the cmd line you suggested and everything looks good aside from:
CERT_ARCHIVED_PROP_ID(19):
3988ce37fa66df4b79d75bb63c7f8d0d_c381bd65-7971-4be2-9c1b-aef143aed909
ERROR: Certificate public key does NOT match stored keyset

|||

So the certificate you are using is corrupted somehow.

One possible reason is that you have a previous installed certificate, and the newly installed certificate does not have permission to over write the private key of the old one. I am assuming you do have a certificates that have both public key and private key is expotable.

Try to clean up your certificate store using MMC. that have same FQDN as this new one has. Then install the certificate in the local store. Try to run as local admin to clean/install the certificate.

Let me know what you get.

Selfsigned certificate is newly added feature in SS2k5 that help to encrypt even user does not have certificate. the self signed certificate is stored in master database. It is briefly mentioned here. As result, it is possible to force encryption without provisioning a valid certificate in SS2k5

http://blogs.msdn.com/sql_protocols/archive/2005/10/04/476705.aspx

|||We cleaned up our MMC and our new cert seems to be fine (not corrupted). We want to use our cert, not the self-signed cert.

As soon as we upgraded, all of our ASP.NET apps that were using Encrypt=True in their connection strings simply stopped working. Nothing else on either box, the server or the client, was changed. We changed the connection string to Encrypt=False and the apps work like they should, aside from not being encrypted. What could cause this?

We have tried just about every MS KB article and recommendation we can find. We created new certificates using a CA server. We made sure they have had private keys and allowed server authentication. Force protocol encryption is set to YES on the server.

We have never been able to get the certificate we create to appear in the list. We are logging on the server as the domain admin and starting the service under the same account.

Any ideas why we can't see the cert in the list or why the encryption failed after a SQL upgrade?

Many thanks!
|||

First, Your sql service should run under admin account, otherwise it has no permissing to the private key and thus the cert would not show up in the drop down list of SSCM, visit KB article for more detail:
http://support.microsoft.com/?kbid=900495.


Secondly, SQL Server 2005 has a new kind cert called self-signed certificate, which means when server can not find a good cert to load in the cert store, it will load such a self-signed cert. the encryption failure you saw is due to the reason that your server might load a self-signed cert(To verify this, you can go to server errorlog and see there is keyword "self-signed certificate"), and you forced client encryption through setting "Encrypt=True". If you already forced server encryption, the connection should be encrypted. And if you require forcing client encryption, you need to have server loading a certificate issued by a trusted CA.

Thirdly, please run "certutil.exe -v -store my", the tool would verify whether the certs you installed are valid;and try change sql service running under LocalSystem account, see whether any cert appear in the list.

|||

The only thing that I can think of is that the certificates that you are generating and the one you used for SS2K do not meet the stricter requirements of SS2K5. Please have a look at this post to see what properties we require from a cert:
http://blogs.msdn.com/sql_protocols/archive/2005/12/30/508311.aspx.

Thanks,
Il-Sung.

|||II-Sung, thanks again for your help.

Ok, IT has had a look at what you said and has had trouble with #4 found on the link you provided.

4) The Certficate’s key usage must include AT_KEYEXCHANGE property, which means Key Encipherment (a0)

They were able to find the Key Encipherment value but ours is not (a0), it's (f0). Not sure if this makes a difference or not.

From running "certutil.exe -v -store my":

Key Usage

Digital Signature, Non-Repudiation, Key Encipherment, Data Encipherment (f0)

|||

Hi Orcabelle,

Would you be able to try using a certificate that has a key usage of 0xA0 instead of 0xF0 and see if that makes a difference?

Also, could you indicate whether you're generating your own self-signed certificate? If so, what is the command that you're using the generate it. I believe it should be similar to:

makecert -r -pe -n "CN= MySQLServerName" -b 01/01/2000 -e 01/01/2036 -eku 1.3.6.1.5.5.7.3.1 -ss my -sr localMachine -sky exchange -sp "Microsoft RSA SChannel Cryptographic Provider" -sy 12

Thanks,
Il-Sung.

|||At this point we're happy to try anything....

Now my question is, how do I change key usage from F to A?
|||

Hi Orcabelle,

I did some more looking into this and a key usage of f0 is perfectly fine. This is very perplexing problem. Could you please confirm that you're looking at the correct entry of the "certutil.exe -v -store my" output? i.e., you've properly correlated the cert hash with the one in the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.x\MSSQLServer\SuperSocketNetLib\Certificate registry key?

Thanks,
Il-Sung.

|||II-Sung,

We have the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.x\MSSQLServer\SuperSocketNetLib\Certificate, but it has no value. We also have the cert hash data, but what syntax should the key be in?

If the cert hash is supposed to automatically appear in this registry key, it does not. When the key value is changed to match the thumbprint (cert hash (sha1)) of the certificate then the MSSQL service will not start. When the value is blanked the service starts as it should.
|||Here is the error we recieve from asp.net 2.0 when Encrypt=True...

"System.Data.SqlClient.SqlException: A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: SSL Provider, error: 0 - The certificate chain was issued by an authority that is not trusted.)
at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at System.Data.Common.DbDataAdapter.QuietOpen(IDbConnection connection, ConnectionState& originalState)
at System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataTable[] dataTables, Int32 startRecord, Int32 maxRecords, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataTable dataTable)
at Security.GetSystemData() in C:\Inetpub\screen\App_Code\Security.vb:line 109
at Security.SecurityCheck() in C:\Inetpub\screen\App_Code\Security.vb:line 94"
|||

Orcabelle,

(1) To configure the server hash in sqlserver 2005, you need to put the ascii form of the Thumbprint in to the registry mentioned above, without any spacec in between and before and after, for example "06065fbcc0fd1b45b04dd67fd236673a9aa6563c". If the certificate specified in the hash is not a valid one from the point a view of sql server, sql server will fail to started. If your case if later, you can look the errorlog, look for certificate related and find what is the root cause.

(2) If you force encryption in the client, asp2.0 in your case, and that the server happens to use a self-signed certificate or a certificate that is not trusted by the client, you will see the error "The certificate chain was issued by an authority that is not trusted". In such case, in order to still use encryption, you can add a connection string property,

"TrustServerCertificate = true", such that client does not validate certificate hierarchy.

http://msdn2.microsoft.com/en-US/library/system.data.sqlclient.sqlconnection.connectionstring(VS.80).aspx

SQL book online, "Using Encryption Without Validation" in SQL Server 2005 Books Online." also have related info.

|||So after speaking with Microsoft, we have determined the issue, but we're still awaiting a possible resolution.

The problem we've run into is caused by our using both an internal (abc.local) and external (xyz.com) domain. All this time, we had been using the FQDN for our external domain, but this wasn't being recognized by SQL Server 2005. As soon as we created a certificate using the FQDN for our internal domain, it was recognized.

That said, we still don't know for sure whether client based encryption is possible using SQL Server 2005 with valid but different named domains. We have tested and server based encryption does seem to work, but we still want to know why client based does not. It should be a two way street or so they say.

Anyway, thank you all for the help you provided. I will post Microsoft's response/recommendations once we hear from them.

Have a good day.

-Matt

Certificate creation problem

Hello to all

I have two SQL 2005 server and I want to start mirroring a database.
Since there's no windows domain I'm trying to use certificates to grant connection between servers.

At this point I find some difficulties...

I've read on MSDN that 'active FOR begin_dialog = ON' option must be specified; look at the code below, when I execute I get following error:

Msg 156, Level 15, State 1, Line 8

Incorrect syntax near the keyword 'FOR'.


CREATE CERTIFICATE Polx

WITH SUBJECT = 'Mirror certificate',

START_DATE = '10/31/2001',

EXPIRY_DATE = '10/31/2009',

active FOR begin_dialog = ON;

GO

CREATE SYMMETRIC KEY Key1

WITH ALGORITHM = RC4

ENCRYPTION BY CERTIFICATE Polx

GO

Any suggestion will be really appreciated!!!

By the way, do I have to create same certificate on the mirror server after creating it on the master?

Thanks, Carlo

You should try removing the comma before the ACTIVE keyword. From my experience with database mirroring, however, I don't remember this clause being required. The certificate used for mirroring needs to exist on both the principal and the mirror.

Thanks
Laurentiu|||

Here's some additional information about setting up database mirroring. I hope this will help:

http://blogs.msdn.com/lcris/archive/2005/09/14/466268.aspx

Thanks
Laurentiu

Centura-Gupta 1.5 and Windows XP

Good day,
We recently change our PC's to Windows XP. I reinstalled all of my application programs including Centura. This is a quite an old version (95/NT), but is the only one we are going to work with for now.
Every time I try to run the program, the Windows Installer popup window comes up. I have installed and reinstalled the program several times, even from backups.
How can I make XP to install a workable program? I already tried the compatibility thing. Every time I uninstall the program I clear all registries, links, anything I can think of.
Thank you.
Is this the old Gupta SQLWindows product? You might have more luck asking
the folks that wrote it, http://www.centurasoft.com/.
Sincerely,
Stephen Dybing
This posting is provided "AS IS" with no warranties, and confers no rights.
"M. Garcia" <anonymous@.discussions.microsoft.com> wrote in message
news:F83BAB58-9C0E-4909-9E4B-9F6B72799963@.microsoft.com...
> Good day,
> We recently change our PC's to Windows XP. I reinstalled all of my
application programs including Centura. This is a quite an old version
(95/NT), but is the only one we are going to work with for now.
> Every time I try to run the program, the Windows Installer popup window
comes up. I have installed and reinstalled the program several times, even
from backups.
> How can I make XP to install a workable program? I already tried the
compatibility thing. Every time I uninstall the program I clear all
registries, links, anything I can think of.
> Thank you.
>

Tuesday, February 14, 2012

Catch22

Hi all,
Our SQL server hardware died and we bought a new server with Windows 2003
server. We have the SQL 2000 CD and the CD with service pack 3a.
When we try to install SQL 2000 we get the warning that anything below SP3
is not supported on W2003 and the installation fails at the server
configuration. We can start the server but starting the Agent fails. We
thought that we might win and tried to run SP3 anyhow but the install stops
with the message that there is no SQL installed.
Does anybody have an idea how we get around this? We searched the KB and
didn't come up with anything.
Thanks for your help
ClausYou will need to download and apply SP3a in order for SQL Server 2000 to
work properly.
"cjobes" <cjobes@.nova-tech.org> wrote in message
news:OMUxbvFaEHA.2908@.TK2MSFTNGP10.phx.gbl...
> Hi all,
> Our SQL server hardware died and we bought a new server with Windows 2003
> server. We have the SQL 2000 CD and the CD with service pack 3a.
> When we try to install SQL 2000 we get the warning that anything below SP3
> is not supported on W2003 and the installation fails at the server
> configuration. We can start the server but starting the Agent fails. We
> thought that we might win and tried to run SP3 anyhow but the install
stops
> with the message that there is no SQL installed.
> Does anybody have an idea how we get around this? We searched the KB and
> didn't come up with anything.
> Thanks for your help
> Claus
>|||Sorry.. short read your message. Try uninstalling SQL Server, reboot,
re-install SQL Server, apply SP3 -before- restarting again.
"Morgan" <abcd@.senditon.com> wrote in message
news:ubUybFHaEHA.2488@.tk2msftngp13.phx.gbl...
> You will need to download and apply SP3a in order for SQL Server 2000 to
> work properly.
> "cjobes" <cjobes@.nova-tech.org> wrote in message
> news:OMUxbvFaEHA.2908@.TK2MSFTNGP10.phx.gbl...
> > Hi all,
> >
> > Our SQL server hardware died and we bought a new server with Windows
2003
> > server. We have the SQL 2000 CD and the CD with service pack 3a.
> > When we try to install SQL 2000 we get the warning that anything below
SP3
> > is not supported on W2003 and the installation fails at the server
> > configuration. We can start the server but starting the Agent fails. We
> > thought that we might win and tried to run SP3 anyhow but the install
> stops
> > with the message that there is no SQL installed.
> >
> > Does anybody have an idea how we get around this? We searched the KB and
> > didn't come up with anything.
> >
> > Thanks for your help
> > Claus
> >
> >
>|||You can install past the warning. SQL agent will fail since Windows 2003
disables the network libraries on any installation below SP3. Start and
stop the SQL server instance once after the base install. You can then
install SP3a. Once SP3a is installed, everything should be fine. You may
have to get refreshed media (SQL 2000a) for the install on Windows 2003 to
work correctly.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"cjobes" <cjobes@.nova-tech.org> wrote in message
news:OMUxbvFaEHA.2908@.TK2MSFTNGP10.phx.gbl...
> Hi all,
> Our SQL server hardware died and we bought a new server with Windows 2003
> server. We have the SQL 2000 CD and the CD with service pack 3a.
> When we try to install SQL 2000 we get the warning that anything below SP3
> is not supported on W2003 and the installation fails at the server
> configuration. We can start the server but starting the Agent fails. We
> thought that we might win and tried to run SP3 anyhow but the install
stops
> with the message that there is no SQL installed.
> Does anybody have an idea how we get around this? We searched the KB and
> didn't come up with anything.
> Thanks for your help
> Claus
>|||Geoff/Morgan
The SQL installation fails at the server configuration. No SQL instance is
present and SP3 will not install because it doesn't find the server. When I
searched the KBs I did find one that said if the server name is small or
mixed letters it could fail. I renamed the server all caps but the problem
is still the same.
Claus
"Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
news:uUXS3jHaEHA.3420@.TK2MSFTNGP12.phx.gbl...
> You can install past the warning. SQL agent will fail since Windows 2003
> disables the network libraries on any installation below SP3. Start and
> stop the SQL server instance once after the base install. You can then
> install SP3a. Once SP3a is installed, everything should be fine. You may
> have to get refreshed media (SQL 2000a) for the install on Windows 2003 to
> work correctly.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "cjobes" <cjobes@.nova-tech.org> wrote in message
> news:OMUxbvFaEHA.2908@.TK2MSFTNGP10.phx.gbl...
> > Hi all,
> >
> > Our SQL server hardware died and we bought a new server with Windows
2003
> > server. We have the SQL 2000 CD and the CD with service pack 3a.
> > When we try to install SQL 2000 we get the warning that anything below
SP3
> > is not supported on W2003 and the installation fails at the server
> > configuration. We can start the server but starting the Agent fails. We
> > thought that we might win and tried to run SP3 anyhow but the install
> stops
> > with the message that there is no SQL installed.
> >
> > Does anybody have an idea how we get around this? We searched the KB and
> > didn't come up with anything.
> >
> > Thanks for your help
> > Claus
> >
> >
>|||Try getting a copy of SQL 2000a. I had similar problems with SQL 2000
Standard Edition on Windows 20003 Standard Edition. If you have an Open or
Select license you can download the correct version, otherwise you will
probably have to contact Microsoft directly for a media refresh. SQL 2000a
is SQL 2000 with the Slammer work patch. Windows 2003 will recognize the
patched DLL and allow you to install correectly. YOu will still have to
install SP3a, but you should at least get past where you are stuck now.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"cjobes" <cjobes@.nova-tech.org> wrote in message
news:eIzMqqHaEHA.1652@.TK2MSFTNGP09.phx.gbl...
> Geoff/Morgan
> The SQL installation fails at the server configuration. No SQL instance is
> present and SP3 will not install because it doesn't find the server. When
I
> searched the KBs I did find one that said if the server name is small or
> mixed letters it could fail. I renamed the server all caps but the problem
> is still the same.
> Claus
> "Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
> news:uUXS3jHaEHA.3420@.TK2MSFTNGP12.phx.gbl...
> > You can install past the warning. SQL agent will fail since Windows
2003
> > disables the network libraries on any installation below SP3. Start and
> > stop the SQL server instance once after the base install. You can then
> > install SP3a. Once SP3a is installed, everything should be fine. You
may
> > have to get refreshed media (SQL 2000a) for the install on Windows 2003
to
> > work correctly.
> >
> > --
> > Geoff N. Hiten
> > Microsoft SQL Server MVP
> > Senior Database Administrator
> > Careerbuilder.com
> >
> > I support the Professional Association for SQL Server
> > www.sqlpass.org
> >
> > "cjobes" <cjobes@.nova-tech.org> wrote in message
> > news:OMUxbvFaEHA.2908@.TK2MSFTNGP10.phx.gbl...
> > > Hi all,
> > >
> > > Our SQL server hardware died and we bought a new server with Windows
> 2003
> > > server. We have the SQL 2000 CD and the CD with service pack 3a.
> > > When we try to install SQL 2000 we get the warning that anything below
> SP3
> > > is not supported on W2003 and the installation fails at the server
> > > configuration. We can start the server but starting the Agent fails.
We
> > > thought that we might win and tried to run SP3 anyhow but the install
> > stops
> > > with the message that there is no SQL installed.
> > >
> > > Does anybody have an idea how we get around this? We searched the KB
and
> > > didn't come up with anything.
> > >
> > > Thanks for your help
> > > Claus
> > >
> > >
> >
> >
>|||Thanks,
Claus
"Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
news:%23kGzetHaEHA.2812@.TK2MSFTNGP11.phx.gbl...
> Try getting a copy of SQL 2000a. I had similar problems with SQL 2000
> Standard Edition on Windows 20003 Standard Edition. If you have an Open
or
> Select license you can download the correct version, otherwise you will
> probably have to contact Microsoft directly for a media refresh. SQL
2000a
> is SQL 2000 with the Slammer work patch. Windows 2003 will recognize the
> patched DLL and allow you to install correectly. YOu will still have to
> install SP3a, but you should at least get past where you are stuck now.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "cjobes" <cjobes@.nova-tech.org> wrote in message
> news:eIzMqqHaEHA.1652@.TK2MSFTNGP09.phx.gbl...
> > Geoff/Morgan
> >
> > The SQL installation fails at the server configuration. No SQL instance
is
> > present and SP3 will not install because it doesn't find the server.
When
> I
> > searched the KBs I did find one that said if the server name is small or
> > mixed letters it could fail. I renamed the server all caps but the
problem
> > is still the same.
> >
> > Claus
> >
> > "Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
> > news:uUXS3jHaEHA.3420@.TK2MSFTNGP12.phx.gbl...
> > > You can install past the warning. SQL agent will fail since Windows
> 2003
> > > disables the network libraries on any installation below SP3. Start
and
> > > stop the SQL server instance once after the base install. You can
then
> > > install SP3a. Once SP3a is installed, everything should be fine. You
> may
> > > have to get refreshed media (SQL 2000a) for the install on Windows
2003
> to
> > > work correctly.
> > >
> > > --
> > > Geoff N. Hiten
> > > Microsoft SQL Server MVP
> > > Senior Database Administrator
> > > Careerbuilder.com
> > >
> > > I support the Professional Association for SQL Server
> > > www.sqlpass.org
> > >
> > > "cjobes" <cjobes@.nova-tech.org> wrote in message
> > > news:OMUxbvFaEHA.2908@.TK2MSFTNGP10.phx.gbl...
> > > > Hi all,
> > > >
> > > > Our SQL server hardware died and we bought a new server with Windows
> > 2003
> > > > server. We have the SQL 2000 CD and the CD with service pack 3a.
> > > > When we try to install SQL 2000 we get the warning that anything
below
> > SP3
> > > > is not supported on W2003 and the installation fails at the server
> > > > configuration. We can start the server but starting the Agent fails.
> We
> > > > thought that we might win and tried to run SP3 anyhow but the
install
> > > stops
> > > > with the message that there is no SQL installed.
> > > >
> > > > Does anybody have an idea how we get around this? We searched the KB
> and
> > > > didn't come up with anything.
> > > >
> > > > Thanks for your help
> > > > Claus
> > > >
> > > >
> > >
> > >
> >
> >
>

Catch22

Hi all,
Our SQL server hardware died and we bought a new server with Windows 2003
server. We have the SQL 2000 CD and the CD with service pack 3a.
When we try to install SQL 2000 we get the warning that anything below SP3
is not supported on W2003 and the installation fails at the server
configuration. We can start the server but starting the Agent fails. We
thought that we might win and tried to run SP3 anyhow but the install stops
with the message that there is no SQL installed.
Does anybody have an idea how we get around this? We searched the KB and
didn't come up with anything.
Thanks for your help
Claus
You will need to download and apply SP3a in order for SQL Server 2000 to
work properly.
"cjobes" <cjobes@.nova-tech.org> wrote in message
news:OMUxbvFaEHA.2908@.TK2MSFTNGP10.phx.gbl...
> Hi all,
> Our SQL server hardware died and we bought a new server with Windows 2003
> server. We have the SQL 2000 CD and the CD with service pack 3a.
> When we try to install SQL 2000 we get the warning that anything below SP3
> is not supported on W2003 and the installation fails at the server
> configuration. We can start the server but starting the Agent fails. We
> thought that we might win and tried to run SP3 anyhow but the install
stops
> with the message that there is no SQL installed.
> Does anybody have an idea how we get around this? We searched the KB and
> didn't come up with anything.
> Thanks for your help
> Claus
>
|||Sorry.. short read your message. Try uninstalling SQL Server, reboot,
re-install SQL Server, apply SP3 -before- restarting again.
"Morgan" <abcd@.senditon.com> wrote in message
news:ubUybFHaEHA.2488@.tk2msftngp13.phx.gbl...[vbcol=seagreen]
> You will need to download and apply SP3a in order for SQL Server 2000 to
> work properly.
> "cjobes" <cjobes@.nova-tech.org> wrote in message
> news:OMUxbvFaEHA.2908@.TK2MSFTNGP10.phx.gbl...
2003[vbcol=seagreen]
SP3
> stops
>
|||You can install past the warning. SQL agent will fail since Windows 2003
disables the network libraries on any installation below SP3. Start and
stop the SQL server instance once after the base install. You can then
install SP3a. Once SP3a is installed, everything should be fine. You may
have to get refreshed media (SQL 2000a) for the install on Windows 2003 to
work correctly.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"cjobes" <cjobes@.nova-tech.org> wrote in message
news:OMUxbvFaEHA.2908@.TK2MSFTNGP10.phx.gbl...
> Hi all,
> Our SQL server hardware died and we bought a new server with Windows 2003
> server. We have the SQL 2000 CD and the CD with service pack 3a.
> When we try to install SQL 2000 we get the warning that anything below SP3
> is not supported on W2003 and the installation fails at the server
> configuration. We can start the server but starting the Agent fails. We
> thought that we might win and tried to run SP3 anyhow but the install
stops
> with the message that there is no SQL installed.
> Does anybody have an idea how we get around this? We searched the KB and
> didn't come up with anything.
> Thanks for your help
> Claus
>
|||Geoff/Morgan
The SQL installation fails at the server configuration. No SQL instance is
present and SP3 will not install because it doesn't find the server. When I
searched the KBs I did find one that said if the server name is small or
mixed letters it could fail. I renamed the server all caps but the problem
is still the same.
Claus
"Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
news:uUXS3jHaEHA.3420@.TK2MSFTNGP12.phx.gbl...[vbcol=seagreen]
> You can install past the warning. SQL agent will fail since Windows 2003
> disables the network libraries on any installation below SP3. Start and
> stop the SQL server instance once after the base install. You can then
> install SP3a. Once SP3a is installed, everything should be fine. You may
> have to get refreshed media (SQL 2000a) for the install on Windows 2003 to
> work correctly.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "cjobes" <cjobes@.nova-tech.org> wrote in message
> news:OMUxbvFaEHA.2908@.TK2MSFTNGP10.phx.gbl...
2003[vbcol=seagreen]
SP3
> stops
>
|||Try getting a copy of SQL 2000a. I had similar problems with SQL 2000
Standard Edition on Windows 20003 Standard Edition. If you have an Open or
Select license you can download the correct version, otherwise you will
probably have to contact Microsoft directly for a media refresh. SQL 2000a
is SQL 2000 with the Slammer work patch. Windows 2003 will recognize the
patched DLL and allow you to install correectly. YOu will still have to
install SP3a, but you should at least get past where you are stuck now.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"cjobes" <cjobes@.nova-tech.org> wrote in message
news:eIzMqqHaEHA.1652@.TK2MSFTNGP09.phx.gbl...
> Geoff/Morgan
> The SQL installation fails at the server configuration. No SQL instance is
> present and SP3 will not install because it doesn't find the server. When
I[vbcol=seagreen]
> searched the KBs I did find one that said if the server name is small or
> mixed letters it could fail. I renamed the server all caps but the problem
> is still the same.
> Claus
> "Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
> news:uUXS3jHaEHA.3420@.TK2MSFTNGP12.phx.gbl...
2003[vbcol=seagreen]
may[vbcol=seagreen]
to[vbcol=seagreen]
> 2003
> SP3
We[vbcol=seagreen]
and
>
|||Thanks,
Claus
"Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
news:%23kGzetHaEHA.2812@.TK2MSFTNGP11.phx.gbl...
> Try getting a copy of SQL 2000a. I had similar problems with SQL 2000
> Standard Edition on Windows 20003 Standard Edition. If you have an Open
or
> Select license you can download the correct version, otherwise you will
> probably have to contact Microsoft directly for a media refresh. SQL
2000a[vbcol=seagreen]
> is SQL 2000 with the Slammer work patch. Windows 2003 will recognize the
> patched DLL and allow you to install correectly. YOu will still have to
> install SP3a, but you should at least get past where you are stuck now.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "cjobes" <cjobes@.nova-tech.org> wrote in message
> news:eIzMqqHaEHA.1652@.TK2MSFTNGP09.phx.gbl...
is[vbcol=seagreen]
When[vbcol=seagreen]
> I
problem[vbcol=seagreen]
> 2003
and[vbcol=seagreen]
then[vbcol=seagreen]
> may
2003[vbcol=seagreen]
> to
below[vbcol=seagreen]
> We
install
> and
>

Catch22

Hi all,
Our SQL server hardware died and we bought a new server with Windows 2003
server. We have the SQL 2000 CD and the CD with service pack 3a.
When we try to install SQL 2000 we get the warning that anything below SP3
is not supported on W2003 and the installation fails at the server
configuration. We can start the server but starting the Agent fails. We
thought that we might win and tried to run SP3 anyhow but the install stops
with the message that there is no SQL installed.
Does anybody have an idea how we get around this? We searched the KB and
didn't come up with anything.
Thanks for your help
ClausYou will need to download and apply SP3a in order for SQL Server 2000 to
work properly.
"cjobes" <cjobes@.nova-tech.org> wrote in message
news:OMUxbvFaEHA.2908@.TK2MSFTNGP10.phx.gbl...
> Hi all,
> Our SQL server hardware died and we bought a new server with Windows 2003
> server. We have the SQL 2000 CD and the CD with service pack 3a.
> When we try to install SQL 2000 we get the warning that anything below SP3
> is not supported on W2003 and the installation fails at the server
> configuration. We can start the server but starting the Agent fails. We
> thought that we might win and tried to run SP3 anyhow but the install
stops
> with the message that there is no SQL installed.
> Does anybody have an idea how we get around this? We searched the KB and
> didn't come up with anything.
> Thanks for your help
> Claus
>|||Sorry.. short read your message. Try uninstalling SQL Server, reboot,
re-install SQL Server, apply SP3 -before- restarting again.
"Morgan" <abcd@.senditon.com> wrote in message
news:ubUybFHaEHA.2488@.tk2msftngp13.phx.gbl...
> You will need to download and apply SP3a in order for SQL Server 2000 to
> work properly.
> "cjobes" <cjobes@.nova-tech.org> wrote in message
> news:OMUxbvFaEHA.2908@.TK2MSFTNGP10.phx.gbl...
2003[vbcol=seagreen]
SP3[vbcol=seagreen]
> stops
>|||You can install past the warning. SQL agent will fail since Windows 2003
disables the network libraries on any installation below SP3. Start and
stop the SQL server instance once after the base install. You can then
install SP3a. Once SP3a is installed, everything should be fine. You may
have to get refreshed media (SQL 2000a) for the install on Windows 2003 to
work correctly.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"cjobes" <cjobes@.nova-tech.org> wrote in message
news:OMUxbvFaEHA.2908@.TK2MSFTNGP10.phx.gbl...
> Hi all,
> Our SQL server hardware died and we bought a new server with Windows 2003
> server. We have the SQL 2000 CD and the CD with service pack 3a.
> When we try to install SQL 2000 we get the warning that anything below SP3
> is not supported on W2003 and the installation fails at the server
> configuration. We can start the server but starting the Agent fails. We
> thought that we might win and tried to run SP3 anyhow but the install
stops
> with the message that there is no SQL installed.
> Does anybody have an idea how we get around this? We searched the KB and
> didn't come up with anything.
> Thanks for your help
> Claus
>|||Geoff/Morgan
The SQL installation fails at the server configuration. No SQL instance is
present and SP3 will not install because it doesn't find the server. When I
searched the KBs I did find one that said if the server name is small or
mixed letters it could fail. I renamed the server all caps but the problem
is still the same.
Claus
"Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
news:uUXS3jHaEHA.3420@.TK2MSFTNGP12.phx.gbl...
> You can install past the warning. SQL agent will fail since Windows 2003
> disables the network libraries on any installation below SP3. Start and
> stop the SQL server instance once after the base install. You can then
> install SP3a. Once SP3a is installed, everything should be fine. You may
> have to get refreshed media (SQL 2000a) for the install on Windows 2003 to
> work correctly.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "cjobes" <cjobes@.nova-tech.org> wrote in message
> news:OMUxbvFaEHA.2908@.TK2MSFTNGP10.phx.gbl...
2003[vbcol=seagreen]
SP3[vbcol=seagreen]
> stops
>|||Try getting a copy of SQL 2000a. I had similar problems with SQL 2000
Standard Edition on Windows 20003 Standard Edition. If you have an Open or
Select license you can download the correct version, otherwise you will
probably have to contact Microsoft directly for a media refresh. SQL 2000a
is SQL 2000 with the Slammer work patch. Windows 2003 will recognize the
patched DLL and allow you to install correectly. YOu will still have to
install SP3a, but you should at least get past where you are stuck now.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"cjobes" <cjobes@.nova-tech.org> wrote in message
news:eIzMqqHaEHA.1652@.TK2MSFTNGP09.phx.gbl...
> Geoff/Morgan
> The SQL installation fails at the server configuration. No SQL instance is
> present and SP3 will not install because it doesn't find the server. When
I
> searched the KBs I did find one that said if the server name is small or
> mixed letters it could fail. I renamed the server all caps but the problem
> is still the same.
> Claus
> "Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
> news:uUXS3jHaEHA.3420@.TK2MSFTNGP12.phx.gbl...
2003[vbcol=seagreen]
may[vbcol=seagreen]
to[vbcol=seagreen]
> 2003
> SP3
We[vbcol=seagreen]
and[vbcol=seagreen]
>|||Thanks,
Claus
"Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
news:%23kGzetHaEHA.2812@.TK2MSFTNGP11.phx.gbl...
> Try getting a copy of SQL 2000a. I had similar problems with SQL 2000
> Standard Edition on Windows 20003 Standard Edition. If you have an Open
or
> Select license you can download the correct version, otherwise you will
> probably have to contact Microsoft directly for a media refresh. SQL
2000a
> is SQL 2000 with the Slammer work patch. Windows 2003 will recognize the
> patched DLL and allow you to install correectly. YOu will still have to
> install SP3a, but you should at least get past where you are stuck now.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "cjobes" <cjobes@.nova-tech.org> wrote in message
> news:eIzMqqHaEHA.1652@.TK2MSFTNGP09.phx.gbl...
is[vbcol=seagreen]
When[vbcol=seagreen]
> I
problem[vbcol=seagreen]
> 2003
and[vbcol=seagreen]
then[vbcol=seagreen]
> may
2003[vbcol=seagreen]
> to
below[vbcol=seagreen]
> We
install[vbcol=seagreen]
> and
>

Catastrophic Error.

Hi. I've Windows 2000 Advanced Server with Service Pack4. Sql-Enterprise with Service pack3.
There's a strange error when i try to open a table for records through Enterprise-Manager; it says "Catastrophic Error" and some times it says "Class not registered". However Query-Analyzer works fine. I can't connect through any Client-Server application to any database, same error.
I've reinstalled SQL thrice but the same problem. Please suggest if any one has faced this problem.
Regards.Its problem with the client tools installed on the machine and never use EM tool to return the records, QA is the best bet.

Replace the client tools alongwith service pack to get rid of the issue.|||Thanx for ur kind response, Satya. As i mentioned; i've tried reinstalling SQL. If i remove the database and reinstall only the client tools, the same problem persists. Neither i can connect through any Client-Server application with or without the client tools. I need to reinstall the operating-sys i guess.
Regards.|||Before going for big-shot lets go this way :
Uninstall client tools and remove all SQL referenced registry keys then reboot.

Perform fresh install from another CD (if avilable) and see the results.

If the problem persists then think about replacing the OS files and I'm sure this is something to do with SQL tools only in some sort of mis-match of DLLs.

BTW,|||Same error; "class not registered". However i am greatful to u for ur kind replies. How do i replace the operating system files; by choosing the "repair" option while installation of operating-system?|||Yes|||I have the exact same problem, did you get a solution for this?|||I have also heard of this but have not had the problem. Is it the case that the OS was installed and patched to SP4 before installing SQL? I think that's the cause, but it's only a theory. Maybe this order is better:

O/S to SP3
SQL to SP3a
O/S to SP4

?

OSCI|||In my case I use windows 2003 server (standard) then SQL 2000 and sp3.
I tried to reinstall everything except the OS..