Merge deadlock

Hi, more or less once a day I receive this message from the merge
replication, because is continuous suddenly stops. I try to put an extra step
on the job to restart it but is ignored. Any clues why my step is ignored or
why this problem is happening?
cheers , Error:
The process could not enumerate changes at the 'Subscriber'.
(Source: Merge Replication Provider (Agent); Error number: -2147200999)
------
Transaction (Process ID 87) was deadlocked on lock resources with another
process and has been chosen as the deadlock victim. Rerun the transaction.
(Source: SUMSTR (Data source); Error number: 1205)
------
The process was successfully stopped.
(Source: Merge Replication Provider (Agent); Error number: -2147200999)
------
If you have large numbers of subscribers you might want to limit concurrent
processing or perhaps schedule your merge agents as opposed to running them
simultaneously or continuously.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Salvador" <Salvador@.discussions.microsoft.com> wrote in message
news:BA09357D-8EE6-42A4-97C3-72384153AD02@.microsoft.com...
> Hi, more or less once a day I receive this message from the merge
> replication, because is continuous suddenly stops. I try to put an extra
step
> on the job to restart it but is ignored. Any clues why my step is ignored
or
> why this problem is happening?
> cheers , Error:
> The process could not enumerate changes at the 'Subscriber'.
> (Source: Merge Replication Provider (Agent); Error number: -2147200999)
> ----
--
> Transaction (Process ID 87) was deadlocked on lock resources with another
> process and has been chosen as the deadlock victim. Rerun the transaction.
> (Source: SUMSTR (Data source); Error number: 1205)
> ----
--
> The process was successfully stopped.
> (Source: Merge Replication Provider (Agent); Error number: -2147200999)
> ----

Merge agent fails due to deadlock

Hi:
I met a problem this morning. the merge replication agen stopped, the
error message shows:
The process could not enumerate changes at the 'Publisher'.
(Source: Merge Replication Provider (Agent); Error number: -2147200999)
-----
Transaction (Process ID 79) was deadlocked on lock resources with
another process and has been chosen as the deadlock victim. Rerun the
transaction.
(Source: XXXXXX (Data source); Error number: 1205)
The process was successfully stopped.
(Source: Merge Replication Provider (Agent); Error number: -2147200999)
I never met this issue before, so please help
1) What may cause this issue?
2) How I could identify which process cause the deadlock issue?
3) Is there any way to log more information to identify what resource
is deadlock, and by who.
Thanks
Yong
Yong,
have a look at enabling traceflags 1204, 1205, 3605 to get more info. Don't
forget to turn off afterwards. Alternatively if you have sql server 2005,
the profiler shows the deadlock tree graphically.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
sql

merge agent

sql server enterprise manager could not start merge agent
error:22022 can any one tell the solution for this would be appreciated.
Message posted via http://www.droptable.com
I think we need more info...what is the whole error message?
However, here are some tips on getting more details.
-Check the agent history (expand steps) for more detail about errors.
-Put an output file on the merge agent (use -Output c:\merge.txt
-OutputVerboseLevel 3)
-Try starting the agent from the command line (with an output file! :-))
-Check SQL Errorlog, SQL Agent Errorlog, and Application and System event
logs for more errors.
Tell us what you find so we can be more help. Or let me know if you need
exact steps on setting up an output file.
Donna
"pardhi a via droptable.com" wrote:

> sql server enterprise manager could not start merge agent
> error:22022 can any one tell the solution for this would be appreciated.
> --
> Message posted via http://www.droptable.com
>
|||Hi Donna
Thanks it is working.Thanks for immediate response.
as you said i copied into the file then saw an error showing (cannot
generate SSPI context) then i stop and restart the agent from then onwards
starts working fine.you have any idea why (cannnot generate sspi context)
cause of the error.
Message posted via http://www.droptable.com

Memory Tab; SQL Server Properties (Accessing)

Hi,
- I cannot access the Memory Tab to change the memory settings.
- I receive the following error message: Error 8651: Could not perform the
requested operation because the minimum query memory is not available.
Decrease the configured value for the 'min memory per query' server
configuration option.
- The maximum memory was accidentily set to 0 in the SQL Server Properties
Memory Tab.
Is there another way to access and change the maximum memory setting other
than through Enterprise Manager?
Thank you.
BillSee sp_configure in SQL Server Books Online.
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"BillC-CA" <BillC-CA@.discussions.microsoft.com> wrote in message
news:E29C205C-BC23-4B3B-BCBC-A95FCC806551@.microsoft.com...
Hi,
- I cannot access the Memory Tab to change the memory settings.
- I receive the following error message: Error 8651: Could not perform the
requested operation because the minimum query memory is not available.
Decrease the configured value for the 'min memory per query' server
configuration option.
- The maximum memory was accidentily set to 0 in the SQL Server Properties
Memory Tab.
Is there another way to access and change the maximum memory setting other
than through Enterprise Manager?
Thank you.
Bill|||Check out sp_configure in BooksOnLine.
--
Andrew J. Kelly SQL MVP
"BillC-CA" <BillC-CA@.discussions.microsoft.com> wrote in message
news:E29C205C-BC23-4B3B-BCBC-A95FCC806551@.microsoft.com...
> Hi,
> - I cannot access the Memory Tab to change the memory settings.
> - I receive the following error message: Error 8651: Could not perform the
> requested operation because the minimum query memory is not available.
> Decrease the configured value for the 'min memory per query' server
> configuration option.
> - The maximum memory was accidentily set to 0 in the SQL Server Properties
> Memory Tab.
> Is there another way to access and change the maximum memory setting other
> than through Enterprise Manager?
> Thank you.
> Bill
>|||Hi Narayana,
Thank you for the suggestion.
I entered the following in the query analyzer, and was then able to access
the memory tab again to make the correction to max memory:
sp_configure 'max server memory', 2147483647
go
reconfigure
go
Thank you!
Bill
"Narayana Vyas Kondreddi" wrote:
> See sp_configure in SQL Server Books Online.
> --
> HTH,
> Vyas, MVP (SQL Server)
> SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
>
> "BillC-CA" <BillC-CA@.discussions.microsoft.com> wrote in message
> news:E29C205C-BC23-4B3B-BCBC-A95FCC806551@.microsoft.com...
> Hi,
> - I cannot access the Memory Tab to change the memory settings.
> - I receive the following error message: Error 8651: Could not perform the
> requested operation because the minimum query memory is not available.
> Decrease the configured value for the 'min memory per query' server
> configuration option.
> - The maximum memory was accidentily set to 0 in the SQL Server Properties
> Memory Tab.
> Is there another way to access and change the maximum memory setting other
> than through Enterprise Manager?
> Thank you.
> Bill
>
>|||Hi Andrew,
Thank you for the suggestion.
I entered the following in the query analyzer, and was then able to access
the memory tab again to make the correction to max memory:
sp_configure 'max server memory', 2147483647
go
reconfigure
go
Thank you!
Bill
"Andrew J. Kelly" wrote:
> Check out sp_configure in BooksOnLine.
> --
> Andrew J. Kelly SQL MVP
>
> "BillC-CA" <BillC-CA@.discussions.microsoft.com> wrote in message
> news:E29C205C-BC23-4B3B-BCBC-A95FCC806551@.microsoft.com...
> > Hi,
> > - I cannot access the Memory Tab to change the memory settings.
> > - I receive the following error message: Error 8651: Could not perform the
> > requested operation because the minimum query memory is not available.
> > Decrease the configured value for the 'min memory per query' server
> > configuration option.
> > - The maximum memory was accidentily set to 0 in the SQL Server Properties
> > Memory Tab.
> >
> > Is there another way to access and change the maximum memory setting other
> > than through Enterprise Manager?
> >
> > Thank you.
> > Bill
> >
>
>

Memory Tab; SQL Server Properties (Accessing)

Hi,
- I cannot access the Memory Tab to change the memory settings.
- I receive the following error message: Error 8651: Could not perform the
requested operation because the minimum query memory is not available.
Decrease the configured value for the 'min memory per query' server
configuration option.
- The maximum memory was accidentily set to 0 in the SQL Server Properties
Memory Tab.
Is there another way to access and change the maximum memory setting other
than through Enterprise Manager?
Thank you.
Bill
See sp_configure in SQL Server Books Online.
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"BillC-CA" <BillC-CA@.discussions.microsoft.com> wrote in message
news:E29C205C-BC23-4B3B-BCBC-A95FCC806551@.microsoft.com...
Hi,
- I cannot access the Memory Tab to change the memory settings.
- I receive the following error message: Error 8651: Could not perform the
requested operation because the minimum query memory is not available.
Decrease the configured value for the 'min memory per query' server
configuration option.
- The maximum memory was accidentily set to 0 in the SQL Server Properties
Memory Tab.
Is there another way to access and change the maximum memory setting other
than through Enterprise Manager?
Thank you.
Bill
|||Check out sp_configure in BooksOnLine.
Andrew J. Kelly SQL MVP
"BillC-CA" <BillC-CA@.discussions.microsoft.com> wrote in message
news:E29C205C-BC23-4B3B-BCBC-A95FCC806551@.microsoft.com...
> Hi,
> - I cannot access the Memory Tab to change the memory settings.
> - I receive the following error message: Error 8651: Could not perform the
> requested operation because the minimum query memory is not available.
> Decrease the configured value for the 'min memory per query' server
> configuration option.
> - The maximum memory was accidentily set to 0 in the SQL Server Properties
> Memory Tab.
> Is there another way to access and change the maximum memory setting other
> than through Enterprise Manager?
> Thank you.
> Bill
>
|||Hi Narayana,
Thank you for the suggestion.
I entered the following in the query analyzer, and was then able to access
the memory tab again to make the correction to max memory:
sp_configure 'max server memory', 2147483647
go
reconfigure
go
Thank you!
Bill
"Narayana Vyas Kondreddi" wrote:

> See sp_configure in SQL Server Books Online.
> --
> HTH,
> Vyas, MVP (SQL Server)
> SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
>
> "BillC-CA" <BillC-CA@.discussions.microsoft.com> wrote in message
> news:E29C205C-BC23-4B3B-BCBC-A95FCC806551@.microsoft.com...
> Hi,
> - I cannot access the Memory Tab to change the memory settings.
> - I receive the following error message: Error 8651: Could not perform the
> requested operation because the minimum query memory is not available.
> Decrease the configured value for the 'min memory per query' server
> configuration option.
> - The maximum memory was accidentily set to 0 in the SQL Server Properties
> Memory Tab.
> Is there another way to access and change the maximum memory setting other
> than through Enterprise Manager?
> Thank you.
> Bill
>
>
|||Hi Andrew,
Thank you for the suggestion.
I entered the following in the query analyzer, and was then able to access
the memory tab again to make the correction to max memory:
sp_configure 'max server memory', 2147483647
go
reconfigure
go
Thank you!
Bill
"Andrew J. Kelly" wrote:

> Check out sp_configure in BooksOnLine.
> --
> Andrew J. Kelly SQL MVP
>
> "BillC-CA" <BillC-CA@.discussions.microsoft.com> wrote in message
> news:E29C205C-BC23-4B3B-BCBC-A95FCC806551@.microsoft.com...
>
>

Memory Tab; SQL Server Properties (Accessing)

Hi,
- I cannot access the Memory Tab to change the memory settings.
- I receive the following error message: Error 8651: Could not perform the
requested operation because the minimum query memory is not available.
Decrease the configured value for the 'min memory per query' server
configuration option.
- The maximum memory was accidentily set to 0 in the SQL Server Properties
Memory Tab.
Is there another way to access and change the maximum memory setting other
than through Enterprise Manager?
Thank you.
BillSee sp_configure in SQL Server Books Online.
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"BillC-CA" <BillC-CA@.discussions.microsoft.com> wrote in message
news:E29C205C-BC23-4B3B-BCBC-A95FCC806551@.microsoft.com...
Hi,
- I cannot access the Memory Tab to change the memory settings.
- I receive the following error message: Error 8651: Could not perform the
requested operation because the minimum query memory is not available.
Decrease the configured value for the 'min memory per query' server
configuration option.
- The maximum memory was accidentily set to 0 in the SQL Server Properties
Memory Tab.
Is there another way to access and change the maximum memory setting other
than through Enterprise Manager?
Thank you.
Bill|||Check out sp_configure in BooksOnLine.
Andrew J. Kelly SQL MVP
"BillC-CA" <BillC-CA@.discussions.microsoft.com> wrote in message
news:E29C205C-BC23-4B3B-BCBC-A95FCC806551@.microsoft.com...
> Hi,
> - I cannot access the Memory Tab to change the memory settings.
> - I receive the following error message: Error 8651: Could not perform the
> requested operation because the minimum query memory is not available.
> Decrease the configured value for the 'min memory per query' server
> configuration option.
> - The maximum memory was accidentily set to 0 in the SQL Server Properties
> Memory Tab.
> Is there another way to access and change the maximum memory setting other
> than through Enterprise Manager?
> Thank you.
> Bill
>|||Hi Narayana,
Thank you for the suggestion.
I entered the following in the query analyzer, and was then able to access
the memory tab again to make the correction to max memory:
sp_configure 'max server memory', 2147483647
go
reconfigure
go
Thank you!
Bill
"Narayana Vyas Kondreddi" wrote:

> See sp_configure in SQL Server Books Online.
> --
> HTH,
> Vyas, MVP (SQL Server)
> SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
>
> "BillC-CA" <BillC-CA@.discussions.microsoft.com> wrote in message
> news:E29C205C-BC23-4B3B-BCBC-A95FCC806551@.microsoft.com...
> Hi,
> - I cannot access the Memory Tab to change the memory settings.
> - I receive the following error message: Error 8651: Could not perform the
> requested operation because the minimum query memory is not available.
> Decrease the configured value for the 'min memory per query' server
> configuration option.
> - The maximum memory was accidentily set to 0 in the SQL Server Properties
> Memory Tab.
> Is there another way to access and change the maximum memory setting other
> than through Enterprise Manager?
> Thank you.
> Bill
>
>|||Hi Andrew,
Thank you for the suggestion.
I entered the following in the query analyzer, and was then able to access
the memory tab again to make the correction to max memory:
sp_configure 'max server memory', 2147483647
go
reconfigure
go
Thank you!
Bill
"Andrew J. Kelly" wrote:

> Check out sp_configure in BooksOnLine.
> --
> Andrew J. Kelly SQL MVP
>
> "BillC-CA" <BillC-CA@.discussions.microsoft.com> wrote in message
> news:E29C205C-BC23-4B3B-BCBC-A95FCC806551@.microsoft.com...
>
>

Memory paging out noted in errorlog

As my SQL Server starts, in the SQL error log, there is a message as
follows:
A significant part of sql server process memory has been paged out. This may
result in a performance degradation. Duration: 0 seconds. Working set (KB):
37376, committed (KB): 105592, memory utilization: 35%.
Do I have to be concerned ? I have 64 bit and 16GB of RAM
What is min/max server memory settings? Are there other processes running
on the server that are eating up memory? Paging in general is horrible for
performance.
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
"Hassan" <hassan@.test.com> wrote in message
news:OtgJd4CJIHA.3672@.TK2MSFTNGP02.phx.gbl...
> As my SQL Server starts, in the SQL error log, there is a message as
> follows:
> A significant part of sql server process memory has been paged out. This
> may result in a performance degradation. Duration: 0 seconds. Working set
> (KB): 37376, committed (KB): 105592, memory utilization: 35%.
> Do I have to be concerned ? I have 64 bit and 16GB of RAM
>

Memory paging out noted in errorlog

As my SQL Server starts, in the SQL error log, there is a message as
follows:
A significant part of sql server process memory has been paged out. This may
result in a performance degradation. Duration: 0 seconds. Working set (KB):
37376, committed (KB): 105592, memory utilization: 35%.
Do I have to be concerned ? I have 64 bit and 16GB of RAMWhat is min/max server memory settings? Are there other processes running
on the server that are eating up memory? Paging in general is horrible for
performance.
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
"Hassan" <hassan@.test.com> wrote in message
news:OtgJd4CJIHA.3672@.TK2MSFTNGP02.phx.gbl...
> As my SQL Server starts, in the SQL error log, there is a message as
> follows:
> A significant part of sql server process memory has been paged out. This
> may result in a performance degradation. Duration: 0 seconds. Working set
> (KB): 37376, committed (KB): 105592, memory utilization: 35%.
> Do I have to be concerned ? I have 64 bit and 16GB of RAM
>

Memory paging out noted in errorlog

As my SQL Server starts, in the SQL error log, there is a message as
follows:
A significant part of sql server process memory has been paged out. This may
result in a performance degradation. Duration: 0 seconds. Working set (KB):
37376, committed (KB): 105592, memory utilization: 35%.
Do I have to be concerned ? I have 64 bit and 16GB of RAMWhat is min/max server memory settings? Are there other processes running
on the server that are eating up memory? Paging in general is horrible for
performance.
--
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
"Hassan" <hassan@.test.com> wrote in message
news:OtgJd4CJIHA.3672@.TK2MSFTNGP02.phx.gbl...
> As my SQL Server starts, in the SQL error log, there is a message as
> follows:
> A significant part of sql server process memory has been paged out. This
> may result in a performance degradation. Duration: 0 seconds. Working set
> (KB): 37376, committed (KB): 105592, memory utilization: 35%.
> Do I have to be concerned ? I have 64 bit and 16GB of RAM
>

Memory Manager

The CPU pegged on a production server this morning. There is a warning
message in the log. I'm not sure what it means. Or what to do to prevent it
in the future.
Date 1/23/2008 4:11:36 AM
Log SQL Server (Archive #1 - 1/23/2008 6:41:00 AM)
Source spid3s
Message
Memory Manager
VM Reserved = 8521512 KB
VM Committed = 8504536 KB
AWE Allocated = 0 KB
Reserved Memory = 1024 KB
Reserved Memory In Use = 0 KB
Then later on
Date 1/23/2008 4:11:36 AM
Log SQL Server (Archive #1 - 1/23/2008 6:41:00 AM)
Source spid3s
Message
MEMORYCLERK_SQLGENERAL (Total)
VM Reserved = 0 KB
VM Committed = 0 KB
AWE Allocated = 0 KB
SM Reserved = 0 KB
SM Committed = 0 KB
SinglePage Allocator = 28920 KB
MultiPage Allocator = 4888 KB
Still later
Date 1/23/2008 4:11:36 AM
Log SQL Server (Archive #1 - 1/23/2008 6:41:00 AM)
Source spid3s
Message
Buffer Counts: Committed=1032192 Target=1047941 Hashed=608946
Internal Reservation=209588 External Reservation=1297
Stolen Potential=571000
Min Free=128 Visible=1047941
Available Paging File=858726400
Finally:
Date 1/23/2008 4:12:19 AM
Log SQL Server (Archive #1 - 1/23/2008 6:41:00 AM)
Source Server
Message
***Stack Dump being sent to D:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\LOG\SQLDump0008.txt
--
Regards,
JamieProbably time to call Microsoft tech support. Or scan the bug fix lists for
all patches you don't have on your server to see if one of them addresses
the symptoms you are seeing.
--
Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net
"thejamie" <thejamie@.discussions.microsoft.com> wrote in message
news:B2F823A0-5AB3-4EF6-8F16-D515052F7DE4@.microsoft.com...
> The CPU pegged on a production server this morning. There is a warning
> message in the log. I'm not sure what it means. Or what to do to prevent
> it
> in the future.
> Date 1/23/2008 4:11:36 AM
> Log SQL Server (Archive #1 - 1/23/2008 6:41:00 AM)
> Source spid3s
> Message
> Memory Manager
> VM Reserved = 8521512 KB
> VM Committed = 8504536 KB
> AWE Allocated = 0 KB
> Reserved Memory = 1024 KB
> Reserved Memory In Use = 0 KB
>
> Then later on
> Date 1/23/2008 4:11:36 AM
> Log SQL Server (Archive #1 - 1/23/2008 6:41:00 AM)
> Source spid3s
> Message
> MEMORYCLERK_SQLGENERAL (Total)
> VM Reserved = 0 KB
> VM Committed = 0 KB
> AWE Allocated = 0 KB
> SM Reserved = 0 KB
> SM Committed = 0 KB
> SinglePage Allocator = 28920 KB
> MultiPage Allocator = 4888 KB
> Still later
> Date 1/23/2008 4:11:36 AM
> Log SQL Server (Archive #1 - 1/23/2008 6:41:00 AM)
> Source spid3s
> Message
> Buffer Counts: Committed=1032192 Target=1047941 Hashed=608946
> Internal Reservation=209588 External Reservation=1297
> Stolen Potential=571000
> Min Free=128 Visible=1047941
> Available Paging File=858726400
>
> Finally:
> Date 1/23/2008 4:12:19 AM
> Log SQL Server (Archive #1 - 1/23/2008 6:41:00 AM)
> Source Server
> Message
> ***Stack Dump being sent to D:\Program Files\Microsoft SQL
> Server\MSSQL.1\MSSQL\LOG\SQLDump0008.txt
>
> --
> Regards,
> Jamie