by Uffe Nielse » Wed, 21 Nov 2001 18:28:47
I have a mysterious problem with Microsoft SQL server 7.0 and a NT 4.0 sp6a
+ option pack.
After installation MMC fails with an dr. watson error.
The only fix is to replace the mmc.exe and other mmc files in
c:\winnt\system32. This will get the mmc back running, but leaves the SQL
server cripled.
Does anyone have a fix to this problem ?
Best regards,
Uffe
by Neil Pik » Thu, 22 Nov 2001 04:18:40
Neil Pike MVP/MCSE. Protech Computing Ltd
Reply here - no email
SQL FAQ (484 entries) see
http://forumsb.compuserve.com/gvforums/UK/default.asp?SRV=MSDevApps
(faqxxx.zip in lib 7)
or www.ntfaq.com/Articles/Index.cfm?DepartmentID=800
or www.sqlserverfaq.com
or www.mssqlserver.com/faq
1. SQL MS 7.0 NT 4.0 SP6a - Database Maintenance Plan
SQL MS 7.0 NT 4.0 SP6a - Database Maintenance Plan
I have a MS SQL 7.0 SP 3 server running on NT 4.0 SP6a.
In Enterprise Manager I can run a back up of a database as
long as I create it and run it right away. I have created
a Database Maintenance Plan to back them up on a daily
schedule but it does not run. Has anyone ever heard of
this? I'm certain that I set it up correctly. Also, the
product that I am running on SQL is called Prolog from
Meridian systems. I used to be able to set up a back up
that run inside of their application. It basically just
sent a call to SQL to do it so I don't think it was any
different than what I am trying to do in Enterprise
Manager. Now for some reason that no longer is working?
Any thoughts would be appreciated.
2. Oracle Default Users and Security
3. Installation PSQL 7 and NT 4.0 Server with Arcserve 6.5 for NT
5. MSSQL 6.5 (un)installation fails on NT 4.0 SP3 Server
7. SQL 6.5 on NT (SP6a) installation problems
8. Search Drivers Recherche des drivers for Paradow 7
9. Installation Sql 7.0 German on NT 4.0 English
10. Installation of SQL Server 2000 on Windows NT 4.0 Server
11. Installation woes with SQL Server 7 on NT Server 4.0
12. Installation of SQL Server on WinNT 4.0 SP6a give the following problem
13. Installation Problem with SQL Server 7 and NT Server 4.0 (SP6)