FS Agent - Cannot enlist in the transaction because the transaction does not exist.
-
jueves, 19 de abril de 2012 15:31
Wondering if anybody has an idea what might be causing this.
On one of my servers, I keep seing the following in the sql server log:
"Cannot enlist in the transaction because the transaction does not exist."
Those error are output on four different spids. When I look at those spids, I find they are all related to the "FS Agent". (File Stream Agent).
Anybody had this issue or has an hypothesis on what might be causing this issue?
Todas las respuestas
-
jueves, 19 de abril de 2012 15:45
Are u on Win2003 OS.
http://support.microsoft.com/kb/955280
Mohd Sufian www.sqlship.wordpress.com Please mark the post as Answered if it helped.
-
jueves, 19 de abril de 2012 18:01No, windows server 2008 r2.
sql server is sql server 2008 r2.- Editado Antoine F jueves, 19 de abril de 2012 18:04
-
viernes, 20 de abril de 2012 7:54ModeradorHi Antoine F,
>> Cannot enlist in the transaction because the transaction does not exist
Regarding to the error message you provided and my research, this cause of this problem is not related to the FILESTREAM feature in SQL Serve. This problem occurs because of an error in the Server service. The Server service incorrectly delays the request of closing file handles. Therefore, the transactions cannot commit.
According to this error message, there is a Hotfix for Windows server 2008. Seems your OS is Server 2008 R2, so pleaser follow the WORKAOUND section from this KB to fix the error.Regards, Amber zhang
-
sábado, 21 de abril de 2012 11:51can u paste the output of sp_configure
Mohd Sufian www.sqlship.wordpress.com Please mark the post as Answered if it helped.
-
martes, 24 de abril de 2012 21:01
Amber, This definitly is the error I get. That said, I run on sql server 2008 r2 on windows server 2008 r2? This KB was written for sql server 2008 and windows server 2008 (no r2).
That said, I installed a fix for the following kb earlier this year: http://support.microsoft.com/kb/2255379
Mohammad, here is the results of sp_configure.
name minimum maximum config_value run_value
----------------------------------- ----------- ----------- ------------ -----------
access check cache bucket count 0 65536 0 0
access check cache quota 0 2147483647 0 0
Ad Hoc Distributed Queries 0 1 0 0
affinity I/O mask -2147483648 2147483647 0 0
affinity mask -2147483648 2147483647 0 0
affinity64 I/O mask -2147483648 2147483647 0 0
affinity64 mask -2147483648 2147483647 0 0
Agent XPs 0 1 1 1
allow updates 0 1 0 0
awe enabled 0 1 0 0
backup compression default 0 1 1 1
blocked process threshold (s) 0 86400 0 0
c2 audit mode 0 1 0 0
clr enabled 0 1 0 0
common criteria compliance enabled 0 1 0 0
cost threshold for parallelism 0 32767 5 5
cross db ownership chaining 0 1 0 0
cursor threshold -1 2147483647 -1 -1
Database Mail XPs 0 1 1 1
default full-text language 0 2147483647 1033 1033
default language 0 9999 0 0
default trace enabled 0 1 1 1
disallow results from triggers 0 1 0 0
EKM provider enabled 0 1 0 0
filestream access level 0 2 2 2
fill factor (%) 0 100 0 0
ft crawl bandwidth (max) 0 32767 100 100
ft crawl bandwidth (min) 0 32767 0 0
ft notify bandwidth (max) 0 32767 100 100
ft notify bandwidth (min) 0 32767 0 0
index create memory (KB) 704 2147483647 0 0
in-doubt xact resolution 0 2 0 0
lightweight pooling 0 1 0 0
locks 5000 2147483647 0 0
max degree of parallelism 0 1024 0 0
max full-text crawl range 0 256 4 4
max server memory (MB) 16 2147483647 2147483647 2147483647
max text repl size (B) -1 2147483647 65536 65536
max worker threads 128 32767 0 0
media retention 0 365 0 0
min memory per query (KB) 512 2147483647 1024 1024
min server memory (MB) 0 2147483647 0 0
nested triggers 0 1 1 1
network packet size (B) 512 32767 4096 4096
Ole Automation Procedures 0 1 0 0
open objects 0 2147483647 0 0
optimize for ad hoc workloads 0 1 0 0
PH timeout (s) 1 3600 60 60
precompute rank 0 1 0 0
priority boost 0 1 0 0
query governor cost limit 0 2147483647 0 0
query wait (s) -1 2147483647 -1 -1
recovery interval (min) 0 32767 0 0
remote access 0 1 1 1
remote admin connections 0 1 0 0
remote login timeout (s) 0 2147483647 20 20
remote proc trans 0 1 0 0
remote query timeout (s) 0 2147483647 600 600
Replication XPs 0 1 0 0
scan for startup procs 0 1 1 1
server trigger recursion 0 1 1 1
set working set size 0 1 0 0
show advanced options 0 1 1 1
SMO and DMO XPs 0 1 1 1
SQL Mail XPs 0 1 0 0
transform noise words 0 1 0 0
two digit year cutoff 1753 9999 2049 2049
user connections 0 32767 0 0
user options 0 32767 0 0
xp_cmdshell 0 1 1 1
Also:select @@versionMicrosoft SQL Server 2008 R2 (SP1) - 10.50.2500.0 (X64)
Jun 17 2011 00:54:03
Copyright (c) Microsoft Corporation
Enterprise Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
-
miércoles, 25 de abril de 2012 5:06
Are you using filestream? Looking at the sp_configure result , you have enabled filestream
2-Enables FILESTREAM for Transact-SQL and Win32 streaming access.
filestream access level 0 2 2 2
Mohd Sufian www.sqlship.wordpress.com Please mark the post as Answered if it helped.
- Editado Mohammad Sufian [MSFT] miércoles, 25 de abril de 2012 5:12
-
miércoles, 25 de abril de 2012 15:28Yes I am.

