Re: Snapshot Creation

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@xxxxxxxxx> wrote in message
news:%232lBCA0rGHA.2464@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxx> wrote in message
news:%23TNjnJRrGHA.2440@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
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.
Otherwise, I seem to have nothing at all going.
SQL Server Scheduled Job 'Replication agents checkup'
(0x44AB1206E3D37C428BD85CE9BBF50E59) - Status: Failed - Invoked on:
2006-07-21 16:20:00 - Message: The job failed. Unable to determine if
the owner (UAB\Genome-SQLServer) of job Replication agents checkup has
server access (reason: Could not obtain information about Windows NT
group/user 'UAB\Genome-SQLServer'. [SQLSTATE 42000] (Error 8198)).














.

Relevant Pages

  • Re: Snapshot only with scheme
    ... Run the snapshot agent ... As for the large amount of data that has accumulated on the publisher - this ... Paul Ibison SQL Server MVP, ... (recommended sql server 2000 replication book: ...
    (microsoft.public.sqlserver.replication)
  • Re: Snapshot Creation
    ... Director of Text Mining and Database Strategy ... Looking for a SQL Server replication book? ... The Microsoft AD account under which the Snapshot agent (and other ...
    (microsoft.public.sqlserver.replication)
  • Re: Snapshot Creation
    ... Director of Text Mining and Database Strategy ... Looking for a SQL Server replication book? ... the snapshot agent properties with the password for the publisher? ...
    (microsoft.public.sqlserver.replication)
  • Re: Snapshot Creation
    ... I may not understand your suggestion. ... the Snapshot agent job from 'sa' to the account under which the distributor ... Looking for a SQL Server replication book? ... There are red circles with white Xs in EM on Replication Monitor, ...
    (microsoft.public.sqlserver.replication)
  • Re: Snapshot Creation
    ... The Microsoft AD account under which the Snapshot agent (and other ... I have since moved the AD account around some more between User, Power User, ... Looking for a SQL Server replication book? ... SQL Server Scheduled Job 'Replication agents checkup' ...
    (microsoft.public.sqlserver.replication)