During Windows startup, at the point where it asks you to click on
your username and asks for your password, I get a message as follows:
"Your SQL Server installation is either corrupt or has been tampered
with (Unable to load SQLBOOT.DLL). Please uninstall then re-run setup
to correct the problem".

I've traced the file to C:\WINDOWS\Cache\MSDERelASP4\Setup\Sqlrun.cab,
where it has the name 
SQLBOOT.dll.CC1A8C58_27D1_4D38_BF1B_COA5CBB90616
Last modified on 03/05/2005 (which suggests to me it's corrupted
rather than tampered with, unless the problem lies back up the chain
of command as it were, and never gets as far as SQLBOOT, IYSWIM).

A search of all files or folders containing SQL throws up, amongst
other things, a readme file at
C:\WINDOWS\Cache\MSDERelASP4\ReadmeSql2k32desksp4.htm
which seems to suggest that the SQL server is part of Win 2000. But I
have WinXP SP2. I suppose they've just used bits of Win 2000 in Win
XP. Also in that folder is a file Setup.exe. Would this be the setup
referred to in the error message? But how do I uninstall the SQL
server in the first place? Probably for good reason, it's not in the
list of files in 'Add/Remove Programs'. I'm reluctant to jump in and
just run Setup.exe in case it just makes things worse.

I have the whole MSDERelASP4 folder backed up, at the end of August,
using MS Backup, and presumably I could restore it in it's entirety.
Is that the way to go?

So far things seem to work more-or-less OK anyway, but I'd like to
repair it if possible so that I don't get the message each time I
start Windows, and presumably I'll come up against something that
doesn't work, eventually.

My computer came with WinXP SP2 ready installed, with the OEM (if
that's the correct term) installation files on the HD. 

-- 
 
Chris

E-mail: christopher[dot]hogg[at]virgin[dot]net

"Chris Hogg"  wrote in message 
news:35d6e5p3m2525k0o627g5dp1nadpaarcge@4ax.com...
> During Windows startup, at the point where it asks you to click on
> your username and asks for your password, I get a message as follows:
> "Your SQL Server installation is either corrupt or has been tampered
> with (Unable to load SQLBOOT.DLL). Please uninstall then re-run setup
> to correct the problem".
>
> I've traced the file to C:\WINDOWS\Cache\MSDERelASP4\Setup\Sqlrun.cab,
> where it has the name
> SQLBOOT.dll.CC1A8C58_27D1_4D38_BF1B_COA5CBB90616
> Last modified on 03/05/2005 (which suggests to me it's corrupted
> rather than tampered with, unless the problem lies back up the chain
> of command as it were, and never gets as far as SQLBOOT, IYSWIM).
>
> A search of all files or folders containing SQL throws up, amongst
> other things, a readme file at
> C:\WINDOWS\Cache\MSDERelASP4\ReadmeSql2k32desksp4.htm
> which seems to suggest that the SQL server is part of Win 2000. But I
> have WinXP SP2. I suppose they've just used bits of Win 2000 in Win
> XP. Also in that folder is a file Setup.exe. Would this be the setup
> referred to in the error message? But how do I uninstall the SQL
> server in the first place? Probably for good reason, it's not in the
> list of files in 'Add/Remove Programs'. I'm reluctant to jump in and
> just run Setup.exe in case it just makes things worse.
>
> I have the whole MSDERelASP4 folder backed up, at the end of August,
> using MS Backup, and presumably I could restore it in it's entirety.
> Is that the way to go?
>
> So far things seem to work more-or-less OK anyway, but I'd like to
> repair it if possible so that I don't get the message each time I
> start Windows, and presumably I'll come up against something that
> doesn't work, eventually.
>
> My computer came with WinXP SP2 ready installed, with the OEM (if
> that's the correct term) installation files on the HD.
>

Windows 2000 is the basis for Windows XP, and XP is often referred to under 
the 2000 banner. And your OEM files will probably only repair Windows, not 
install it. Beware!!!

If you haven't made any drastic changes to your computer in the last few 
days, the best thing to try is System Restore to a point about a week ago, 
or the last time you know for sure everything was OK. 9 times out of 10 this 
solves any problems that may develop. The System Restore short cut is 
generally in the Accessories>System Tools folder from the Start Menu. 
Otherwise you will find the executable file at:
C:\WINDOWS\system32\Restore\rstrui.exe

System Restore only affects program and hardware changes you may have made; 
eg program installations or uninstalls, saved program data such as high 
scores and program preferences, Windows Updates, user details and any 
hardware you may have added or removed. It doesn't affect your own files 
that you save via a save button. These will still be where you put them. So 
if you don't mind losing some of this update data, you can go back as far as 
you wish. Go back too far, and you will have to re-install any programs that 
were installed after that date. Restore points are highlighted on the 
calendar in System Restore, with a note of why they were created. Pick one 
you feel is safe. If it doesn't work, System Restore is completely 
reversible.

Also note, if you switch on Windows Automatic Update, Service Pack 3 (SP3) 
is available. Otherwise you can do a manual search for it in the Microsoft 
website.

jim, Northampton

On Sat, 24 Oct 2009 18:12:05 +0100, Chris Hogg 
wrote the following to uk.comp.misc:

> During Windows startup, at the point where it asks you to click on
> your username and asks for your password, I get a message as follows:
> "Your SQL Server installation is either corrupt or has been tampered
> with (Unable to load SQLBOOT.DLL). Please uninstall then re-run setup
> to correct the problem".
>
> I've traced the file to C:\WINDOWS\Cache\MSDERelASP4\Setup\Sqlrun.cab,
> where it has the name 
> SQLBOOT.dll.CC1A8C58_27D1_4D38_BF1B_COA5CBB90616
> Last modified on 03/05/2005 (which suggests to me it's corrupted
> rather than tampered with, unless the problem lies back up the chain
> of command as it were, and never gets as far as SQLBOOT, IYSWIM).
>
> A search of all files or folders containing SQL throws up, amongst
> other things, a readme file at
> C:\WINDOWS\Cache\MSDERelASP4\ReadmeSql2k32desksp4.htm
> which seems to suggest that the SQL server is part of Win 2000.

SQL Server is *not* a standard part of Windows, of any version. Have you
played with SQL Server, SQL Server Express or MSDE in the past at all? It
sounds like what you have is MSDE Release A Service Pack 4. MSDE is the
predecessor of SQL Server Express and this version was based on SQL Server
2000. See http://www.dotnetking.com/ArticleDetails.aspx?ArticleID=134 for
more details. You can download the setup files for MSDE from
http://bit.ly/168Ti4 and service pack 4 from http://bit.ly/2u1AOt to
reinstall it. After that you can remove it properly if you want.

mh.
-- 
http://www.nukesoft.co.uk
http://personal.nukesoft.co.uk

From address is a blackhole. Reply-to address is valid.

Thanks for those replies. I'd already tried System Restore, and
although it's served me well in the past, it didn't work this time.
I've not heard of SQL before now, and certainly never consciously used
it. But I was glad to hear it's not part of Windows, which meant I
could look elsewhere. 

Over the weekend I've found that the SQL server is connected with the
Pinnacle Studio video editing suite of programmes. I had installed
this some time ago for a particular project, but one or two ancillary
bits failed to install successfully, and I don't use it now. As it
occupied a lot of disc space I had tried to uninstall it, but not all
of it would uninstall, probably due to the partly unsuccessful
installation in the first place.  This was almost certainly the cause
of the error message I was getting. 

Knowing that SQL wasn't part of Windows but was linked to Pinnacle, I
just set about deleting all the remaining bits of Pinnacle I could
find with Explorer, but leaving anything obviously to do with SQS
itself, just in case. I tidied up the loose ends with a disc repair
utility and it all seems OK now with no unwanted error messages.

Thanks again both.

-- 
 
Chris

E-mail: christopher[dot]hogg[at]virgin[dot]net