Jim, I've run into this problem many times. My way of fixing it is having
the job owner being sa and then right clicking on it and starting it. BTW -
"Jim" <please.reply@group> wrote in message
news:%23bYx88$rGHA.2052@TK2MSFTNGP05.phx.gbl...
> One interesting note...
>
> This does create a snapshot, when run at the command line, logged onto the
> Distributor/Publisher with my AD account (Windows administrator and SQL
> server administrator) :
>
> snapshot -Publisher [<publisher_server_name>] -PublisherDB
> [<publisher_db>] -Distributor [<distributor_server_name>] -Publication
> [<publication_name>] -DistributorSecurityMode 1 -Output
> E:\MSSQL_ReplData\snapshot_agent_log.txt -Outputverboselevel 2
>
> The log is created too!
>
> But making my AD account the owner of the Snapshot Agent job, results in
> the previously described *non-running* of the job.
>
> Jim
>
>
> "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message
> news:euVPKT5rGHA.4512@TK2MSFTNGP02.phx.gbl...
>> Ok, we are getting somewhere (I think), can you replace the password on
>> the snapshot agent properties with the password for the publisher?
>>
>> --
>> Hilary Cotter
>> Director of Text Mining and Database Strategy
>> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
>>
>> This posting is my own and doesn't necessarily represent RelevantNoise's
>> positions, strategies or opinions.
>>
>> 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 >>
>>
>>
>> "Jim" <please.reply@group> wrote in message
>> news:ec9w8P1rGHA.4844@TK2MSFTNGP05.phx.gbl...
>>> Thank you, Hilary.
>>>
>>> I have just tried as you suggested. In the Snapshot agent properties,
>>> general tab, set the Owner to "sa". I clicked "Apply" and "OK".
>>> Right-clicking on the agent and selecting "Start Agent" resulted in a
>>> "Failed" status and "...Check error details for more information..."
>>> But "Error Details" is grayed out. There is nothing helpful in the SQL
>>> Server log or Event Logs. I do see "Login failed for user 'sa'", but
>>> that is extremely common.
>>>
>>> There are red circles with white Xs in EM on Replication Monitor,
>>> Publishers, ...; same on Agents and Snapshot Agents.
>>>
>>> I'm glad to see some things happening. Don't currently know what to try
>>> next, though. :-)
>>>
>>> Jim
>>>
>>>
>>> "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message
>>> news:%232lBCA0rGHA.2464@TK2MSFTNGP03.phx.gbl...
>>>> Make the job owner sa and start it up again.
>>>>
>>>> --
>>>> Hilary Cotter
>>>> Director of Text Mining and Database Strategy
>>>> RelevantNOISE.Com - Dedicated to mining blogs for business
>>>> intelligence.
>>>>
>>>> This posting is my own and doesn't necessarily represent
>>>> RelevantNoise's positions, strategies or opinions.
>>>>
>>>> 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 >>>>
>>>>
>>>>
>>>> "Jim" <please.reply@group> wrote in message
>>>> news:uzV0dVzrGHA.3960@TK2MSFTNGP02.phx.gbl...
>>>>> Hi again, Hilary! Thanks for the reply!
>>>>>
>>>>> I have enabled logging, as you suggested at the level of "2". So all
>>>>> activity should go to the log. Then I have again attempted to start
>>>>> the Snapshot agent. No logs are created.
>>>>>
>>>>> The Microsoft AD account under which the Snapshot agent (and other
>>>>> replication-related agents) is (are) running had only "User" status.
>>>>> I noticed in the Security Event log that it was being denied access to
>>>>> directories and files in C:\WINNT\system32. So, I made it a "Power
>>>>> User", and that helped. Then I made it an "Administrator" and that
>>>>> helped more. But still no Snapshot agent log! :-(
>>>>>
>>>>> I have since moved the AD account around some more between User, Power
>>>>> User, and Administrator. Now no entries are appearing in the Security
>>>>> Event log as they were before. I have changed nothing else. This is
>>>>> weird! (and rather frustrating :-)
>>>>>
>>>>> Any more suggestions, anyone?
>>>>>
>>>>> Best regards,
>>>>> Jim
>>>>>
>>>>>
>>>>> "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message
>>>>> news:%23TNjnJRrGHA.2440@TK2MSFTNGP03.phx.gbl...
>>>>>> Can you enable logging to see if it reveals anything.
>>>>>>
>>>>>>
http://support.microsoft.com/kb/312292/en-us >>>>>>
>>>>>> --
>>>>>> Hilary Cotter
>>>>>> Director of Text Mining and Database Strategy
>>>>>> RelevantNOISE.Com - Dedicated to mining blogs for business
>>>>>> intelligence.
>>>>>>
>>>>>> This posting is my own and doesn't necessarily represent
>>>>>> RelevantNoise's positions, strategies or opinions.
>>>>>>
>>>>>> 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 >>>>>>
>>>>>>
>>>>>>
>>>>>> "Jim" <please.reply@group> wrote in message
>>>>>> news:OFlSl1QrGHA.5008@TK2MSFTNGP05.phx.gbl...
>>>>>>> Distributor/Publisher and Subscriber:
>>>>>>> Windows Server 2003 SP1
>>>>>>> SQL Server 2000 SP4
>>>>>>>
>>>>>>> Distributor/Publisher and Subscriber created through SQL Server
>>>>>>> wizardry. Asked for initial Snapshot to be created immediately. It
>>>>>>> wasn't.
>>>>>>>
>>>>>>> Snapshot Agent shows as "Never started". Right-clicking on the
>>>>>>> Snapshot Agent and selecting "Start agent" results in nothing--no
>>>>>>> snapshot, no error message, no Event Log entries. Nothing.
>>>>>>>
>>>>>>> I could really use some help here. I found one thread from March
>>>>>>> 2005 where a guy resorted to scripting what this replication is
>>>>>>> supposed to do. I'd prefer to set it up to run as it is supposed to
>>>>>>> run. Is this possible?
>>>>>>>
>>>>>>> Thread from 2005:
>>>>>>>
http://groups.google.com/group/microsoft.public.sqlserver.replication/browse_thread/thread/553cb851010ce48/b0e47aceeea46ee4?lnk=st&q=&rnum=2#b0e47aceeea46ee4
>>>>>>>
>>>>>>> Thanks!
>>>>>>>
>>>>>>> Jim
>>>>>>>
>>>>>>> P.S. The replication manager is set to refresh every 10 minutes,
>>>>>>> and each time the below error output appears in the Application Log.