Recipe for disaster

[Swifty]

First off, see http://swiftys.org.uk/images/recipies.jpg

My recipe:

1. Start with Windows XP Professional (optional, I did)
2. Install Microsoft Office Accounting 2007; you get SQL Server
installed as part of it.
3. Remove Microsoft Office Accounting 2007 (the SQL Server component is
also mostly removed)
4. Re-boot. You get a window entitled "SQL Writer" telling you that
SQLDUMPER failed to start.

Does anyone have the recipe for successfully preventing this message?
I've seen suggestions to re-install SQL Server, but why would I want
that? I don't think I had it in step 1 (above).

 

[Guest]

First off, see http://swiftys.org.uk/images/recipies.jpg

My recipe:

1. Start with Windows XP Professional (optional, I did)
2. Install Microsoft Office Accounting 2007; you get SQL Server
installed as part of it.
3. Remove Microsoft Office Accounting 2007 (the SQL Server component is
also mostly removed)
4. Re-boot. You get a window entitled "SQL Writer" telling you that
SQLDUMPER failed to start.

Does anyone have the recipe for successfully preventing this message?
I've seen suggestions to re-install SQL Server, but why would I want
that? I don't think I had it in step 1 (above).

Hi Steve,
This and entry or Orphans left behind try to remove from both the windows
Explorer and the registry by downloading this tool:
AutoRuns for Windows v8.61
By Mark Russinovich and Bryce Cogswell
http://www.microsoft.com/technet/sysinternals/utilities/Autoruns.mspx
Open a run command and type in:
services.msc click [OK].
On the services Control Panel locate the SQL Service and Disable it.

How to uninstall an instance of SQL Server 2005 manually
http://support.microsoft.com/kb/909967

SQL Server 2005 connectivity and Volume Shadow Copy Service (VSS)
http://support.microsoft.com/kb/919023


Try to start with clean boot and uncheck the line from start up for the
application (Windows Accounting 2007) from starting up.
To do that do this:
Open a run command and type in:
msconfig click [OK] on the System Configuration click on StartUp Tap and
uncheck the line as mention for the windows accounting 2007 and the SQLDUMPER.

Reboot and see if you will get the error, does it appear?.
If yes, then open a run command and type in:
sfc /scannow click [OK] and wait for it to finish, then Run Disk CleanUp
and Reboot.
HTH.
Let us know.
nass

 

[Swifty]

Let us know.

Actually, it was easier than I'd anticipated. The trick was convincing
myself that I believed my own assertion that I didn't have SQL Server
before I started. Once I started believing that, I went into Add/Remove
programs and scythed out three other "Microsoft SQL mumble" things, and
the problem went away.

The only product that I have which contains anything remotely like an
SQL database(*) is Windows Media Player, and it's not complaining. So
neither am I, now.

(*) If you ignore IBM DB2, part of my (IBM) day job, that is.