Does changing the SQL Server Service Account impact FILESTREAM data?

I have a stand-alone SQL Server 2008 instance that I need to change the SQL Server service account from LocalSystem to a domain account. However, I was wondering if there was any impact on FILESTREAM enabled databases that are hosted on the SQL Server?
Specifically, has anyone ever changed the SQL Server service account when using FILESTREAM ...
Sincerely,
Sean Fitzgerald
BOL says : Only the account under which the SQL Server service account runs is granted NTFS permissions to the FILESTREAM container.So, if you start SQL Server under different account , that account wil have access to use fliestream data (read / write)
At the database level ,If a user has permission to the FILESTREAM column in a table, the user can open the associated files..
Abhay Chaudhary OCP 9i, MCTS/MCITP (SQL Server 2005, 2008, 2005 BI) ms-abhay.blogspot.com/

Similar Messages

SCVMM 2008 R2 - "The SQL Server service account does not have permission to access Active Directory Domain Services (AD DS)."

I know this question has been asked before, but never for R2, that I can tell, and the posted fixes aren't working. I have just installed SCVMM 2008 R2 on a Windows Server 2008 R2 server, using a remote SQL 2008 SP1 database. When I attempt to connect to SCVMM, I get the following error:
"The SQL Server service account does not have permission to access Active Directory Domain Services (AD DS).
Ensure that the SQL Server service is running under a domain account or a computer account that has permission to access AD DS. For more information, see "Some applications and APIs require access to authorization information on account objects" in the Microsoft Knowledge Base at http://go.microsoft.com/fwlink/?LinkId=121054.
ID: 2607"
What I've seen online is that this is usually becuase the domain account SCVMM is running as does not have the proper permissions on the SQL database. Here's what I've confirmed:
1) My SCVMM service account is a local admin on the SCVMM server
2) My SCVMM service account is a dbowner on the SCVMM database in SQL
3) My SQL service account is a dbowner on the SCVMM database in SQL
4) My SQL service account is a domain user (even made it a domain admin, just in case, and it still "doesn't have access to AD DS," which is obviously untrue)
5) Neither service account is locked out
Has anyone run in to this? It says in Technet that remote SQL 2008 is supported, as long as the SQL management studio is installed to the SCVMM server, and I installed and patched before I began the SCVMM installation. I just don't know what else to try - I have no errors in event logs, no issues during the installation itself...
Andrew Topp

That answer was very unhelpful fr33m4n. The individual mentions that they've received the error that points to the KB article. I currently receive the same error -- there seems to be no resolution. I've run the Microsoft VBS script to add TAUG to the WAAG
as suggested by 331951, and that made absolutely no difference.
1) My SCVMM service account is a local admin on the SCVMM server
2) My SCVMM service account is a dbowner on the SCVMM database in SQL
3) My SQL service account is a dbowner on the SCVMM database in SQL
4) My SQL service account is a domain user (even made it a domain admin, just in case, and it still
"doesn't have access to AD DS," which is obviously untrue)
The user is also a member of WAAG, the machines have delegated authority to each other. Is there any other solution?

SQL Server Service account setup

Yes, you would have to create a login for it. See your other post for info about the error you're getting.

I am currently running MS SQL 2008 R2 on a Windows Server 2008 R2 box. The SQL services are currently running under the NetworkService account and I want to change this to a domain account but I am having some trouble. I have created the domain account and have tried to go into SSCM and change the account there but I get various errors depending on the service I try to change. When changing the account on the SQL Server Service I get an error "Access is Denied"
I am assuming I need to assign some rights to this new account BUT I thought changing the account in SSCM would do that automatically but it looks like that assumption is wrong.
What is the best procedure for changing the SQL Server Service account to a domain account on SQL Server 2008?
This topic first appeared in the Spiceworks Community

SQL Server Service Account - Domain Account - WMI Provider Error - 0x80092004

Hi,
if I try to use an domain account for SQL service start using SQL configuration Manager I receive the error
WMI Provider Error - 0x80092004
in Popup Window and in Eventlog 5 Error Events from Source MSSQLSERVER:
26014:
Unable to load user-specified certificate [Cert Hash(sha1) "BA78B5DBF93CCD7EFA1860C99B0D6141D480199A"]. The server will not accept a connection. You should verify that the certificate is correctly installed. See "Configuring Certificate for
Use by SSL" in Books Online.
17182:
TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property. "
17182:
TDSSNIClient initialization failed with error 0x80092004, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Cannot find object or property.
17826:
Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
17120:
SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
After I put the account in local administrator group the service starts up.
I want to use the lowest privileges. Do I really need the SQL server service account in local administrator group? How to fix the error?
thanks

Hi baschuel,
It is recommended to run SQL Server service by using the lowest possible user rights and it is supported to use a domain account instead of an account from local Administrators group to configure SQL Server service. According to your error messages, the
issue could be due to that the incorrect certificate is used, or the domain account has no access to the Crypto folder(C:\ProgramData\Microsoft\Crypto). To troubleshoot the issue, you could follow the two solutions below.
1.Import the correct certificate following the steps in the article:
http://windows.microsoft.com/en-hk/windows/import-export-certificates-private-keys#1TC=windows-7
2.Grant the domain account full access to the Crypto folder.
Regards,
Michelle Li
If you have any feedback on our support, please click
here.

After changing 'MS SQL server' service's user name SDAC doesn't work properly

I've changed 'MS SQL Server' service user name
from .\admin (have had such already) to network_services
and now my oracle linked servers to Oracle instance stopped to work.
Namely, 'Cannot create an instance of OLE DB provider "OraOLEDB.Oracle" for linked server Ora_RO'.
In event log i see next:
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID
{2206CDB0-19C1-11D1-89E0-00C04FD7A829}
and APPID
{2206CDB0-19C1-11D1-89E0-00C04FD7A829}
to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.
So, MSDAINITIALIZE Class fails to start. I cannot locate this service under dcomcnfg. Could you help me?

The error seems to be clear what is causing the issue, check this link to fix this issue
Here the scenario is with SharePoint instead oracle so you can make out:-
http://www.wictorwilen.se/Post/Fix-the-SharePoint-DCOM-10016-error-on-Windows-Server-2008-R2.aspx
http://social.technet.microsoft.com/Forums/en-US/696204d5-b07e-46db-a785-737ea57b8da2/distributed-com-error-message
Mark ANSWER if this reply resolves your query, If helpful then VOTE HELPFUL
INSQLSERVER.COM
Mohammad Nizamuddin

Reviewing Windows NT Rights and Privileges Granted for SQL Server Service Accounts

Hi Folks,
I am an experienced .NET apps developer who has been tasked with writing a bunch of technical controls for all the SQL Server instances on a domain.
So for the last month I have been diving in the deep end learning Powershell, dba and infrastructure tasks. This is still a work in progress, so be kind to me.. ;o)
So the task I am stuck on is described in the section on 'Reviewing Windows NT Rights and Privileges Granted for SQL Server Service Accounts' http://technet.microsoft.com/en-us/library/ms143504(v=sql.105).aspx
I have not been able to find cmdlets that gives me this information. I have found some exes which come frustratingly close like NTRights.exe. This lets me specify a computer name which is great, but only seems to let you set or deny permissions, not just
list them!
Any help with this would be very much appreciated as I am firmly stuck. As per comments above also bear in mind that up until around 1.5 months ago I had never used powershell / knew very much at all about SQL server admin etc. Feeling much more comfortable
with them now, but much less so with Active Directory/ windows permission structures etc so please can I ask anyone kind enough to reply to try and keep the acronyms down as much as humanly possible.. ;o)
Cheers
Kieron

Hi Kieron,
Take a look at this module, it makes permissions much easier to work with than what's currently available:
https://gallery.technet.microsoft.com/scriptcenter/PowerShellAccessControl-d3be7b83
Don't retire TechNet! -
(Don't give up yet - 13,085+ strong and growing)

SQL Server services accounts using Managed Service Accounts

Hi guys,
Need your feedback on something, is it wiser to use Managed Service Accounts or normal domain accounts to run SQL Server services? MSA's only work in a single computer, so for every environment I would need to create a new set of sql services accounts.
If I create a single account wouldn't it be simpler? For instance domain\sqlservices and set it on every service and every environment (dev, qa and production)

Hi
It is a good question but the answer is not black or white. The answer is depend like most configuration questions.
I recommend you to use
Google to find blogs about the issue.
You can start from this links, which are great starting point for you question:
Best Practices For Using SQL Server Service Accounts
Book Online
Ronen Ariely
[Personal Site] [Blog] [Facebook]

The specified credentials that were provided for the SQL Server service are not valid

after i enter account name and password for server configuration...the error appear...is it problem with acc name or password?help!!

Hi help933,
According to your description, when you use the Server Configuration page of the SQL Server Installation Wizard to assign login accounts to SQL Server services, you can
assign the same login account to all SQL Server services, or you can configure each service account individually. You can also specify whether services start automatically, are started manually, or are disabled.
For example, on Windows Vista and Windows Server 2008 ,most accounts are set to the default NETWORK SERVICE account.
For more information, see:
http://msdn.microsoft.com/en-us/library/cc281953.aspx
Also there is a similar issue about seivice account, you can review the following post.
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/c7139740-ab93-48c2-b357-31bb7935b83d/rc0-rs-installation-problem-the-credentials-you-provided-for-reporting-services-service-are?forum=sqlsetupandupgrade
Thanks,
Sofiya Li
Sofiya Li
TechNet Community Support

SQL server service accounts question

We created a test SQL environment using a Technet evaluation copy of Windows Server 2012 along with an evaluation copy of SQL2012. After testing, everything is working as planned so were going to enter the product keys for both Windows Server and SQL 2012.
My question is that once we have our Server licensed we’re going to start a new domain and recreate all the user accounts but I installed SQL using a local user account I created called ”sqladmin”. Once Server 2012 is the DC in the new domain will I need to
change all the service accounts for SQL in order for it to function or can I still use the local “sqladmin” user account? If I can re-use that local account are there any downside to that? What’s the best practice in this scenario

Once Server 2012 is the DC in the new domain will I need to change all the service accounts for SQL in order for it to function or can I still use the local “sqladmin” user account? If I can re-use that local account are there any downside to that?
What’s the best practice in this scenario
Hi,
You can use your sqladmin account but that wont be a good security practice. You should always follow principal of least privilege and should run SQL server with domain account having least privilege.Below link will help you in this
Configure SQL server account and services
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers
My TechNet Wiki Articles

Want to change the SQL Server Agent Job History Text Files Location

We have SQL Server 2014 installed on a couple servers, but they were not consistent on directory paths during the installs. I am trying to get the servers to all match.
On one server, SQL Server the Agent Log and Job History files were being written to [H:\Data Root Directory\MSSQL12.MSSQLSERVER\MSSQL\Log].
I want to change that to [H:\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log] to match the other server.
I have ALREADY gone into SSMS - [SQL Server Agent] - [Properties] and changed the "Error Log " "Fle Name" to [H:\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log\SQLAGENT.OUT]. And that is working great.
In [SQL Server Configuration Manager] - [SQL Server (MSSQLSERVER)] - [Properties] - Startup Parameters entries have been changed to the new path (-d, -e, and -l), and under [Advanced] both Data Path and Dump Directory are pointing to the new path.
In [SQL Server Configuration Manager] - [SQL Server Agent (MSSQLSERVER)] - [Properties] - [Advanced] Dump Directory is pointing to the new path.
However, the job's History text files are still being written to the old path.
There is no setting in the Jobs or the Maintenance Plans that controls the history file location.
I have searched the registry and changed three settings from the old path to the new path. The registry does NOT contain any more references to the old path.
I rebooted the server, but when the jobs run their history text files are still be written to the old path.
Does anybody have any ideas?? Thanks

I checked the [Job] - [Step] - [Advanced ] - "Output File", and the field is blank.
I then reviewed all the tabs and left menu items in the Job...I cannot find any where the references the old path.
I then went to the Maintenance Plan and checked every thing there. Still cannot find what is referencing this old path.
SQL Server is also still writing xel files to this old path...if that offers any clues.
The text file being generated is the recap of the Job run. Starts with this:
Microsoft(R) Server Maintenance Utility (Unicode) Version 12.0.2430
Report was generated on "xxxxxxxxxxxxxxx".
Maintenance Plan: SQL_Backups_Log
Duration: 00:00:03
Status: Succeeded.
Details:
Thanks for the ideas....

Cannot start the SQL server service after you install Active Directory

Good Morning,
Im the system admin for a small company. We have a dedicated domain controller but it is the only one. To get a second domain controller up and running on our domain, I installed the AD role on our file and SQL server. After the reboot
we couldnt get SQL up and running. I found this article
http://support.microsoft.com/kb/929665
In the article it reads
To work around this issue, repair Windows Internal Database. To do this, run the following command line at a command prompt:
Msiexec /i SSEE_10.msi CALLERID=OCSetup.exe REINSTALL=ALL REINSTALLMODE=omus /qn REBOOT=ReallySupress /l*v <var><Log_File_Path></var>
My question is what is the Log_File_Path? Is that where I installed the AD log path?
My DBA is also looking into this as well.
Thanks in advance,
Brian
Brian Fink, MCSE

Hi Brain,
what's version of SQL Server that you have installed and what's your operationg system version info?
If you are running SQL Server 2008, which is not supported on the Windows Server 2008/2008 R2 domain controll (DC), even on Windows Server 2003 DC, there are limitations. Microsoft does not recommend to install SQL Server instances and DC on the same server,
for more information, see Install SQL Server on a Domain Controller (http://msdn.microsoft.com/en-us/library/ms143506.aspx#DC_Support).
There are some threads in the forum talked about installing SQL Server and DC on the same server, here are some for your references:
http://social.technet.microsoft.com/Forums/en-US/sqlsetupandupgrade/thread/1a2963ff-90d7-4bba-97ce-fa15f70fb6a8/
http://social.technet.microsoft.com/Forums/en-US/sqlsetupandupgrade/thread/981ef726-d04a-4063-8008-cc7bbad854ab/
Hope this helps. Please feel free to let me know if you have more questions.
Best Regards,
Chunsong Feng [MSFT]
Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

SQL Server Service is not reflecting to the new name.

Hi,
I just rename the computer and use the command below to rename the SQL Server but the SQL Server Service is not reflecting to the new name.
Is there a way to change the SQL Server Service and agent to reflect the new name or do I have to re-install sql server.
I am using SQL 2008 R2.
Thank you in advance.

If running "SELECT
@@servername" yields the old server name, it means the instance has not been renamed.
you must run statement to drop the old name of the instance and recreate it with the new name as the default (local) one..
EXEC master.dbo.sp_dropserver 'MACHINENAME\OLDINSTANCENAME'
go
EXEC master.dbo.sp_addserver 'MACHINENAME\newINSTANCENAME', 'local'
go
I took the code here:
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/c07ab906-dabf-4303-9737-d430d82c4f42/how-to-rename-instance-of-sql-server-2008-r2?forum=sqltools
Once you did this, look at your maintenance plans. I sometime end up having one or two still following the old name. Especially if you create this new server from a copy of another virtualized one.

Changing sql server service and sql server agent service startup account in SQL Server hosting SharePoint DB

Hi
i have a sharepoint deployment with one SQL Server (running on VM) hosting the config DB and another SQL Server (Physical Host because VM was running out of space) to host the huge Content DBs. I need to schedule automatic backups of the Content DBs to a
network share. For that i need to run the SQL Server Service with an account having permissions to the share as suggested in https://support.microsoft.com/kb/207187?wa=wsignin1.0
I tried changing the logon as a service account to a domain
account which has permissions to the Network Share and is also in local Administrators group of SQL Server and has "public and sysadmin" roles in SQL Server but that caused an issue. the SharePoint Web Application started showing a White Screen so
I had to revert back to the default accounts i.e. NT Service\SQLSERVERAGENT and NT Service\MSSQLSERVER. I viewed the event logs . These are the types of error i got after changing the logon as a service account to a domain account
1) Information Rights Management (IRM): Retried too many times to initialize IRM client. Cannot retry more. Retried times is:0x5.
System
Provider
[ Name]
Microsoft-SharePoint Products-SharePoint Foundation
[ Guid]
{6FB7E0CD-52E7-47DD-997A-241563931FC2}
EventID
5148
Version
15
Level
2
Task
9
Opcode
0
Keywords
0x4000000000000000
TimeCreated
[ SystemTime]
2015-02-02T04:46:04.750899500Z
EventRecordID
176477
Correlation
[ ActivityID]
{8FACE59C-1E17-50D0-7135-25FDB824CDBE}
Execution
[ ProcessID]
6912
[ ThreadID]
8872
Channel
Application
Computer
Security
[ UserID]
S-1-5-21-876248814-3204482948-604612597-111753
EventData
hex0
0x5
2)
Unknown SQL Exception 0 occurred. Additional error information from SQL Server is included below.
The target principal name is incorrect. Cannot generate SSPI context.
System
Provider
[ Name]
Microsoft-SharePoint Products-SharePoint Foundation
[ Guid]
{6FB7E0CD-52E7-47DD-997A-241563931FC2}
EventID
5586
Version
15
Level
2
Task
3
Opcode
0
Keywords
0x4000000000000000
TimeCreated
[ SystemTime]
2015-02-02T07:01:35.843757700Z
EventRecordID
176490
Correlation
[ ActivityID]
{50B4E59C-5E3A-50D0-7135-22AD91909F02}
Execution
[ ProcessID]
6912
[ ThreadID]
5452
Channel
Application
Computer
Security
[ UserID]
S-1-5-17
EventData
int0
0
string1
The target principal name is incorrect. Cannot generate SSPI context.

Hi Aparna,
According to your description, you get the above two errors when scheduling backups of Content DB. Right?
Based on those two error messages, they are related to the service principal name(SPN) for SQL Server service. Please verify the if the SPN is registered successfully. You can view it in ADSI Edit or use command line. Please see:
http://blogs.msdn.com/b/psssql/archive/2010/03/09/what-spn-do-i-use-and-how-does-it-get-there.aspx
When installing SQL Server, those two services below should be registered:
MSSQLSvc/servername:1433
MSSQLSvc/servername
Please check if those SPNs or duplicated SPNs exist. You can use command to reset SPN or remove duplicated SPN and add new one. See:
Setspn.
We have also met this issue when this SPN is registered under Administrator. Please try to register it under Computer. You can add it in ADSI Edit.
If you have any question, please feel free to ask.
Simon Hou
TechNet Community Support

Managed Service Accounts to run SQL Server Service

Has anyone played around with using managed service accounts for running the SQL Server Service? I am on a forest functional level of 2008R2 and was thinking about how cool it would be to use those for SQL Server. Unfortunately, I hear that it's not supported
by Microsoft and yet I've read about people doing that but would like to know if anyone has first hand experience. Otherwise, if not recommended, I'll stick to the old fashioned way of creating typical user accounts. Thanks in advance!

Hi Scott hi Sean
I see that my first answer was badly phrased.
Let me try to make it more clear:
Managed Service Accounts(MSA):
Works with Kerberos including Delegation, but:
NOT working with cluster nodes
NOT working for load balancing using Kerberos
More information:
http://blogs.technet.com/b/askds/archive/2009/09/10/managed-service-accounts-understanding-implementing-best-practices-and-troubleshooting.aspx
Group Managed Service Accounts (GMSA):
Works with Kerberos including Delegation, but:
NOT supported with Failover Clustered Instances
Here is the connect item:
http://connect.microsoft.com/SQLServer/feedback/details/767211/gmsa-for-sql-server-failover-clusters
@all Please feel free to vote(!). I am waiting for this as well.
This is the state of my information today. Feel free to correct me if you know of any changes.
Andreas Wolter (Blog |
Twitter)
MCM - Microsoft Certified Master SQL Server 2008
MCSM - Microsoft Certified Solutions Master Data Platform, SQL Server 2012
www.andreas-wolter.com |
www.SarpedonQualityLab.com

Can't Start the SQL Server & SQL Server Agent Services

Hello i had to make Help Please.
2014-10-31 12:18:55.66 Server Feb 10 2012 19:39:15
Copyright (c) Microsoft Standard Edition (64-bit) 2014-10-31 12:18:55.69 Server 2014-10-31 12:18:55.69 Server 2014-10-31 12:18:55.69 Server 2014-10-31 12:18:55.69 Server 2014-10-31 12:18:55.69 Server 2014-10-31 12:18:55.69 Server 2014-10-31 12:18:55.69 Server 2014-10-31 12:18:55.69 Server -d C:\Program Files\Microsoft -e C:\Program Files\Microsoft -l C:\Program Files\Microsoft 2014-10-31 12:18:55.69 Server -s "MSSQLSERVER"
2014-10-31 12:18:56.21 Server 2014-10-31 12:18:56.21 Server 2014-10-31 12:18:56.21 Server 2014-10-31 12:18:56.21 Server 2014-10-31 12:18:58.04 Server 2014-10-31 12:18:58.05 Server 2014-10-31 12:18:58.07 Server 2014-10-31 12:18:58.08 Server 2014-10-31 12:18:58.15 spid5s 2014-10-31 12:18:58.71 Server 2014-10-31 12:18:59.22 spid5s 2014-10-31 12:18:59.24 spid5s 2014-10-31 12:18:59.81 spid5s 2014-10-31 12:18:59.98 spid5s 2014-10-31 12:19:00.76 spid13s 2014-10-31 12:19:00.80 spid13s 2014-10-31 12:19:00.80 spid13s 2014-10-31 12:19:00.80 spid13s 2014-10-31 12:19:00.80 spid13s 2014-10-31 12:19:00.80 spid13s 2014-10-31 12:19:00.80 spid13s 2014-10-31 12:19:00.80 Server 2014-10-31 12:19:00.80 Server 2014-10-31 12:19:00.80 Server 2014-10-31 12:19:00.81 Server 2014-10-31 12:19:00.81 spid13s 2014-10-31 12:19:00.81 Server 2014-10-31 12:19:00.81 Server 2014-10-31 12:19:00.86 Server 2014-10-31 12:19:22.49 spid15s 2014-10-31 12:19:22.68 spid17s 2014-10-31 12:19:22.69 spid9s 2014-10-31 12:19:22.69 spid18s 2014-10-31 12:19:22.69 spid19s 2014-10-31 12:19:22.71 spid9s 2014-10-31 12:19:22.90 spid9s 2014-10-31 12:19:23.36 spid9s 2014-10-31 12:19:23.46 spid9s 2014-10-31 12:19:23.67 spid20s 2014-10-31 12:19:23.67 spid20s 2014-10-31 12:19:23.73 spid20s 2014-10-31 12:19:24.67 spid5s 2014-11-01 00:00:08.70 spid28s 2014-11-02 00:00:23.48 spid29s 2014-11-03 00:00:53.66 spid29s 2014-11-04 00:00:08.08 spid19s 2014-11-04 18:03:23.74 spid53 2014-11-04 18:03:23.79 spid53 2014-11-04 18:03:24.72 spid54 2014-11-04 18:03:24.78 spid54 2014-11-04 18:03:27.74 spid53 2014-11-04 18:28:12.10 spid52 2014-11-04 18:28:12.13 spid52 2014-11-05 00:00:26.82 spid18s a copy of my setup for a coworker in a different country to work with i can't make this two services to start. A timed out error shows and maybe the logs say something but i can't understand it.
Microsoft SQL Server 2012 - 11.0.2100.60 (X64)
Corporation
on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)
(c) Microsoft Corporation.
All rights reserved.
Server process ID is 2540.
System Manufacturer: 'VMware, Inc.', System Model: 'VMware Virtual Platform'.
Authentication mode is MIXED.
Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
The service account is 'NT Service\MSSQLSERVER'. This is an informational message; no user action is required.
Registry startup parameters:
SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\master.mdf
SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Log\ERRORLOG
SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
Command Line Startup Parameters:
SQL Server detected 1 sockets with 2 cores per socket and 2 logical processors per socket, 2 total logical processors; using 2 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
Detected 3071 MB of RAM. This is an informational message; no user action is required.
Using conventional memory in the memory manager.
This instance of SQL Server last reported using a process ID of 2532 at 31/10/2014 12:18:20 p.m. (local) 31/10/2014 06:18:20 p.m. (UTC). This is an informational message only; no user action is required.
Node configuration: node 0: CPU mask: 0x0000000000000003:0 Active CPU mask: 0x0000000000000003:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
Software Usage Metrics is disabled.
Starting up database 'master'.
CLR version v4.0.30319 loaded.
SQL Server Audit is starting the audits. This is an informational message. No user action is required.
SQL Server Audit has started the audits. This is an informational message. No user action is required.
SQL Trace ID 1 was started by login "sa".
Server name is 'WIN-3FNEFF25D4V'. This is an informational message only. No user action is required.
A self-generated certificate was successfully loaded for encryption.
Server is listening on [ 'any' <ipv6> 1435].
Server is listening on [ 'any' <ipv4> 1435].
Server is listening on [ 'any' <ipv6> 1433].
Server is listening on [ 'any' <ipv4> 1433].
Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
Server local connection provider is ready to accept connection on [ \\.\pipe\sql\query ].
Server is listening on [ ::1 <ipv6> 1434].
Server is listening on [ 127.0.0.1 <ipv4> 1434].
Dedicated admin connection support was established for listening locally on port 1434.
SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service. This is an informational message. No user action is required.
SQL Server is now ready for client connections. This is an informational message; no user action is required.
The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/WIN-3FNEFF25D4V ] for the SQL Server service. Windows return code: 0xffffffff, state: 63. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered.
The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/WIN-3FNEFF25D4V:1433 ] for the SQL Server service. Windows return code: 0xffffffff, state: 63. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered.
Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
A new instance of the full-text filter daemon host process has been successfully started.
Starting up database 'msdb'.
Starting up database 'mssqlsystemresource'.
Starting up database 'CMOVILBD'.
Starting up database 'ArgusTec'.
The resource database build version is 11.00.2100. This is an informational message only. No user action is required.
Starting up database 'model'.
Clearing tempdb database.
Starting up database 'tempdb'.
The Service Broker endpoint is in disabled or stopped state.
The Database Mirroring endpoint is in disabled or stopped state.
Service Broker manager has started.
Recovery is complete. This is an informational message only. No user action is required.
This instance of SQL Server has been using a process ID of 2540 since 31/10/2014 12:19:24 p.m. (local) 31/10/2014 06:19:24 p.m. (UTC). This is an informational message only; no user action is required.
This instance of SQL Server has been using a process ID of 2540 since 31/10/2014 12:19:24 p.m. (local) 31/10/2014 06:19:24 p.m. (UTC). This is an informational message only; no user action is required.
This instance of SQL Server has been using a process ID of 2540 since 31/10/2014 12:19:24 p.m. (local) 31/10/2014 06:19:24 p.m. (UTC). This is an informational message only; no user action is required.
This instance of SQL Server has been using a process ID of 2540 since 31/10/2014 12:19:24 p.m. (local) 31/10/2014 06:19:24 p.m. (UTC). This is an informational message only; no user action is required.
Attempting to load library 'xpsqlbot.dll' into memory. This is an informational message only. No user action is required.
Using 'xpsqlbot.dll' version '2011.110.2100' to execute extended stored procedure 'xp_qv'. This is an informational message only; no user action is required.
Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
Using 'xpstar.dll' version '2011.110.2100' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
Starting up database 'Argus'.
Attempting to load library 'xplog70.dll' into memory. This is an informational message only. No user action is required.
Using 'xplog70.dll' version '2011.110.2100' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required.
This instance of SQL Server has been using a process ID of 2540 since 31/10/2014 12:19:24 p.m. (local) 31/10/2014 06:19:24 p.m. (UTC). This is an informational message only; no user action is required.

Sorry i feel so stupid. Here it is. I can clearly see the errors now
2014-11-05 10:49:47.43 Server Microsoft SQL Server 2008 (SP1) - 10.0.2531.0 (X64)
Mar 29 2009 10:11:52
Copyright (c) 1988-2008 Microsoft Corporation
Express Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (VM)
2014-11-05 10:49:47.43 Server (c) 2005 Microsoft Corporation.
2014-11-05 10:49:47.43 Server All rights reserved.
2014-11-05 10:49:47.43 Server Server process ID is 4596.
2014-11-05 10:49:47.43 Server System Manufacturer: 'VMware, Inc.', System Model: 'VMware Virtual Platform'.
2014-11-05 10:49:47.43 Server Authentication mode is MIXED.
2014-11-05 10:49:47.43 Server Logging SQL Server messages in file 'c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\Log\ERRORLOG'.
2014-11-05 10:49:47.43 Server This instance of SQL Server last reported using a process ID of 5720 at 05/11/2014 10:28:35 a.m. (local) 05/11/2014 04:28:35 p.m. (UTC). This is an informational message only; no user action is required.
2014-11-05 10:49:47.43 Server Registry startup parameters:
-d c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\DATA\master.mdf
-e c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\Log\ERRORLOG
-l c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\DATA\mastlog.ldf
2014-11-05 10:49:47.44 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2014-11-05 10:49:47.44 Server Detected 2 CPUs. This is an informational message; no user action is required.
2014-11-05 10:49:47.46 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2014-11-05 10:49:47.49 Server Node configuration: node 0: CPU mask: 0x0000000000000003 Active CPU mask: 0x0000000000000003. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2014-11-05 10:49:47.50 spid7s Starting up database 'master'.
2014-11-05 10:49:47.59 spid7s FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'SQLEXPRESS'.
2014-11-05 10:49:47.60 spid7s SQL Trace ID 1 was started by login "sa".
2014-11-05 10:49:47.60 spid7s Starting up database 'mssqlsystemresource'.
2014-11-05 10:49:47.61 spid7s The resource database build version is 10.00.2531. This is an informational message only. No user action is required.
2014-11-05 10:49:47.67 spid7s Server name is 'WIN-3FNEFF25D4V\SQLEXPRESS'. This is an informational message only. No user action is required.
2014-11-05 10:49:47.67 spid10s Starting up database 'model'.
2014-11-05 10:49:47.68 spid7s Informational: No full-text supported languages found.
2014-11-05 10:49:47.68 spid7s Starting up database 'msdb'.
2014-11-05 10:49:47.76 spid10s Clearing tempdb database.
2014-11-05 10:49:47.83 Server A self-generated certificate was successfully loaded for encryption.
2014-11-05 10:49:47.83 Server Error: 26023, Severity: 16, State: 1.
2014-11-05 10:49:47.83 Server Server TCP provider failed to listen on [ 'any' <ipv6> 1433]. Tcp port is already in use.
2014-11-05 10:49:47.83 Server Error: 17182, Severity: 16, State: 1.
2014-11-05 10:49:47.83 Server TDSSNIClient initialization failed with error 0x2740, status code 0xa. Reason: Unable to initialize the TCP/IP listener.
2014-11-05 10:49:47.83 Server Error: 17182, Severity: 16, State: 1.
2014-11-05 10:49:47.83 Server TDSSNIClient initialization failed with error 0x2740, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors.
2014-11-05 10:49:47.83 Server Error: 17826, Severity: 18, State: 3.
2014-11-05 10:49:47.83 Server Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
2014-11-05 10:49:47.83 Server Error: 17120, Severity: 16, State: 1.
2014-11-05 10:49:47.83 Server SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

Does changing the SQL Server Service Account impact FILESTREAM data?

Similar Messages

Maybe you are looking for