A snapshot was not generated because no subscriptions needed initi

Full error I am getting: a snapshot was not generated because no
subscriptions needed initialization
Scenario: I run the New Publication Wizard to create and add a
Transactional Publication with Updateable Subscriptions to my SQL Server. I
choose the script option at the end of the Wizard and save the script that
the Wizard generates. The publication is created fine and an initial snapshot
is created for the publication. Obviously I have no Subscribers to the
Publication yet...I just created it, but the Snapshot is created without
issue. That's cool, that's what is wanted.
The Problem: Now, if the Publication is Deleted from the SQL
Server(successfully...no errors & no funkiness), and I then run the script
that the Wizard created for me, the initial Snapshot does not get created as
it did thru the Wizard, but everything else involving the script is fine. I
get the aforementioned error at the top of this message. This sucks. Isn't
this script supposed to do exactly what I just did in the Wizard? I want the
Snapshot created in the same fashion as it was when the Wizard did it. What
is going on that is different between the Wizard and the script that the
Wizard created (and something must be different)? I did not alter the
script in any way from what the Wizard gave me. Is there some trick or
workaround to get this behavior? Am I missing the boat on something here?
Thanks.
Chris Jones
Application Development Consultant
Chris,
Check to see if the sp_addpublication in the generated script has the
parameter @.immediate_sync set to 'true'.
When creating the publication if the immediate sync property is set to
'true', a snapshot for the publication will be generated everytime the
snapshot agent runs even if the publication doesn't have any
subscriptions....else if @.immediate_sync is set to 'false', the snapshot
will not be generated because the publication does not have any subscriptions
yet.
HTH
Emaniel
"Chris" wrote:

> Full error I am getting: a snapshot was not generated because no
> subscriptions needed initialization
> Scenario: I run the New Publication Wizard to create and add a
> Transactional Publication with Updateable Subscriptions to my SQL Server. I
> choose the script option at the end of the Wizard and save the script that
> the Wizard generates. The publication is created fine and an initial snapshot
> is created for the publication. Obviously I have no Subscribers to the
> Publication yet...I just created it, but the Snapshot is created without
> issue. That's cool, that's what is wanted.
> The Problem: Now, if the Publication is Deleted from the SQL
> Server(successfully...no errors & no funkiness), and I then run the script
> that the Wizard created for me, the initial Snapshot does not get created as
> it did thru the Wizard, but everything else involving the script is fine. I
> get the aforementioned error at the top of this message. This sucks. Isn't
> this script supposed to do exactly what I just did in the Wizard? I want the
> Snapshot created in the same fashion as it was when the Wizard did it. What
> is going on that is different between the Wizard and the script that the
> Wizard created (and something must be different)? I did not alter the
> script in any way from what the Wizard gave me. Is there some trick or
> workaround to get this behavior? Am I missing the boat on something here?
> --
> Thanks.
> Chris Jones
> Application Development Consultant

'A required privilege is not held by the client' when re-initalization

Hi all,
the sys admin has changed the service a/c to another admin. id. But now, i can't start the replication jobs even re-created the publication and subscription with the new admin. id. Any advise? Thanks in advance!

'Executed as user: test.com\admin. A required privilege is not held by the client. The step failed.'

Hi Stephaine,

How do your admin change the service account? He/she might use Windows Service Control Manager to change account. To solve the issue, please refer to this KB article (http://support.microsoft.com/kb/911305/en-us).

Thanks,

Peng

|||an issue i found was that sql server agent and ssis had been changed to not use the local system account. this caused me to continually get the dreaded --> "A required privilege is not held by the client" error. i fought with it all afternoon and eventually updated the services to use the local system account and it worked. perhaps this will save some other as much time as i wasted.

'A required privilege is not held by the client' when re-initalization

Hi all,
the sys admin has changed the service a/c to another admin. id. But now, i can't start the replication jobs even re-created the publication and subscription with the new admin. id. Any advise? Thanks in advance!

'Executed as user: test.com\admin. A required privilege is not held by the client. The step failed.'

Hi Stephaine,

How do your admin change the service account? He/she might use Windows Service Control Manager to change account. To solve the issue, please refer to this KB article (http://support.microsoft.com/kb/911305/en-us).

Thanks,

Peng

|||an issue i found was that sql server agent and ssis had been changed to not use the local system account. this caused me to continually get the dreaded --> "A required privilege is not held by the client" error. i fought with it all afternoon and eventually updated the services to use the local system account and it worked. perhaps this will save some other as much time as i wasted.

A problem with SQL Server Authentication?

Hi everybody...
I need to implement a publication but I got the next message when I start
the assistant: "SQL Server Agent on 'USER07' currently uses the system
account, which causes replication between servers to fail. In the following
dialog box, specify another account for the Service startup account". I
don't know which account I have to specify because the error persist. Do I
have to create a new account?
Thanks very much for any help!
Juan
juan,
if you're using replication across different boxes, you'll need a domain
user as the startup account for the SQL Server agent.
There's a few sections on this under Replication, Security in BOL.
HTH,
Paul Ibison
|||If I might just quibble with Paul's excellent answer.
For a push subscription the SQL Agent Account on the distribution must be
able to access the snapshot share on the publisher. This share is by default
\\PublisherServerName\C$\Program Files\Microsoft SQL
Server\MSSQL\ReplData\UNC
If your Publisher and Distributor are on the same server this is not a
problem.
Its only a problem when you are doing pull subscriptions, because then its
your SQL Server agent account on the Subscriber which must be able to map a
drive to
\\PublisherServerName\C$\Program Files\Microsoft SQL
Server\MSSQL\ReplData\UNC
So for this to work
1) your Subscriber must be part of the admin group on the Publisher, and you
select the impersonate the SQL Server Agent account on the Publisher
or
2) you change the share name to a share which the SQL Server agent account
on the subscriber can access and give permission to this account to access
the share and the underlying files and folders.
If you are in an untrusted domain you can use pass through authentication
http://support.microsoft.com/default...&Product=sql2k
and if you are an internet user you will have to use either the everyone
group/account (not recommended) or use FTP (recommended).
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:Om$SH07IEHA.228@.TK2MSFTNGP10.phx.gbl...
> juan,
> if you're using replication across different boxes, you'll need a domain
> user as the startup account for the SQL Server agent.
> There's a few sections on this under Replication, Security in BOL.
> HTH,
> Paul Ibison
>