I am having some trouble setting up replication on my MSDE 2000 server installation.
When using the set up replication set up wizard, I get through all the screens
correctly, the Distrubution database is created, and then I get error 14113 - Could
not execute c:\...\osql" -E -I60 -t60 -d"distribution" -b -i "..\instdist.sql" -o
"..\instdist.out"
I am using the enterprise manager to enable replication. I have successfully enabled distributor / replication on other installations prior to this one.
I have attached the instdist.out file as a text file.
Any feedback would be appreciated!I'm having the exact same problem. Figure anything out yet?
Originally posted by huntertx
I am having some trouble setting up replication on my MSDE 2000 server installation.
When using the set up replication set up wizard, I get through all the screens
correctly, the Distrubution database is created, and then I get error 14113 - Could
not execute c:\...\osql" -E -I60 -t60 -d"distribution" -b -i "..\instdist.sql" -o
"..\instdist.out"
I am using the enterprise manager to enable replication. I have successfully enabled distributor / replication on other installations prior to this one.
I have attached the instdist.out file as a text file.
Any feedback would be appreciated!|||Yep... Just re-apply SP3 and it should fix the problem. It worked for me!
Showing posts with label wizard. Show all posts
Showing posts with label wizard. Show all posts
Wednesday, March 28, 2012
Replication Error
I am using Replication wizard and created Publisher with
name "Services3 and Subscriber is HOffice with
Subscription database is GinFactory1 and using Windows
authentication Mode. Subscription is Push Subscription.
It create sanapshot and also transfer data in GinFactory1
as soon as Wizard has been completed. But when i try to
synchronize Subscription using option start sunchronizing
it returns error "Publication is invalid" .What can be
reason of it?Please give me detail description if u have.
Thanks in advance
Normally the publication is invalid error message means that your snapshot
files are too old. Can you regenerate your snapshot (right click on your
snapshot agent and select start agent), and then restart your distribution
agent?
You may get a message telling you the no snapshot was generated as
subscriptions needed reinitialization.
If you get this message right click on your publication, publication
properties, go to the subscribers tab, located your subscriber and click
reinitialize. Then restart your snapshot agent.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Saima" <ucoxk@.yahoo.com> wrote in message
news:3fa701c47308$49893d40$a601280a@.phx.gbl...
> I am using Replication wizard and created Publisher with
> name "Services3 and Subscriber is HOffice with
> Subscription database is GinFactory1 and using Windows
> authentication Mode. Subscription is Push Subscription.
> It create sanapshot and also transfer data in GinFactory1
> as soon as Wizard has been completed. But when i try to
> synchronize Subscription using option start sunchronizing
> it returns error "Publication is invalid" .What can be
> reason of it?Please give me detail description if u have.
> Thanks in advance
|||It is not too old . i just do it after 5 minutes
>--Original Message--
>Normally the publication is invalid error message means
that your snapshot
>files are too old. Can you regenerate your snapshot
(right click on your
>snapshot agent and select start agent), and then restart
your distribution
>agent?
>You may get a message telling you the no snapshot was
generated as
>subscriptions needed reinitialization.
>If you get this message right click on your publication,
publication
>properties, go to the subscribers tab, located your
subscriber and click[vbcol=seagreen]
>reinitialize. Then restart your snapshot agent.
>--
>Hilary Cotter
>Looking for a book on SQL Server replication?
>http://www.nwsu.com/0974973602.html
>
>"Saima" <ucoxk@.yahoo.com> wrote in message
>news:3fa701c47308$49893d40$a601280a@.phx.gbl...
with[vbcol=seagreen]
GinFactory1[vbcol=seagreen]
sunchronizing[vbcol=seagreen]
have.
>
>.
>
|||can you script out your publication and post it here?
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Saima" <ucoxk@.yahoo.com> wrote in message
news:44de01c4733d$c1287570$a601280a@.phx.gbl...[vbcol=seagreen]
> It is not too old . i just do it after 5 minutes
> that your snapshot
> (right click on your
> your distribution
> generated as
> publication
> subscriber and click
> with
> GinFactory1
> sunchronizing
> have.
name "Services3 and Subscriber is HOffice with
Subscription database is GinFactory1 and using Windows
authentication Mode. Subscription is Push Subscription.
It create sanapshot and also transfer data in GinFactory1
as soon as Wizard has been completed. But when i try to
synchronize Subscription using option start sunchronizing
it returns error "Publication is invalid" .What can be
reason of it?Please give me detail description if u have.
Thanks in advance
Normally the publication is invalid error message means that your snapshot
files are too old. Can you regenerate your snapshot (right click on your
snapshot agent and select start agent), and then restart your distribution
agent?
You may get a message telling you the no snapshot was generated as
subscriptions needed reinitialization.
If you get this message right click on your publication, publication
properties, go to the subscribers tab, located your subscriber and click
reinitialize. Then restart your snapshot agent.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Saima" <ucoxk@.yahoo.com> wrote in message
news:3fa701c47308$49893d40$a601280a@.phx.gbl...
> I am using Replication wizard and created Publisher with
> name "Services3 and Subscriber is HOffice with
> Subscription database is GinFactory1 and using Windows
> authentication Mode. Subscription is Push Subscription.
> It create sanapshot and also transfer data in GinFactory1
> as soon as Wizard has been completed. But when i try to
> synchronize Subscription using option start sunchronizing
> it returns error "Publication is invalid" .What can be
> reason of it?Please give me detail description if u have.
> Thanks in advance
|||It is not too old . i just do it after 5 minutes
>--Original Message--
>Normally the publication is invalid error message means
that your snapshot
>files are too old. Can you regenerate your snapshot
(right click on your
>snapshot agent and select start agent), and then restart
your distribution
>agent?
>You may get a message telling you the no snapshot was
generated as
>subscriptions needed reinitialization.
>If you get this message right click on your publication,
publication
>properties, go to the subscribers tab, located your
subscriber and click[vbcol=seagreen]
>reinitialize. Then restart your snapshot agent.
>--
>Hilary Cotter
>Looking for a book on SQL Server replication?
>http://www.nwsu.com/0974973602.html
>
>"Saima" <ucoxk@.yahoo.com> wrote in message
>news:3fa701c47308$49893d40$a601280a@.phx.gbl...
with[vbcol=seagreen]
GinFactory1[vbcol=seagreen]
sunchronizing[vbcol=seagreen]
have.
>
>.
>
|||can you script out your publication and post it here?
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Saima" <ucoxk@.yahoo.com> wrote in message
news:44de01c4733d$c1287570$a601280a@.phx.gbl...[vbcol=seagreen]
> It is not too old . i just do it after 5 minutes
> that your snapshot
> (right click on your
> your distribution
> generated as
> publication
> subscriber and click
> with
> GinFactory1
> sunchronizing
> have.
Monday, March 26, 2012
Replication distribution cleanup error
I used the SQL Server 2005 publication wizard to set up transactional replication. It scheduled a job called "Distribution clean up: distribution" that calls sp_MSdistribution_cleanup. The job fails every time it runs. The xp_cmdshell is enabled and SQL Server Agent runs under an account that has sufficient privileges to execute it. The account also has full rights to the repldata subdirectories. I have applied service pack 1.
I looked through the sp_MSdistribution_cleanup code and it looks like there are two stored procedures and one function missing from the SQL server databases. They are
master.dbo.sp_MSunc_to_drive sys.fn_escapecmdshellsymbolsremovequotes sys.sp_MSdrop_distribution_agentidWhere can I get a copy of these stored procedures? The expired distribution data is slowly consuming my remaining hard drive space. Thanks.
Joe
Hi, Joe,
There seems to be a bug in our code where we should not call master.dbo.sp_MSunc_to_drive, instead we should call sys.sp_MSunc_to_drive. In SQL Server 2005, we have move most of the system sps to mssqlsystemresource database, and some of them are hidden from end users as they're not supposed to be used directly by customers. sys.sp_MSunc_to_drive, sys.fn_escapecmdshellsymbolsremovequotes and sys.sp_MSdrop_distribution_agentid are hidden sps/function thus you don't see them but they do exist.
I will do more research and see if there is a workaround.
By the way, can you post the exact error message you're seeing from distribution cleanup job (by using replication monitor to view the job history)? Are you using dynamic snapshot merge replication? Any specific information about your replication setup would be helpful.
Thanks,
Zhiqiang Feng
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Thanks for answering me so quickly. The problem has been resolved. The account under which xp_cmdshell was executing did not have the proper access to the repldata share.
Joe
|||
Glad to hear that the problem is solved. The issue mentioned in my post is a minor issue and should not cause any functional problems. It would be helpful for other visitors of this thread if you can post the error message you're seeing before it's fixed (it should still be available in replication agent history).
Thanks,
Zhiqiang Feng
This posting is provided "AS IS" with no warranties, and confers no rights.
|||I'm really sorry, but the clean up agent already deleted the history. I think part of the message was "Could not clean up the distribution transaction tables."
Joe
sqlWednesday, March 21, 2012
Replication between 2 SQL from 2 Windows SBS 2003?
Replication between 2 SQL from 2 Windows SBS 2003?
I have 2 SBS servers with SQL 2000. I would like to do a Merge
replication, I did it using wizard and everywhere I choose not trusted
connection but SQL login and password:
Configure '192.168.10.3' as a Publisher. Use '192.168.10.3' as the
Distributor.
Use '\\192.168.10.3\f$\Microsoft SQL
Server\MSSQL\ReplData' as the root snapshot folder for
Publishers using this Distributor.
Store the distribution database 'distribution' in 'f:\Microsoft
SQL Server\MSSQL\Data'.
Store the distribution database log file in 'f:\Microsoft SQL
Server\MSSQL\Data'.
Enable the following databases on '192.168.10.3' for merge
replication:
SampleDataBase
Enable the following servers as Subscribers to
publications on '192.168.10.3':
10.9.0.1
But I receive:
SQL Server Enterprise Manager could not configure '192.168.10.3' as the
Distributor for '192.168.10.3'.
Error 18483: Could not connect to server â'NSSâ' because
â'distributor_adminâ' is not defined as a remote login at the server.
But:
SELECT @.@.SERVERNAME, SERVERPROPERTY('ServerName') returns
NSS NSS
So it seems properly.
Ping nss working properly..
I need help!!! Any concepts? Maybe something connected with
distributor_admin and trusted connection â' I heard somewhere that it is
possible to disable trusted connection for distributor_admin but I donâ't
know how to do it?Hello,
I understand that when you try to create a merge replication, you receive
the error message "Error 18483: Could not connect to server "NSS" because
"distributor_admin" is not defined as a remote login at the server."
However, the servername is correct and it is the same as
SERVERPROPERTY('ServerName'). If I'm off-base, please let me know.
This issue could occur when the Machine name at windows level (Hostname) is
different from SQL Server Name (Select @.@.servername).
And this happens when the machine on which SQL Server is installed is
renamed after SQL Server installation. If it is so you will have to do the
following using Query Analyzer:
Sp_dropserver ?<server>?
(Replace <server> with the name returned by Select @.@.servername query)
Sp_addserver ?<server>?, ?local?
(Replace <server> with the machine name (Hostname) if it is default
instance otherwise <server>\instancename for named instance)
Also, did you try to use servername "NSS" when configure merge replication
and not using IP adress directly? I suspect this issue may also related to
network name resolution.
More related information:
818334 Replication setup is not successful when SQL Server is deployed by
using a disk image
http://support.microsoft.com/default.aspx?scid=kb;EN-US;818334
321822 HOW TO: Replicate Between Computers Running SQL Server in
Non-Trusted Domains or Across the Internet
http://support.microsoft.com/default.aspx?scid=kb;EN-US;321822
If you have any update, please let's know. Thank you.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Community Support
==================================================Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
<http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
<http://msdn.microsoft.com/subscriptions/support/default.aspx>.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Peter Yang [MSFT] napisaÅ?(a):
> Hello,
> I understand that when you try to create a merge replication, you receive
> the error message "Error 18483: Could not connect to server "NSS" because
> "distributor_admin" is not defined as a remote login at the server."
> However, the servername is correct and it is the same as
> SERVERPROPERTY('ServerName'). If I'm off-base, please let me know.
yes its true!
> This issue could occur when the Machine name at windows level (Hostname) is
> different from SQL Server Name (Select @.@.servername).
> And this happens when the machine on which SQL Server is installed is
> renamed after SQL Server installation. If it is so you will have to do the
> following using Query Analyzer:
Select @.@.servername
returns
NSS
and full computer name is:
nss.domain.local
it is a domain server (SBS)
so computer name is nss and never been changed!
> Sp_dropserver �<server>�
> (Replace <server> with the name returned by Select @.@.servername query)
>
> Sp_addserver �<server>�, �local�
> (Replace <server> with the machine name (Hostname) if it is default
> instance otherwise <server>\instancename for named instance)
> Also, did you try to use servername "NSS" when configure merge replication
> and not using IP adress directly? I suspect this issue may also related to
> network name resolution.
> More related information:
>
> 818334 Replication setup is not successful when SQL Server is deployed by
> using a disk image
> http://support.microsoft.com/default.aspx?scid=kb;EN-US;818334
>
> 321822 HOW TO: Replicate Between Computers Running SQL Server in
> Non-Trusted Domains or Across the Internet
> http://support.microsoft.com/default.aspx?scid=kb;EN-US;321822
I will try it this...
I have 2 SBS servers with SQL 2000. I would like to do a Merge
replication, I did it using wizard and everywhere I choose not trusted
connection but SQL login and password:
Configure '192.168.10.3' as a Publisher. Use '192.168.10.3' as the
Distributor.
Use '\\192.168.10.3\f$\Microsoft SQL
Server\MSSQL\ReplData' as the root snapshot folder for
Publishers using this Distributor.
Store the distribution database 'distribution' in 'f:\Microsoft
SQL Server\MSSQL\Data'.
Store the distribution database log file in 'f:\Microsoft SQL
Server\MSSQL\Data'.
Enable the following databases on '192.168.10.3' for merge
replication:
SampleDataBase
Enable the following servers as Subscribers to
publications on '192.168.10.3':
10.9.0.1
But I receive:
SQL Server Enterprise Manager could not configure '192.168.10.3' as the
Distributor for '192.168.10.3'.
Error 18483: Could not connect to server â'NSSâ' because
â'distributor_adminâ' is not defined as a remote login at the server.
But:
SELECT @.@.SERVERNAME, SERVERPROPERTY('ServerName') returns
NSS NSS
So it seems properly.
Ping nss working properly..
I need help!!! Any concepts? Maybe something connected with
distributor_admin and trusted connection â' I heard somewhere that it is
possible to disable trusted connection for distributor_admin but I donâ't
know how to do it?Hello,
I understand that when you try to create a merge replication, you receive
the error message "Error 18483: Could not connect to server "NSS" because
"distributor_admin" is not defined as a remote login at the server."
However, the servername is correct and it is the same as
SERVERPROPERTY('ServerName'). If I'm off-base, please let me know.
This issue could occur when the Machine name at windows level (Hostname) is
different from SQL Server Name (Select @.@.servername).
And this happens when the machine on which SQL Server is installed is
renamed after SQL Server installation. If it is so you will have to do the
following using Query Analyzer:
Sp_dropserver ?<server>?
(Replace <server> with the name returned by Select @.@.servername query)
Sp_addserver ?<server>?, ?local?
(Replace <server> with the machine name (Hostname) if it is default
instance otherwise <server>\instancename for named instance)
Also, did you try to use servername "NSS" when configure merge replication
and not using IP adress directly? I suspect this issue may also related to
network name resolution.
More related information:
818334 Replication setup is not successful when SQL Server is deployed by
using a disk image
http://support.microsoft.com/default.aspx?scid=kb;EN-US;818334
321822 HOW TO: Replicate Between Computers Running SQL Server in
Non-Trusted Domains or Across the Internet
http://support.microsoft.com/default.aspx?scid=kb;EN-US;321822
If you have any update, please let's know. Thank you.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Community Support
==================================================Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
<http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
<http://msdn.microsoft.com/subscriptions/support/default.aspx>.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Peter Yang [MSFT] napisaÅ?(a):
> Hello,
> I understand that when you try to create a merge replication, you receive
> the error message "Error 18483: Could not connect to server "NSS" because
> "distributor_admin" is not defined as a remote login at the server."
> However, the servername is correct and it is the same as
> SERVERPROPERTY('ServerName'). If I'm off-base, please let me know.
yes its true!
> This issue could occur when the Machine name at windows level (Hostname) is
> different from SQL Server Name (Select @.@.servername).
> And this happens when the machine on which SQL Server is installed is
> renamed after SQL Server installation. If it is so you will have to do the
> following using Query Analyzer:
Select @.@.servername
returns
NSS
and full computer name is:
nss.domain.local
it is a domain server (SBS)
so computer name is nss and never been changed!
> Sp_dropserver �<server>�
> (Replace <server> with the name returned by Select @.@.servername query)
>
> Sp_addserver �<server>�, �local�
> (Replace <server> with the machine name (Hostname) if it is default
> instance otherwise <server>\instancename for named instance)
> Also, did you try to use servername "NSS" when configure merge replication
> and not using IP adress directly? I suspect this issue may also related to
> network name resolution.
> More related information:
>
> 818334 Replication setup is not successful when SQL Server is deployed by
> using a disk image
> http://support.microsoft.com/default.aspx?scid=kb;EN-US;818334
>
> 321822 HOW TO: Replicate Between Computers Running SQL Server in
> Non-Trusted Domains or Across the Internet
> http://support.microsoft.com/default.aspx?scid=kb;EN-US;321822
I will try it this...
Replication between 2 SQL from 2 Windows SBS 2003?
Replication between 2 SQL from 2 Windows SBS 2003?
I have 2 SBS servers with SQL 2000. I would like to do a Merge
replication, I did it using wizard and everywhere I choose not trusted
connection but SQL login and password:
Configure '192.168.10.3' as a Publisher. Use '192.168.10.3' as the
Distributor.
Use '\\192.168.10.3\f$\Microsoft SQL
Server\MSSQL\ReplData' as the root snapshot folder for
Publishers using this Distributor.
Store the distribution database 'distribution' in 'f:\Microsoft
SQL Server\MSSQL\Data'.
Store the distribution database log file in 'f:\Microsoft SQL
Server\MSSQL\Data'.
Enable the following databases on '192.168.10.3' for merge
replication:
SampleDataBase
Enable the following servers as Subscribers to
publications on '192.168.10.3':
10.9.0.1
But I receive:
SQL Server Enterprise Manager could not configure '192.168.10.3' as the
Distributor for '192.168.10.3'.
Error 18483: Could not connect to server ‘NSS’ because
‘distributor_admin’ is not defined as a remote login at the server.
But:
SELECT @.@.SERVERNAME, SERVERPROPERTY('ServerName') returns
NSS NSS
So it seems properly.
Ping nss working properly..
I need help!!! Any concepts? Maybe something connected with
distributor_admin and trusted connection – I heard somewhere that it is
possible to disable trusted connection for distributor_admin but I don’t
know how to do it?Hello,
I understand that when you try to create a merge replication, you receive
the error message "Error 18483: Could not connect to server "NSS" because
"distributor_admin" is not defined as a remote login at the server."
However, the servername is correct and it is the same as
SERVERPROPERTY('ServerName'). If I'm off-base, please let me know.
This issue could occur when the Machine name at windows level (Hostname) is
different from SQL Server Name (Select @.@.servername).
And this happens when the machine on which SQL Server is installed is
renamed after SQL Server installation. If it is so you will have to do the
following using Query Analyzer:
Sp_dropserver <server>
(Replace <server> with the name returned by Select @.@.servername query)
Sp_addserver <server>, local
(Replace <server> with the machine name (Hostname) if it is default
instance otherwise <server>\instancename for named instance)
Also, did you try to use servername "NSS" when configure merge replication
and not using IP adress directly? I suspect this issue may also related to
network name resolution.
More related information:
818334 Replication setup is not successful when SQL Server is deployed by
using a disk image
http://support.microsoft.com/defaul...kb;EN-US;818334
321822 HOW TO: Replicate Between Computers Running SQL Server in
Non-Trusted Domains or Across the Internet
http://support.microsoft.com/defaul...kb;EN-US;321822
If you have any update, please let's know. Thank you.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Community Support
========================================
==========
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscript...ault.aspx#notif
ications
<http://msdn.microsoft.com/subscript...ps/default.aspx>.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
<http://msdn.microsoft.com/subscript...rt/default.aspx>.
========================================
==========
This posting is provided "AS IS" with no warranties, and confers no rights.|||Peter Yang [MSFT] napisa?(a):
> Hello,
> I understand that when you try to create a merge replication, you receive
> the error message "Error 18483: Could not connect to server "NSS" because
> "distributor_admin" is not defined as a remote login at the server."
> However, the servername is correct and it is the same as
> SERVERPROPERTY('ServerName'). If I'm off-base, please let me know.
yes its true!
> This issue could occur when the Machine name at windows level (Hostname) i
s
> different from SQL Server Name (Select @.@.servername).
> And this happens when the machine on which SQL Server is installed is
> renamed after SQL Server installation. If it is so you will have to do the
> following using Query Analyzer:
Select @.@.servername
returns
NSS
and full computer name is:
nss.domain.local
it is a domain server (SBS)
so computer name is nss and never been changed!
> Sp_dropserver ?<server>?
> (Replace <server> with the name returned by Select @.@.servername query)
>
> Sp_addserver ?<server>?, ?local?
> (Replace <server> with the machine name (Hostname) if it is default
> instance otherwise <server>\instancename for named instance)
> Also, did you try to use servername "NSS" when configure merge replication
> and not using IP adress directly? I suspect this issue may also related to
> network name resolution.
> More related information:
>
> 818334 Replication setup is not successful when SQL Server is deployed by
> using a disk image
> http://support.microsoft.com/defaul...kb;EN-US;818334
>
> 321822 HOW TO: Replicate Between Computers Running SQL Server in
> Non-Trusted Domains or Across the Internet
> http://support.microsoft.com/defaul...kb;EN-US;321822
I will try it this...
I have 2 SBS servers with SQL 2000. I would like to do a Merge
replication, I did it using wizard and everywhere I choose not trusted
connection but SQL login and password:
Configure '192.168.10.3' as a Publisher. Use '192.168.10.3' as the
Distributor.
Use '\\192.168.10.3\f$\Microsoft SQL
Server\MSSQL\ReplData' as the root snapshot folder for
Publishers using this Distributor.
Store the distribution database 'distribution' in 'f:\Microsoft
SQL Server\MSSQL\Data'.
Store the distribution database log file in 'f:\Microsoft SQL
Server\MSSQL\Data'.
Enable the following databases on '192.168.10.3' for merge
replication:
SampleDataBase
Enable the following servers as Subscribers to
publications on '192.168.10.3':
10.9.0.1
But I receive:
SQL Server Enterprise Manager could not configure '192.168.10.3' as the
Distributor for '192.168.10.3'.
Error 18483: Could not connect to server ‘NSS’ because
‘distributor_admin’ is not defined as a remote login at the server.
But:
SELECT @.@.SERVERNAME, SERVERPROPERTY('ServerName') returns
NSS NSS
So it seems properly.
Ping nss working properly..
I need help!!! Any concepts? Maybe something connected with
distributor_admin and trusted connection – I heard somewhere that it is
possible to disable trusted connection for distributor_admin but I don’t
know how to do it?Hello,
I understand that when you try to create a merge replication, you receive
the error message "Error 18483: Could not connect to server "NSS" because
"distributor_admin" is not defined as a remote login at the server."
However, the servername is correct and it is the same as
SERVERPROPERTY('ServerName'). If I'm off-base, please let me know.
This issue could occur when the Machine name at windows level (Hostname) is
different from SQL Server Name (Select @.@.servername).
And this happens when the machine on which SQL Server is installed is
renamed after SQL Server installation. If it is so you will have to do the
following using Query Analyzer:
Sp_dropserver <server>
(Replace <server> with the name returned by Select @.@.servername query)
Sp_addserver <server>, local
(Replace <server> with the machine name (Hostname) if it is default
instance otherwise <server>\instancename for named instance)
Also, did you try to use servername "NSS" when configure merge replication
and not using IP adress directly? I suspect this issue may also related to
network name resolution.
More related information:
818334 Replication setup is not successful when SQL Server is deployed by
using a disk image
http://support.microsoft.com/defaul...kb;EN-US;818334
321822 HOW TO: Replicate Between Computers Running SQL Server in
Non-Trusted Domains or Across the Internet
http://support.microsoft.com/defaul...kb;EN-US;321822
If you have any update, please let's know. Thank you.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Community Support
========================================
==========
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscript...ault.aspx#notif
ications
<http://msdn.microsoft.com/subscript...ps/default.aspx>.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
<http://msdn.microsoft.com/subscript...rt/default.aspx>.
========================================
==========
This posting is provided "AS IS" with no warranties, and confers no rights.|||Peter Yang [MSFT] napisa?(a):
> Hello,
> I understand that when you try to create a merge replication, you receive
> the error message "Error 18483: Could not connect to server "NSS" because
> "distributor_admin" is not defined as a remote login at the server."
> However, the servername is correct and it is the same as
> SERVERPROPERTY('ServerName'). If I'm off-base, please let me know.
yes its true!
> This issue could occur when the Machine name at windows level (Hostname) i
s
> different from SQL Server Name (Select @.@.servername).
> And this happens when the machine on which SQL Server is installed is
> renamed after SQL Server installation. If it is so you will have to do the
> following using Query Analyzer:
Select @.@.servername
returns
NSS
and full computer name is:
nss.domain.local
it is a domain server (SBS)
so computer name is nss and never been changed!
> Sp_dropserver ?<server>?
> (Replace <server> with the name returned by Select @.@.servername query)
>
> Sp_addserver ?<server>?, ?local?
> (Replace <server> with the machine name (Hostname) if it is default
> instance otherwise <server>\instancename for named instance)
> Also, did you try to use servername "NSS" when configure merge replication
> and not using IP adress directly? I suspect this issue may also related to
> network name resolution.
> More related information:
>
> 818334 Replication setup is not successful when SQL Server is deployed by
> using a disk image
> http://support.microsoft.com/defaul...kb;EN-US;818334
>
> 321822 HOW TO: Replicate Between Computers Running SQL Server in
> Non-Trusted Domains or Across the Internet
> http://support.microsoft.com/defaul...kb;EN-US;321822
I will try it this...
Tuesday, March 20, 2012
Replication and Timestamp
Hi,
I have a database that has tables with Timestamp field. I am trying to do a
transactional replication on this db. The wizard changed my "Subscription"
table's timestamp field to Binary format.
Now, the problem is that a report application (we didn't write it) require
this TimeStamp field as Timestamp datatype for it to work. We create the
replication mainly because of this application (we don't want it to take up
any real cpu cycle on the live server). Switching this field back to
timestamp breaks the replication.
Help...
thanks,
Alex
Hi Alex,
You may want to consider using merge replication or
transactional replication with the queued updating
option. For these replications, when articles contain a
timestamp column, the timestamp column is replicated,
but the literal timestamp values are not. The timestamp
values are regenerated when applying the initial
snapshot rows at the Subscriber. This allows timestamp
to continue using optimistic concurrency control (a
frequent usage). For snapshot and transactional
publications, and publications that allow immediate
updating, the literal values for a timestamp column are
replicated, but the data type for the replicated values
is changed to binary (8) on the Subscriber.
This information can be found at the "Data Needs and
Characteristics" topic in BOL:
http://msdn.microsoft.com/library/en...lsql/replplan_
5jub.asp
If you have any further questions, please feel free to
let me know.
Sincerely,
William Wang
Microsoft Online Partner Support
Get Secure! - <www.microsoft.com/security>
================================================== ===
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and
confers no rights.
--
>Reply-To: "Smartikat" <Smartikat@.online.nospam>
>From: "Smartikat" <Smartikat@.online.nospam>
>Subject: Replication and Timestamp
>Date: Thu, 9 Dec 2004 16:20:43 -0800
>Lines: 19
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
>X-RFC2646: Format=Flowed; Original
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
>Message-ID: <#JaVY4k3EHA.1396@.tk2msftngp13.phx.gbl>
>Newsgroups: microsoft.public.sqlserver.replication
>NNTP-Posting-Host: 63.171.237.106
>Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFT NGP08.p
hx.gbl!tk2msftngp13.phx.gbl
>Xref: cpmsftngxa10.phx.gbl
microsoft.public.sqlserver.replication:57801
>X-Tomcat-NG: microsoft.public.sqlserver.replication
>Hi,
>I have a database that has tables with Timestamp field.
I am trying to do a
>transactional replication on this db. The wizard
changed my "Subscription"
>table's timestamp field to Binary format.
>Now, the problem is that a report application (we
didn't write it) require
>this TimeStamp field as Timestamp datatype for it to
work. We create the
>replication mainly because of this application (we
don't want it to take up
>any real cpu cycle on the live server). Switching this
field back to
>timestamp breaks the replication.
>Help...
>thanks,
>Alex
>
>
|||Well, it works to a point...
Here is the problem I am faced with using this new method (Queued Update
setup).
1) Snapshot works fine.
2) When Transactional Replication happens, it will error out with "Syntax
Error/Access Denied Error".
3) Error happens because the Replication Wizard created a bunch of SPs on
the subscriber. And all these SPs contain space " ", "," and "$" in its
name. Main reason is that my Table names where these SPs based on contain "
", "," and "$".
4) Before switching to Queued Update method, I have a Tab named "Command"
under the Article setup screen. Now it is gone.
If there is a way for me to change the SPs name and tell the server to use
them, I am set. Or if there is a way for me to disable all these SPs, I
will be set too...
Please Help.
Alex
"William Wang[MSFT]" <v-rxwang@.online.microsoft.com> wrote in message
news:XI86lfo3EHA.3956@.cpmsftngxa10.phx.gbl...
> Hi Alex,
> You may want to consider using merge replication or
> transactional replication with the queued updating
> option. For these replications, when articles contain a
> timestamp column, the timestamp column is replicated,
> but the literal timestamp values are not. The timestamp
> values are regenerated when applying the initial
> snapshot rows at the Subscriber. This allows timestamp
> to continue using optimistic concurrency control (a
> frequent usage). For snapshot and transactional
> publications, and publications that allow immediate
> updating, the literal values for a timestamp column are
> replicated, but the data type for the replicated values
> is changed to binary (8) on the Subscriber.
> This information can be found at the "Data Needs and
> Characteristics" topic in BOL:
> http://msdn.microsoft.com/library/en...lsql/replplan_
> 5jub.asp
> If you have any further questions, please feel free to
> let me know.
> Sincerely,
> William Wang
> Microsoft Online Partner Support
> Get Secure! - <www.microsoft.com/security>
> ================================================== ===
> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and
> confers no rights.
> --
> cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFT NGP08.p
> hx.gbl!tk2msftngp13.phx.gbl
> microsoft.public.sqlserver.replication:57801
> I am trying to do a
> changed my "Subscription"
> didn't write it) require
> work. We create the
> don't want it to take up
> field back to
>
|||Hi Alex,
A BUG has been filed for the type of problem you are
having with replication.
Q306608 BUG: Distribution Agent May Fail with Incorrect
Syntax
http://support.microsoft.com/?id=306608
The only workaround was to rename the tables without the
special characters.
The problem is that when Logreader generates the command
it does not use delimiters. There is no way to configure
it work differently. You may consider creating the
article differently. On the publication properties,
click the ... button and uncheck the "replace
insert/update/delete..." checkboxes to force the use of
straight SQL to deliver the commands. This is also
available with scripting as options on sp_addarticle
where @.ins_cmd/upd_cmd/del_cmd='SQL'. Replication will
perform slower but it should work. Please give this a
try and let me know how it works for you.
Sincerely,
William Wang
Microsoft Online Partner Support
Get Secure! - <www.microsoft.com/security>
================================================== ===
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and
confers no rights.
--
>Reply-To: "Smartikat" <Smartikat@.online.nospam>
>From: "Smartikat" <Smartikat@.online.nospam>
>References: <#JaVY4k3EHA.1396@.tk2msftngp13.phx.gbl>
<XI86lfo3EHA.3956@.cpmsftngxa10.phx.gbl>
>Subject: Re: Replication and Timestamp
>Date: Fri, 10 Dec 2004 16:13:22 -0800
>Lines: 116
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
>X-RFC2646: Format=Flowed; Original
>Message-ID: <OT5w6Yx3EHA.3236@.TK2MSFTNGP15.phx.gbl>
>Newsgroups: microsoft.public.sqlserver.replication
>NNTP-Posting-Host: 63.171.237.106
>Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFT NGP08.p
hx.gbl!TK2MSFTNGP15.phx.gbl
>Xref: cpmsftngxa10.phx.gbl
microsoft.public.sqlserver.replication:57831
>X-Tomcat-NG: microsoft.public.sqlserver.replication
>Well, it works to a point...
>Here is the problem I am faced with using this new
method (Queued Update
>setup).
>1) Snapshot works fine.
>2) When Transactional Replication happens, it will
error out with "Syntax
>Error/Access Denied Error".
>3) Error happens because the Replication Wizard
created a bunch of SPs on
>the subscriber. And all these SPs contain space " ",
"," and "$" in its
>name. Main reason is that my Table names where these
SPs based on contain "
>", "," and "$".
>4) Before switching to Queued Update method, I have a
Tab named "Command"
>under the Article setup screen. Now it is gone.
>If there is a way for me to change the SPs name and
tell the server to use
>them, I am set. Or if there is a way for me to disable
all these SPs, I
>will be set too...
>Please Help.
>Alex
>
>"William Wang[MSFT]" <v-rxwang@.online.microsoft.com>
wrote in message[vbcol=seagreen]
>news:XI86lfo3EHA.3956@.cpmsftngxa10.phx.gbl...
a[vbcol=seagreen]
timestamp[vbcol=seagreen]
are[vbcol=seagreen]
values[vbcol=seagreen]
http://msdn.microsoft.com/library/en...lsql/replplan_[vbcol=seagreen]
and[vbcol=seagreen]
V6.00.2900.2180[vbcol=seagreen]
cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFT NGP08.p[vbcol=seagreen]
field.[vbcol=seagreen]
this
>
>
|||William...
Thanks for the info... But unfortunately, I cannot change the Table Name at
the source. It is because the Source tables are from Navision (Another
Microsoft Product). And Navision uses Company Name + '$" to prefix the
table names.
Any chance for there is a hot fix for it?
Thanks,
Alex
"William Wang[MSFT]" <v-rxwang@.online.microsoft.com> wrote in message
news:nLxDm8P4EHA.1512@.cpmsftngxa10.phx.gbl...
> Hi Alex,
> A BUG has been filed for the type of problem you are
> having with replication.
>
> Q306608 BUG: Distribution Agent May Fail with Incorrect
> Syntax
> http://support.microsoft.com/?id=306608
>
> The only workaround was to rename the tables without the
> special characters.
> The problem is that when Logreader generates the command
> it does not use delimiters. There is no way to configure
> it work differently. You may consider creating the
> article differently. On the publication properties,
> click the ... button and uncheck the "replace
> insert/update/delete..." checkboxes to force the use of
> straight SQL to deliver the commands. This is also
> available with scripting as options on sp_addarticle
> where @.ins_cmd/upd_cmd/del_cmd='SQL'. Replication will
> perform slower but it should work. Please give this a
> try and let me know how it works for you.
>
> Sincerely,
> William Wang
> Microsoft Online Partner Support
> Get Secure! - <www.microsoft.com/security>
> ================================================== ===
> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and
> confers no rights.
> --
> <XI86lfo3EHA.3956@.cpmsftngxa10.phx.gbl>
> cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFT NGP08.p
> hx.gbl!TK2MSFTNGP15.phx.gbl
> microsoft.public.sqlserver.replication:57831
> method (Queued Update
> error out with "Syntax
> created a bunch of SPs on
> "," and "$" in its
> SPs based on contain "
> Tab named "Command"
> tell the server to use
> all these SPs, I
> wrote in message
> a
> timestamp
> are
> values
> http://msdn.microsoft.com/library/en...lsql/replplan_
> and
> V6.00.2900.2180
> cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFT NGP08.p
> field.
> this
>
|||If there isn't a hotfix, as a work-around you might want to consider
transactionally replicating an indexed view of the table. If the subscriber
has to use the name as the tablename - ie with the hyphen, then a 'normal'
view on the subscriber could be used at that end.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Hi Alex,
I'm sorry that I could not find other workarounds
regarding this issue, and there is not a hotfix for now.
However, I'm glad to tell you that this issue is planned
to be fixed in the next version of SQL Server. Currently
you may consider using Snapshot replication.
Feel free to let me know if I could explain anything
further.
Sincerely,
William Wang
Microsoft Online Partner Support
Get Secure! - <www.microsoft.com/security>
================================================== ===
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and
confers no rights.
--
>Reply-To: "Smartikat" <Smartikat@.online.nospam>
>From: "Smartikat" <Smartikat@.online.nospam>
>References: <#JaVY4k3EHA.1396@.tk2msftngp13.phx.gbl>
<XI86lfo3EHA.3956@.cpmsftngxa10.phx.gbl>
<OT5w6Yx3EHA.3236@.TK2MSFTNGP15.phx.gbl>
<nLxDm8P4EHA.1512@.cpmsftngxa10.phx.gbl>
>Subject: Re: Replication and Timestamp
>Date: Mon, 13 Dec 2004 10:41:13 -0800
>Lines: 223
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
>X-RFC2646: Format=Flowed; Original
>Message-ID: <uoTwTNU4EHA.2592@.TK2MSFTNGP09.phx.gbl>
>Newsgroups: microsoft.public.sqlserver.replication
>NNTP-Posting-Host: 63.171.237.106
>Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXA03.phx.gbl!TK2MSFT NGP08.p
hx.gbl!TK2MSFTNGP09.phx.gbl
>Xref: cpmsftngxa10.phx.gbl
microsoft.public.sqlserver.replication:57875
>X-Tomcat-NG: microsoft.public.sqlserver.replication
>William...
>Thanks for the info... But unfortunately, I cannot
change the Table Name at
>the source. It is because the Source tables are from
Navision (Another
>Microsoft Product). And Navision uses Company Name +
'$" to prefix the
>table names.
>Any chance for there is a hot fix for it?
>Thanks,
>Alex
>
>"William Wang[MSFT]" <v-rxwang@.online.microsoft.com>
wrote in message[vbcol=seagreen]
>news:nLxDm8P4EHA.1512@.cpmsftngxa10.phx.gbl...
Incorrect[vbcol=seagreen]
the[vbcol=seagreen]
command[vbcol=seagreen]
configure[vbcol=seagreen]
of[vbcol=seagreen]
and[vbcol=seagreen]
V6.00.2900.2180[vbcol=seagreen]
cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFT NGP08.p[vbcol=seagreen]
disable[vbcol=seagreen]
contain[vbcol=seagreen]
replicated,[vbcol=seagreen]
timestamp[vbcol=seagreen]
http://msdn.microsoft.com/library/en...lsql/replplan_[vbcol=seagreen]
to[vbcol=seagreen]
================================================== ===[vbcol=seagreen]
via[vbcol=seagreen]
================================================== ===[vbcol=seagreen]
6.00.2900.2180[vbcol=seagreen]
cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFT NGP08.p
>
>
I have a database that has tables with Timestamp field. I am trying to do a
transactional replication on this db. The wizard changed my "Subscription"
table's timestamp field to Binary format.
Now, the problem is that a report application (we didn't write it) require
this TimeStamp field as Timestamp datatype for it to work. We create the
replication mainly because of this application (we don't want it to take up
any real cpu cycle on the live server). Switching this field back to
timestamp breaks the replication.
Help...
thanks,
Alex
Hi Alex,
You may want to consider using merge replication or
transactional replication with the queued updating
option. For these replications, when articles contain a
timestamp column, the timestamp column is replicated,
but the literal timestamp values are not. The timestamp
values are regenerated when applying the initial
snapshot rows at the Subscriber. This allows timestamp
to continue using optimistic concurrency control (a
frequent usage). For snapshot and transactional
publications, and publications that allow immediate
updating, the literal values for a timestamp column are
replicated, but the data type for the replicated values
is changed to binary (8) on the Subscriber.
This information can be found at the "Data Needs and
Characteristics" topic in BOL:
http://msdn.microsoft.com/library/en...lsql/replplan_
5jub.asp
If you have any further questions, please feel free to
let me know.
Sincerely,
William Wang
Microsoft Online Partner Support
Get Secure! - <www.microsoft.com/security>
================================================== ===
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and
confers no rights.
--
>Reply-To: "Smartikat" <Smartikat@.online.nospam>
>From: "Smartikat" <Smartikat@.online.nospam>
>Subject: Replication and Timestamp
>Date: Thu, 9 Dec 2004 16:20:43 -0800
>Lines: 19
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
>X-RFC2646: Format=Flowed; Original
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
>Message-ID: <#JaVY4k3EHA.1396@.tk2msftngp13.phx.gbl>
>Newsgroups: microsoft.public.sqlserver.replication
>NNTP-Posting-Host: 63.171.237.106
>Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFT NGP08.p
hx.gbl!tk2msftngp13.phx.gbl
>Xref: cpmsftngxa10.phx.gbl
microsoft.public.sqlserver.replication:57801
>X-Tomcat-NG: microsoft.public.sqlserver.replication
>Hi,
>I have a database that has tables with Timestamp field.
I am trying to do a
>transactional replication on this db. The wizard
changed my "Subscription"
>table's timestamp field to Binary format.
>Now, the problem is that a report application (we
didn't write it) require
>this TimeStamp field as Timestamp datatype for it to
work. We create the
>replication mainly because of this application (we
don't want it to take up
>any real cpu cycle on the live server). Switching this
field back to
>timestamp breaks the replication.
>Help...
>thanks,
>Alex
>
>
|||Well, it works to a point...
Here is the problem I am faced with using this new method (Queued Update
setup).
1) Snapshot works fine.
2) When Transactional Replication happens, it will error out with "Syntax
Error/Access Denied Error".
3) Error happens because the Replication Wizard created a bunch of SPs on
the subscriber. And all these SPs contain space " ", "," and "$" in its
name. Main reason is that my Table names where these SPs based on contain "
", "," and "$".
4) Before switching to Queued Update method, I have a Tab named "Command"
under the Article setup screen. Now it is gone.
If there is a way for me to change the SPs name and tell the server to use
them, I am set. Or if there is a way for me to disable all these SPs, I
will be set too...
Please Help.
Alex
"William Wang[MSFT]" <v-rxwang@.online.microsoft.com> wrote in message
news:XI86lfo3EHA.3956@.cpmsftngxa10.phx.gbl...
> Hi Alex,
> You may want to consider using merge replication or
> transactional replication with the queued updating
> option. For these replications, when articles contain a
> timestamp column, the timestamp column is replicated,
> but the literal timestamp values are not. The timestamp
> values are regenerated when applying the initial
> snapshot rows at the Subscriber. This allows timestamp
> to continue using optimistic concurrency control (a
> frequent usage). For snapshot and transactional
> publications, and publications that allow immediate
> updating, the literal values for a timestamp column are
> replicated, but the data type for the replicated values
> is changed to binary (8) on the Subscriber.
> This information can be found at the "Data Needs and
> Characteristics" topic in BOL:
> http://msdn.microsoft.com/library/en...lsql/replplan_
> 5jub.asp
> If you have any further questions, please feel free to
> let me know.
> Sincerely,
> William Wang
> Microsoft Online Partner Support
> Get Secure! - <www.microsoft.com/security>
> ================================================== ===
> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and
> confers no rights.
> --
> cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFT NGP08.p
> hx.gbl!tk2msftngp13.phx.gbl
> microsoft.public.sqlserver.replication:57801
> I am trying to do a
> changed my "Subscription"
> didn't write it) require
> work. We create the
> don't want it to take up
> field back to
>
|||Hi Alex,
A BUG has been filed for the type of problem you are
having with replication.
Q306608 BUG: Distribution Agent May Fail with Incorrect
Syntax
http://support.microsoft.com/?id=306608
The only workaround was to rename the tables without the
special characters.
The problem is that when Logreader generates the command
it does not use delimiters. There is no way to configure
it work differently. You may consider creating the
article differently. On the publication properties,
click the ... button and uncheck the "replace
insert/update/delete..." checkboxes to force the use of
straight SQL to deliver the commands. This is also
available with scripting as options on sp_addarticle
where @.ins_cmd/upd_cmd/del_cmd='SQL'. Replication will
perform slower but it should work. Please give this a
try and let me know how it works for you.
Sincerely,
William Wang
Microsoft Online Partner Support
Get Secure! - <www.microsoft.com/security>
================================================== ===
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and
confers no rights.
--
>Reply-To: "Smartikat" <Smartikat@.online.nospam>
>From: "Smartikat" <Smartikat@.online.nospam>
>References: <#JaVY4k3EHA.1396@.tk2msftngp13.phx.gbl>
<XI86lfo3EHA.3956@.cpmsftngxa10.phx.gbl>
>Subject: Re: Replication and Timestamp
>Date: Fri, 10 Dec 2004 16:13:22 -0800
>Lines: 116
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
>X-RFC2646: Format=Flowed; Original
>Message-ID: <OT5w6Yx3EHA.3236@.TK2MSFTNGP15.phx.gbl>
>Newsgroups: microsoft.public.sqlserver.replication
>NNTP-Posting-Host: 63.171.237.106
>Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFT NGP08.p
hx.gbl!TK2MSFTNGP15.phx.gbl
>Xref: cpmsftngxa10.phx.gbl
microsoft.public.sqlserver.replication:57831
>X-Tomcat-NG: microsoft.public.sqlserver.replication
>Well, it works to a point...
>Here is the problem I am faced with using this new
method (Queued Update
>setup).
>1) Snapshot works fine.
>2) When Transactional Replication happens, it will
error out with "Syntax
>Error/Access Denied Error".
>3) Error happens because the Replication Wizard
created a bunch of SPs on
>the subscriber. And all these SPs contain space " ",
"," and "$" in its
>name. Main reason is that my Table names where these
SPs based on contain "
>", "," and "$".
>4) Before switching to Queued Update method, I have a
Tab named "Command"
>under the Article setup screen. Now it is gone.
>If there is a way for me to change the SPs name and
tell the server to use
>them, I am set. Or if there is a way for me to disable
all these SPs, I
>will be set too...
>Please Help.
>Alex
>
>"William Wang[MSFT]" <v-rxwang@.online.microsoft.com>
wrote in message[vbcol=seagreen]
>news:XI86lfo3EHA.3956@.cpmsftngxa10.phx.gbl...
a[vbcol=seagreen]
timestamp[vbcol=seagreen]
are[vbcol=seagreen]
values[vbcol=seagreen]
http://msdn.microsoft.com/library/en...lsql/replplan_[vbcol=seagreen]
and[vbcol=seagreen]
V6.00.2900.2180[vbcol=seagreen]
cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFT NGP08.p[vbcol=seagreen]
field.[vbcol=seagreen]
this
>
>
|||William...
Thanks for the info... But unfortunately, I cannot change the Table Name at
the source. It is because the Source tables are from Navision (Another
Microsoft Product). And Navision uses Company Name + '$" to prefix the
table names.
Any chance for there is a hot fix for it?
Thanks,
Alex
"William Wang[MSFT]" <v-rxwang@.online.microsoft.com> wrote in message
news:nLxDm8P4EHA.1512@.cpmsftngxa10.phx.gbl...
> Hi Alex,
> A BUG has been filed for the type of problem you are
> having with replication.
>
> Q306608 BUG: Distribution Agent May Fail with Incorrect
> Syntax
> http://support.microsoft.com/?id=306608
>
> The only workaround was to rename the tables without the
> special characters.
> The problem is that when Logreader generates the command
> it does not use delimiters. There is no way to configure
> it work differently. You may consider creating the
> article differently. On the publication properties,
> click the ... button and uncheck the "replace
> insert/update/delete..." checkboxes to force the use of
> straight SQL to deliver the commands. This is also
> available with scripting as options on sp_addarticle
> where @.ins_cmd/upd_cmd/del_cmd='SQL'. Replication will
> perform slower but it should work. Please give this a
> try and let me know how it works for you.
>
> Sincerely,
> William Wang
> Microsoft Online Partner Support
> Get Secure! - <www.microsoft.com/security>
> ================================================== ===
> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and
> confers no rights.
> --
> <XI86lfo3EHA.3956@.cpmsftngxa10.phx.gbl>
> cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFT NGP08.p
> hx.gbl!TK2MSFTNGP15.phx.gbl
> microsoft.public.sqlserver.replication:57831
> method (Queued Update
> error out with "Syntax
> created a bunch of SPs on
> "," and "$" in its
> SPs based on contain "
> Tab named "Command"
> tell the server to use
> all these SPs, I
> wrote in message
> a
> timestamp
> are
> values
> http://msdn.microsoft.com/library/en...lsql/replplan_
> and
> V6.00.2900.2180
> cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFT NGP08.p
> field.
> this
>
|||If there isn't a hotfix, as a work-around you might want to consider
transactionally replicating an indexed view of the table. If the subscriber
has to use the name as the tablename - ie with the hyphen, then a 'normal'
view on the subscriber could be used at that end.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Hi Alex,
I'm sorry that I could not find other workarounds
regarding this issue, and there is not a hotfix for now.
However, I'm glad to tell you that this issue is planned
to be fixed in the next version of SQL Server. Currently
you may consider using Snapshot replication.
Feel free to let me know if I could explain anything
further.
Sincerely,
William Wang
Microsoft Online Partner Support
Get Secure! - <www.microsoft.com/security>
================================================== ===
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and
confers no rights.
--
>Reply-To: "Smartikat" <Smartikat@.online.nospam>
>From: "Smartikat" <Smartikat@.online.nospam>
>References: <#JaVY4k3EHA.1396@.tk2msftngp13.phx.gbl>
<XI86lfo3EHA.3956@.cpmsftngxa10.phx.gbl>
<OT5w6Yx3EHA.3236@.TK2MSFTNGP15.phx.gbl>
<nLxDm8P4EHA.1512@.cpmsftngxa10.phx.gbl>
>Subject: Re: Replication and Timestamp
>Date: Mon, 13 Dec 2004 10:41:13 -0800
>Lines: 223
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
>X-RFC2646: Format=Flowed; Original
>Message-ID: <uoTwTNU4EHA.2592@.TK2MSFTNGP09.phx.gbl>
>Newsgroups: microsoft.public.sqlserver.replication
>NNTP-Posting-Host: 63.171.237.106
>Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXA03.phx.gbl!TK2MSFT NGP08.p
hx.gbl!TK2MSFTNGP09.phx.gbl
>Xref: cpmsftngxa10.phx.gbl
microsoft.public.sqlserver.replication:57875
>X-Tomcat-NG: microsoft.public.sqlserver.replication
>William...
>Thanks for the info... But unfortunately, I cannot
change the Table Name at
>the source. It is because the Source tables are from
Navision (Another
>Microsoft Product). And Navision uses Company Name +
'$" to prefix the
>table names.
>Any chance for there is a hot fix for it?
>Thanks,
>Alex
>
>"William Wang[MSFT]" <v-rxwang@.online.microsoft.com>
wrote in message[vbcol=seagreen]
>news:nLxDm8P4EHA.1512@.cpmsftngxa10.phx.gbl...
Incorrect[vbcol=seagreen]
the[vbcol=seagreen]
command[vbcol=seagreen]
configure[vbcol=seagreen]
of[vbcol=seagreen]
and[vbcol=seagreen]
V6.00.2900.2180[vbcol=seagreen]
cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFT NGP08.p[vbcol=seagreen]
disable[vbcol=seagreen]
contain[vbcol=seagreen]
replicated,[vbcol=seagreen]
timestamp[vbcol=seagreen]
http://msdn.microsoft.com/library/en...lsql/replplan_[vbcol=seagreen]
to[vbcol=seagreen]
================================================== ===[vbcol=seagreen]
via[vbcol=seagreen]
================================================== ===[vbcol=seagreen]
6.00.2900.2180[vbcol=seagreen]
cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFT NGP08.p
>
>
Friday, March 9, 2012
Replication -- New Subscription Wizard SQL Mobile error, please help..
I'm following the steps of sample SQL Server Mobile Tutorials..
error on my replication subscription wizard :
I've got the same problem: I can't generate the snapshot.
ErrorMessage:
The replication agent failed to create the directory '\\<pcname>\snapshot\unc\<pcname>_SQLMOBILE_SQLMOBILEPUBLICATION\20060426091803\'.
firstly thanks for your fast reply!
I've checked the publisher's properties and the permissions, the account does have the write permission. I even tried to use the admininstrator account, still the same problem.
error on my replication subscription wizard :
"Initialiazing SQL Server Reconciler has failed
HRESULT 0x80045003 (29045)
The initial snapshot for publication 'SQLMobile' is not yet available. Start the Snapshot Agent to generate the snapshot for this publication. If this snapshot is currently being generated, wait for the process to complete and restart the syncronization.
HRESULT 0x80045003 (0)"
error while waiting synchronizing Data in New Subcription Wizard!!
anyone can help?how to solve this problem?the error says the snapshot wasn't available. Did you create the snapshot already?|||of course I did create the snapshot (I succeed create publication on database engine), like I said..I exactly followed the instruction from the SQL Server Mobile tutorial (MSDN Help).
but when I came to New Subscription Wizard step, It fail to synchronize.
please help me "_"|||
Hi feby,
Check and do the following:
1) Open SQL Server 2005 Management Studio
2) In Object Explorer; expand Replication ==> Publications Tab
3) Right Click on the publication you are interested to subscribe to
4) Choose 'View Snapshot Agent Status'
5) Make sure that 'Snapshot is 100% generated'. If it is already, regenerate again!
Just finishing 'New Publication Wizard' does not complete generation of snapshot. When you complete the above wizard, a snapshot agent job is created + started. Please make sure that the snapshot agent job is completed with 100% with above 'View Snapshot Agent Status'.
If you are getting some errors in generating snapshot, check the credentials of snapshot agent and make sure that snapshot (share or folder) has write security permissions for that user.
Thanks,
Laxmi Narsimha Rao ORUGANTI, MSFT, SQL Everywhere, Microsoft Corporation
[Please move this thread to SQL Server Mobile forum]
|||Hi thereI've got the same problem: I can't generate the snapshot.
ErrorMessage:
The replication agent failed to create the directory '\\<pcname>\snapshot\unc\<pcname>_SQLMOBILE_SQLMOBILEPUBLICATION\20060426091803\'.
I 've set the security permission for the snapshot folder according to the tutorial:
http://msdn2.microsoft.com/en-us/library/ms171908.aspx
for both users (just to make sure)
What i am unsure of, is why they create 2 users: the snapshot_agent (for the snapshot folder) an the IUSR_pcname (for securing the publication)
Which user is doing what and are they related to each other?
According to the MS tutorial (securing Publication step 6) you should see the IUSR in this list, well I couldn't see that user until I gave him the db_owner role, so is that correct, does that user need more roles?
Well I couldn't retrieve the publication, so I added the snapshot_agent user in step 6 an received the errormessage above.
I would be glad, if anyone could help me!
Thanks
Florian Weber, University of Computerscience, Rapperswil, Switzerland
|||Hi
well it seems clearer now, the snapshot_agent is for acessing the snapshot folder an the IUSR_pcname for the anonymous accessing over the IIS.
I also reconfigured the login accounts according to the tutorial.
Unfortunately I still receive the error message that the replication agent fails to create the directory for the snapshot.
The sharing and security settings should be right (write access for the snapshot_agent and the IUSR_pcname)
Has anyone an idea what could be the problem?
Another thing which I am not sure is if the snapshot directory must be the same directory as the virtual directory of the IIS (well I suppose so, because I should access the snapshot from a mobile sql database)
Florian Weber, University of Computerscience, Rapperswil, Switzerland|||
Hi, it looks like you don't have the write permission to the snapshot share. you can find the what is the snapshot folder by running sp_helpdistributor or from the UI to check the publisher's properties.
you will need to give the accout that run the snapshot agent the write permission to this folder.
thanks
yunwen
|||Hi Yunwenfirstly thanks for your fast reply!
I've checked the publisher's properties and the permissions, the account does have the write permission. I even tried to use the admininstrator account, still the same problem.
In my desperation i tried it on another machine and surprisingly it was running perfectly. So it seems that I have some kind of configuration problem with windows on my machine. I think I have to set it up and try it again.
At least I know now how it's working. so thank you!
Greets Florian
|||now my replication & agent are running, but when I deployed the sample program from the tutorial it shows error "Could not connect the database server through IIS" (or error something like that).
I have VS2003 installed on my computer. after my replication running,
I can't create new web project from VS2003. it say : "The Web server reported the following error when attemping to create or open the Web project located at the following URL 'http://localhost/WebApplication'. 'A connection with the server could not be established'."
(like tag IMG below "http://img142.imageshack.us/img142/5429/errorestablished3ma.jpg") any idea why it happen?coz before adjusting replication I can create project, I tried make a virtual directory but it doesn't help (all I know the IIS is still running)|||any body here?|||
i have the exactly same problem and i just have made a clean install i have formated the hard drive but i still having that problem
any advise for solving it?
|||It seem my shared folder can't be accessed, it say about permission!but the strange is..when I plug my LAN cable, that share folder can be accessed!!any clue?|||Seems like we are all having the same problem. I need to run LAN and Web Sync, so I am using RMO to build out the LAN system now. I have permissions for the share and system at full for testing. When the pull subscription is created from the subscriber machine the subscription is left uninitialized the only feedback I have is a failure to create a new snapshot directory.
Event Type: Error
Event Source: <MS SQL SERVER 2005 Instance Name>
Event Category: (2)
Event ID: 14151
Date: 9/20/2006
Time: 10:31:15 AM
User: N/A
Computer: <MS Windows Server 2003 Machine Name>
Description:
Replication-Replication Snapshot Subsystem: agent <merge replication snapshot agent name> failed.
The replication agent had encountered an exception.
Source: Replication
Exception Type: Microsoft.SqlServer.Replication.ReplicationAgentException
Exception Message: The replication agent failed to create the directory <new sub directory name within replication shared directory>
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Replication -- New Subscription Wizard SQL Mobile error, please help..
I'm following the steps of sample SQL Server Mobile Tutorials..
error on my replication subscription wizard :
I've got the same problem: I can't generate the snapshot.
ErrorMessage:
The replication agent failed to create the directory '\\<pcname>\snapshot\unc\<pcname>_SQLMOBILE_SQLMOBILEPUBLICATION\20060426091803\'.
firstly thanks for your fast reply!
I've checked the publisher's properties and the permissions, the account does have the write permission. I even tried to use the admininstrator account, still the same problem.
error on my replication subscription wizard :
"Initialiazing SQL Server Reconciler has failed
HRESULT 0x80045003 (29045)
The initial snapshot for publication 'SQLMobile' is not yet available. Start the Snapshot Agent to generate the snapshot for this publication. If this snapshot is currently being generated, wait for the process to complete and restart the syncronization.
HRESULT 0x80045003 (0)"
error while waiting synchronizing Data in New Subcription Wizard!!
anyone can help?how to solve this problem?the error says the snapshot wasn't available. Did you create the snapshot already?|||of course I did create the snapshot (I succeed create publication on database engine), like I said..I exactly followed the instruction from the SQL Server Mobile tutorial (MSDN Help).
but when I came to New Subscription Wizard step, It fail to synchronize.
please help me "_"|||
Hi feby,
Check and do the following:
1) Open SQL Server 2005 Management Studio
2) In Object Explorer; expand Replication ==> Publications Tab
3) Right Click on the publication you are interested to subscribe to
4) Choose 'View Snapshot Agent Status'
5) Make sure that 'Snapshot is 100% generated'. If it is already, regenerate again!
Just finishing 'New Publication Wizard' does not complete generation of snapshot. When you complete the above wizard, a snapshot agent job is created + started. Please make sure that the snapshot agent job is completed with 100% with above 'View Snapshot Agent Status'.
If you are getting some errors in generating snapshot, check the credentials of snapshot agent and make sure that snapshot (share or folder) has write security permissions for that user.
Thanks,
Laxmi Narsimha Rao ORUGANTI, MSFT, SQL Everywhere, Microsoft Corporation
[Please move this thread to SQL Server Mobile forum]
|||Hi thereI've got the same problem: I can't generate the snapshot.
ErrorMessage:
The replication agent failed to create the directory '\\<pcname>\snapshot\unc\<pcname>_SQLMOBILE_SQLMOBILEPUBLICATION\20060426091803\'.
I 've set the security permission for the snapshot folder according to the tutorial:
http://msdn2.microsoft.com/en-us/library/ms171908.aspx
for both users (just to make sure)
What i am unsure of, is why they create 2 users: the snapshot_agent (for the snapshot folder) an the IUSR_pcname (for securing the publication)
Which user is doing what and are they related to each other?
According to the MS tutorial (securing Publication step 6) you should see the IUSR in this list, well I couldn't see that user until I gave him the db_owner role, so is that correct, does that user need more roles?
Well I couldn't retrieve the publication, so I added the snapshot_agent user in step 6 an received the errormessage above.
I would be glad, if anyone could help me!
Thanks
Florian Weber, University of Computerscience, Rapperswil, Switzerland
|||Hi
well it seems clearer now, the snapshot_agent is for acessing the snapshot folder an the IUSR_pcname for the anonymous accessing over the IIS.
I also reconfigured the login accounts according to the tutorial.
Unfortunately I still receive the error message that the replication agent fails to create the directory for the snapshot.
The sharing and security settings should be right (write access for the snapshot_agent and the IUSR_pcname)
Has anyone an idea what could be the problem?
Another thing which I am not sure is if the snapshot directory must be the same directory as the virtual directory of the IIS (well I suppose so, because I should access the snapshot from a mobile sql database)
Florian Weber, University of Computerscience, Rapperswil, Switzerland|||
Hi, it looks like you don't have the write permission to the snapshot share. you can find the what is the snapshot folder by running sp_helpdistributor or from the UI to check the publisher's properties.
you will need to give the accout that run the snapshot agent the write permission to this folder.
thanks
yunwen
|||Hi Yunwenfirstly thanks for your fast reply!
I've checked the publisher's properties and the permissions, the account does have the write permission. I even tried to use the admininstrator account, still the same problem.
In my desperation i tried it on another machine and surprisingly it was running perfectly. So it seems that I have some kind of configuration problem with windows on my machine. I think I have to set it up and try it again.
At least I know now how it's working. so thank you!
Greets Florian
|||now my replication & agent are running, but when I deployed the sample program from the tutorial it shows error "Could not connect the database server through IIS" (or error something like that).
I have VS2003 installed on my computer. after my replication running,
I can't create new web project from VS2003. it say : "The Web server reported the following error when attemping to create or open the Web project located at the following URL 'http://localhost/WebApplication'. 'A connection with the server could not be established'."
(like tag IMG below "http://img142.imageshack.us/img142/5429/errorestablished3ma.jpg") any idea why it happen?coz before adjusting replication I can create project, I tried make a virtual directory but it doesn't help (all I know the IIS is still running)|||any body here?|||
i have the exactly same problem and i just have made a clean install i have formated the hard drive but i still having that problem
any advise for solving it?
|||It seem my shared folder can't be accessed, it say about permission!but the strange is..when I plug my LAN cable, that share folder can be accessed!!any clue?|||Seems like we are all having the same problem. I need to run LAN and Web Sync, so I am using RMO to build out the LAN system now. I have permissions for the share and system at full for testing. When the pull subscription is created from the subscriber machine the subscription is left uninitialized the only feedback I have is a failure to create a new snapshot directory.
Event Type: Error
Event Source: <MS SQL SERVER 2005 Instance Name>
Event Category: (2)
Event ID: 14151
Date: 9/20/2006
Time: 10:31:15 AM
User: N/A
Computer: <MS Windows Server 2003 Machine Name>
Description:
Replication-Replication Snapshot Subsystem: agent <merge replication snapshot agent name> failed.
The replication agent had encountered an exception.
Source: Replication
Exception Type: Microsoft.SqlServer.Replication.ReplicationAgentException
Exception Message: The replication agent failed to create the directory <new sub directory name within replication shared directory>
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Replication -- New Subscription Wizard SQL Mobile error, please help..
I'm following the steps of sample SQL Server Mobile Tutorials..
error on my replication subscription wizard :
I've got the same problem: I can't generate the snapshot.
ErrorMessage:
The replication agent failed to create the directory '\\<pcname>\snapshot\unc\<pcname>_SQLMOBILE_SQLMOBILEPUBLICATION\20060426091803\'.
firstly thanks for your fast reply!
I've checked the publisher's properties and the permissions, the account does have the write permission. I even tried to use the admininstrator account, still the same problem.
error on my replication subscription wizard :
"Initialiazing SQL Server Reconciler has failed
HRESULT 0x80045003 (29045)
The initial snapshot for publication 'SQLMobile' is not yet available. Start the Snapshot Agent to generate the snapshot for this publication. If this snapshot is currently being generated, wait for the process to complete and restart the syncronization.
HRESULT 0x80045003 (0)"
error while waiting synchronizing Data in New Subcription Wizard!!
anyone can help?how to solve this problem?the error says the snapshot wasn't available. Did you create the snapshot already?|||of course I did create the snapshot (I succeed create publication on database engine), like I said..I exactly followed the instruction from the SQL Server Mobile tutorial (MSDN Help).
but when I came to New Subscription Wizard step, It fail to synchronize.
please help me "_"|||
Hi feby,
Check and do the following:
1) Open SQL Server 2005 Management Studio
2) In Object Explorer; expand Replication ==> Publications Tab
3) Right Click on the publication you are interested to subscribe to
4) Choose 'View Snapshot Agent Status'
5) Make sure that 'Snapshot is 100% generated'. If it is already, regenerate again!
Just finishing 'New Publication Wizard' does not complete generation of snapshot. When you complete the above wizard, a snapshot agent job is created + started. Please make sure that the snapshot agent job is completed with 100% with above 'View Snapshot Agent Status'.
If you are getting some errors in generating snapshot, check the credentials of snapshot agent and make sure that snapshot (share or folder) has write security permissions for that user.
Thanks,
Laxmi Narsimha Rao ORUGANTI, MSFT, SQL Everywhere, Microsoft Corporation
[Please move this thread to SQL Server Mobile forum]
|||Hi thereI've got the same problem: I can't generate the snapshot.
ErrorMessage:
The replication agent failed to create the directory '\\<pcname>\snapshot\unc\<pcname>_SQLMOBILE_SQLMOBILEPUBLICATION\20060426091803\'.
I 've set the security permission for the snapshot folder according to the tutorial:
http://msdn2.microsoft.com/en-us/library/ms171908.aspx
for both users (just to make sure)
What i am unsure of, is why they create 2 users: the snapshot_agent (for the snapshot folder) an the IUSR_pcname (for securing the publication)
Which user is doing what and are they related to each other?
According to the MS tutorial (securing Publication step 6) you should see the IUSR in this list, well I couldn't see that user until I gave him the db_owner role, so is that correct, does that user need more roles?
Well I couldn't retrieve the publication, so I added the snapshot_agent user in step 6 an received the errormessage above.
I would be glad, if anyone could help me!
Thanks
Florian Weber, University of Computerscience, Rapperswil, Switzerland|||Hi
well it seems clearer now, the snapshot_agent is for acessing the snapshot folder an the IUSR_pcname for the anonymous accessing over the IIS.
I also reconfigured the login accounts according to the tutorial.
Unfortunately I still receive the error message that the replication agent fails to create the directory for the snapshot.
The sharing and security settings should be right (write access for the snapshot_agent and the IUSR_pcname)
Has anyone an idea what could be the problem?
Another thing which I am not sure is if the snapshot directory must be the same directory as the virtual directory of the IIS (well I suppose so, because I should access the snapshot from a mobile sql database)
Florian Weber, University of Computerscience, Rapperswil, Switzerland|||
Hi, it looks like you don't have the write permission to the snapshot share. you can find the what is the snapshot folder by running sp_helpdistributor or from the UI to check the publisher's properties.
you will need to give the accout that run the snapshot agent the write permission to this folder.
thanks
yunwen
|||Hi Yunwenfirstly thanks for your fast reply!
I've checked the publisher's properties and the permissions, the account does have the write permission. I even tried to use the admininstrator account, still the same problem.
In my desperation i tried it on another machine and surprisingly it was running perfectly. So it seems that I have some kind of configuration problem with windows on my machine. I think I have to set it up and try it again.
At least I know now how it's working. so thank you!
Greets Florian|||now my replication & agent are running, but when I deployed the
sample program from the tutorial it shows error "Could not connect the
database server through IIS" (or error something like that).
I
have VS2003 installed on my computer. after my replication running,
I can't create new web project from VS2003. it say : "The Web server reported the following error when attemping to create or open the Web project located at the following URL 'http://localhost/WebApplication'. 'A connection with the server could not be established'."
(like tag IMG below "http://img142.imageshack.us/img142/5429/errorestablished3ma.jpg")
any idea why it happen?coz before adjusting replication I can create
project, I tried make a virtual directory but it doesn't help (all I know the IIS is still running)|||any body here?|||
i have the exactly same problem and i just have made a clean install i have formated the hard drive but i still having that problem
any advise for solving it?
|||It seem my shared folder can't be accessed, it say about permission!but the strange is..when I plug my LAN cable, that share folder can be accessed!!any clue?|||Seems like we are all having the same problem. I need to run LAN and Web Sync, so I am using RMO to build out the LAN system now. I have permissions for the share and system at full for testing. When the pull subscription is created from the subscriber machine the subscription is left uninitialized the only feedback I have is a failure to create a new snapshot directory.
Event Type: Error
Event Source: <MS SQL SERVER 2005 Instance Name>
Event Category: (2)
Event ID: 14151
Date: 9/20/2006
Time: 10:31:15 AM
User: N/A
Computer: <MS Windows Server 2003 Machine Name>
Description:
Replication-Replication Snapshot Subsystem: agent <merge replication snapshot agent name> failed.
The replication agent had encountered an exception.
Source: Replication
Exception Type: Microsoft.SqlServer.Replication.ReplicationAgentException
Exception Message: The replication agent failed to create the directory <new sub directory name within replication shared directory>
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Replication -- New Subscription Wizard SQL Mobile error, please help..
I'm following the steps of sample SQL Server Mobile Tutorials..
error on my replication subscription wizard :
I've got the same problem: I can't generate the snapshot.
ErrorMessage:
The replication agent failed to create the directory '\\<pcname>\snapshot\unc\<pcname>_SQLMOBILE_SQLMOBILEPUBLICATION\20060426091803\'.
firstly thanks for your fast reply!
I've checked the publisher's properties and the permissions, the account does have the write permission. I even tried to use the admininstrator account, still the same problem.
error on my replication subscription wizard :
"Initialiazing SQL Server Reconciler has failed
HRESULT 0x80045003 (29045)
The initial snapshot for publication 'SQLMobile' is not yet available. Start the Snapshot Agent to generate the snapshot for this publication. If this snapshot is currently being generated, wait for the process to complete and restart the syncronization.
HRESULT 0x80045003 (0)"
error while waiting synchronizing Data in New Subcription Wizard!!
anyone can help?how to solve this problem?the error says the snapshot wasn't available. Did you create the snapshot already?|||of course I did create the snapshot (I succeed create publication on database engine), like I said..I exactly followed the instruction from the SQL Server Mobile tutorial (MSDN Help).
but when I came to New Subscription Wizard step, It fail to synchronize.
please help me "_"|||
Hi feby,
Check and do the following:
1) Open SQL Server 2005 Management Studio
2) In Object Explorer; expand Replication ==> Publications Tab
3) Right Click on the publication you are interested to subscribe to
4) Choose 'View Snapshot Agent Status'
5) Make sure that 'Snapshot is 100% generated'. If it is already, regenerate again!
Just finishing 'New Publication Wizard' does not complete generation of snapshot. When you complete the above wizard, a snapshot agent job is created + started. Please make sure that the snapshot agent job is completed with 100% with above 'View Snapshot Agent Status'.
If you are getting some errors in generating snapshot, check the credentials of snapshot agent and make sure that snapshot (share or folder) has write security permissions for that user.
Thanks,
Laxmi Narsimha Rao ORUGANTI, MSFT, SQL Everywhere, Microsoft Corporation
[Please move this thread to SQL Server Mobile forum]
|||Hi thereI've got the same problem: I can't generate the snapshot.
ErrorMessage:
The replication agent failed to create the directory '\\<pcname>\snapshot\unc\<pcname>_SQLMOBILE_SQLMOBILEPUBLICATION\20060426091803\'.
I 've set the security permission for the snapshot folder according to the tutorial:
http://msdn2.microsoft.com/en-us/library/ms171908.aspx
for both users (just to make sure)
What i am unsure of, is why they create 2 users: the snapshot_agent (for the snapshot folder) an the IUSR_pcname (for securing the publication)
Which user is doing what and are they related to each other?
According to the MS tutorial (securing Publication step 6) you should see the IUSR in this list, well I couldn't see that user until I gave him the db_owner role, so is that correct, does that user need more roles?
Well I couldn't retrieve the publication, so I added the snapshot_agent user in step 6 an received the errormessage above.
I would be glad, if anyone could help me!
Thanks
Florian Weber, University of Computerscience, Rapperswil, Switzerland|||Hi
well it seems clearer now, the snapshot_agent is for acessing the snapshot folder an the IUSR_pcname for the anonymous accessing over the IIS.
I also reconfigured the login accounts according to the tutorial.
Unfortunately I still receive the error message that the replication agent fails to create the directory for the snapshot.
The sharing and security settings should be right (write access for the snapshot_agent and the IUSR_pcname)
Has anyone an idea what could be the problem?
Another thing which I am not sure is if the snapshot directory must be the same directory as the virtual directory of the IIS (well I suppose so, because I should access the snapshot from a mobile sql database)
Florian Weber, University of Computerscience, Rapperswil, Switzerland|||
Hi, it looks like you don't have the write permission to the snapshot share. you can find the what is the snapshot folder by running sp_helpdistributor or from the UI to check the publisher's properties.
you will need to give the accout that run the snapshot agent the write permission to this folder.
thanks
yunwen
|||Hi Yunwenfirstly thanks for your fast reply!
I've checked the publisher's properties and the permissions, the account does have the write permission. I even tried to use the admininstrator account, still the same problem.
In my desperation i tried it on another machine and surprisingly it was running perfectly. So it seems that I have some kind of configuration problem with windows on my machine. I think I have to set it up and try it again.
At least I know now how it's working. so thank you!
Greets Florian|||now my replication & agent are running, but when I deployed the
sample program from the tutorial it shows error "Could not connect the
database server through IIS" (or error something like that).
I
have VS2003 installed on my computer. after my replication running,
I can't create new web project from VS2003. it say : "The Web server reported the following error when attemping to create or open the Web project located at the following URL 'http://localhost/WebApplication'. 'A connection with the server could not be established'."
(like tag IMG below "http://img142.imageshack.us/img142/5429/errorestablished3ma.jpg")
any idea why it happen?coz before adjusting replication I can create
project, I tried make a virtual directory but it doesn't help (all I know the IIS is still running)|||any body here?|||
i have the exactly same problem and i just have made a clean install i have formated the hard drive but i still having that problem
any advise for solving it?
|||It seem my shared folder can't be accessed, it say about permission!but the strange is..when I plug my LAN cable, that share folder can be accessed!!any clue?|||Seems like we are all having the same problem. I need to run LAN and Web Sync, so I am using RMO to build out the LAN system now. I have permissions for the share and system at full for testing. When the pull subscription is created from the subscriber machine the subscription is left uninitialized the only feedback I have is a failure to create a new snapshot directory.
Event Type: Error
Event Source: <MS SQL SERVER 2005 Instance Name>
Event Category: (2)
Event ID: 14151
Date: 9/20/2006
Time: 10:31:15 AM
User: N/A
Computer: <MS Windows Server 2003 Machine Name>
Description:
Replication-Replication Snapshot Subsystem: agent <merge replication snapshot agent name> failed.
The replication agent had encountered an exception.
Source: Replication
Exception Type: Microsoft.SqlServer.Replication.ReplicationAgentException
Exception Message: The replication agent failed to create the directory <new sub directory name within replication shared directory>
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Wednesday, March 7, 2012
Replication - Can not create Publication database
Hi,
I am trying to use Enterprise Manager Wizard to create a new
Publication database but I got the following message.
Error 2812: Could not find stored procedure
MyDB.dbo.sp_MSadd_logreader_agent
There seems that some replication stored procedures.
Any help?
Thanks in Advance"Ned" <nedabada@.yahoo.ca> wrote in message
news:3578739c.0501071331.3e845f66@.posting.google.c om...
> Hi,
> I am trying to use Enterprise Manager Wizard to create a new
> Publication database but I got the following message.
> Error 2812: Could not find stored procedure
> MyDB.dbo.sp_MSadd_logreader_agent
> There seems that some replication stored procedures.
> Any help?
> Thanks in Advance
You might get a better answer in microsoft.public.sqlserver.replication.
There are also lots of similar posts in the past, although I don't know if
any will apply to your situation exactly - Google "sql 2000 replication
error 2812" or something similar.
Simon
Saturday, February 25, 2012
Replication
I have replication configured in an sql 2005 environment. I have
executed the wizard twice but each time the following maintenance jobs
are missing
Reinitialize subscriptions having data validation failures
Agent history clean up: distribution
Replication monitoring refresher for distribution.
Replication agents checkup
Distribution clean up: distribution
Expired subscription clean up
If someone can tell me what most be done to have these jobs created
or why the wizard failed to create them it would be a big help.What do you set up exactly? Distributor, Publisher and Subscriber? Also what
Replication method do you setup? Merge, Transactional, Snapshot?
--
Ekrem Önsoy
"NC3" <ncoleman3@.yahoo.com> wrote in message
news:1191870323.081389.186990@.r29g2000hsg.googlegroups.com...
>I have replication configured in an sql 2005 environment. I have
> executed the wizard twice but each time the following maintenance jobs
> are missing
>
> Reinitialize subscriptions having data validation failures
> Agent history clean up: distribution
> Replication monitoring refresher for distribution.
> Replication agents checkup
> Distribution clean up: distribution
> Expired subscription clean up
> If someone can tell me what most be done to have these jobs created
> or why the wizard failed to create them it would be a big help.
>|||On Oct 8, 4:22 pm, Ekrem =D6nsoy <ek...@.btegitim.com> wrote:
> What do you set up exactly? Distributor, Publisher and Subscriber? Also w=hat
> Replication method do you setup? Merge, Transactional, Snapshot?
> --
> Ekrem =D6nsoy
> "NC3" <ncolem...@.yahoo.com> wrote in message
> news:1191870323.081389.186990@.r29g2000hsg.googlegroups.com...
>
> >I have replication configured in an sql 2005 environment. I have
> > executed the wizard twice but each time the following maintenance jobs
> > are missing
> > Reinitialize subscriptions having data validation failures
> > Agent history clean up: distribution
> > Replication monitoring refresher for distribution.
> > Replication agents checkup
> > Distribution clean up: distribution
> > Expired subscription clean up
> > If someone can tell me what most be done to have these jobs created
> > or why the wizard failed to create them it would be a big help.- Hide q=uoted text -
> - Show quoted text -
I have transactional replication configured using a remote distributor
to 'push' articles to a subscriber with ALL jobs configured to run at
the distributor.|||Hello,
What version of SQL 2005 you are using. As there was bug prior SP1. try
increasing the size of your model db try configuring again.
Thanks
Ajay Rengunthwar
MCDBA,MCTS
"NC3" <ncoleman3@.yahoo.com> wrote in message
news:1191876823.867493.221310@.50g2000hsm.googlegroups.com...
On Oct 8, 4:22 pm, Ekrem Önsoy <ek...@.btegitim.com> wrote:
> What do you set up exactly? Distributor, Publisher and Subscriber? Also
> what
> Replication method do you setup? Merge, Transactional, Snapshot?
> --
> Ekrem Önsoy
> "NC3" <ncolem...@.yahoo.com> wrote in message
> news:1191870323.081389.186990@.r29g2000hsg.googlegroups.com...
>
> >I have replication configured in an sql 2005 environment. I have
> > executed the wizard twice but each time the following maintenance jobs
> > are missing
> > Reinitialize subscriptions having data validation failures
> > Agent history clean up: distribution
> > Replication monitoring refresher for distribution.
> > Replication agents checkup
> > Distribution clean up: distribution
> > Expired subscription clean up
> > If someone can tell me what most be done to have these jobs created
> > or why the wizard failed to create them it would be a big help.- Hide
> > quoted text -
> - Show quoted text -
I have transactional replication configured using a remote distributor
to 'push' articles to a subscriber with ALL jobs configured to run at
the distributor.
executed the wizard twice but each time the following maintenance jobs
are missing
Reinitialize subscriptions having data validation failures
Agent history clean up: distribution
Replication monitoring refresher for distribution.
Replication agents checkup
Distribution clean up: distribution
Expired subscription clean up
If someone can tell me what most be done to have these jobs created
or why the wizard failed to create them it would be a big help.What do you set up exactly? Distributor, Publisher and Subscriber? Also what
Replication method do you setup? Merge, Transactional, Snapshot?
--
Ekrem Önsoy
"NC3" <ncoleman3@.yahoo.com> wrote in message
news:1191870323.081389.186990@.r29g2000hsg.googlegroups.com...
>I have replication configured in an sql 2005 environment. I have
> executed the wizard twice but each time the following maintenance jobs
> are missing
>
> Reinitialize subscriptions having data validation failures
> Agent history clean up: distribution
> Replication monitoring refresher for distribution.
> Replication agents checkup
> Distribution clean up: distribution
> Expired subscription clean up
> If someone can tell me what most be done to have these jobs created
> or why the wizard failed to create them it would be a big help.
>|||On Oct 8, 4:22 pm, Ekrem =D6nsoy <ek...@.btegitim.com> wrote:
> What do you set up exactly? Distributor, Publisher and Subscriber? Also w=hat
> Replication method do you setup? Merge, Transactional, Snapshot?
> --
> Ekrem =D6nsoy
> "NC3" <ncolem...@.yahoo.com> wrote in message
> news:1191870323.081389.186990@.r29g2000hsg.googlegroups.com...
>
> >I have replication configured in an sql 2005 environment. I have
> > executed the wizard twice but each time the following maintenance jobs
> > are missing
> > Reinitialize subscriptions having data validation failures
> > Agent history clean up: distribution
> > Replication monitoring refresher for distribution.
> > Replication agents checkup
> > Distribution clean up: distribution
> > Expired subscription clean up
> > If someone can tell me what most be done to have these jobs created
> > or why the wizard failed to create them it would be a big help.- Hide q=uoted text -
> - Show quoted text -
I have transactional replication configured using a remote distributor
to 'push' articles to a subscriber with ALL jobs configured to run at
the distributor.|||Hello,
What version of SQL 2005 you are using. As there was bug prior SP1. try
increasing the size of your model db try configuring again.
Thanks
Ajay Rengunthwar
MCDBA,MCTS
"NC3" <ncoleman3@.yahoo.com> wrote in message
news:1191876823.867493.221310@.50g2000hsm.googlegroups.com...
On Oct 8, 4:22 pm, Ekrem Önsoy <ek...@.btegitim.com> wrote:
> What do you set up exactly? Distributor, Publisher and Subscriber? Also
> what
> Replication method do you setup? Merge, Transactional, Snapshot?
> --
> Ekrem Önsoy
> "NC3" <ncolem...@.yahoo.com> wrote in message
> news:1191870323.081389.186990@.r29g2000hsg.googlegroups.com...
>
> >I have replication configured in an sql 2005 environment. I have
> > executed the wizard twice but each time the following maintenance jobs
> > are missing
> > Reinitialize subscriptions having data validation failures
> > Agent history clean up: distribution
> > Replication monitoring refresher for distribution.
> > Replication agents checkup
> > Distribution clean up: distribution
> > Expired subscription clean up
> > If someone can tell me what most be done to have these jobs created
> > or why the wizard failed to create them it would be a big help.- Hide
> > quoted text -
> - Show quoted text -
I have transactional replication configured using a remote distributor
to 'push' articles to a subscriber with ALL jobs configured to run at
the distributor.
Subscribe to:
Posts (Atom)