Thursday, March 29, 2012
Change IP in SQL Cluster
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
Saturday, February 25, 2012
Certification Exam on reporting service
--
SincerelyThere is course 2030
(http://www.microsoft.com/traincert/syllabi/2030AFINAL.ASP) but it is not
part of any certification track yet.
--
Hope this helps.
---
Teo Lachev, MCSD, MCT
Author: "Microsoft Reporting Services in Action"
http://www.prologika.com
"Frank RS" <FrankRS@.discussions.microsoft.com> wrote in message
news:AD66A6C8-22D8-4388-86BE-3060C84013F1@.microsoft.com...
> Does anybody have any idea if there is certification exam yet?
> --
> Sincerely
>
Certificate not found
Hello I haw trouble getting the service broker to work I have 3 instances of SQL servers:
1 “Sender”SQL 2005 Server
2 “Receiver 1” SQLEXPRESS 2005
3 “Recevier 2” SQLEXPRESS 2005
What I wont is to be abele to do is to send a message from “Sender” to “Receiver 1” or “Recevier 2”.
I am abele to send a message from “Sender” to “Receiver 1” but if I send a message to “Receiver 2” I get a dialog security problem I think. If I use profiler I can se in “Receiver 2” the events:
Broker:Connection
Audit Broker Login
Broker:Message Classify
Audit Broker Conversation = Certificate not found
Broker:Message Undeliverable
And I cant find what′s wrong, this Is my scripts for etch instance.
“Sender”
USE master
CREATE CERTIFICATE Cert_ROBOTSRV
WITH SUBJECT = 'Cert_ROBOTSRV_auth',
START_DATE = '02/15/2007',
EXPIRY_DATE = '02/15/2015'
GO
BACKUP CERTIFICATE Cert_ROBOTSRV TO FILE = 'C:\Cert_ROBOTSRV'
GO
CREATE ENDPOINT SBEndpointServer STATE = STARTED
AS TCP (LISTENER_PORT = 5723)
FOR SERVICE_BROKER (AUTHENTICATION = CERTIFICATE Cert_ROBOTSRV)
GO
CREATE USER andon
CREATE CERTIFICATE Cert_sevapc311_pub AUTHORIZATION andon
FROM FILE = 'C:\Cert_sevapc311'
--DROP CERTIFICATE Cert_Andonpc017_Trans
CREATE CERTIFICATE Cert_Andonpc017_Trans AUTHORIZATION andon
FROM FILE = 'C:\Cert_andonpc017_Trans'
--DROP LOGIN sbLogin
CREATE LOGIN sbLogin
FROM CERTIFICATE Cert_Andonpc017_Trans;
GO
GRANT CONNECT ON ENDPOINT::SBEndpointServer TO [public]
GRANT CONNECT ON ENDPOINT::SBEndpointServer TO andon
GO
-
USE AndonDB
CREATE ROUTE Grafik_sevapc311
WITH SERVICE_NAME = 'Grafik_Service_Recive_sevapc311',
BROKER_INSTANCE = '7C737F42-2DF6-46E7-A6B6-89D1A9608DE2',
ADDRESS = 'TCP://sevapc311:5723'
GO
--DROP ROUTE Grafik_andonpc017
CREATE ROUTE Grafik_Andonpc017
WITH SERVICE_NAME = 'Grafik_Service_Recive_Andonpc017',
BROKER_INSTANCE = 'AE2B294A-B02E-4709-A51E-CFBFD0E478C1',
ADDRESS = 'TCP://192.168.20.106:5723'
GO
CREATE CERTIFICATE Cert_ROBOTSRV_Dialog
WITH SUBJECT = 'Cert_ROBOTSRV_auth',
START_DATE = '02/15/2007',
EXPIRY_DATE = '02/15/2015'
GO
BACKUP CERTIFICATE Cert_ROBOTSRV_Dialog TO FILE = 'C:\Cert_ROBOTSRV_Dialog'
GO
CREATE CERTIFICATE Cert_sevapc311_pub_Dialog AUTHORIZATION andon
FROM FILE = 'C:\Cert_sevapc311_Dialog'
--DROP CERTIFICATE Cert_andonpc017_Dialog
CREATE CERTIFICATE Cert_Andonpc017_Dialog AUTHORIZATION andon
FROM FILE = 'C:\Cert_andonpc017_Dialog'
GRANT SEND ON SERVICE::[Grafik_Service_Send_ROBOTSRV]
TO andon
CREATE USER sbLogin
GRANT SEND ON SERVICE::[Grafik_Service_Send_ROBOTSRV]
TO sbLogin
GO
--GRANT SEND ON SERVICE::[Grafik_Service_Send_ROBOTSRV]
--TO [VADERSTAD\vrobot]
--GO
-- Grant RECEIVE permission on the queue.
GRANT RECEIVE ON [Grafik_Queue]
TO andon
GO
GRANT CONTROL ON SERVICE::[Grafik_Service_Send_ROBOTSRV]
TO andon
GO
--DROP REMOTE SERVICE BINDING Grafik_sevap
CREATE REMOTE SERVICE BINDING Grafik_sevap
TO SERVICE 'Grafik_Service_Recive_sevapc311'
WITH USER = andon
GO
--DROP REMOTE SERVICE BINDING Grafik_andonpc017
CREATE REMOTE SERVICE BINDING Grafik_andonpc017
TO SERVICE 'Grafik_Service_Recive_Andonpc017'
WITH USER = andon
“Receiver 1”
use master
CREATE MASTER KEY ENCRYPTION BY PASSWORD = 'andonANDON'
CREATE CERTIFICATE Cert_sevapc311
WITH SUBJECT = 'Cert_sevapc311_Auth',
START_DATE = '02/15/2007',
EXPIRY_DATE = '02/15/2015'
GO
BACKUP CERTIFICATE Cert_sevapc311 To FILE = 'C:\Cert_sevapc311'
CREATE ENDPOINT SBEndpointklient STATE = STARTED
AS TCP (LISTENER_PORT = 5723)
FOR SERVICE_BROKER (AUTHENTICATION = CERTIFICATE Cert_sevapc311)
CREATE CERTIFICATE Cert_ROBOTSRV_pub AUTHORIZATION andon
FROM FILE = 'C:\Cert_ROBOTSRV';
GRANT CONNECT ON ENDPOINT::SBEndpointklient to andon
-
use KlientDB
GRANT SEND ON SERVICE::[Grafik_Service_Recive_sevapc311]
TO andon
GO
GRANT CONTROL ON SERVICE::[Grafik_Service_Recive_sevapc311]
TO andon
GO
GRANT RECEIVE ON [Grafik_Queue]
TO andon
GO
CREATE Route Grafik_ROBOTSRV
WITH
SERVICE_NAME = 'Grafik_Service_Send_ROBOTSRV',
BROKER_INSTANCE = '2BA192F8-0BA3-4237-A156-21AFF7C65481',
ADDRESS = 'TCP://ROBOTSRV:5723'
CREATE MASTER KEY ENCRYPTION BY PASSWORD = 'andonANDON'
CREATE CERTIFICATE Cert_sevapc311_Dialog
WITH SUBJECT = 'Cert_sevapc311_Auth',
START_DATE = '02/15/2007',
EXPIRY_DATE = '02/15/2015'
GO
BACKUP CERTIFICATE Cert_sevapc311_Dialog To FILE = 'C:\Cert_sevapc311_Dialog'
CREATE CERTIFICATE Cert_ROBOTSRV_pub_Dialog AUTHORIZATION andon
FROM FILE = 'C:\Cert_ROBOTSRV_Dialog';
“Receiver 2”
use master
CREATE MASTER KEY ENCRYPTION BY PASSWORD = 'andonANDON'
--DROP CERTIFICATE Cert_Andonpc017_Trans
CREATE CERTIFICATE Cert_Andonpc017_Trans
WITH SUBJECT = 'Cert_Andonpc017_Auth',
START_DATE = '02/15/2007',
EXPIRY_DATE = '02/15/2015'
GO
BACKUP CERTIFICATE Cert_Andonpc017_Trans To FILE = 'F:\Cert_Andonpc017_Trans'
CREATE ENDPOINT SBEndpointklient STATE = STARTED
AS TCP (LISTENER_PORT = 5723)
FOR SERVICE_BROKER (AUTHENTICATION = CERTIFICATE Cert_Andonpc017_Trans)
--DROP USER andon
CREATE USER andon
--DROP CERTIFICATE Cert_ROBOTSRV
CREATE CERTIFICATE Cert_ROBOTSRV AUTHORIZATION andon
FROM FILE = 'C:\Cert_ROBOTSRV';
CREATE LOGIN sbLogin
FROM CERTIFICATE Cert_ROBOTSRV;
GO
GRANT CONNECT ON ENDPOINT::SBEndpointklient TO [public]
--Select * from sys.certificates
use KlientDB
create user andon
Grant SEND ON SERVICE::[Grafik_Service_Recive_Andonpc017] to [Public]
GRANT SEND ON SERVICE::[Grafik_Service_Recive_Andonpc017]
TO andon
GO
GRANT CONTROL ON SERVICE::[Grafik_Service_Recive_Andonpc017]
TO andon
GO
GRANT RECEIVE ON [Grafik_Queue]
TO andon
GO
--DROP Route Grafik_ROBOTSRV
CREATE Route Grafik_ROBOTSRV
WITH
SERVICE_NAME = 'Grafik_Service_Send_ROBOTSRV',
BROKER_INSTANCE = '2BA192F8-0BA3-4237-A156-21AFF7C65481',
ADDRESS = 'TCP://ROBOTSRV:5723'
--Dialog S?kerhet
CREATE MASTER KEY ENCRYPTION BY PASSWORD = 'andonANDON'
--Drop CERTIFICATE Cert_Andonpc017_Dialog
CREATE CERTIFICATE Cert_Andonpc017_Dialog
WITH SUBJECT = 'Cert_Andonpc017_Auth',
START_DATE = '02/15/2007',
EXPIRY_DATE = '02/15/2015'
GO
BACKUP CERTIFICATE Cert_Andonpc017_Dialog To FILE = 'F:\Cert_Andonpc017_Dialog'
--Drop CERTIFICATE Cert_ROBOTSRV_Dialog
CREATE CERTIFICATE Cert_ROBOTSRV_Dialog AUTHORIZATION andon
FROM FILE = 'C:\Cert_ROBOTSRV_Dialog';
The Security Audit:Audit Broker Conversation event details will contain the Issuer Name and Serial Number of the certificate not found (I think they are the UserName and RemoteLogin columns). You can then look up sys.certificates on the sender side to make sure the sender is using the certificates you expect.
HTH,
~ Remus
Ok thanks.
I will look if I can find what′s wrong.
I got it to work when I turned of the dialog security by deleting RSB.
Certificate loading issue - when creating certificate from SQL Server to SQL Server Express on t
Hi, We are trying to implement Service Broker between SQL Server Express and SQL Server on the Same machine and we are having problems with certificates. We are creating a certificate on SQL Server, backing up the certificate on a file system and then loading certificate on the SQL Server Express from the file and we are keep getting the following error: Msg 15208, Level 16, State 1, Line 1 The certificate, asymmetric key, or private key file does not exist or has invalid format.
Following script runs fine on SQL Server.
Code Snippet
use master
Create Master Key Encryption BY Password = '45Gme*3^&fwu';
BACKUP MASTER KEY TO FILE = 'C:\ServiceBroker\PrivateKeyMasterB.pvk'
ENCRYPTION BY PASSWORD = '45Gme*3^&fwu'
Create Certificate EndPointCertificateC
WITH Subject = 'C.Server.Local',
START_DATE = '06/01/2006',
EXPIRY_DATE = '01/01/2008'
ACTIVE FOR BEGIN_DIALOG = ON;
BACKUP CERTIFICATE EndPointCertificateC
TO FILE = 'C:\ServiceBroker\EndPointCertificateC.cer'
Following script runs on SQL Server Express:
Code Snippet
Create Certificate EndPointCertificateC
From FILE = 'C:\ServiceBroker\EndPointCertificateC.cer'
WITH PRIVATE KEY (
FILE = 'C:\ServiceBroker\PrivateKeyMasterB.pvk',
DECRYPTION BY PASSWORD = '45Gme*3^&fwu'
);
If we run the script other way around, it works fine. If we use the SQL Server on some other machine, the script works fine. But only on the same machine, it throws this error. We made sure the permissions and everything. Let us know if there is any work around or what are we doing wrong.
Any help is appreciated. Thank you,
This must be a permisssion issue. The SQL Server Express service account does not have access to the .cer and/or .pvk file.|||We did give permission to $SQLServerExpress to the folders where we generate the files. And all we are trying to perform this using sa account, I am not sure which other permission we are missing.
|||Folder permissions are not enough. The files created (*.cer and *.pvk) will be ACL-ed by the creator instance to prevent any other account access, overwriting any permsision inherited from the folder permissions. So if for instance the SQL Express is running as NETWORK SERVICE, or as a (domain) user account, then it will not be able to see the files. You must explicitly grant read permissions on the two created files. Why this work on all other machines is probably because on all other machines the SQL Express and the Enterprise instance run as the same account, but not on this machine.
The account you log in as ('sa') has no relevance, all that matter here is the service account.
Certificate loading issue - when creating certificate from SQL Server to SQL Server Express on t
Hi, We are trying to implement Service Broker between SQL Server Express and SQL Server on the Same machine and we are having problems with certificates. We are creating a certificate on SQL Server, backing up the certificate on a file system and then loading certificate on the SQL Server Express from the file and we are keep getting the following error: Msg 15208, Level 16, State 1, Line 1 The certificate, asymmetric key, or private key file does not exist or has invalid format.
Following script runs fine on SQL Server.
Code Snippet
use master
Create Master Key Encryption BY Password ='45Gme*3^&fwu';
BACKUP MASTER KEYTOFILE='C:\ServiceBroker\PrivateKeyMasterB.pvk'
ENCRYPTION BY PASSWORD ='45Gme*3^&fwu'
CreateCertificate EndPointCertificateC
WITH Subject ='C.Server.Local',
START_DATE ='06/01/2006',
EXPIRY_DATE ='01/01/2008'
ACTIVE FOR BEGIN_DIALOG =ON;
BACKUPCERTIFICATE EndPointCertificateC
TOFILE='C:\ServiceBroker\EndPointCertificateC.cer'
Following script runs on SQL Server Express:
Code Snippet
CreateCertificate EndPointCertificateC
FromFILE='C:\ServiceBroker\EndPointCertificateC.cer'
WITH PRIVATE KEY(
FILE='C:\ServiceBroker\PrivateKeyMasterB.pvk',
DECRYPTION BY PASSWORD ='45Gme*3^&fwu'
);
If we run the script other way around, it works fine. If we use the SQL Server on some other machine, the script works fine. But only on the same machine, it throws this error. We made sure the permissions and everything. Let us know if there is any work around or what are we doing wrong.
Any help is appreciated. Thank you,
This must be a permisssion issue. The SQL Server Express service account does not have access to the .cer and/or .pvk file.|||We did give permission to $SQLServerExpress to the folders where we generate the files. And all we are trying to perform this using sa account, I am not sure which other permission we are missing.
|||Folder permissions are not enough. The files created (*.cer and *.pvk) will be ACL-ed by the creator instance to prevent any other account access, overwriting any permsision inherited from the folder permissions. So if for instance the SQL Express is running as NETWORK SERVICE, or as a (domain) user account, then it will not be able to see the files. You must explicitly grant read permissions on the two created files. Why this work on all other machines is probably because on all other machines the SQL Express and the Enterprise instance run as the same account, but not on this machine.
The account you log in as ('sa') has no relevance, all that matter here is the service account.
Thursday, February 16, 2012
Catching an exception from a Web service task
Hi!
I am quite new using SSIS and I have a problem with catching an (SOAP) exception from a Web service task. Some times my web service task can fail and when the web service is failing, it is throwing an exception. When the task succeeds the result is being put into a variable, That part is not a problem.
But catching an exception is. I have tried to use a script task and tried to get exception from the dts object model. I have not yet succeeded on that. But it might be a possible way to go. A different approach might be creating an OnError event on my web service task which I can create a task when triggered. But I have not found any solution yet and I hope some people out there have done this before or have a solution on this.
Regards
Geir F
I forget to tell that I want the error description text from the exception that is thrown from the web service task because I want to log the errors. So what I hope is to have a script task that executes when web service fails and to write some code to catch the error description.
Current status on this is that the script task executes when the WS fails (red arrow). Nice. The web service returns an object, say TestOutput variable. When the WS succeeds, I can convert the object into a integer datatype and catch the value. But when it fails, I don't know to catch the error description. When executing the package, I can see the error description on th progress tab, so there must be a way for me to get the error too :-)
Regards
GF
Tuesday, February 14, 2012
Catch22
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
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
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.
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..
Catalogue Report Manager is not installing
I installed SQL Server 2005 Express Edition with Advanced Services with Service Pack 2 but catalogue Report Manager it was not installed. To me will not address under the reference http: // localhost/reports$SQLExpress since such catalogue is not present in IIS. In what there can be a problem?
Thank's
Hi,are you sure that Reporting Services is installed ? You will need to have IIS as a prerequisite before installing Reporting Services, otherwise it wwon′t be installed.
HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de|||
yes, but I have't installed Report Manager .
Thank's for help!!
Friday, February 10, 2012
Case-Sensitive Search
We have two systems, a Financial system and a Professional Service Automated
system. The database currently has a collation of case-insensitive
(MSSQL2K). The Financial system happened to have incorrectly exported a
ProjectCode value that was in all lower case to the other system where in
expects a ProjectCode value to be in UPPERCASE. I would to be able to write
a query that will identify all rows in a table in the financial system where
the ProjectCode is in lowercase in the case-insensitive environment.
TIA,
bpdee
See "collate" clause in BOL.
Example:
select
*
from
(
select 1, cast('microsoft sql server 2000' as varchar(25))
union all
select 2, cast('MICROSOFT SQL SERVER 2000' as varchar(25))
) t1(c1, c2)
where
c2 like 'microsoft sql server 2000' collate SQL_Latin1_General_CP1_CS_AS
AMB
"bpdee" wrote:
> Hi,
> We have two systems, a Financial system and a Professional Service Automated
> system. The database currently has a collation of case-insensitive
> (MSSQL2K). The Financial system happened to have incorrectly exported a
> ProjectCode value that was in all lower case to the other system where in
> expects a ProjectCode value to be in UPPERCASE. I would to be able to write
> a query that will identify all rows in a table in the financial system where
> the ProjectCode is in lowercase in the case-insensitive environment.
> TIA,
> bpdee
Case-Sensitive Search
We have two systems, a Financial system and a Professional Service Automated
system. The database currently has a collation of case-insensitive
(MSSQL2K). The Financial system happened to have incorrectly exported a
ProjectCode value that was in all lower case to the other system where in
expects a ProjectCode value to be in UPPERCASE. I would to be able to write
a query that will identify all rows in a table in the financial system where
the ProjectCode is in lowercase in the case-insensitive environment.
TIA,
bpdeeSee "collate" clause in BOL.
Example:
select
*
from
(
select 1, cast('microsoft sql server 2000' as varchar(25))
union all
select 2, cast('MICROSOFT SQL SERVER 2000' as varchar(25))
) t1(c1, c2)
where
c2 like 'microsoft sql server 2000' collate SQL_Latin1_General_CP1_CS_AS
AMB
"bpdee" wrote:
> Hi,
> We have two systems, a Financial system and a Professional Service Automat
ed
> system. The database currently has a collation of case-insensitive
> (MSSQL2K). The Financial system happened to have incorrectly exported a
> ProjectCode value that was in all lower case to the other system where in
> expects a ProjectCode value to be in UPPERCASE. I would to be able to wri
te
> a query that will identify all rows in a table in the financial system whe
re
> the ProjectCode is in lowercase in the case-insensitive environment.
> TIA,
> bpdee
Case-Sensitive Search
We have two systems, a Financial system and a Professional Service Automated
system. The database currently has a collation of case-insensitive
(MSSQL2K). The Financial system happened to have incorrectly exported a
ProjectCode value that was in all lower case to the other system where in
expects a ProjectCode value to be in UPPERCASE. I would to be able to write
a query that will identify all rows in a table in the financial system where
the ProjectCode is in lowercase in the case-insensitive environment.
TIA,
bpdeeSee "collate" clause in BOL.
Example:
select
*
from
(
select 1, cast('microsoft sql server 2000' as varchar(25))
union all
select 2, cast('MICROSOFT SQL SERVER 2000' as varchar(25))
) t1(c1, c2)
where
c2 like 'microsoft sql server 2000' collate SQL_Latin1_General_CP1_CS_AS
AMB
"bpdee" wrote:
> Hi,
> We have two systems, a Financial system and a Professional Service Automated
> system. The database currently has a collation of case-insensitive
> (MSSQL2K). The Financial system happened to have incorrectly exported a
> ProjectCode value that was in all lower case to the other system where in
> expects a ProjectCode value to be in UPPERCASE. I would to be able to write
> a query that will identify all rows in a table in the financial system where
> the ProjectCode is in lowercase in the case-insensitive environment.
> TIA,
> bpdee