marrowyung
asked on
SQL server error
hi,
we see application log of a SQL server show this error:
1) sqlservr (1336) An attempt to open the file "C:\Windows\system32\LogFi les\Sum\Ap i.log" for read only access failed with system error 5 (0x00000005): "Access is denied. ". The open file operation will fail with error -1032 (0xfffffbf8).
and
2)
The Open Procedure for service "BITS" in DLL "C:\Windows\System32\bitsp erf.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.
the first one. I google it and it shows :
https://stackoverflow.com/questions/25830912/error-occurred-while-opening-logfile-c-windows-system32-logfiles-sum-api-log
https://support.microsoft.com/zh-tw/help/2811566/error-1032-messages-in-the-application-log-in-windows-server-2012?wa=wsignin1.0
but I am wondering why SQL server need to write to this folder and why we want to change read/write permission for the SQL server ! we are not the first day to run that box but now, funny error like this happened.
please share experience on this!
we see application log of a SQL server show this error:
1) sqlservr (1336) An attempt to open the file "C:\Windows\system32\LogFi
and
2)
The Open Procedure for service "BITS" in DLL "C:\Windows\System32\bitsp
the first one. I google it and it shows :
https://stackoverflow.com/questions/25830912/error-occurred-while-opening-logfile-c-windows-system32-logfiles-sum-api-log
https://support.microsoft.com/zh-tw/help/2811566/error-1032-messages-in-the-application-log-in-windows-server-2012?wa=wsignin1.0
but I am wondering why SQL server need to write to this folder and why we want to change read/write permission for the SQL server ! we are not the first day to run that box but now, funny error like this happened.
please share experience on this!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
If the service passwords were changed via "services.msc", there are a couple of things that do not happen (e.g. switching of permissions from one account to the new credentials on the file system & registry, re-creation of the instance keys, etc)
ASKER
ok. for this I didn't know.
actually this is the first server I install has this problem. the Windows is a VM and not setup by me.
the installation wizard should assign the SQL server service account with appropriate right AFTER the installation.
so there are nothing can be done ?
actually this is the first server I install has this problem. the Windows is a VM and not setup by me.
the installation wizard should assign the SQL server service account with appropriate right AFTER the installation.
so there are nothing can be done ?
so there are nothing can be done?
You can "add read/write permissions manually to the service accounts that are used by SQL Server (sqlservr.exe) and SQL Server Analysis Services (msmdsrv.exe) to access the \Windows\System32\LogFiles
ASKER
yeah, but this method is a bit straight ! can't see why we need to do it manually ONCE we upgrade SP.
ASKER
tks and I might come back later .. I hope not.
ASKER
hi, why does it matter ?
it seems someone reboot it so it happen ! but it keep running everyday and no one complain.