Hi there,
I am trying to install reporting services on our server at work. It is a Win2k server OS, with SS2k on it. It does not have VS .NET installed. Is it possible for me to set up the server so that it is the central repository for all our reports and then develop and design the reports from my development box, which does have VS .NET installed? When I install SSRS on my development box it creates the Reports and ReportServer Virtual Directories on IIS but for the server it does not do this. Is there a way of moving these folders to the server from my development box or some way of getting this to work?
I feel like I am banging my head against a brick wall at the moment, getting nowhere fast.
Please any help would be great.Yes, this configuration should work. One thing on your development box, you
should not install the server components, rather install the Report Designer
feature under the client components.
-Lukasz
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"PLSH" <PLSH@.discussions.microsoft.com> wrote in message
news:21C8997D-373B-41FE-BCC5-9C4B835F2295@.microsoft.com...
> Hi there,
> I am trying to install reporting services on our server at work. It is a
> Win2k server OS, with SS2k on it. It does not have VS .NET installed. Is
> it possible for me to set up the server so that it is the central
> repository for all our reports and then develop and design the reports
> from my development box, which does have VS .NET installed? When I install
> SSRS on my development box it creates the Reports and ReportServer Virtual
> Directories on IIS but for the server it does not do this. Is there a way
> of moving these folders to the server from my development box or some way
> of getting this to work?
> I feel like I am banging my head against a brick wall at the moment,
> getting nowhere fast.
> Please any help would be great.
>|||I just replied to another mail you posted, but will duplicate here. On the
server box, you should just be getting a warning about VS not being
installed. You should continue past this and select to install the server
components and the Client tools (samples and BOL if you want them).
On the Dev boxes, only install the Designer component, BOL if you want each
Dev to have a local copy.
Hope that helps.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"PLSH" <PLSH@.discussions.microsoft.com> wrote in message
news:21C8997D-373B-41FE-BCC5-9C4B835F2295@.microsoft.com...
> Hi there,
> I am trying to install reporting services on our server at work. It is a
Win2k server OS, with SS2k on it. It does not have VS .NET installed. Is it
possible for me to set up the server so that it is the central repository
for all our reports and then develop and design the reports from my
development box, which does have VS .NET installed? When I install SSRS on
my development box it creates the Reports and ReportServer Virtual
Directories on IIS but for the server it does not do this. Is there a way of
moving these folders to the server from my development box or some way of
getting this to work?
> I feel like I am banging my head against a brick wall at the moment,
getting nowhere fast.
> Please any help would be great.
>sql
Showing posts with label win2k. Show all posts
Showing posts with label win2k. Show all posts
Wednesday, March 28, 2012
Monday, March 19, 2012
Installing SQL Server 2005 Express
I am working on Win2K Pro & had SQL Server 2005 Express & SQL Server Management Studio installed. The SQL Server name was Merver\SQLEXPRESS. Due to some unavoidable reasons, I had to repair (& not re-install) Win2K but after doing so, I found that I am not able to connect to the database server. I uninstalled all the components related to SQL Server 2005 Express (like Management Studio, Support Files, BOL etc.) from my m/c & then restarted my m/c.
After doing so, I first re-installed SQL Server 2005 Express & other related components (I intended to install SQL Server 2005 Management Studio after installing SQL Server 2005 Express). While installing SQL Server 2005 Express, all the steps get executed successfully except for the last one which happens to be SQL Server Database Services. At this point, I get the following error:
An instance with the same name is already installed on this computer. To proceed with SQL Server Setup, provide a unique instance name.
The problem is after I click the OK button, I am not even given the option to change the instance name! The Status message corresponding to SQL Server Database Services just says Setup failed. Refer to the Setup log for details. Finally, when I click the Next button, the next dialog finishes the Setup (showing the Finish button).
Now how do I overcome this problem? Please note that the Authentication mode I am using is Windows Authentication.
Someone please suggest me a concrete solution. It's driving me nuts! My receding hairline is getting further receded!
Lastly, please note that, as far as possible, I would like to keep the instance name as Merver\SQLEXPRESS only.
Hi,
Refer this link http://blogs.msdn.com/astebner/archive/2005/12/08/501885.aspx
HTH
Hemantgiri S. Goswami
|||Thank you so very much, Hemantgiri....that blog really helped me overcome this problem...
Regards,
Arpan
Installing SQL Server 2005 Express
I am working on Win2K Pro & had SQL Server 2005 Express & SQL Server Management Studio installed. The SQL Server name was Merver\SQLEXPRESS. Due to some unavoidable reasons, I had to repair (& not re-install) Win2K but after doing so, I found that I am not able to connect to the database server. I uninstalled all the components related to SQL Server 2005 Express (like Management Studio, Support Files, BOL etc.) from my m/c & then restarted my m/c.
After doing so, I first re-installed SQL Server 2005 Express & other related components (I intended to install SQL Server 2005 Management Studio after installing SQL Server 2005 Express). While installing SQL Server 2005 Express, all the steps get executed successfully except for the last one which happens to be SQL Server Database Services. At this point, I get the following error:
An instance with the same name is already installed on this computer. To proceed with SQL Server Setup, provide a unique instance name.
The problem is after I click the OK button, I am not even given the option to change the instance name! The Status message corresponding to SQL Server Database Services just says Setup failed. Refer to the Setup log for details. Finally, when I click the Next button, the next dialog finishes the Setup (showing the Finish button).
Now how do I overcome this problem? Please note that the Authentication mode I am using is Windows Authentication.
Someone please suggest me a concrete solution. It's driving me nuts! My receding hairline is getting further receded!
Lastly, please note that, as far as possible, I would like to keep the instance name as Merver\SQLEXPRESS only.
Hi,
Refer this link http://blogs.msdn.com/astebner/archive/2005/12/08/501885.aspx
HTH
Hemantgiri S. Goswami
|||Thank you so very much, Hemantgiri....that blog really helped me overcome this problem...
Regards,
Arpan
Friday, February 24, 2012
Installing SQL 2k Ent in AD environment
While installing SQL Server 2k Ent Ed on a Win2k Server in an Active
Directory environemnt, I have noticed two things different from
installing in a non-AD environment.
1. Using the MS SELECT CD, I am prompted to enter CD-KEY. Normally,
SELECT CDs do not prompt for cd-key. I entered all 1s and was able to
continue.
2. After the install is completed, I can not connect to the server
using Windows authentication. When I try to register the server in
Ent Mgr using my windows login information, I get the following error:
Cannot Generate SSPI Conext Error
I do not get this if I register the server using the sa account.
Do I have to do something different in the Active Directory before
installing SQL Server 2k?
Thanks
JonI don't know about the 1st question, but for the 2nd use the "HOW TO:
Troubleshoot the "Cannot Generate SSPI Context" Error Message" KB article at
http://support.microsoft.com/defaul...b;en-us;811889.
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com
"jtw" <jwright@.mailboxspot.com> wrote in message
news:l3qo00dcrgja0l7ih0blnucgs2nural6s1@.
4ax.com...
Directory environemnt, I have noticed two things different from
installing in a non-AD environment.
1. Using the MS SELECT CD, I am prompted to enter CD-KEY. Normally,
SELECT CDs do not prompt for cd-key. I entered all 1s and was able to
continue.
2. After the install is completed, I can not connect to the server
using Windows authentication. When I try to register the server in
Ent Mgr using my windows login information, I get the following error:
Cannot Generate SSPI Conext Error
I do not get this if I register the server using the sa account.
Do I have to do something different in the Active Directory before
installing SQL Server 2k?
Thanks
JonI don't know about the 1st question, but for the 2nd use the "HOW TO:
Troubleshoot the "Cannot Generate SSPI Context" Error Message" KB article at
http://support.microsoft.com/defaul...b;en-us;811889.
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com
"jtw" <jwright@.mailboxspot.com> wrote in message
news:l3qo00dcrgja0l7ih0blnucgs2nural6s1@.
4ax.com...
quote:
>
> While installing SQL Server 2k Ent Ed on a Win2k Server in an Active
> Directory environemnt, I have noticed two things different from
> installing in a non-AD environment.
> 1. Using the MS SELECT CD, I am prompted to enter CD-KEY. Normally,
> SELECT CDs do not prompt for cd-key. I entered all 1s and was able to
> continue.
> 2. After the install is completed, I can not connect to the server
> using Windows authentication. When I try to register the server in
> Ent Mgr using my windows login information, I get the following error:
> Cannot Generate SSPI Conext Error
> I do not get this if I register the server using the sa account.
>
> Do I have to do something different in the Active Directory before
> installing SQL Server 2k?
>
> Thanks
> Jon
>
Installing SQL 2k Ent in AD environment
While installing SQL Server 2k Ent Ed on a Win2k Server in an Active
Directory environemnt, I have noticed two things different from
installing in a non-AD environment.
1. Using the MS SELECT CD, I am prompted to enter CD-KEY. Normally,
SELECT CDs do not prompt for cd-key. I entered all 1s and was able to
continue.
2. After the install is completed, I can not connect to the server
using Windows authentication. When I try to register the server in
Ent Mgr using my windows login information, I get the following error:
Cannot Generate SSPI Conext Error
I do not get this if I register the server using the sa account.
Do I have to do something different in the Active Directory before
installing SQL Server 2k?
Thanks
JonI don't know about the 1st question, but for the 2nd use the "HOW TO:
Troubleshoot the "Cannot Generate SSPI Context" Error Message" KB article at
http://support.microsoft.com/default.aspx?scid=kb;en-us;811889.
--
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com
"jtw" <jwright@.mailboxspot.com> wrote in message
news:l3qo00dcrgja0l7ih0blnucgs2nural6s1@.4ax.com...
>
> While installing SQL Server 2k Ent Ed on a Win2k Server in an Active
> Directory environemnt, I have noticed two things different from
> installing in a non-AD environment.
> 1. Using the MS SELECT CD, I am prompted to enter CD-KEY. Normally,
> SELECT CDs do not prompt for cd-key. I entered all 1s and was able to
> continue.
> 2. After the install is completed, I can not connect to the server
> using Windows authentication. When I try to register the server in
> Ent Mgr using my windows login information, I get the following error:
> Cannot Generate SSPI Conext Error
> I do not get this if I register the server using the sa account.
>
> Do I have to do something different in the Active Directory before
> installing SQL Server 2k?
>
> Thanks
> Jon
>
Directory environemnt, I have noticed two things different from
installing in a non-AD environment.
1. Using the MS SELECT CD, I am prompted to enter CD-KEY. Normally,
SELECT CDs do not prompt for cd-key. I entered all 1s and was able to
continue.
2. After the install is completed, I can not connect to the server
using Windows authentication. When I try to register the server in
Ent Mgr using my windows login information, I get the following error:
Cannot Generate SSPI Conext Error
I do not get this if I register the server using the sa account.
Do I have to do something different in the Active Directory before
installing SQL Server 2k?
Thanks
JonI don't know about the 1st question, but for the 2nd use the "HOW TO:
Troubleshoot the "Cannot Generate SSPI Context" Error Message" KB article at
http://support.microsoft.com/default.aspx?scid=kb;en-us;811889.
--
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com
"jtw" <jwright@.mailboxspot.com> wrote in message
news:l3qo00dcrgja0l7ih0blnucgs2nural6s1@.4ax.com...
>
> While installing SQL Server 2k Ent Ed on a Win2k Server in an Active
> Directory environemnt, I have noticed two things different from
> installing in a non-AD environment.
> 1. Using the MS SELECT CD, I am prompted to enter CD-KEY. Normally,
> SELECT CDs do not prompt for cd-key. I entered all 1s and was able to
> continue.
> 2. After the install is completed, I can not connect to the server
> using Windows authentication. When I try to register the server in
> Ent Mgr using my windows login information, I get the following error:
> Cannot Generate SSPI Conext Error
> I do not get this if I register the server using the sa account.
>
> Do I have to do something different in the Active Directory before
> installing SQL Server 2k?
>
> Thanks
> Jon
>
Sunday, February 19, 2012
Installing SQL 2000 Client Tools
Hi,
I'm attempting to install SQL 2000 Client Tools on my Win2k Professional workstation. However, it will not install because it claims that there is not enough disc space. The amount of space which it detects is the measly 60Mb left on my 2Gb C: drive, and apparently does not see the rather more capacious, and more than adequate 2.6Gb left of my 3.5Gb D: drive. I see no option during the install for changing this.
Any tips? Thanks in advance...Andrew.This is by design. Client tool is hardcoded to installed to the program files directory. You could overcome this by one of these two methods:
1. modify registry key - HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Curr entVersion\ProgramFilesDir
2. use SetPF program by Gert - http://www.sqldev.net/misc/setpf.htm|||Thanks OJ,
This has partially worked as now the install sees my spacious D: drive as the Program Files drive. However, SQL Client Tools is looking to my 'System Drive' for its space, which it sees as my C: drive. Is there another Key I can change?
thanks, Andrew|||There are DLLs that must be installed to system folder. You might want to clear out tmp to ensure proper disk requirement. If your system drive is that low in space, you would have more than just installation problem, your OS+many other apps would require disk space for cache.
I'm attempting to install SQL 2000 Client Tools on my Win2k Professional workstation. However, it will not install because it claims that there is not enough disc space. The amount of space which it detects is the measly 60Mb left on my 2Gb C: drive, and apparently does not see the rather more capacious, and more than adequate 2.6Gb left of my 3.5Gb D: drive. I see no option during the install for changing this.
Any tips? Thanks in advance...Andrew.This is by design. Client tool is hardcoded to installed to the program files directory. You could overcome this by one of these two methods:
1. modify registry key - HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Curr entVersion\ProgramFilesDir
2. use SetPF program by Gert - http://www.sqldev.net/misc/setpf.htm|||Thanks OJ,
This has partially worked as now the install sees my spacious D: drive as the Program Files drive. However, SQL Client Tools is looking to my 'System Drive' for its space, which it sees as my C: drive. Is there another Key I can change?
thanks, Andrew|||There are DLLs that must be installed to system folder. You might want to clear out tmp to ensure proper disk requirement. If your system drive is that low in space, you would have more than just installation problem, your OS+many other apps would require disk space for cache.
Installing SP4 on New node in cluster on Win2K3
We have a single node cluster using SQL2K EE running on Win2K EE, and this
has been running fine for a year or so. We finally have our new data centre
completed, and the additional hardware installed for us to install the second
node.
1) I installed Cluster services and added the second node to the cluster.
2) Ran COMClust to add DTC as a cluster resource
3) On the Active Node installed SQL2K, and selected advanced options,
Maintain SQL Server . . . .
4) Checked SQL Server resources in Cluster Manager, every thing looks good.
5) Tried to install SP4 from the new passive node - Failed doesn't own
resources in the Cluster
6) Tried installing SP4 from the active node . . . Got a bit further but the
install fails with a 'Setup was unable to complete the operation on all nodes
in the cluster'
At this point I am really stumped Looking at the SQLSP.log file it ends with
16:38:12 Begin SDPassword Dialog
16:38:12 Begin: CheckSAPassword
16:38:12 WARNING : No Blank SA Pwd
16:38:12 End: CheckSAPassword
16:38:12 Begin: SdShowSp3WrngDlg
and searching the net threw up a reference to this
http://support.microsoft.com/kb/815431/] KB article. Although this is not
strictly relevant I am wondering if there is an issue with installing a non
SP SQL2K on Win2K3, and then when trying to install SP4 its checking to see
what SP level its at and rejecting it as it doesn't have SP3 Installed.
So then What I did, was to try failing the cluster over so that I could
apply the fix from the new node. While the cluster group fails over, the SQL
group makes and attempt, but then SQL Server fails to start and it all fails
back to the other node.
I then removed SQL Server (from the active node) on the Passive node.
Rebooted the new passive node, and Installed SQL2K SP3a on the new node
successfully. I then tried to install SP4 (From the Active Node), and that
failed with the same error.
Any one have any Ideas?
Regards
Tony
Slipstream sql server sp4 and then try to do the install from the active
node. Also make sure that nobody else is logged onto the active and passive
nodes.
AS
"BC DBA" wrote:
> We have a single node cluster using SQL2K EE running on Win2K EE, and this
> has been running fine for a year or so. We finally have our new data centre
> completed, and the additional hardware installed for us to install the second
> node.
> 1) I installed Cluster services and added the second node to the cluster.
> 2) Ran COMClust to add DTC as a cluster resource
> 3) On the Active Node installed SQL2K, and selected advanced options,
> Maintain SQL Server . . . .
> 4) Checked SQL Server resources in Cluster Manager, every thing looks good.
> 5) Tried to install SP4 from the new passive node - Failed doesn't own
> resources in the Cluster
> 6) Tried installing SP4 from the active node . . . Got a bit further but the
> install fails with a 'Setup was unable to complete the operation on all nodes
> in the cluster'
> At this point I am really stumped Looking at the SQLSP.log file it ends with
> 16:38:12 Begin SDPassword Dialog
> 16:38:12 Begin: CheckSAPassword
> 16:38:12 WARNING : No Blank SA Pwd
> 16:38:12 End: CheckSAPassword
> 16:38:12 Begin: SdShowSp3WrngDlg
> and searching the net threw up a reference to this
> http://support.microsoft.com/kb/815431/] KB article. Although this is not
> strictly relevant I am wondering if there is an issue with installing a non
> SP SQL2K on Win2K3, and then when trying to install SP4 its checking to see
> what SP level its at and rejecting it as it doesn't have SP3 Installed.
> So then What I did, was to try failing the cluster over so that I could
> apply the fix from the new node. While the cluster group fails over, the SQL
> group makes and attempt, but then SQL Server fails to start and it all fails
> back to the other node.
> I then removed SQL Server (from the active node) on the Passive node.
> Rebooted the new passive node, and Installed SQL2K SP3a on the new node
> successfully. I then tried to install SP4 (From the Active Node), and that
> failed with the same error.
> Any one have any Ideas?
> --
> Regards
> Tony
|||16:38:12 Begin: SdShowSp3WrngDlg
Yes, this is your problem. However, you've indicated that you are running
on Win2K EE, which doesn't exist (only Advanced Server), plus, this security
dialog only presents itself on a Windows Server 2003.
So, let's assume that you are running Windows 2000 Advanced Server on the
active (original) node and Windows Server 2003 EE on the new node.
Your steps through the installation process is correct; however, you will
need to get the new node to the same SP level as the old before the cluster
will successfully move resources to the new node.
There are three issues. The dialog above requires you to apply SP3 or later
before resources will run on new node; however, there is a bug in the SP4
installation package that misreads the new 4 digit Build number 2039 as 203
or 039, both of which are less than the 760 Build for SP3.
You must run service packs from the node that currently owns the cluster
resources, and since you cannot move resources to the new node yet, you must
reapply SP3 on the active (original) node. The installation will detect
that it will be a Binary Only installation to the new node.
Lastly, there is one other security issue in that until the new node has
been updated to SP3, TCP/IP protocol has been disabled. To work around this
issue, on BOTH cluster nodes, you must create NAMED PIPE aliases to the
Virtual SQL Server instance. Since the RTM installation uses this protocol,
this issue does not occur, but it does for any SP installations.
Once SP3 has been applied, you will still not be able to move resources to
new node. You must reapply SP4 plus any additional hot fixes. If you use
AWE, you will definitely want to apply the 2040 HF; moreover, you may want
to consider applying the latest publicly available HF, as it is the most
current build supported, Build 2187.
After this, you should be able to move resources successfully between both
nodes; however, Microsoft only limitedly supports mixed cluster
environments. At this point, you should uninstall the original node from
the cluster, evict the node, and rebuild it as a Windows Server 2003
installation. Then, you will need to follow the procedures above to
reintroduce this node as a clustered member. (As an aside, on Win2K3, you
do not have to run the COMCLUST utility anymore).
One final word of advice, SQL Server 2000 mainstream support expires in
April 2008. You should seriously consider upgrading to SQL Server 2005 as
soon as possible. Moreover, CTP2 for SQL Server 2008 was just released in
this month, with a target EOY 2007 1st QTR 2008 launch expectation, which
means even SS2K5 mainstream support does not have a long expected lifespan.
So, get moving.
Sincerely,
Anthony Thomas
"BC DBA" <BCDBA@.discussions.microsoft.com> wrote in message
news:88FBFA1A-2239-4E19-833F-83A55858ACCC@.microsoft.com...
> We have a single node cluster using SQL2K EE running on Win2K EE, and this
> has been running fine for a year or so. We finally have our new data
centre
> completed, and the additional hardware installed for us to install the
second
> node.
> 1) I installed Cluster services and added the second node to the cluster.
> 2) Ran COMClust to add DTC as a cluster resource
> 3) On the Active Node installed SQL2K, and selected advanced options,
> Maintain SQL Server . . . .
> 4) Checked SQL Server resources in Cluster Manager, every thing looks
good.
> 5) Tried to install SP4 from the new passive node - Failed doesn't own
> resources in the Cluster
> 6) Tried installing SP4 from the active node . . . Got a bit further but
the
> install fails with a 'Setup was unable to complete the operation on all
nodes
> in the cluster'
> At this point I am really stumped Looking at the SQLSP.log file it ends
with
> 16:38:12 Begin SDPassword Dialog
> 16:38:12 Begin: CheckSAPassword
> 16:38:12 WARNING : No Blank SA Pwd
> 16:38:12 End: CheckSAPassword
> 16:38:12 Begin: SdShowSp3WrngDlg
> and searching the net threw up a reference to this
> http://support.microsoft.com/kb/815431/] KB article. Although this is not
> strictly relevant I am wondering if there is an issue with installing a
non
> SP SQL2K on Win2K3, and then when trying to install SP4 its checking to
see
> what SP level its at and rejecting it as it doesn't have SP3 Installed.
> So then What I did, was to try failing the cluster over so that I could
> apply the fix from the new node. While the cluster group fails over, the
SQL
> group makes and attempt, but then SQL Server fails to start and it all
fails
> back to the other node.
> I then removed SQL Server (from the active node) on the Passive node.
> Rebooted the new passive node, and Installed SQL2K SP3a on the new node
> successfully. I then tried to install SP4 (From the Active Node), and that
> failed with the same error.
> Any one have any Ideas?
> --
> Regards
> Tony
has been running fine for a year or so. We finally have our new data centre
completed, and the additional hardware installed for us to install the second
node.
1) I installed Cluster services and added the second node to the cluster.
2) Ran COMClust to add DTC as a cluster resource
3) On the Active Node installed SQL2K, and selected advanced options,
Maintain SQL Server . . . .
4) Checked SQL Server resources in Cluster Manager, every thing looks good.
5) Tried to install SP4 from the new passive node - Failed doesn't own
resources in the Cluster
6) Tried installing SP4 from the active node . . . Got a bit further but the
install fails with a 'Setup was unable to complete the operation on all nodes
in the cluster'
At this point I am really stumped Looking at the SQLSP.log file it ends with
16:38:12 Begin SDPassword Dialog
16:38:12 Begin: CheckSAPassword
16:38:12 WARNING : No Blank SA Pwd
16:38:12 End: CheckSAPassword
16:38:12 Begin: SdShowSp3WrngDlg
and searching the net threw up a reference to this
http://support.microsoft.com/kb/815431/] KB article. Although this is not
strictly relevant I am wondering if there is an issue with installing a non
SP SQL2K on Win2K3, and then when trying to install SP4 its checking to see
what SP level its at and rejecting it as it doesn't have SP3 Installed.
So then What I did, was to try failing the cluster over so that I could
apply the fix from the new node. While the cluster group fails over, the SQL
group makes and attempt, but then SQL Server fails to start and it all fails
back to the other node.
I then removed SQL Server (from the active node) on the Passive node.
Rebooted the new passive node, and Installed SQL2K SP3a on the new node
successfully. I then tried to install SP4 (From the Active Node), and that
failed with the same error.
Any one have any Ideas?
Regards
Tony
Slipstream sql server sp4 and then try to do the install from the active
node. Also make sure that nobody else is logged onto the active and passive
nodes.
AS
"BC DBA" wrote:
> We have a single node cluster using SQL2K EE running on Win2K EE, and this
> has been running fine for a year or so. We finally have our new data centre
> completed, and the additional hardware installed for us to install the second
> node.
> 1) I installed Cluster services and added the second node to the cluster.
> 2) Ran COMClust to add DTC as a cluster resource
> 3) On the Active Node installed SQL2K, and selected advanced options,
> Maintain SQL Server . . . .
> 4) Checked SQL Server resources in Cluster Manager, every thing looks good.
> 5) Tried to install SP4 from the new passive node - Failed doesn't own
> resources in the Cluster
> 6) Tried installing SP4 from the active node . . . Got a bit further but the
> install fails with a 'Setup was unable to complete the operation on all nodes
> in the cluster'
> At this point I am really stumped Looking at the SQLSP.log file it ends with
> 16:38:12 Begin SDPassword Dialog
> 16:38:12 Begin: CheckSAPassword
> 16:38:12 WARNING : No Blank SA Pwd
> 16:38:12 End: CheckSAPassword
> 16:38:12 Begin: SdShowSp3WrngDlg
> and searching the net threw up a reference to this
> http://support.microsoft.com/kb/815431/] KB article. Although this is not
> strictly relevant I am wondering if there is an issue with installing a non
> SP SQL2K on Win2K3, and then when trying to install SP4 its checking to see
> what SP level its at and rejecting it as it doesn't have SP3 Installed.
> So then What I did, was to try failing the cluster over so that I could
> apply the fix from the new node. While the cluster group fails over, the SQL
> group makes and attempt, but then SQL Server fails to start and it all fails
> back to the other node.
> I then removed SQL Server (from the active node) on the Passive node.
> Rebooted the new passive node, and Installed SQL2K SP3a on the new node
> successfully. I then tried to install SP4 (From the Active Node), and that
> failed with the same error.
> Any one have any Ideas?
> --
> Regards
> Tony
|||16:38:12 Begin: SdShowSp3WrngDlg
Yes, this is your problem. However, you've indicated that you are running
on Win2K EE, which doesn't exist (only Advanced Server), plus, this security
dialog only presents itself on a Windows Server 2003.
So, let's assume that you are running Windows 2000 Advanced Server on the
active (original) node and Windows Server 2003 EE on the new node.
Your steps through the installation process is correct; however, you will
need to get the new node to the same SP level as the old before the cluster
will successfully move resources to the new node.
There are three issues. The dialog above requires you to apply SP3 or later
before resources will run on new node; however, there is a bug in the SP4
installation package that misreads the new 4 digit Build number 2039 as 203
or 039, both of which are less than the 760 Build for SP3.
You must run service packs from the node that currently owns the cluster
resources, and since you cannot move resources to the new node yet, you must
reapply SP3 on the active (original) node. The installation will detect
that it will be a Binary Only installation to the new node.
Lastly, there is one other security issue in that until the new node has
been updated to SP3, TCP/IP protocol has been disabled. To work around this
issue, on BOTH cluster nodes, you must create NAMED PIPE aliases to the
Virtual SQL Server instance. Since the RTM installation uses this protocol,
this issue does not occur, but it does for any SP installations.
Once SP3 has been applied, you will still not be able to move resources to
new node. You must reapply SP4 plus any additional hot fixes. If you use
AWE, you will definitely want to apply the 2040 HF; moreover, you may want
to consider applying the latest publicly available HF, as it is the most
current build supported, Build 2187.
After this, you should be able to move resources successfully between both
nodes; however, Microsoft only limitedly supports mixed cluster
environments. At this point, you should uninstall the original node from
the cluster, evict the node, and rebuild it as a Windows Server 2003
installation. Then, you will need to follow the procedures above to
reintroduce this node as a clustered member. (As an aside, on Win2K3, you
do not have to run the COMCLUST utility anymore).
One final word of advice, SQL Server 2000 mainstream support expires in
April 2008. You should seriously consider upgrading to SQL Server 2005 as
soon as possible. Moreover, CTP2 for SQL Server 2008 was just released in
this month, with a target EOY 2007 1st QTR 2008 launch expectation, which
means even SS2K5 mainstream support does not have a long expected lifespan.
So, get moving.
Sincerely,
Anthony Thomas
"BC DBA" <BCDBA@.discussions.microsoft.com> wrote in message
news:88FBFA1A-2239-4E19-833F-83A55858ACCC@.microsoft.com...
> We have a single node cluster using SQL2K EE running on Win2K EE, and this
> has been running fine for a year or so. We finally have our new data
centre
> completed, and the additional hardware installed for us to install the
second
> node.
> 1) I installed Cluster services and added the second node to the cluster.
> 2) Ran COMClust to add DTC as a cluster resource
> 3) On the Active Node installed SQL2K, and selected advanced options,
> Maintain SQL Server . . . .
> 4) Checked SQL Server resources in Cluster Manager, every thing looks
good.
> 5) Tried to install SP4 from the new passive node - Failed doesn't own
> resources in the Cluster
> 6) Tried installing SP4 from the active node . . . Got a bit further but
the
> install fails with a 'Setup was unable to complete the operation on all
nodes
> in the cluster'
> At this point I am really stumped Looking at the SQLSP.log file it ends
with
> 16:38:12 Begin SDPassword Dialog
> 16:38:12 Begin: CheckSAPassword
> 16:38:12 WARNING : No Blank SA Pwd
> 16:38:12 End: CheckSAPassword
> 16:38:12 Begin: SdShowSp3WrngDlg
> and searching the net threw up a reference to this
> http://support.microsoft.com/kb/815431/] KB article. Although this is not
> strictly relevant I am wondering if there is an issue with installing a
non
> SP SQL2K on Win2K3, and then when trying to install SP4 its checking to
see
> what SP level its at and rejecting it as it doesn't have SP3 Installed.
> So then What I did, was to try failing the cluster over so that I could
> apply the fix from the new node. While the cluster group fails over, the
SQL
> group makes and attempt, but then SQL Server fails to start and it all
fails
> back to the other node.
> I then removed SQL Server (from the active node) on the Passive node.
> Rebooted the new passive node, and Installed SQL2K SP3a on the new node
> successfully. I then tried to install SP4 (From the Active Node), and that
> failed with the same error.
> Any one have any Ideas?
> --
> Regards
> Tony
Subscribe to:
Posts (Atom)