MDAC 2.7 in Windows NT Cluster with SQL 7.0

Hope fully there is someone who has done a similar stupid thing! We have got
ourselves into a bit of trouble when MDAC 2.7 was accidentally (?) installed
onto our Windows NT Cluster wich still runs SQL 7.0.
The result was that the SQL Agent stopped working. However the 2
applications that access the database running on the same cluster are all
working 100% and all client application accessing the database are working
correctly.
The solution offered by Microsoft in KB 820754 is that we should either:
- uncluster SQL
- re-install the sytem from scratch
- Install SQL 2000
Neither of these options are very appealing at this point as the system is
due for a major upgrade to Windows 2003/SQL 2000 in the near future (2-6
month)
Has anyone had a similar problem and how was the problem solved ? What risk
would we have if we continued to run like this and just removed the SQL Agent
resource. Currently we use the SQL Agent to schedule a few database
maintenace tasks which could easily be done manually.
Andrew
You could try to use the MDAC rollback functionality to recover the 2.5
installation. You could also try to reinstall 2.5. Otherwise, you are
pretty much as how the KC describes it, leave it alone and do without or do
some sort of rebuild.
Sincerely,
Anthony Thomas

"Andrew Caldwell" <AndrewCaldwell@.discussions.microsoft.com> wrote in
message news:D721101F-CEDB-4E01-9AF3-1F79882AD1F2@.microsoft.com...
Hope fully there is someone who has done a similar stupid thing! We have
got
ourselves into a bit of trouble when MDAC 2.7 was accidentally (?) installed
onto our Windows NT Cluster wich still runs SQL 7.0.
The result was that the SQL Agent stopped working. However the 2
applications that access the database running on the same cluster are all
working 100% and all client application accessing the database are working
correctly.
The solution offered by Microsoft in KB 820754 is that we should either:
- uncluster SQL
- re-install the sytem from scratch
- Install SQL 2000
Neither of these options are very appealing at this point as the system is
due for a major upgrade to Windows 2003/SQL 2000 in the near future (2-6
month)
Has anyone had a similar problem and how was the problem solved ? What risk
would we have if we continued to run like this and just removed the SQL
Agent
resource. Currently we use the SQL Agent to schedule a few database
maintenace tasks which could easily be done manually.
Andrew
|||Thanks
We found a way to rollback the MDAC to 2.5 which seems to have worked.
Andrew
Andrew
"Anthony Thomas" wrote:

> You could try to use the MDAC rollback functionality to recover the 2.5
> installation. You could also try to reinstall 2.5. Otherwise, you are
> pretty much as how the KC describes it, leave it alone and do without or do
> some sort of rebuild.
> Sincerely,
>
> Anthony Thomas
>
> --
> "Andrew Caldwell" <AndrewCaldwell@.discussions.microsoft.com> wrote in
> message news:D721101F-CEDB-4E01-9AF3-1F79882AD1F2@.microsoft.com...
> Hope fully there is someone who has done a similar stupid thing! We have
> got
> ourselves into a bit of trouble when MDAC 2.7 was accidentally (?) installed
> onto our Windows NT Cluster wich still runs SQL 7.0.
> The result was that the SQL Agent stopped working. However the 2
> applications that access the database running on the same cluster are all
> working 100% and all client application accessing the database are working
> correctly.
> The solution offered by Microsoft in KB 820754 is that we should either:
> - uncluster SQL
> - re-install the sytem from scratch
> - Install SQL 2000
> Neither of these options are very appealing at this point as the system is
> due for a major upgrade to Windows 2003/SQL 2000 in the near future (2-6
> month)
> Has anyone had a similar problem and how was the problem solved ? What risk
> would we have if we continued to run like this and just removed the SQL
> Agent
> resource. Currently we use the SQL Agent to schedule a few database
> maintenace tasks which could easily be done manually.
> --
> Andrew
>
>