SQL Server Performance

Can not retrieve agent status

Discussion in 'SQL Server 2005 Replication' started by LiangZhu1, Apr 3, 2007.

  1. LiangZhu1 New Member

    Hello, Everybody,

    I am using SQL Server 2005 work group Edition SP2 and Hotfix1.

    I am doing Transaction Replication between my central Server & client server. After I created the new publisher, I got the following fatal exception:

    "An exception occurred while executing a transact-sql statment or batch.
    Lock request time out period exceeded
    The statment has been terminated (microsoft sql server, error:1222)"

    After that exception, the snapshot agent works fine but when I tried to start the log reader agent I got the following message:

    "Could not retrieve agent status. (no agent status information is available. (View
    Log Reader Agent status)

    I just can not start the log reader agent. I have tried recreated the publisher, restart the sql server agent, increased the QueryTimeout to 3600 and I even killed the sql server agent jobs associated with the publisher, none of them helped.
    I will be very much appreciated if someone could give me some help!

    Thank you!
    Liang
  2. dineshasanka Moderator

  3. LiangZhu1 New Member

    Dine,

    Thank you for the reply! I have updated my SQL Server 2005 Work Group with sp2 and the hotfix associated with sp2. They did not make any difference.

    Thank you,
    Liang
  4. satya Moderator

    Do you mean to say you are using Workgroup edition or SQL is installed in workgroup>

    Satya SKJ
    Microsoft SQL Server MVP
    Writer, Contributing Editor & Moderator
    http://www.SQL-Server-Performance.Com
    This posting is provided AS IS with no rights for the sake of knowledge sharing. The greatest discovery of my generation is that a human being can alter his life by altering his attitudes of mind.
  5. LiangZhu1 New Member

    I am using Sql Server 2005 Workgroup edition for the client, and enterprice edition for the Central Server.
  6. MohammedU New Member

    What athentication are you using?
    Do you see any blocking on the server?
    Run the profiler and see what is going on behind the scene...and add error event to the profiler...


    MohammedU.
    Moderator
    SQL-Server-Performance.com

    All postings are provided “AS IS” with no warranties for accuracy.
  7. LiangZhu1 New Member


    I have used the window administrator login for the snapshot and logread agent. Is there a way to run the profiler in Workgroup edition? I know that functionality exits in the Enterprice edition but I do not know how to do that in the workgroup
  8. LiangZhu1 New Member


    Good call! I have ran the profiler, and I have seen this message from the trace file.

    "the process could not execute 'sp_repldone/sp_replcounter' on server

    what can I do now? I have tried delete and recreate the publisher, stop and start the sql server agent, increase the QueryTimeout to 3600 and I even kill the sql server agent jobs associated with the publisher. What can I do now?
  9. MohammedU New Member

  10. satya Moderator

    Try restarting SQLAgent and logreader agent that might fix the problem.

    Satya SKJ
    Microsoft SQL Server MVP
    Writer, Contributing Editor & Moderator
    http://www.SQL-Server-Performance.Com
    This posting is provided AS IS with no rights for the sake of knowledge sharing. The greatest discovery of my generation is that a human being can alter his life by altering his attitudes of mind.
  11. LiangZhu1 New Member

    Thank you vary Much for the all your Help!
  12. MohammedU New Member

    Did your issue resolved? If yes, can you please share the solution.

    MohammedU.
    Moderator
    SQL-Server-Performance.com

    All postings are provided “AS IS” with no warranties for accuracy.
  13. LiangZhu1 New Member

    MohammedU,

    I have not resolved that problem yet. I have tried to disable and enable the distribution, stop and start the sql agent and log agent and then I have recreated the publication again with the UI, the error was still there. I am thinking to try to create the publication again with script.

    I will let you know how it will turn out.

    Thank you,
    Liang
  14. MohammedU New Member

  15. LiangZhu1 New Member

    Thank you for the site! I did check out the site.
    I did not have the luck to get rid of that error just yet, my script could got a bug. Right now, I really need to get that PK violation resolved.

    Thank you,
    Liang

Share This Page