coexistence

can sql2000 and sql express 2005 coexist on the same machine?

if so, are there any rules or restrictions I must follow when installing sql express?

TIA!

Just specify another instance name and another port (if using TCP/IP), thats all.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de|||

If you have control over such things, make sure to install SQL 2000 before SQL 2005. There is an issue with SQL Browser and instance discovery when you install them in the wrong order. Check out the KB at http://support.microsoft.com/kb/905618/en-us for details.

Mike

cnfgsvr.exe - unable to locate dll

Hello,

Please help - I get the following error message while installing SQL server

cnfgsvr.exe - unable to locate dll
the dynamic link library sqlunirl.dll could not be found in the specified path C:\Progra~1\Micros~1\80\Tools\Binn;,;C:\Winnt\syst em;C:\winnt\system32;C:\winnt;C:\winnt\system32\WB EM;C:\Progra~1\Symantec\PCAW~1\:C:\Program Files\Microsoft SQL Server\80\Tools\BINN

(pressed ok)

Setup failed to configure the server. Refer to the server error logs and C:winnt/sqlstp log for more information.I had a similar problem, do you managed to resolve the issue?|||Which version of sql server are you installing - desktop/server ...

Check out the following article:

article (http://support.microsoft.com/default.aspx?scid=KB;EN-US;q317328&)|||I am trying to install SQL2000 standard server on a NT 4 server with service pack 6A. On the same machine, I also have SQL 6.5 and 7 which is running Ok.

From the log, it say the driver has not installed properly after copying sqlunirl.dll into system 32 which probably point to MDAC, try to clear the registry but it does not help.

Any clue?|||I had this exact issue. I tried the installation over and over again and checked all the log files as Microsoft suggests on their website.
Believe it or not, the way I got it to work was pretty simple.
All I did was stick the CD ROM in another networked computers CD ROM. Connected to the CDROM over the network and then installed. It installed with no problems.
Seems as though there may be a hardware issue with reading this CD with certain CD ROM drives.
I wasted an hour or so searching the log files only to come up with nothing and this took care of it on the first shot.

Good luck to anyone else that gets this error.

Clustering failure on install

Hi,

Where can I post issues with SQL 2005 clustering. Is there any prereq that needs to be followed before installing SQL 2005 on a windows cluster?

Thanks

go here http://msdn2.microsoft.com/en-us/library/ms189910.aspx|||

You can certainly post here about any clustering issues you may encounter. The SQL Server 2005 Failover Clustering whitepaper will be released soon (and has full install instructions with screen captures). As far as prereqs, the link that was provided is good. But make sure that your Windows level cluster is rock solid and tested before installing SQL Server. The security is a bit different with SQL Server 2005 failover clustering, so pay attention to that.

Other than that, the install itself is straightforward. No real gotchas there except all nodes do not get the full compliment of client tools. If you install the client tools, they will only go on the server which initiated the install and you will need to install them on the other nodes. If you do not need the full compliment of admin tools on eachnode, then you don't have to worry about it.

If you want even more, the Apress book SQL Server 2005 High Availability is due out later this year. The book covers clustering both Windows (from a SQL perspective) & SQL - not just the SQL piece. It is spread out over two chapters and should be 250 - 300 pages for those two chapters alone.

|||adminup, did the article help?|||

Thanks It helped.

Th eonly other question is that before installing the SQL cluster do we need to configure the MSDTC or is there any prereq required after the Windows 2003 cluster is setup?

|||Yes, you should configure the clustered DTC prior to installing SQL Server as per http://support.microsoft.com/kb/301600/en-us and http://support.microsoft.com/kb/817064/en-us.|||

Hi Thanks while actually installing i get this error message I have checked the windows scheduling and it is started.

setup failed to start on the remote machine. Check the task scheduler event log on the reote machine

Why I am getting this error

|||If your other node or nodes do not have access to the CD-ROM or install point, that is a likely cause of this. It could also be a missed configuration step in the preparation, but it's most likely access to the install bits.|||

Thanks it was a share from a remote machine. Now the setup is fine I can SQL directories created on both the machine however it fails on database install there is no error log that corresponds to this.

I have enabled MSDTC and all the prereq but still the setup fails at the database creation points.

Any ideas?

Anup

|||sql setup log might give some clues as why it fails.|||

As OJ says, the logs should be telling and are VERY descriptive in SQL Server 2005.What part of the DB install does it choke on?

|||Thanks I figured it out it was probably a share from network drive to MSDTC service accont which was causing this but all well now set up completed thanks for all the help|||

I had the similar error on 64 bit STD edition installation of default instance , with another named instance already installed without any issues.I had to go ask the Task manager to interact with desktop on but the servers and restart the tast manger service in both. I am still not sure why does the TM needs to interact with desktop on the other (non installation passive node ).

Clustering failure on install

Hi,

Where can I post issues with SQL 2005 clustering. Is there any prereq that needs to be followed before installing SQL 2005 on a windows cluster?

Thanks

go here http://msdn2.microsoft.com/en-us/library/ms189910.aspx|||

You can certainly post here about any clustering issues you may encounter. The SQL Server 2005 Failover Clustering whitepaper will be released soon (and has full install instructions with screen captures). As far as prereqs, the link that was provided is good. But make sure that your Windows level cluster is rock solid and tested before installing SQL Server. The security is a bit different with SQL Server 2005 failover clustering, so pay attention to that.

Other than that, the install itself is straightforward. No real gotchas there except all nodes do not get the full compliment of client tools. If you install the client tools, they will only go on the server which initiated the install and you will need to install them on the other nodes. If you do not need the full compliment of admin tools on eachnode, then you don't have to worry about it.

If you want even more, the Apress book SQL Server 2005 High Availability is due out later this year. The book covers clustering both Windows (from a SQL perspective) & SQL - not just the SQL piece. It is spread out over two chapters and should be 250 - 300 pages for those two chapters alone.

|||adminup, did the article help?|||

Thanks It helped.

Th eonly other question is that before installing the SQL cluster do we need to configure the MSDTC or is there any prereq required after the Windows 2003 cluster is setup?

|||Yes, you should configure the clustered DTC prior to installing SQL Server as per http://support.microsoft.com/kb/301600/en-us and http://support.microsoft.com/kb/817064/en-us.|||

Hi Thanks while actually installing i get this error message I have checked the windows scheduling and it is started.

setup failed to start on the remote machine. Check the task scheduler event log on the reote machine

Why I am getting this error

|||If your other node or nodes do not have access to the CD-ROM or install point, that is a likely cause of this. It could also be a missed configuration step in the preparation, but it's most likely access to the install bits.|||

Thanks it was a share from a remote machine. Now the setup is fine I can SQL directories created on both the machine however it fails on database install there is no error log that corresponds to this.

I have enabled MSDTC and all the prereq but still the setup fails at the database creation points.

Any ideas?

Anup

|||sql setup log might give some clues as why it fails.|||

As OJ says, the logs should be telling and are VERY descriptive in SQL Server 2005.What part of the DB install does it choke on?

|||Thanks I figured it out it was probably a share from network drive to MSDTC service accont which was causing this but all well now set up completed thanks for all the help|||

I had the similar error on 64 bit STD edition installation of default instance , with another named instance already installed without any issues.I had to go ask the Task manager to interact with desktop on but the servers and restart the tast manger service in both. I am still not sure why does the TM needs to interact with desktop on the other (non installation passive node ).

Clustering

Hi,

Where can I post issues with SQL 2005 clustering. Is there any prereq that needs to be followed before installing SQL 2005 on a windows cluster?

Thanks

go here http://msdn2.microsoft.com/en-us/library/ms189910.aspx|||

You can certainly post here about any clustering issues you may encounter. The SQL Server 2005 Failover Clustering whitepaper will be released soon (and has full install instructions with screen captures). As far as prereqs, the link that was provided is good. But make sure that your Windows level cluster is rock solid and tested before installing SQL Server. The security is a bit different with SQL Server 2005 failover clustering, so pay attention to that.

Other than that, the install itself is straightforward. No real gotchas there except all nodes do not get the full compliment of client tools. If you install the client tools, they will only go on the server which initiated the install and you will need to install them on the other nodes. If you do not need the full compliment of admin tools on eachnode, then you don't have to worry about it.

If you want even more, the Apress book SQL Server 2005 High Availability is due out later this year. The book covers clustering both Windows (from a SQL perspective) & SQL - not just the SQL piece. It is spread out over two chapters and should be 250 - 300 pages for those two chapters alone.

|||adminup, did the article help?|||

Thanks It helped.

Th eonly other question is that before installing the SQL cluster do we need to configure the MSDTC or is there any prereq required after the Windows 2003 cluster is setup?

|||Yes, you should configure the clustered DTC prior to installing SQL Server as per http://support.microsoft.com/kb/301600/en-us and http://support.microsoft.com/kb/817064/en-us.|||

Hi Thanks while actually installing i get this error message I have checked the windows scheduling and it is started.

setup failed to start on the remote machine. Check the task scheduler event log on the reote machine

Why I am getting this error

|||If your other node or nodes do not have access to the CD-ROM or install point, that is a likely cause of this. It could also be a missed configuration step in the preparation, but it's most likely access to the install bits.|||

Thanks it was a share from a remote machine. Now the setup is fine I can SQL directories created on both the machine however it fails on database install there is no error log that corresponds to this.

I have enabled MSDTC and all the prereq but still the setup fails at the database creation points.

Any ideas?

Anup

|||sql setup log might give some clues as why it fails.|||

As OJ says, the logs should be telling and are VERY descriptive in SQL Server 2005.What part of the DB install does it choke on?

|||Thanks I figured it out it was probably a share from network drive to MSDTC service accont which was causing this but all well now set up completed thanks for all the help|||

I had the similar error on 64 bit STD edition installation of default instance , with another named instance already installed without any issues.I had to go ask the Task manager to interact with desktop on but the servers and restart the tast manger service in both. I am still not sure why does the TM needs to interact with desktop on the other (non installation passive node ).

Cluster-aware SP

Hi,
I've read that installing a SQL Server SP is cluster-aware.
I'm just not sure what this means.
Does this mean that when running the setup on the active node (given 2
nodes), the setup will
- install files on the passive node (node2)
- failover to the other node (node2)
- install files on the first node (node1)
- failback to node1
or is this way off?
After installing the nodes probably needs a reboot. Running on node1;
- reboot node2
- when back up, failover to node2
- reboot node1
- when back up, failback to node1
'
Thanks for any enlightening.
Regards,audunj@.gmail.com wrote:
> Hi,
> I've read that installing a SQL Server SP is cluster-aware.
> I'm just not sure what this means.
> Does this mean that when running the setup on the active node (given 2
> nodes), the setup will
> - install files on the passive node (node2)
> - failover to the other node (node2)
> - install files on the first node (node1)
> - failback to node1
> or is this way off?
> After installing the nodes probably needs a reboot. Running on node1;
> - reboot node2
> - when back up, failover to node2
> - reboot node1
> - when back up, failback to node1
> '
> Thanks for any enlightening.
> Regards,
>
SP will install files on both nodes but will ask for reatart only the
node you started sp, you need to restart the other one also (you'll
probably want to wait till the first one boots up)|||Cluster aware means acting appropriately in all cluster situations. If you
install a SP to an instance starting on the host node, it will update all
binaries on all accessable nodes AND run SQL update scripts. It will advise
you about rebooting both the local and remote node(s) but will not force a
reboot. If you run the SP from an node that does not currently host the
target instance, it will update local binaries only. Again, it will advise
but not force a reboot. This is covered in the Service Pack README file.
Hotfixes exhibit the same behavior. In some circumstances, SPs will not do
a binary-only local update and you will have to run the service pack again
on the entire instance.
Geoff N. Hiten
Microsoft SQL Server MVP
<audunj@.gmail.com> wrote in message
news:1118300953.720619.248550@.g44g2000cwa.googlegroups.com...
> Hi,
> I've read that installing a SQL Server SP is cluster-aware.
> I'm just not sure what this means.
> Does this mean that when running the setup on the active node (given 2
> nodes), the setup will
> - install files on the passive node (node2)
> - failover to the other node (node2)
> - install files on the first node (node1)
> - failback to node1
> or is this way off?
> After installing the nodes probably needs a reboot. Running on node1;
> - reboot node2
> - when back up, failover to node2
> - reboot node1
> - when back up, failback to node1
> '
> Thanks for any enlightening.
> Regards,
>|||Hi, thanx for the feedback.
How about availability during this SP installation? Will the server be
available for user connections as long as I do not reboot the nodes at
the same time? Or will I have to schedule with downtime?
TIA,
"Geoff N. Hiten" <sqlcraftsman@.gmail.com> wrote in
news:eNMygcPbFHA.2696@.TK2MSFTNGP09.phx.gbl:
> Cluster aware means acting appropriately in all cluster situations.
> If you install a SP to an instance starting on the host node, it will
> update all binaries on all accessable nodes AND run SQL update
> scripts. It will advise you about rebooting both the local and remote
> node(s) but will not force a reboot. If you run the SP from an node
> that does not currently host the target instance, it will update local
> binaries only. Again, it will advise but not force a reboot. This
> is covered in the Service Pack README file. Hotfixes exhibit the same
> behavior. In some circumstances, SPs will not do a binary-only local
> update and you will have to run the service pack again on the entire
> instance.
> Geoff N. Hiten
> Microsoft SQL Server MVP
>
> <audunj@.gmail.com> wrote in message
> news:1118300953.720619.248550@.g44g2000cwa.googlegroups.com...
>> Hi,
>> I've read that installing a SQL Server SP is cluster-aware.
>> I'm just not sure what this means.
>> Does this mean that when running the setup on the active node (given
>> 2 nodes), the setup will
>> - install files on the passive node (node2)
>> - failover to the other node (node2)
>> - install files on the first node (node1)
>> - failback to node1
>> or is this way off?
>> After installing the nodes probably needs a reboot. Running on node1;
>> - reboot node2
>> - when back up, failover to node2
>> - reboot node1
>> - when back up, failback to node1
>> '
>> Thanks for any enlightening.
>> Regards,
>|||If you are applying the SP to an entire instance, that SQL server instance
will be unavailable. If you are updating local binaries only such as
replacing a failed node, then the instance will remain online.
Geoff N. Hiten
Microsoft SQL Server MVP
"Gurba" <gurbao@.hotmail.com> wrote in message
news:Xns96718D200BF43gurbaohotmailcom@.129.250.171.67...
> Hi, thanx for the feedback.
> How about availability during this SP installation? Will the server be
> available for user connections as long as I do not reboot the nodes at
> the same time? Or will I have to schedule with downtime?
> TIA,
>
> "Geoff N. Hiten" <sqlcraftsman@.gmail.com> wrote in
> news:eNMygcPbFHA.2696@.TK2MSFTNGP09.phx.gbl:
>> Cluster aware means acting appropriately in all cluster situations.
>> If you install a SP to an instance starting on the host node, it will
>> update all binaries on all accessable nodes AND run SQL update
>> scripts. It will advise you about rebooting both the local and remote
>> node(s) but will not force a reboot. If you run the SP from an node
>> that does not currently host the target instance, it will update local
>> binaries only. Again, it will advise but not force a reboot. This
>> is covered in the Service Pack README file. Hotfixes exhibit the same
>> behavior. In some circumstances, SPs will not do a binary-only local
>> update and you will have to run the service pack again on the entire
>> instance.
>> Geoff N. Hiten
>> Microsoft SQL Server MVP
>>
>> <audunj@.gmail.com> wrote in message
>> news:1118300953.720619.248550@.g44g2000cwa.googlegroups.com...
>> Hi,
>> I've read that installing a SQL Server SP is cluster-aware.
>> I'm just not sure what this means.
>> Does this mean that when running the setup on the active node (given
>> 2 nodes), the setup will
>> - install files on the passive node (node2)
>> - failover to the other node (node2)
>> - install files on the first node (node1)
>> - failback to node1
>> or is this way off?
>> After installing the nodes probably needs a reboot. Running on node1;
>> - reboot node2
>> - when back up, failover to node2
>> - reboot node1
>> - when back up, failback to node1
>> '
>> Thanks for any enlightening.
>> Regards,
>>
>

Cluster-aware SP

Hi,
I've read that installing a SQL Server SP is cluster-aware.
I'm just not sure what this means.
Does this mean that when running the setup on the active node (given 2
nodes), the setup will
- install files on the passive node (node2)
- failover to the other node (node2)
- install files on the first node (node1)
- failback to node1
or is this way off?
After installing the nodes probably needs a reboot. Running on node1;
- reboot node2
- when back up, failover to node2
- reboot node1
- when back up, failback to node1
'
Thanks for any enlightening.
Regards,audunj@.gmail.com wrote:
> Hi,
> I've read that installing a SQL Server SP is cluster-aware.
> I'm just not sure what this means.
> Does this mean that when running the setup on the active node (given 2
> nodes), the setup will
> - install files on the passive node (node2)
> - failover to the other node (node2)
> - install files on the first node (node1)
> - failback to node1
> or is this way off?
> After installing the nodes probably needs a reboot. Running on node1;
> - reboot node2
> - when back up, failover to node2
> - reboot node1
> - when back up, failback to node1
> '
> Thanks for any enlightening.
> Regards,
>
SP will install files on both nodes but will ask for reatart only the
node you started sp, you need to restart the other one also (you'll
probably want to wait till the first one boots up)|||Cluster aware means acting appropriately in all cluster situations. If you
install a SP to an instance starting on the host node, it will update all
binaries on all accessable nodes AND run SQL update scripts. It will advise
you about rebooting both the local and remote node(s) but will not force a
reboot. If you run the SP from an node that does not currently host the
target instance, it will update local binaries only. Again, it will advise
but not force a reboot. This is covered in the Service Pack README file.
Hotfixes exhibit the same behavior. In some circumstances, SPs will not do
a binary-only local update and you will have to run the service pack again
on the entire instance.
Geoff N. Hiten
Microsoft SQL Server MVP
<audunj@.gmail.com> wrote in message
news:1118300953.720619.248550@.g44g2000cwa.googlegroups.com...
> Hi,
> I've read that installing a SQL Server SP is cluster-aware.
> I'm just not sure what this means.
> Does this mean that when running the setup on the active node (given 2
> nodes), the setup will
> - install files on the passive node (node2)
> - failover to the other node (node2)
> - install files on the first node (node1)
> - failback to node1
> or is this way off?
> After installing the nodes probably needs a reboot. Running on node1;
> - reboot node2
> - when back up, failover to node2
> - reboot node1
> - when back up, failback to node1
> '
> Thanks for any enlightening.
> Regards,
>|||Hi, thanx for the feedback.
How about availability during this SP installation? Will the server be
available for user connections as long as I do not reboot the nodes at
the same time? Or will I have to schedule with downtime?
TIA,
"Geoff N. Hiten" <sqlcraftsman@.gmail.com> wrote in
news:eNMygcPbFHA.2696@.TK2MSFTNGP09.phx.gbl:

> Cluster aware means acting appropriately in all cluster situations.
> If you install a SP to an instance starting on the host node, it will
> update all binaries on all accessable nodes AND run SQL update
> scripts. It will advise you about rebooting both the local and remote
> node(s) but will not force a reboot. If you run the SP from an node
> that does not currently host the target instance, it will update local
> binaries only. Again, it will advise but not force a reboot. This
> is covered in the Service Pack README file. Hotfixes exhibit the same
> behavior. In some circumstances, SPs will not do a binary-only local
> update and you will have to run the service pack again on the entire
> instance.
> Geoff N. Hiten
> Microsoft SQL Server MVP
>
> <audunj@.gmail.com> wrote in message
> news:1118300953.720619.248550@.g44g2000cwa.googlegroups.com...
>|||If you are applying the SP to an entire instance, that SQL server instance
will be unavailable. If you are updating local binaries only such as
replacing a failed node, then the instance will remain online.
Geoff N. Hiten
Microsoft SQL Server MVP
"Gurba" <gurbao@.hotmail.com> wrote in message
news:Xns96718D200BF43gurbaohotmailcom@.12
9.250.171.67...
> Hi, thanx for the feedback.
> How about availability during this SP installation? Will the server be
> available for user connections as long as I do not reboot the nodes at
> the same time? Or will I have to schedule with downtime?
> TIA,
>
> "Geoff N. Hiten" <sqlcraftsman@.gmail.com> wrote in
> news:eNMygcPbFHA.2696@.TK2MSFTNGP09.phx.gbl:
>
>

Cluster-aware SP

Hi,
I've read that installing a SQL Server SP is cluster-aware.
I'm just not sure what this means.
Does this mean that when running the setup on the active node (given 2
nodes), the setup will
- install files on the passive node (node2)
- failover to the other node (node2)
- install files on the first node (node1)
- failback to node1
or is this way off?
After installing the nodes probably needs a reboot. Running on node1;
- reboot node2
- when back up, failover to node2
- reboot node1
- when back up, failback to node1
?
Thanks for any enlightening.
Regards,
audunj@.gmail.com wrote:
> Hi,
> I've read that installing a SQL Server SP is cluster-aware.
> I'm just not sure what this means.
> Does this mean that when running the setup on the active node (given 2
> nodes), the setup will
> - install files on the passive node (node2)
> - failover to the other node (node2)
> - install files on the first node (node1)
> - failback to node1
> or is this way off?
> After installing the nodes probably needs a reboot. Running on node1;
> - reboot node2
> - when back up, failover to node2
> - reboot node1
> - when back up, failback to node1
> ?
> Thanks for any enlightening.
> Regards,
>
SP will install files on both nodes but will ask for reatart only the
node you started sp, you need to restart the other one also (you'll
probably want to wait till the first one boots up)
|||Cluster aware means acting appropriately in all cluster situations. If you
install a SP to an instance starting on the host node, it will update all
binaries on all accessable nodes AND run SQL update scripts. It will advise
you about rebooting both the local and remote node(s) but will not force a
reboot. If you run the SP from an node that does not currently host the
target instance, it will update local binaries only. Again, it will advise
but not force a reboot. This is covered in the Service Pack README file.
Hotfixes exhibit the same behavior. In some circumstances, SPs will not do
a binary-only local update and you will have to run the service pack again
on the entire instance.
Geoff N. Hiten
Microsoft SQL Server MVP
<audunj@.gmail.com> wrote in message
news:1118300953.720619.248550@.g44g2000cwa.googlegr oups.com...
> Hi,
> I've read that installing a SQL Server SP is cluster-aware.
> I'm just not sure what this means.
> Does this mean that when running the setup on the active node (given 2
> nodes), the setup will
> - install files on the passive node (node2)
> - failover to the other node (node2)
> - install files on the first node (node1)
> - failback to node1
> or is this way off?
> After installing the nodes probably needs a reboot. Running on node1;
> - reboot node2
> - when back up, failover to node2
> - reboot node1
> - when back up, failback to node1
> ?
> Thanks for any enlightening.
> Regards,
>
|||Hi, thanx for the feedback.
How about availability during this SP installation? Will the server be
available for user connections as long as I do not reboot the nodes at
the same time? Or will I have to schedule with downtime?
TIA,
"Geoff N. Hiten" <sqlcraftsman@.gmail.com> wrote in
news:eNMygcPbFHA.2696@.TK2MSFTNGP09.phx.gbl:

> Cluster aware means acting appropriately in all cluster situations.
> If you install a SP to an instance starting on the host node, it will
> update all binaries on all accessable nodes AND run SQL update
> scripts. It will advise you about rebooting both the local and remote
> node(s) but will not force a reboot. If you run the SP from an node
> that does not currently host the target instance, it will update local
> binaries only. Again, it will advise but not force a reboot. This
> is covered in the Service Pack README file. Hotfixes exhibit the same
> behavior. In some circumstances, SPs will not do a binary-only local
> update and you will have to run the service pack again on the entire
> instance.
> Geoff N. Hiten
> Microsoft SQL Server MVP
>
> <audunj@.gmail.com> wrote in message
> news:1118300953.720619.248550@.g44g2000cwa.googlegr oups.com...
>
|||If you are applying the SP to an entire instance, that SQL server instance
will be unavailable. If you are updating local binaries only such as
replacing a failed node, then the instance will remain online.
Geoff N. Hiten
Microsoft SQL Server MVP
"Gurba" <gurbao@.hotmail.com> wrote in message
news:Xns96718D200BF43gurbaohotmailcom@.129.250.171. 67...
> Hi, thanx for the feedback.
> How about availability during this SP installation? Will the server be
> available for user connections as long as I do not reboot the nodes at
> the same time? Or will I have to schedule with downtime?
> TIA,
>
> "Geoff N. Hiten" <sqlcraftsman@.gmail.com> wrote in
> news:eNMygcPbFHA.2696@.TK2MSFTNGP09.phx.gbl:
>