Re: SQL Server 2005 faulure when updating to SP1
- From: "csteiner" <csteiner@xxxxxxxxxxxx>
- Date: 28 Jun 2006 08:07:43 -0700
Deleting the 4 Back-Up Exec files worked like a charm!! This fix
really should be easier to find. I spent a day and a half looking for
it, and happened across it by dumb luck. I'm sure we're not the first
people to install SP1 on a SQL 2005 Server, and run Back-Up Exec. This
almost smells like a KB article or something....
JL Morrison wrote:
Damn Backup Exec!!!! Only the local administrator had rights to those
files...not Local Administrators Group.
Thanks for finding the "fix" for this.
JL Morrison
"s025jak" <s025jak@xxxxxxxxxxxxxx> wrote in message
news:3CF203D6-87F9-4795-987E-DFD119847D12@xxxxxxxxxxxxxxxx
That makes sense now. Last night when I did the uninstall and re-install
I
had to take ownership of the files to delete them. We also use the latest
version of BackupExec here at my company. It didn't dawn on me at the
time,
but now I realize that the extensions are for the Veritas BackupExec
Intelligent Disaster Recovery. I never thought to look at them when
initially troubleshooting the problem because I was only looking the the
database files themselves and they were OK. The weird thing is that the
Sysinternals Filemon utiliy never picked up an error when the ACLs were
trying to be set and failing due to the $4IDR files. Hopefully this helps
out a lot of people.
"swblake" wrote:
I had the same problem with SP1 install and "database Services" error
message. When I removed the $4IDR files the SP1 was successful. I believe
the
files are from Backup Exec software. From what I found out, when the SP1
install runs, it ATEMPTS to change permissions in the C:\Program
Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data folder and according to
Vincent's first reply
"From the error log, it clearly indicates that there are issue with
setting
permission for the files under data folder.Setup was doing ACL on the
following directory recursively down to each file. Please check the ACL
of
the files"
If you were to look at the permissions on the $4IDR files only the Backup
Exec had rights to the $4IDR files.
I hope this gets the word out on the SP1 install and how to get around
the
problem.
"s025jak" wrote:
swblake,
I had to finally just uninstall SQL Server, re-install, install the SP,
and
re-attach the databases last night to get this resolved quickly. I did
see 4
files with the extensions that you had mentioned. I had to take
ownership of
them in order to delete them after I uninstalled SQL Server. Do you
think
that they were causing problems with the SP installation?
- Jason K.
"swblake" wrote:
s025jak Vincent you have the right idea, check for files that have
$4IDR in
the file name. If they are present remove or change the rights.
Backup Exec
creates those files.
"s025jak" wrote:
This is going to be a long one. I know there have been several
posts in the
Microsoft newsgroups and other blogs and newsgroups on the web, but
I haven't
seen any yet that can answer the problem that a lot of people are
having with
the 'Database Services' not getting upgraded. > - Jason K
.
- References:
- Re: SQL Server 2005 faulure when updating to SP1
- From: JL Morrison
- Re: SQL Server 2005 faulure when updating to SP1
- Prev by Date: Removing SQL Server from the domain
- Next by Date: Maintenance plan problems on new setup
- Previous by thread: Re: SQL Server 2005 faulure when updating to SP1
- Next by thread: Know a list of machines on a network running SQL SERVER
- Index(es):
Relevant Pages
|
