Post reply

Snapshot Agent Failure

  • December 8, 2009 at 10:13 pm

    #1089649

    I checked the permissions and all. It is full control only for the agent login.

    Thanks

  • December 9, 2009 at 4:26 am

    #1089740

    This is the error code I obtained when I run from command prompt today

    2009-12-09 11:06:51.52

    2009-12-09 11:06:51.52 Microsoft (R) SQL Server Snapshot Agent

    2009-12-09 11:06:51.52 [Assembly Version = 9.0.242.0, File Version = 9.00.4035.0

    0]

    2009-12-09 11:06:51.52 Copyright (C) 1988-2005 Microsoft Corporation. All rights

    reserved.

    2009-12-09 11:06:51.54 The timestamps prepended to the output lines are expresse

    d in terms of UTC time.

    2009-12-09 11:06:51.54 User-specified agent parameter values:

    2009-12-09 11:06:51.54 --------------------------------------

    2009-12-09 11:06:51.54 -Publisher <publishername>

    2009-12-09 11:06:51.54 -PublisherDB <publisherdbname>

    2009-12-09 11:06:51.54 -Publication <snapshot>

    2009-12-09 11:06:51.54 -Distributor <distributorname>

    2009-12-09 11:06:51.54 -DistributorSecurityMode 1

    2009-12-09 11:06:51.54 --------------------------------------

    2009-12-09 11:06:51.54 Connecting to Distributor '<distributorname>'

    2009-12-09 11:06:51.87 The replication agent had encountered an exception.

    2009-12-09 11:06:51.87 Source: Replication

    2009-12-09 11:06:51.87 Exception Type: Microsoft.SqlServer.Replication.ReplicationAgentException

    2009-12-09 11:06:51.87 Exception Message: The Distributor '<distributorname>' does not recognize '<publishername>:<publisherdbname><snapshot>' as a valid publication.

    2009-12-09 11:06:51.87 Message Code: 54003

    2009-12-09 11:06:51.87

    Thanks

  • December 9, 2009 at 6:48 am

    #1089794

    Does that publication exist? The error reports that the distributor is unable to find a publication of that name.

    Bru Medishetty

    Blog -- LearnSQLWithBru

    Join on Facebook Page Facebook.comLearnSQLWithBru

    Twitter -- BruMedishetty

  • December 9, 2009 at 9:53 pm

    #1090341

    I have created the publication and then I checked the snapshot agent status, where I got the error "The system cannot find the path specified". I tried to create another publication which also giving the same error.

    Thanks

  • December 10, 2009 at 7:10 am

    #1090522

    When i have run from command prompt as DISTRIB.exe -publisher<> PublisherDB [] -subscriber [] it is throwing the error "The system cannot find the path specified"

    Thanks

  • December 10, 2009 at 7:14 am

    #1090527

    Is this on a production system? Just don't want to cripple your prod boxes.

    Can you try reconfigure distribution this time choosing a different location for the ReplData.

    Of course, if you have existing publications that are working and running, this can't be done.

    I am trying to figure out if there are any issues with that location in particular.

    Bru Medishetty

    Blog -- LearnSQLWithBru

    Join on Facebook Page Facebook.comLearnSQLWithBru

    Twitter -- BruMedishetty

  • December 10, 2009 at 11:42 am

    #1090760

    I also had the same issue "Path not found" for my "Snapshot agent" had to call support found the key below had changed. Never found out why. Changed the location to path for snapshot agent - No errors. Hope it works for you!

    HKLM\software\Microsoft\Microsoft SQL Server\90\VerSpecificRootDir

  • December 10, 2009 at 1:15 pm

    #1090843

    What kind of replication is being used? Are the distributor and publisher on the same server? Are there any cross domain issues here?

  • December 11, 2009 at 12:30 am

    #1091013

    I have changed the path in the registry. The agent is working now.

    \software\Microsoft\Microsoft SQL Server\90\VerSpecificRootDir to correct path.

    Thanks for all replies....

    Thanks

  • December 11, 2009 at 6:31 am

    #1091121

    You are welcome and thanks for posting the resolution step for the issue, appreciate it.

    Bru Medishetty

    Blog -- LearnSQLWithBru

    Join on Facebook Page Facebook.comLearnSQLWithBru

    Twitter -- BruMedishetty

  • July 9, 2011 at 5:54 am

    #1350726

    We too had an issue with this. We installed SQL Server 2008 R2 w/ sp1 onto the D: drive in a 2 node cluster and encountered error when generating snapshot for a transactional replication publication: The directory name is invalid.

    Using Procmon, we traced this back to what you've listed here...

    HKLM\software\Microsoft\Microsoft SQL Server\100 VerSpecificRootDir

    --- value was D:\Program Files\Microsoft SQL Server\100\ (our specified installation dir)

    Using regedit, we modified this VerSpecificRootDir value to:

    C:\Program Files\Microsoft SQL Server\100\ --- and the snapshot worked immediately.

    Our only concern is will other processes now be corrupted/broken- due to the change in the Registry setting here? We're testing this now. (SSIS, SSRS, SQL, Jobs, etc) We'll post our results.

    BT

  • December 8, 2011 at 11:02 pm

    #1419061

    where did you configured Distributor,is at 2005 or 2000 server.

Viewing 12 posts - 16 through 26 (of 26 total)

You must be logged in to reply to this topic. Login to reply