Showing posts with label causes. Show all posts
Showing posts with label causes. Show all posts

Wednesday, March 28, 2012

replication error

i have a problem

when i select distributor and click next

"SQL server agent on 'PC-...' currently uses the system account, which causes replication between servers to fail. In te following dialog box, specify another account for the Service startup account"

and

"SQL server enterprise manager couldn not configure 'PC-...' as the distributor for 'PC-...'

Error 18483: Could not connect to server 'PC-...' because 'distributor admin' is not defined as a remote login at the server."

what can i do?I would start by setting up the sql server agent to use a domain user account. I am no replication expert. Not yet anyways. That project is coming soon.|||My suggestions are:

1. Create a domain user specifically for SQL replication, and no other purpose
2. Before you get a new machine involved with replication, make that domain user a local administrator on the new machine.
3. Start the SQL Agent on the machine that is the distributor using the domain accout from step 1.

Depending on how far you got with the replication installation, you may want to reinstall Replication. I know that I would!

-PatP

Wednesday, March 21, 2012

Replication Between Different Versions of SQL Server causes access denied error.

I am getting the following error:
SQL Server does not exist or access denied. Error number 17.
The publication and distributor is SQL Server 7.0 from internal lan.
The subscriber is SQL Server 2000 from external wan outside of the firewall.
Using SQL Server Enterprise Manager 7.0 on the publication server will not
allow me to register the subscriber as it says "You must upgrade your SQL
Enterprise Manager and SQL-DMO (SQLOLE) to SQL Server 2000(SQLDMO) to
connecti to this server". But if I use a non participanting SQL Server
Enterprise Manager 2000 within the internal lan it will allow me to register
and connect to the browser and I am able to view the database and its
tables.
In addition I can connect to the subscriber using Query Analyzer in version
7.0.
According to the MSDN under the section Replication Between Different
Versions of SQL Server, I fit the same criteria as Combination 2 for
snapshot replication ie. Publisher SQL Server 7.0/Distributor SQL Server
7.0/Subscriber SQL Server 2000.
So why does the push subscription fail?
Regards
Peter
Hello Peter,
This is expected behavior when trying to access SQL Server 2000 from SQL
7.0 version of SQL DMO. You will be able to connect to SQL Server 2000 from
SQL 7.0 version of Query Analyzer, but not Enterprise Manager. The
resolution is to upgrade the client tools to SQL 2000.
Also, as you have mentioned, you could use a SQL 2000 Eneterprise Manager
on a different server to work around this issue.
Combination 2 you referred to does not indicate that you could configure
this in SQL 7 Enterprise Manager. Since it is from SQL 2000 BOL, actually
you could only configure this from a SQL 2000 Enterprise Manager.
Hope this helps.
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.
This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/tec...rview/40010469
Others: https://partner.microsoft.com/US/tec...pportoverview/
If you are outside the United States, please visit our International
Support page:
http://support.microsoft.com/default...national.aspx.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>From: "Peter Lapic" <plapic@.shop-a-docket.com.au>
>Subject: Replication Between Different Versions of SQL Server causes
access denied error.
>Date: Mon, 31 Oct 2005 16:30:49 +1000
>Lines: 32
>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: <u130mSe3FHA.3136@.TK2MSFTNGP09.phx.gbl>
>Newsgroups: microsoft.public.sqlserver.replication
>NNTP-Posting-Host: 61.88.17.230
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFT NGP09.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.replication:17479
>X-Tomcat-NG: microsoft.public.sqlserver.replication
>I am getting the following error:
>SQL Server does not exist or access denied. Error number 17.
>The publication and distributor is SQL Server 7.0 from internal lan.
>The subscriber is SQL Server 2000 from external wan outside of the
firewall.
>Using SQL Server Enterprise Manager 7.0 on the publication server will not
>allow me to register the subscriber as it says "You must upgrade your SQL
>Enterprise Manager and SQL-DMO (SQLOLE) to SQL Server 2000(SQLDMO) to
>connecti to this server". But if I use a non participanting SQL Server
>Enterprise Manager 2000 within the internal lan it will allow me to
register
>and connect to the browser and I am able to view the database and its
>tables.
>In addition I can connect to the subscriber using Query Analyzer in
version
>7.0.
>According to the MSDN under the section Replication Between Different
>Versions of SQL Server, I fit the same criteria as Combination 2 for
>snapshot replication ie. Publisher SQL Server 7.0/Distributor SQL Server
>7.0/Subscriber SQL Server 2000.
>So why does the push subscription fail?
>Regards
>Peter
>
>
>
>
|||I have created the publication on SQL Server 7.0 server via SQL Server 2000
Enterprise and created a push subscription. As soon as the snapshoot was
ready to send I get the same error "The process could not connect to
Subscriber" (SQL Server does not exist or access denied. Error number: 17)
even though I could setup the subscriber and select the destination
database.
Regards
Peter
"Peter Yang [MSFT]" <petery@.online.microsoft.com> wrote in message
news:exdZMBf3FHA.3220@.TK2MSFTNGXA01.phx.gbl...
> Hello Peter,
> This is expected behavior when trying to access SQL Server 2000 from SQL
> 7.0 version of SQL DMO. You will be able to connect to SQL Server 2000
> from
> SQL 7.0 version of Query Analyzer, but not Enterprise Manager. The
> resolution is to upgrade the client tools to SQL 2000.
> Also, as you have mentioned, you could use a SQL 2000 Eneterprise Manager
> on a different server to work around this issue.
> Combination 2 you referred to does not indicate that you could configure
> this in SQL 7 Enterprise Manager. Since it is from SQL 2000 BOL, actually
> you could only configure this from a SQL 2000 Enterprise Manager.
> Hope this helps.
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> Business-Critical Phone Support (BCPS) provides you with technical phone
> support at no charge during critical LAN outages or "business down"
> situations. This benefit is available 24 hours a day, 7 days a week to all
> Microsoft technology partners in the United States and Canada.
> This and other support options are available here:
> BCPS:
> https://partner.microsoft.com/US/tec...rview/40010469
> Others: https://partner.microsoft.com/US/tec...pportoverview/
> If you are outside the United States, please visit our International
> Support page:
> http://support.microsoft.com/default...national.aspx.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> --
> access denied error.
> firewall.
> register
> version
>
|||Hello Peter,
This seems to be a MDAC issue. I suggest that you install latest MDAC 2.8
SP1 if it is on Win2000 server.
899456 Release manifest for MDAC 2.8 Service Pack 1 (2.81.1117.6)
http://support.microsoft.com/?id=899456
Also, please use SQL client network utility to make sure TCPIP and named
pipes are enabled. Also, you may want to create an Alais for SQL 2000
(subscriber) to test the situation.
Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
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.
--
>From: "Peter Lapic" <plapic@.shop-a-docket.com.au>
>References: <u130mSe3FHA.3136@.TK2MSFTNGP09.phx.gbl>
<exdZMBf3FHA.3220@.TK2MSFTNGXA01.phx.gbl>
>Subject: Re: Replication Between Different Versions of SQL Server causes
access denied error.
>Date: Tue, 1 Nov 2005 10:09:26 +1000
>Lines: 117
>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: <uaV8Pin3FHA.700@.TK2MSFTNGP15.phx.gbl>
>Newsgroups: microsoft.public.sqlserver.replication
>NNTP-Posting-Host: 61.88.17.230
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFT NGP15.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.replication:17507
>X-Tomcat-NG: microsoft.public.sqlserver.replication
>I have created the publication on SQL Server 7.0 server via SQL Server
2000[vbcol=seagreen]
>Enterprise and created a push subscription. As soon as the snapshoot was
>ready to send I get the same error "The process could not connect to
>Subscriber" (SQL Server does not exist or access denied. Error number: 17)
>even though I could setup the subscriber and select the destination
>database.
>Regards
>Peter
>"Peter Yang [MSFT]" <petery@.online.microsoft.com> wrote in message
>news:exdZMBf3FHA.3220@.TK2MSFTNGXA01.phx.gbl...
all[vbcol=seagreen]
https://partner.microsoft.com/US/tec...rview/40010469[vbcol=seagreen]
https://partner.microsoft.com/US/tec...pportoverview/[vbcol=seagreen]
not
>
>
|||The penny dropped!
Whilst I did configure SQL client network on my development pc to browse the
external database I didn't realise I had to configure it again on the
distributor server. The replication wizard sort of misled me as part of it
process what to nonimate the subscriber which it found on my development pc
whereas it should have failed it the distributor couldn't recognise it.
Regards
Peter
"Peter Yang [MSFT]" <petery@.online.microsoft.com> wrote in message
news:bCGcbYo3FHA.2984@.TK2MSFTNGXA01.phx.gbl...
> Hello Peter,
> This seems to be a MDAC issue. I suggest that you install latest MDAC 2.8
> SP1 if it is on Win2000 server.
> 899456 Release manifest for MDAC 2.8 Service Pack 1 (2.81.1117.6)
> http://support.microsoft.com/?id=899456
> Also, please use SQL client network utility to make sure TCPIP and named
> pipes are enabled. Also, you may want to create an Alais for SQL 2000
> (subscriber) to test the situation.
> Regards,
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Partner Support
> 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.
>
> --
> <exdZMBf3FHA.3220@.TK2MSFTNGXA01.phx.gbl>
> access denied error.
> 2000
> all
> https://partner.microsoft.com/US/tec...rview/40010469
> https://partner.microsoft.com/US/tec...pportoverview/
> not
>
|||Hello Peter,
Glad to hear the issue is resolved. :-)
Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
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.
| From: "Peter Lapic" <plapic@.shop-a-docket.com.au>
| References: <u130mSe3FHA.3136@.TK2MSFTNGP09.phx.gbl>
<exdZMBf3FHA.3220@.TK2MSFTNGXA01.phx.gbl>
<uaV8Pin3FHA.700@.TK2MSFTNGP15.phx.gbl>
<bCGcbYo3FHA.2984@.TK2MSFTNGXA01.phx.gbl>
| Subject: Re: Replication Between Different Versions of SQL Server causes
access denied error.
| Date: Thu, 3 Nov 2005 10:00:07 +1000
| Lines: 190
| 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: <Ow70RmA4FHA.3540@.TK2MSFTNGP10.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.replication
| NNTP-Posting-Host: 61.88.17.230
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFT NGP10.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.replication:17574
| X-Tomcat-NG: microsoft.public.sqlserver.replication
|
| The penny dropped!
| Whilst I did configure SQL client network on my development pc to browse
the
| external database I didn't realise I had to configure it again on the
| distributor server. The replication wizard sort of misled me as part of
it
| process what to nonimate the subscriber which it found on my development
pc
| whereas it should have failed it the distributor couldn't recognise it.
|
| Regards
| Peter
|
| "Peter Yang [MSFT]" <petery@.online.microsoft.com> wrote in message
| news:bCGcbYo3FHA.2984@.TK2MSFTNGXA01.phx.gbl...
| > Hello Peter,
| >
| > This seems to be a MDAC issue. I suggest that you install latest MDAC
2.8
| > SP1 if it is on Win2000 server.
| >
| > 899456 Release manifest for MDAC 2.8 Service Pack 1 (2.81.1117.6)
| > http://support.microsoft.com/?id=899456
| >
| > Also, please use SQL client network utility to make sure TCPIP and named
| > pipes are enabled. Also, you may want to create an Alais for SQL 2000
| > (subscriber) to test the situation.
| >
| > Regards,
| >
| > Peter Yang
| > MCSE2000/2003, MCSA, MCDBA
| > Microsoft Online Partner Support
| >
| > 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.
| >
| >
| > --
| >>From: "Peter Lapic" <plapic@.shop-a-docket.com.au>
| >>References: <u130mSe3FHA.3136@.TK2MSFTNGP09.phx.gbl>
| > <exdZMBf3FHA.3220@.TK2MSFTNGXA01.phx.gbl>
| >>Subject: Re: Replication Between Different Versions of SQL Server causes
| > access denied error.
| >>Date: Tue, 1 Nov 2005 10:09:26 +1000
| >>Lines: 117
| >>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: <uaV8Pin3FHA.700@.TK2MSFTNGP15.phx.gbl>
| >>Newsgroups: microsoft.public.sqlserver.replication
| >>NNTP-Posting-Host: 61.88.17.230
| >>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFT NGP15.phx.gbl
| >>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.replication:17507
| >>X-Tomcat-NG: microsoft.public.sqlserver.replication
| >>
| >>I have created the publication on SQL Server 7.0 server via SQL Server
| > 2000
| >>Enterprise and created a push subscription. As soon as the snapshoot was
| >>ready to send I get the same error "The process could not connect to
| >>Subscriber" (SQL Server does not exist or access denied. Error number:
17)
| >>even though I could setup the subscriber and select the destination
| >>database.
| >>
| >>Regards
| >>Peter
| >>
| >>"Peter Yang [MSFT]" <petery@.online.microsoft.com> wrote in message
| >>news:exdZMBf3FHA.3220@.TK2MSFTNGXA01.phx.gbl...
| >>> Hello Peter,
| >>>
| >>> This is expected behavior when trying to access SQL Server 2000 from
SQL
| >>> 7.0 version of SQL DMO. You will be able to connect to SQL Server 2000
| >>> from
| >>> SQL 7.0 version of Query Analyzer, but not Enterprise Manager. The
| >>> resolution is to upgrade the client tools to SQL 2000.
| >>>
| >>> Also, as you have mentioned, you could use a SQL 2000 Eneterprise
| >>> Manager
| >>> on a different server to work around this issue.
| >>>
| >>> Combination 2 you referred to does not indicate that you could
configure
| >>> this in SQL 7 Enterprise Manager. Since it is from SQL 2000 BOL,
| >>> actually
| >>> you could only configure this from a SQL 2000 Enterprise Manager.
| >>>
| >>> Hope this helps.
| >>>
| >>> Peter Yang
| >>> MCSE2000/2003, MCSA, MCDBA
| >>> Microsoft Online Partner Support
| >>>
| >>> When responding to posts, please "Reply to Group" via your newsreader
so
| >>> that others may learn and benefit from your issue.
| >>>
| >>> ================================================== ===
| >>>
| >>> Business-Critical Phone Support (BCPS) provides you with technical
phone
| >>> support at no charge during critical LAN outages or "business down"
| >>> situations. This benefit is available 24 hours a day, 7 days a week to
| > all
| >>> Microsoft technology partners in the United States and Canada.
| >>>
| >>> This and other support options are available here:
| >>>
| >>> BCPS:
| >>>
| >
https://partner.microsoft.com/US/tec...rview/40010469
| >>>
| >>> Others:
| > https://partner.microsoft.com/US/tec...pportoverview/
| >>>
| >>> If you are outside the United States, please visit our International
| >>> Support page:
| >>> http://support.microsoft.com/default...national.aspx.
| >>>
| >>> ================================================== ===
| >>>
| >>> This posting is provided "AS IS" with no warranties, and confers no
| >>> rights.
| >>>
| >>>
| >>> --
| >>>>From: "Peter Lapic" <plapic@.shop-a-docket.com.au>
| >>>>Subject: Replication Between Different Versions of SQL Server causes
| >>> access denied error.
| >>>>Date: Mon, 31 Oct 2005 16:30:49 +1000
| >>>>Lines: 32
| >>>>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: <u130mSe3FHA.3136@.TK2MSFTNGP09.phx.gbl>
| >>>>Newsgroups: microsoft.public.sqlserver.replication
| >>>>NNTP-Posting-Host: 61.88.17.230
| >>>>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFT NGP09.phx.gbl
| >>>>Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.sqlserver.replication:17479
| >>>>X-Tomcat-NG: microsoft.public.sqlserver.replication
| >>>>
| >>>>I am getting the following error:
| >>>>SQL Server does not exist or access denied. Error number 17.
| >>>>
| >>>>The publication and distributor is SQL Server 7.0 from internal lan.
| >>>>The subscriber is SQL Server 2000 from external wan outside of the
| >>> firewall.
| >>>>
| >>>>Using SQL Server Enterprise Manager 7.0 on the publication server will
| > not
| >>>>allow me to register the subscriber as it says "You must upgrade your
| >>>>SQL
| >>>>Enterprise Manager and SQL-DMO (SQLOLE) to SQL Server 2000(SQLDMO) to
| >>>>connecti to this server". But if I use a non participanting SQL Server
| >>>>Enterprise Manager 2000 within the internal lan it will allow me to
| >>> register
| >>>>and connect to the browser and I am able to view the database and its
| >>>>tables.
| >>>>
| >>>>In addition I can connect to the subscriber using Query Analyzer in
| >>> version
| >>>>7.0.
| >>>>
| >>>>According to the MSDN under the section Replication Between Different
| >>>>Versions of SQL Server, I fit the same criteria as Combination 2 for
| >>>>snapshot replication ie. Publisher SQL Server 7.0/Distributor SQL
Server
| >>>>7.0/Subscriber SQL Server 2000.
| >>>>
| >>>>So why does the push subscription fail?
| >>>>
| >>>>Regards
| >>>>Peter
| >>>>
| >>>>
| >>>>
| >>>>
| >>>>
| >>>>
| >>>>
| >>>
| >>
| >>
| >>
| >
|
|
|

Friday, March 9, 2012

Replication - SQLServer Agent uses System Account

When I attempt to set up replication on my local box, I receive the error -'SQLServer Agent uses the Systems Account, which causes replication betweem servers to fail'.
Why does this happen? And can I overcome this?
Thanks :)
BiancaStart SQLServerAgent service using a domain account. This account must have the appropriate rights on teh Publisher, Distributor and Subscriber computers (depending on the replication type)

Originally posted by Bianca_J
When I attempt to set up replication on my local box, I receive the error -'SQLServer Agent uses the Systems Account, which causes replication betweem servers to fail'.

Why does this happen? And can I overcome this?

Thanks :)

Bianca|||Thank you for your post :)

What is a Domain Account?

Is this set up in Windows 2000? And if I set up a Domain Account in my local Windows 2000 box - how do I have right over a remore server?

Thanks

Bianca