• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 471
  • Last Modified:

service pack error for sql server 2005

I tried to update the sql server 2005 from service pack 3 to service pack 4 but after updating, I got the followin log msj for only database

Product                   : Database Services (MSSQLSERVER)
Product Version (Previous): 4035
Product Version (Final)   :
Status                    : Failure
Log File                  : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB2463332_sqlrun_sql.msp.log
Error Number              : 29538
Error Description         : MSP Error: 29538  SQL Server Setup did not have the administrator permissions required to rename a file: e:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mssqlsystemresource1.ldf. To continue, verify that the file exists, and either grant administrator permissions to the account currently running Setup or log in with an administrator account. Then run SQL Server Setup again.
---------

and I checked that resource databases is available in the location e:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA so what causes this problem?

thanks


msresource.JPG
0
teodor76
Asked:
teodor76
  • 2
1 Solution
 
Daniel_PLDB Expert/ArchitectCommented:
Did you run installation as an administrator?
0
 
teodor76Author Commented:
yes,I have admin rights on this server
0
 
Daniel_PLDB Expert/ArchitectCommented:
In this problem there are mainy 3 follwoing reasons:

1. The SQL Server service account doesn’t have sufficient privileges on the DATA folder of SQL Server

2. It is a recommendation that the MSSQLSYSTEMRESOURCE files (MDF and LDF) be in the same location as the master database (KB947989) - it isn't in your case

3. Some services are restarting the SQL service if it is stopped.

SQL Server Setup performs setup in two phases: in the first phase it replaces of binaries and the second phase is running the configuration scripts for updating the metadata.
During the first phase, the SQL Server service is stopped. In case, you have a service which restarts the SQL service at that point, then issue like yours may happen.
0

Featured Post

Important Lessons on Recovering from Petya

In their most recent webinar, Skyport Systems explores ways to isolate and protect critical databases to keep the core of your company safe from harm.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now