Hi,
I've installed SQL 2000 SP3 on a Windows 2000 server with Active Directory (not the PDC), but when I try to logon using a Windows account (domain\user) I get the following error:
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
SQL State: 28000
DB error: 18456
The same happens when I try to logon with the Query Analyzer or register the server in Enterprise Manager. I looked around other forums to figure this one out but none of the tips there worked:
- Authentication is mixed mode
- IIS is not installed
- There is a login created in SQL for the Windows user
Any idea's?In the back of my mind somewhere, I have a recollection that when AD is installed the Local Users for that server are disabled. Was the user you were trying to log in as Local or Domain?
I think I would try creating a Domain User, adding that user into the Local Computer Administrators group and then logging in as that Domain User.
Regards,
Hugh Scott
Originally posted by dbJeff
Hi,
I've installed SQL 2000 SP3 on a Windows 2000 server with Active Directory (not the PDC), but when I try to logon using a Windows account (domain\user) I get the following error:
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
SQL State: 28000
DB error: 18456
The same happens when I try to logon with the Query Analyzer or register the server in Enterprise Manager. I looked around other forums to figure this one out but none of the tips there worked:
- Authentication is mixed mode
- IIS is not installed
- There is a login created in SQL for the Windows user
Any idea's?|||Hugh, you're right that Local Users are disabled with AD, but Local Groups are as well. Any other idea's?
Originally posted by hmscott
In the back of my mind somewhere, I have a recollection that when AD is installed the Local Users for that server are disabled. Was the user you were trying to log in as Local or Domain?
I think I would try creating a Domain User, adding that user into the Local Computer Administrators group and then logging in as that Domain User.
Regards,
Hugh Scott|||D'oh! That wasn't very smart of me!
Did you try using sp_grantaccess to ensure that the domain account you were trying to use can access the server?
I don't have much experience running SQL Server with AD; I am running a home network with AD and SQL running on the PDC. I am authenticating using a local account on my Windows XP notebook with no problems. Before I promoted the server to DC, I had a local account with identical credentials in the Administrators group. I have had no problems keeping that account up and running.
I'm afraid I don't have many other suggestions...sorry.
Regards,
Hugh
Originally posted by dbJeff
Hugh, you're right that Local Users are disabled with AD, but Local Groups are as well. Any other idea's?
Showing posts with label sp3. Show all posts
Showing posts with label sp3. Show all posts
Thursday, March 29, 2012
error 18456 when running job
sql2k sp3
Ive got a job that creates a folder both on the local box
and on the remote box. This job has run every nite
successfully for a few weeks now. Last nite it failed with
message: Login failed for user 'NT AUTHORITY\ANONYMOUS
LOGON'. [SQLSTATE 28000] (Error 18456). The step failed.
I havent changed anything security or services related.
The sql services for both boxes run in the same domain
admin account.
Any ideas?
Thanks, Chris.Try making the job owner sa. I've seen this and it ideespeared when I did that.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as ugroup=microsoft.public.sqlserver
"chris" <chrisr@.fingps.com> wrote in message news:034901c36693$a4ce8750$a501280a@.phx.gbl...
> sql2k sp3
> Ive got a job that creates a folder both on the local box
> and on the remote box. This job has run every nite
> successfully for a few weeks now. Last nite it failed with
> message: Login failed for user 'NT AUTHORITY\ANONYMOUS
> LOGON'. [SQLSTATE 28000] (Error 18456). The step failed.
> I havent changed anything security or services related.
> The sql services for both boxes run in the same domain
> admin account.
> Any ideas?
> Thanks, Chris.
Ive got a job that creates a folder both on the local box
and on the remote box. This job has run every nite
successfully for a few weeks now. Last nite it failed with
message: Login failed for user 'NT AUTHORITY\ANONYMOUS
LOGON'. [SQLSTATE 28000] (Error 18456). The step failed.
I havent changed anything security or services related.
The sql services for both boxes run in the same domain
admin account.
Any ideas?
Thanks, Chris.Try making the job owner sa. I've seen this and it ideespeared when I did that.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as ugroup=microsoft.public.sqlserver
"chris" <chrisr@.fingps.com> wrote in message news:034901c36693$a4ce8750$a501280a@.phx.gbl...
> sql2k sp3
> Ive got a job that creates a folder both on the local box
> and on the remote box. This job has run every nite
> successfully for a few weeks now. Last nite it failed with
> message: Login failed for user 'NT AUTHORITY\ANONYMOUS
> LOGON'. [SQLSTATE 28000] (Error 18456). The step failed.
> I havent changed anything security or services related.
> The sql services for both boxes run in the same domain
> admin account.
> Any ideas?
> Thanks, Chris.
Monday, March 26, 2012
Error 17883
Hi,
We have a SQL server 2000 enterprise edition on SP3 on windows NT, and got
the following error recently:
Error: 17883, Severity: 1, State: 0
The Scheduler 0 appears to be hung. SPID 0, ECID 0, UMS Context 0x0233C8D8.
Error: 17883, Severity: 1, State: 0
The Scheduler 0 appears to be hung. SPID 0, ECID 0, UMS Context 0x0233B4F0.
Error: 17883, Severity: 1, State: 0
The Scheduler 0 appears to be hung. SPID 0, ECID 0, UMS Context 0x0233B8E0.
Error: 17883, Severity: 1, State: 0
The Scheduler 1 appears to be hung. SPID 0, ECID 0, UMS Context 0x023339C0.
SQL server contains databases that are used by Crystal Reports which in turn
is used by an application.
Any suggestions or comments are welcome.
Thanks!Hello Sharman!
This is a known issue by Microsoft and they have a Fix document about this.
You may want to read it from the following address:
http://support.microsoft.com/default.aspx/kb/815056
Ekrem Ã?nsoy
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:03F33925-3ED7-4BDF-9502-7953C4C11857@.microsoft.com...
> Hi,
> We have a SQL server 2000 enterprise edition on SP3 on windows NT, and got
> the following error recently:
> Error: 17883, Severity: 1, State: 0
> The Scheduler 0 appears to be hung. SPID 0, ECID 0, UMS Context
> 0x0233C8D8.
> Error: 17883, Severity: 1, State: 0
> The Scheduler 0 appears to be hung. SPID 0, ECID 0, UMS Context
> 0x0233B4F0.
> Error: 17883, Severity: 1, State: 0
> The Scheduler 0 appears to be hung. SPID 0, ECID 0, UMS Context
> 0x0233B8E0.
> Error: 17883, Severity: 1, State: 0
> The Scheduler 1 appears to be hung. SPID 0, ECID 0, UMS Context
> 0x023339C0.
> SQL server contains databases that are used by Crystal Reports which in
> turn
> is used by an application.
> Any suggestions or comments are welcome.
> Thanks!
>sql
We have a SQL server 2000 enterprise edition on SP3 on windows NT, and got
the following error recently:
Error: 17883, Severity: 1, State: 0
The Scheduler 0 appears to be hung. SPID 0, ECID 0, UMS Context 0x0233C8D8.
Error: 17883, Severity: 1, State: 0
The Scheduler 0 appears to be hung. SPID 0, ECID 0, UMS Context 0x0233B4F0.
Error: 17883, Severity: 1, State: 0
The Scheduler 0 appears to be hung. SPID 0, ECID 0, UMS Context 0x0233B8E0.
Error: 17883, Severity: 1, State: 0
The Scheduler 1 appears to be hung. SPID 0, ECID 0, UMS Context 0x023339C0.
SQL server contains databases that are used by Crystal Reports which in turn
is used by an application.
Any suggestions or comments are welcome.
Thanks!Hello Sharman!
This is a known issue by Microsoft and they have a Fix document about this.
You may want to read it from the following address:
http://support.microsoft.com/default.aspx/kb/815056
Ekrem Ã?nsoy
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:03F33925-3ED7-4BDF-9502-7953C4C11857@.microsoft.com...
> Hi,
> We have a SQL server 2000 enterprise edition on SP3 on windows NT, and got
> the following error recently:
> Error: 17883, Severity: 1, State: 0
> The Scheduler 0 appears to be hung. SPID 0, ECID 0, UMS Context
> 0x0233C8D8.
> Error: 17883, Severity: 1, State: 0
> The Scheduler 0 appears to be hung. SPID 0, ECID 0, UMS Context
> 0x0233B4F0.
> Error: 17883, Severity: 1, State: 0
> The Scheduler 0 appears to be hung. SPID 0, ECID 0, UMS Context
> 0x0233B8E0.
> Error: 17883, Severity: 1, State: 0
> The Scheduler 1 appears to be hung. SPID 0, ECID 0, UMS Context
> 0x023339C0.
> SQL server contains databases that are used by Crystal Reports which in
> turn
> is used by an application.
> Any suggestions or comments are welcome.
> Thanks!
>sql
Error 16954
Hello.
What maybe the reason of error 16954: "Executing SQL Directly; no
cursor". I have SQL 2000 SP3, application runs from client machine. What
elements can affect this error?
bye...
__ __
|__\\ | || |_// / \\ \_// FreeBSD: The Power To Serve
|__// |__|| | \\ \__// / \\ +--+
+[ http://bukox.prv.pl ][ http://total.bukox.dmkproject.pl ]+Hi
Does this werror occur every time, or only now and then?
What code is being executed?
Regards
Mike
"[BuKoX]" wrote:
> Hello.
> What maybe the reason of error 16954: "Executing SQL Directly; no
> cursor". I have SQL 2000 SP3, application runs from client machine. What
> elements can affect this error?
> bye...
> --
> __ __
> |__\\ | || |_// / \\ \_// FreeBSD: The Power To Serve
> |__// |__|| | \\ \__// / \\ +--+
> +[ http://bukox.prv.pl ][ http://total.bukox.dmkproject.pl ]+
>|||Mike Epprecht (SQL MVP) wrote:
> Does this werror occur every time, or only now and then?
> What code is being executed?
This error occured as long as application is running and queries are
executed (every queries). Application connect db through MDAC.
bye...
__ __
|__\\ | || |_// / \\ \_// FreeBSD: The Power To Serve
|__// |__|| | \\ \__// / \\ +--+
+[ http://bukox.prv.pl ][ http://total.bukox.dmkproject.pl ]+|||does your SQLServer crash (or very slow) after this?
any other application(s) able to connect and run a query on this server
after that?
What maybe the reason of error 16954: "Executing SQL Directly; no
cursor". I have SQL 2000 SP3, application runs from client machine. What
elements can affect this error?
bye...
__ __
|__\\ | || |_// / \\ \_// FreeBSD: The Power To Serve
|__// |__|| | \\ \__// / \\ +--+
+[ http://bukox.prv.pl ][ http://total.bukox.dmkproject.pl ]+Hi
Does this werror occur every time, or only now and then?
What code is being executed?
Regards
Mike
"[BuKoX]" wrote:
> Hello.
> What maybe the reason of error 16954: "Executing SQL Directly; no
> cursor". I have SQL 2000 SP3, application runs from client machine. What
> elements can affect this error?
> bye...
> --
> __ __
> |__\\ | || |_// / \\ \_// FreeBSD: The Power To Serve
> |__// |__|| | \\ \__// / \\ +--+
> +[ http://bukox.prv.pl ][ http://total.bukox.dmkproject.pl ]+
>|||Mike Epprecht (SQL MVP) wrote:
> Does this werror occur every time, or only now and then?
> What code is being executed?
This error occured as long as application is running and queries are
executed (every queries). Application connect db through MDAC.
bye...
__ __
|__\\ | || |_// / \\ \_// FreeBSD: The Power To Serve
|__// |__|| | \\ \__// / \\ +--+
+[ http://bukox.prv.pl ][ http://total.bukox.dmkproject.pl ]+|||does your SQLServer crash (or very slow) after this?
any other application(s) able to connect and run a query on this server
after that?
Error 16954
Hello.
What maybe the reason of error 16954: "Executing SQL Directly; no
cursor". I have SQL 2000 SP3, application runs from client machine. What
elements can affect this error?
bye...
--
__ __
|__\\ | || |_// / \\ \_// FreeBSD: The Power To Serve
|__// |__|| | \\ \__// / \\ +--+
+[ http://bukox.prv.pl ][ http://total.bukox.dmkproject.pl ]+Hi
Does this werror occur every time, or only now and then?
What code is being executed?
Regards
Mike
"[BuKoX]" wrote:
> Hello.
> What maybe the reason of error 16954: "Executing SQL Directly; no
> cursor". I have SQL 2000 SP3, application runs from client machine. What
> elements can affect this error?
> bye...
> --
> __ __
> |__\\ | || |_// / \\ \_// FreeBSD: The Power To Serve
> |__// |__|| | \\ \__// / \\ +--+
> +[ http://bukox.prv.pl ][ http://total.bukox.dmkproject.pl ]+
>|||Mike Epprecht (SQL MVP) wrote:
> Does this werror occur every time, or only now and then?
> What code is being executed?
This error occured as long as application is running and queries are
executed (every queries). Application connect db through MDAC.
bye...
--
__ __
|__\\ | || |_// / \\ \_// FreeBSD: The Power To Serve
|__// |__|| | \\ \__// / \\ +--+
+[ http://bukox.prv.pl ][ http://total.bukox.dmkproject.pl ]+|||does your SQLServer crash (or very slow) after this?
any other application(s) able to connect and run a query on this server
after that?
What maybe the reason of error 16954: "Executing SQL Directly; no
cursor". I have SQL 2000 SP3, application runs from client machine. What
elements can affect this error?
bye...
--
__ __
|__\\ | || |_// / \\ \_// FreeBSD: The Power To Serve
|__// |__|| | \\ \__// / \\ +--+
+[ http://bukox.prv.pl ][ http://total.bukox.dmkproject.pl ]+Hi
Does this werror occur every time, or only now and then?
What code is being executed?
Regards
Mike
"[BuKoX]" wrote:
> Hello.
> What maybe the reason of error 16954: "Executing SQL Directly; no
> cursor". I have SQL 2000 SP3, application runs from client machine. What
> elements can affect this error?
> bye...
> --
> __ __
> |__\\ | || |_// / \\ \_// FreeBSD: The Power To Serve
> |__// |__|| | \\ \__// / \\ +--+
> +[ http://bukox.prv.pl ][ http://total.bukox.dmkproject.pl ]+
>|||Mike Epprecht (SQL MVP) wrote:
> Does this werror occur every time, or only now and then?
> What code is being executed?
This error occured as long as application is running and queries are
executed (every queries). Application connect db through MDAC.
bye...
--
__ __
|__\\ | || |_// / \\ \_// FreeBSD: The Power To Serve
|__// |__|| | \\ \__// / \\ +--+
+[ http://bukox.prv.pl ][ http://total.bukox.dmkproject.pl ]+|||does your SQLServer crash (or very slow) after this?
any other application(s) able to connect and run a query on this server
after that?
Error 16954
Hello.
What maybe the reason of error 16954: "Executing SQL Directly; no
cursor". I have SQL 2000 SP3, application runs from client machine. What
elements can affect this error?
bye...
__ __
|__\\ | || |_// / \\ \_// FreeBSD: The Power To Serve
|__// |__|| | \\ \__// / \\ +--+
+[ http://bukox.prv.pl ][ http://total.bukox.dmkproject.pl ]+
Hi
Does this werror occur every time, or only now and then?
What code is being executed?
Regards
Mike
"[BuKoX]" wrote:
> Hello.
> What maybe the reason of error 16954: "Executing SQL Directly; no
> cursor". I have SQL 2000 SP3, application runs from client machine. What
> elements can affect this error?
> bye...
> --
> __ __
> |__\\ | || |_// / \\ \_// FreeBSD: The Power To Serve
> |__// |__|| | \\ \__// / \\ +--+
> +[ http://bukox.prv.pl ][ http://total.bukox.dmkproject.pl ]+
>
|||Mike Epprecht (SQL MVP) wrote:
> Does this werror occur every time, or only now and then?
> What code is being executed?
This error occured as long as application is running and queries are
executed (every queries). Application connect db through MDAC.
bye...
__ __
|__\\ | || |_// / \\ \_// FreeBSD: The Power To Serve
|__// |__|| | \\ \__// / \\ +--+
+[ http://bukox.prv.pl ][ http://total.bukox.dmkproject.pl ]+
|||does your SQLServer crash (or very slow) after this?
any other application(s) able to connect and run a query on this server
after that?
What maybe the reason of error 16954: "Executing SQL Directly; no
cursor". I have SQL 2000 SP3, application runs from client machine. What
elements can affect this error?
bye...
__ __
|__\\ | || |_// / \\ \_// FreeBSD: The Power To Serve
|__// |__|| | \\ \__// / \\ +--+
+[ http://bukox.prv.pl ][ http://total.bukox.dmkproject.pl ]+
Hi
Does this werror occur every time, or only now and then?
What code is being executed?
Regards
Mike
"[BuKoX]" wrote:
> Hello.
> What maybe the reason of error 16954: "Executing SQL Directly; no
> cursor". I have SQL 2000 SP3, application runs from client machine. What
> elements can affect this error?
> bye...
> --
> __ __
> |__\\ | || |_// / \\ \_// FreeBSD: The Power To Serve
> |__// |__|| | \\ \__// / \\ +--+
> +[ http://bukox.prv.pl ][ http://total.bukox.dmkproject.pl ]+
>
|||Mike Epprecht (SQL MVP) wrote:
> Does this werror occur every time, or only now and then?
> What code is being executed?
This error occured as long as application is running and queries are
executed (every queries). Application connect db through MDAC.
bye...
__ __
|__\\ | || |_// / \\ \_// FreeBSD: The Power To Serve
|__// |__|| | \\ \__// / \\ +--+
+[ http://bukox.prv.pl ][ http://total.bukox.dmkproject.pl ]+
|||does your SQLServer crash (or very slow) after this?
any other application(s) able to connect and run a query on this server
after that?
Wednesday, March 21, 2012
Error 14294 in replication
Hi
I have a server with Windows 2000 Server SP4 and SQL 2000 with SP3.
This server has several published databases that they replicate data to
another server.
All the replications is of transactional type.
When creating to publish another database it leaves me the following error:
Error 14294
Supply either @.job_id or @.job_name to indentify the job.
That I can make to correct the problem?
Thank you
are you or have you deployed the other publications using a script?
If you, you must use unique publication names and ensure that you don't
specify a snapshot agent name, log reader agent name, or distribution agent
name.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Mario" <Mario@.discussions.microsoft.com> wrote in message
news:C083E5F7-8740-4ACC-B73E-51B6B35FCE62@.microsoft.com...
> Hi
> I have a server with Windows 2000 Server SP4 and SQL 2000 with SP3.
> This server has several published databases that they replicate data to
> another server.
> All the replications is of transactional type.
> When creating to publish another database it leaves me the following
error:
> Error 14294
> Supply either @.job_id or @.job_name to indentify the job.
> That I can make to correct the problem?
> Thank you
|||Hi Hilary
I don′t use a script, my publications was created by wizard.
"Hilary Cotter" wrote:
> are you or have you deployed the other publications using a script?
> If you, you must use unique publication names and ensure that you don't
> specify a snapshot agent name, log reader agent name, or distribution agent
> name.
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "Mario" <Mario@.discussions.microsoft.com> wrote in message
> news:C083E5F7-8740-4ACC-B73E-51B6B35FCE62@.microsoft.com...
> error:
>
>
|||Can you do a Select @.@.SERVERNAME on your publisher and see what server name
it returns? Did you rename this server recently.
There are some reports that this error can be cleared by disabling
replication on your publisher and then recreating it.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Mario" <Mario@.discussions.microsoft.com> wrote in message
news:C083E5F7-8740-4ACC-B73E-51B6B35FCE62@.microsoft.com...
> Hi
> I have a server with Windows 2000 Server SP4 and SQL 2000 with SP3.
> This server has several published databases that they replicate data to
> another server.
> All the replications is of transactional type.
> When creating to publish another database it leaves me the following
error:
> Error 14294
> Supply either @.job_id or @.job_name to indentify the job.
> That I can make to correct the problem?
> Thank you
I have a server with Windows 2000 Server SP4 and SQL 2000 with SP3.
This server has several published databases that they replicate data to
another server.
All the replications is of transactional type.
When creating to publish another database it leaves me the following error:
Error 14294
Supply either @.job_id or @.job_name to indentify the job.
That I can make to correct the problem?
Thank you
are you or have you deployed the other publications using a script?
If you, you must use unique publication names and ensure that you don't
specify a snapshot agent name, log reader agent name, or distribution agent
name.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Mario" <Mario@.discussions.microsoft.com> wrote in message
news:C083E5F7-8740-4ACC-B73E-51B6B35FCE62@.microsoft.com...
> Hi
> I have a server with Windows 2000 Server SP4 and SQL 2000 with SP3.
> This server has several published databases that they replicate data to
> another server.
> All the replications is of transactional type.
> When creating to publish another database it leaves me the following
error:
> Error 14294
> Supply either @.job_id or @.job_name to indentify the job.
> That I can make to correct the problem?
> Thank you
|||Hi Hilary
I don′t use a script, my publications was created by wizard.
"Hilary Cotter" wrote:
> are you or have you deployed the other publications using a script?
> If you, you must use unique publication names and ensure that you don't
> specify a snapshot agent name, log reader agent name, or distribution agent
> name.
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "Mario" <Mario@.discussions.microsoft.com> wrote in message
> news:C083E5F7-8740-4ACC-B73E-51B6B35FCE62@.microsoft.com...
> error:
>
>
|||Can you do a Select @.@.SERVERNAME on your publisher and see what server name
it returns? Did you rename this server recently.
There are some reports that this error can be cleared by disabling
replication on your publisher and then recreating it.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Mario" <Mario@.discussions.microsoft.com> wrote in message
news:C083E5F7-8740-4ACC-B73E-51B6B35FCE62@.microsoft.com...
> Hi
> I have a server with Windows 2000 Server SP4 and SQL 2000 with SP3.
> This server has several published databases that they replicate data to
> another server.
> All the replications is of transactional type.
> When creating to publish another database it leaves me the following
error:
> Error 14294
> Supply either @.job_id or @.job_name to indentify the job.
> That I can make to correct the problem?
> Thank you
Monday, March 19, 2012
Error 14113 while trying to setup replication on SQL Server 2000 S
Hi,
I'm trying to run the wizard to setup replication on a SQL Server 2000 SP3.
Entering the parameters goes without a problem but when executing the script
I'm getting an error 14113:
SQL Server Enterprise MAnager could not configure 'XYZ' as the distributor
for 'XYZ'.
Error 14113: Could not execute c:\... \instdist.sql
I have all the necessary rights on the DB server and on Win 2003.
I also noticed that XP_CMDSHELL doesn't work on this server (probably needed
to execute the previous line) so I executed the instdist.sql manually in
query analyzer.
This clearly isn't enough to get replication working.
The problem with XP_CMDSHELL:
Msg 50001, Level 1, State 50001
xpsql.cpp: Error 1260 from CreateProcess on line 675
I already dropped XP_CMDSHELL:
exec sp_dropextendedproc 'xp_cmdshell'
then replaced the dll with one from another server (just in case) and
re-installed it:
exec sp_addextendedproc 'xp_cmdshell', 'xplog70.dll'
all with the same result.
IMHO both problems are related. Any suggestions?
Tanks in advance,
Gaston.
Can you try to run command shell from within query analyzer? Can you create
subfolders within your snapshot location?
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Gaston" <Gaston@.discussions.microsoft.com> wrote in message
news:ADC431B8-38B5-477D-BE35-AFBF9D6903EC@.microsoft.com...
> Hi,
> I'm trying to run the wizard to setup replication on a SQL Server 2000
> SP3.
> Entering the parameters goes without a problem but when executing the
> script
> I'm getting an error 14113:
> SQL Server Enterprise MAnager could not configure 'XYZ' as the distributor
> for 'XYZ'.
> Error 14113: Could not execute c:\... \instdist.sql
> I have all the necessary rights on the DB server and on Win 2003.
> I also noticed that XP_CMDSHELL doesn't work on this server (probably
> needed
> to execute the previous line) so I executed the instdist.sql manually in
> query analyzer.
> This clearly isn't enough to get replication working.
> The problem with XP_CMDSHELL:
> Msg 50001, Level 1, State 50001
> xpsql.cpp: Error 1260 from CreateProcess on line 675
> I already dropped XP_CMDSHELL:
> exec sp_dropextendedproc 'xp_cmdshell'
> then replaced the dll with one from another server (just in case) and
> re-installed it:
> exec sp_addextendedproc 'xp_cmdshell', 'xplog70.dll'
> all with the same result.
> IMHO both problems are related. Any suggestions?
> Tanks in advance,
> Gaston.
>
|||If you mean if I can run "xp_cmdshell" fromwithin query analyzer: No, this
doesn't work.
The problem with XP_CMDSHELL:
> Msg 50001, Level 1, State 50001
> xpsql.cpp: Error 1260 from CreateProcess on line 675
And it seems that the OSQL command wouldn't even be executed, so the
distribution server can't be setup.
I can create subfolders on the snapshot location, np.
Thanks already,
Gaston.
"Hilary Cotter" wrote:
> Can you try to run command shell from within query analyzer? Can you create
> subfolders within your snapshot location?
> --
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Gaston" <Gaston@.discussions.microsoft.com> wrote in message
> news:ADC431B8-38B5-477D-BE35-AFBF9D6903EC@.microsoft.com...
>
>
|||I suspect this is your problem.
Can you reapply SP3, or better yet SP4 and try again?
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Gaston" <Gaston@.discussions.microsoft.com> wrote in message
news:667B866F-107F-47AB-9355-AC6C9CDF9CE5@.microsoft.com...[vbcol=seagreen]
> If you mean if I can run "xp_cmdshell" fromwithin query analyzer: No, this
> doesn't work.
> The problem with XP_CMDSHELL:
> And it seems that the OSQL command wouldn't even be executed, so the
> distribution server can't be setup.
> I can create subfolders on the snapshot location, np.
> Thanks already,
> Gaston.
>
> "Hilary Cotter" wrote:
|||Hi Hilary,
The xp_cmdshell works after we applied SP4. So now we're on to the
replication problem. I suppose that this will work now as well!
Thanks for your efforts so far!
/Gaston Verelst
"Hilary Cotter" wrote:
> I suspect this is your problem.
> Can you reapply SP3, or better yet SP4 and try again?
> --
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Gaston" <Gaston@.discussions.microsoft.com> wrote in message
> news:667B866F-107F-47AB-9355-AC6C9CDF9CE5@.microsoft.com...
>
>
|||Hi Hilary,
The replication is up and running, thanks for your support!
Kind regards,
Gaston Verelst (Belgium)
"Hilary Cotter" wrote:
> I suspect this is your problem.
> Can you reapply SP3, or better yet SP4 and try again?
> --
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Gaston" <Gaston@.discussions.microsoft.com> wrote in message
> news:667B866F-107F-47AB-9355-AC6C9CDF9CE5@.microsoft.com...
>
>
I'm trying to run the wizard to setup replication on a SQL Server 2000 SP3.
Entering the parameters goes without a problem but when executing the script
I'm getting an error 14113:
SQL Server Enterprise MAnager could not configure 'XYZ' as the distributor
for 'XYZ'.
Error 14113: Could not execute c:\... \instdist.sql
I have all the necessary rights on the DB server and on Win 2003.
I also noticed that XP_CMDSHELL doesn't work on this server (probably needed
to execute the previous line) so I executed the instdist.sql manually in
query analyzer.
This clearly isn't enough to get replication working.
The problem with XP_CMDSHELL:
Msg 50001, Level 1, State 50001
xpsql.cpp: Error 1260 from CreateProcess on line 675
I already dropped XP_CMDSHELL:
exec sp_dropextendedproc 'xp_cmdshell'
then replaced the dll with one from another server (just in case) and
re-installed it:
exec sp_addextendedproc 'xp_cmdshell', 'xplog70.dll'
all with the same result.
IMHO both problems are related. Any suggestions?
Tanks in advance,
Gaston.
Can you try to run command shell from within query analyzer? Can you create
subfolders within your snapshot location?
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Gaston" <Gaston@.discussions.microsoft.com> wrote in message
news:ADC431B8-38B5-477D-BE35-AFBF9D6903EC@.microsoft.com...
> Hi,
> I'm trying to run the wizard to setup replication on a SQL Server 2000
> SP3.
> Entering the parameters goes without a problem but when executing the
> script
> I'm getting an error 14113:
> SQL Server Enterprise MAnager could not configure 'XYZ' as the distributor
> for 'XYZ'.
> Error 14113: Could not execute c:\... \instdist.sql
> I have all the necessary rights on the DB server and on Win 2003.
> I also noticed that XP_CMDSHELL doesn't work on this server (probably
> needed
> to execute the previous line) so I executed the instdist.sql manually in
> query analyzer.
> This clearly isn't enough to get replication working.
> The problem with XP_CMDSHELL:
> Msg 50001, Level 1, State 50001
> xpsql.cpp: Error 1260 from CreateProcess on line 675
> I already dropped XP_CMDSHELL:
> exec sp_dropextendedproc 'xp_cmdshell'
> then replaced the dll with one from another server (just in case) and
> re-installed it:
> exec sp_addextendedproc 'xp_cmdshell', 'xplog70.dll'
> all with the same result.
> IMHO both problems are related. Any suggestions?
> Tanks in advance,
> Gaston.
>
|||If you mean if I can run "xp_cmdshell" fromwithin query analyzer: No, this
doesn't work.
The problem with XP_CMDSHELL:
> Msg 50001, Level 1, State 50001
> xpsql.cpp: Error 1260 from CreateProcess on line 675
And it seems that the OSQL command wouldn't even be executed, so the
distribution server can't be setup.
I can create subfolders on the snapshot location, np.
Thanks already,
Gaston.
"Hilary Cotter" wrote:
> Can you try to run command shell from within query analyzer? Can you create
> subfolders within your snapshot location?
> --
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Gaston" <Gaston@.discussions.microsoft.com> wrote in message
> news:ADC431B8-38B5-477D-BE35-AFBF9D6903EC@.microsoft.com...
>
>
|||I suspect this is your problem.
Can you reapply SP3, or better yet SP4 and try again?
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Gaston" <Gaston@.discussions.microsoft.com> wrote in message
news:667B866F-107F-47AB-9355-AC6C9CDF9CE5@.microsoft.com...[vbcol=seagreen]
> If you mean if I can run "xp_cmdshell" fromwithin query analyzer: No, this
> doesn't work.
> The problem with XP_CMDSHELL:
> And it seems that the OSQL command wouldn't even be executed, so the
> distribution server can't be setup.
> I can create subfolders on the snapshot location, np.
> Thanks already,
> Gaston.
>
> "Hilary Cotter" wrote:
|||Hi Hilary,
The xp_cmdshell works after we applied SP4. So now we're on to the
replication problem. I suppose that this will work now as well!
Thanks for your efforts so far!
/Gaston Verelst
"Hilary Cotter" wrote:
> I suspect this is your problem.
> Can you reapply SP3, or better yet SP4 and try again?
> --
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Gaston" <Gaston@.discussions.microsoft.com> wrote in message
> news:667B866F-107F-47AB-9355-AC6C9CDF9CE5@.microsoft.com...
>
>
|||Hi Hilary,
The replication is up and running, thanks for your support!
Kind regards,
Gaston Verelst (Belgium)
"Hilary Cotter" wrote:
> I suspect this is your problem.
> Can you reapply SP3, or better yet SP4 and try again?
> --
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Gaston" <Gaston@.discussions.microsoft.com> wrote in message
> news:667B866F-107F-47AB-9355-AC6C9CDF9CE5@.microsoft.com...
>
>
Error 1355
I have just reformatted my XP Pro laptop and reinstalled all my software.
I have SQL 2000 SP3 Developer Edition on it.
Just noticed that I am getting warnings in the Application Log with the
following info:
Event ID: 19011
SuperSocket info: (SpnRegister) : Error 1355.
Can anyone shed any light on this error?
Thanks
Hi,
Have a look into the below link:-
http://support.microsoft.com/default...b;en-us;303411
Thanks
Hari
MCDBA
"Keith" <@..> wrote in message news:uqjWaP1OEHA.252@.TK2MSFTNGP10.phx.gbl...
> I have just reformatted my XP Pro laptop and reinstalled all my software.
> I have SQL 2000 SP3 Developer Edition on it.
> Just noticed that I am getting warnings in the Application Log with the
> following info:
> Event ID: 19011
> SuperSocket info: (SpnRegister) : Error 1355.
> Can anyone shed any light on this error?
> Thanks
>
|||Hi,
>http://support.microsoft.com/default.aspx?scid=kb;en-
IT IS to win 2000
I try install SQL Enerprise 2000 in Win XP Pro and
not finish install.
Lool the link
htt://200.207.217.132/avg/erro090.jpg
>--Original Message--
>Hi,
>Have a look into the below link:-
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;303411
>Thanks
>Hari
>MCDBA
>
>"Keith" <@..> wrote in message
news:uqjWaP1OEHA.252@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
reinstalled all my software.[vbcol=seagreen]
Application Log with the
>
>.
>
I have SQL 2000 SP3 Developer Edition on it.
Just noticed that I am getting warnings in the Application Log with the
following info:
Event ID: 19011
SuperSocket info: (SpnRegister) : Error 1355.
Can anyone shed any light on this error?
Thanks
Hi,
Have a look into the below link:-
http://support.microsoft.com/default...b;en-us;303411
Thanks
Hari
MCDBA
"Keith" <@..> wrote in message news:uqjWaP1OEHA.252@.TK2MSFTNGP10.phx.gbl...
> I have just reformatted my XP Pro laptop and reinstalled all my software.
> I have SQL 2000 SP3 Developer Edition on it.
> Just noticed that I am getting warnings in the Application Log with the
> following info:
> Event ID: 19011
> SuperSocket info: (SpnRegister) : Error 1355.
> Can anyone shed any light on this error?
> Thanks
>
|||Hi,
>http://support.microsoft.com/default.aspx?scid=kb;en-
IT IS to win 2000
I try install SQL Enerprise 2000 in Win XP Pro and
not finish install.
Lool the link
htt://200.207.217.132/avg/erro090.jpg
>--Original Message--
>Hi,
>Have a look into the below link:-
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;303411
>Thanks
>Hari
>MCDBA
>
>"Keith" <@..> wrote in message
news:uqjWaP1OEHA.252@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
reinstalled all my software.[vbcol=seagreen]
Application Log with the
>
>.
>
Error 1355
I have just reformatted my XP Pro laptop and reinstalled all my software.
I have SQL 2000 SP3 Developer Edition on it.
Just noticed that I am getting warnings in the Application Log with the
following info:
Event ID: 19011
SuperSocket info: (SpnRegister) : Error 1355.
Can anyone shed any light on this error?
ThanksHi,
Have a look into the below link:-
http://support.microsoft.com/default.aspx?scid=kb;en-us;303411
Thanks
Hari
MCDBA
"Keith" <@..> wrote in message news:uqjWaP1OEHA.252@.TK2MSFTNGP10.phx.gbl...
> I have just reformatted my XP Pro laptop and reinstalled all my software.
> I have SQL 2000 SP3 Developer Edition on it.
> Just noticed that I am getting warnings in the Application Log with the
> following info:
> Event ID: 19011
> SuperSocket info: (SpnRegister) : Error 1355.
> Can anyone shed any light on this error?
> Thanks
>|||Hi,
>http://support.microsoft.com/default.aspx?scid=kb;en-
IT IS to win 2000
I try install SQL Enerprise 2000 in Win XP Pro and
not finish install.
Lool the link
htt://200.207.217.132/avg/erro090.jpg
>--Original Message--
>Hi,
>Have a look into the below link:-
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;303411
>Thanks
>Hari
>MCDBA
>
>"Keith" <@..> wrote in message
news:uqjWaP1OEHA.252@.TK2MSFTNGP10.phx.gbl...
>> I have just reformatted my XP Pro laptop and
reinstalled all my software.
>> I have SQL 2000 SP3 Developer Edition on it.
>> Just noticed that I am getting warnings in the
Application Log with the
>> following info:
>> Event ID: 19011
>> SuperSocket info: (SpnRegister) : Error 1355.
>> Can anyone shed any light on this error?
>> Thanks
>>
>
>.
>
I have SQL 2000 SP3 Developer Edition on it.
Just noticed that I am getting warnings in the Application Log with the
following info:
Event ID: 19011
SuperSocket info: (SpnRegister) : Error 1355.
Can anyone shed any light on this error?
ThanksHi,
Have a look into the below link:-
http://support.microsoft.com/default.aspx?scid=kb;en-us;303411
Thanks
Hari
MCDBA
"Keith" <@..> wrote in message news:uqjWaP1OEHA.252@.TK2MSFTNGP10.phx.gbl...
> I have just reformatted my XP Pro laptop and reinstalled all my software.
> I have SQL 2000 SP3 Developer Edition on it.
> Just noticed that I am getting warnings in the Application Log with the
> following info:
> Event ID: 19011
> SuperSocket info: (SpnRegister) : Error 1355.
> Can anyone shed any light on this error?
> Thanks
>|||Hi,
>http://support.microsoft.com/default.aspx?scid=kb;en-
IT IS to win 2000
I try install SQL Enerprise 2000 in Win XP Pro and
not finish install.
Lool the link
htt://200.207.217.132/avg/erro090.jpg
>--Original Message--
>Hi,
>Have a look into the below link:-
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;303411
>Thanks
>Hari
>MCDBA
>
>"Keith" <@..> wrote in message
news:uqjWaP1OEHA.252@.TK2MSFTNGP10.phx.gbl...
>> I have just reformatted my XP Pro laptop and
reinstalled all my software.
>> I have SQL 2000 SP3 Developer Edition on it.
>> Just noticed that I am getting warnings in the
Application Log with the
>> following info:
>> Event ID: 19011
>> SuperSocket info: (SpnRegister) : Error 1355.
>> Can anyone shed any light on this error?
>> Thanks
>>
>
>.
>
Error 1355
I have just reformatted my XP Pro laptop and reinstalled all my software.
I have SQL 2000 SP3 Developer Edition on it.
Just noticed that I am getting warnings in the Application Log with the
following info:
Event ID: 19011
SuperSocket info: (SpnRegister) : Error 1355.
Can anyone shed any light on this error?
ThanksHi,
Have a look into the below link:-
http://support.microsoft.com/defaul...kb;en-us;303411
Thanks
Hari
MCDBA
"Keith" <@..> wrote in message news:uqjWaP1OEHA.252@.TK2MSFTNGP10.phx.gbl...
> I have just reformatted my XP Pro laptop and reinstalled all my software.
> I have SQL 2000 SP3 Developer Edition on it.
> Just noticed that I am getting warnings in the Application Log with the
> following info:
> Event ID: 19011
> SuperSocket info: (SpnRegister) : Error 1355.
> Can anyone shed any light on this error?
> Thanks
>|||Hi,
>http://support.microsoft.com/default.aspx?scid=kb;en-
IT IS to win 2000
I try install SQL Enerprise 2000 in Win XP Pro and
not finish install.
Lool the link
htt://200.207.217.132/avg/erro090.jpg
>--Original Message--
>Hi,
>Have a look into the below link:-
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;303411
>Thanks
>Hari
>MCDBA
>
>"Keith" <@..> wrote in message
news:uqjWaP1OEHA.252@.TK2MSFTNGP10.phx.gbl...
reinstalled all my software.[vbcol=seagreen]
Application Log with the[vbcol=seagreen]
>
>.
>
I have SQL 2000 SP3 Developer Edition on it.
Just noticed that I am getting warnings in the Application Log with the
following info:
Event ID: 19011
SuperSocket info: (SpnRegister) : Error 1355.
Can anyone shed any light on this error?
ThanksHi,
Have a look into the below link:-
http://support.microsoft.com/defaul...kb;en-us;303411
Thanks
Hari
MCDBA
"Keith" <@..> wrote in message news:uqjWaP1OEHA.252@.TK2MSFTNGP10.phx.gbl...
> I have just reformatted my XP Pro laptop and reinstalled all my software.
> I have SQL 2000 SP3 Developer Edition on it.
> Just noticed that I am getting warnings in the Application Log with the
> following info:
> Event ID: 19011
> SuperSocket info: (SpnRegister) : Error 1355.
> Can anyone shed any light on this error?
> Thanks
>|||Hi,
>http://support.microsoft.com/default.aspx?scid=kb;en-
IT IS to win 2000
I try install SQL Enerprise 2000 in Win XP Pro and
not finish install.
Lool the link
htt://200.207.217.132/avg/erro090.jpg
>--Original Message--
>Hi,
>Have a look into the below link:-
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;303411
>Thanks
>Hari
>MCDBA
>
>"Keith" <@..> wrote in message
news:uqjWaP1OEHA.252@.TK2MSFTNGP10.phx.gbl...
reinstalled all my software.[vbcol=seagreen]
Application Log with the[vbcol=seagreen]
>
>.
>
Sunday, February 19, 2012
Error - could not initialize the Publisher
Hi,
I was synchronizing two SQL Server 2k (SP3) using merge replication for the last 4 months. There was an error in one partiucular table at the publisher because of which synchronization had stopped for around 14-18 hours between these two servers. I fixed
this table using the DBCC checktable with the REPAIR_DATA_LOSS option. No data as such was lost though.
Now when I sychronize the servers I get the following error - "The merge process could not initialize the Publisher 'ECOSYSTEM:MLEcosystem'."
I am attaching the contents of the log file below -
__________________________________________________ _______________________________________
__________________________________________________ _______________________________________
I have tried changing the merge agent profile's Query Timeout, Login Timeout parameter and quite a few parameters to solve this problem as these two servers synchronize over the Internet.
The MSmerge_genhistory at the subscriber has 7000 rows and the one at the publisher has around 8000 rows.
Can someone please advise as to how to synchronize these servers?
Thank you in advance.
Regards,
Manish
which table did you repair? If it is one of the replication system tables
you will have probably have to drop your subscription and rebuild it.
I'd try a re-initialization first.
"Manish Buttan" <manish@.ccipl.com> wrote in message
news:962865EC-16EE-457C-9353-26E105834430@.microsoft.com...
> Hi,
> I was synchronizing two SQL Server 2k (SP3) using merge replication for
the last 4 months. There was an error in one partiucular table at the
publisher because of which synchronization had stopped for around 14-18
hours between these two servers. I fixed this table using the DBCC
checktable with the REPAIR_DATA_LOSS option. No data as such was lost
though.
> Now when I sychronize the servers I get the following error - "The merge
process could not initialize the Publisher 'ECOSYSTEM:MLEcosystem'."
> I am attaching the contents of the log file below -
>
__________________________________________________ __________________________
_____________
>
>
__________________________________________________ __________________________
_____________
>
> I have tried changing the merge agent profile's Query Timeout, Login
Timeout parameter and quite a few parameters to solve this problem as these
two servers synchronize over the Internet.
> The MSmerge_genhistory at the subscriber has 7000 rows and the one at the
publisher has around 8000 rows.
> Can someone please advise as to how to synchronize these servers?
> Thank you in advance.
> Regards,
> Manish
>
>
>
|||Hi Paul, Yuan & Hillary,
I just wanted to thank you all for helping me fix this problem.
It was more of a bandwidth problem I guess. Once all the employees in my company left for the day, I tried to sync the servers, it synchronized without any problem.
This problem occured as the synchronization didn't happen for nearly 18 hours and there was too much data to synchronize at once.
How do I make sure that this problem does not happen again?
Thank you all again!
Regards,
Manish Buttan
|||Manish,
To be honest based on the error message I'm still not sure that this is the problem, but if it is you could try limiting the number of concurrent merge processes or schedule synchronization of the merge agents so as not to overlap (I'm assuming you have m
ultiple subscribers).
HTH,
Paul Ibison
|||Hi Paul,
Thank you once again!
I have only one subscriber. So I dont think it can be because of multiple merge agents running at the same time.
Also, it would really help if you can point me to some URL or if you yourself can give me some tips to configure the merge agent for an unreliable/slow connection.
Thank you.
Regards,
Manish
|||Manish,
have a look at the properties of the merge agent profile. In particular the
QueryTimeout needs maximising. You can use the Slow Link Profile as a model
then increase this parameter.
Profile parameters:
http://msdn.microsoft.com/library/de...lmerg_4y2h.asp
http://msdn.microsoft.com/library/de...plmon_5vqd.asp
Regards,
Paul Ibison
|||Hi Manish,
I also include the followiing articles for your reference.
315521 INF: How to Troubleshoot SQL Server Merge Replication Problems
http://support.microsoft.com/?id=315521
315642 INF: Information that PSS needs to troubleshoot SQL Server
replication
http://support.microsoft.com/?id=315642
Please feel free to let me know if you need further assistance on this
issue.
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
|||Hi Yuan/Paul,
Thank you for all the help you have provided.
Regards,
Manish
I was synchronizing two SQL Server 2k (SP3) using merge replication for the last 4 months. There was an error in one partiucular table at the publisher because of which synchronization had stopped for around 14-18 hours between these two servers. I fixed
this table using the DBCC checktable with the REPAIR_DATA_LOSS option. No data as such was lost though.
Now when I sychronize the servers I get the following error - "The merge process could not initialize the Publisher 'ECOSYSTEM:MLEcosystem'."
I am attaching the contents of the log file below -
__________________________________________________ _______________________________________
__________________________________________________ _______________________________________
I have tried changing the merge agent profile's Query Timeout, Login Timeout parameter and quite a few parameters to solve this problem as these two servers synchronize over the Internet.
The MSmerge_genhistory at the subscriber has 7000 rows and the one at the publisher has around 8000 rows.
Can someone please advise as to how to synchronize these servers?
Thank you in advance.
Regards,
Manish
which table did you repair? If it is one of the replication system tables
you will have probably have to drop your subscription and rebuild it.
I'd try a re-initialization first.
"Manish Buttan" <manish@.ccipl.com> wrote in message
news:962865EC-16EE-457C-9353-26E105834430@.microsoft.com...
> Hi,
> I was synchronizing two SQL Server 2k (SP3) using merge replication for
the last 4 months. There was an error in one partiucular table at the
publisher because of which synchronization had stopped for around 14-18
hours between these two servers. I fixed this table using the DBCC
checktable with the REPAIR_DATA_LOSS option. No data as such was lost
though.
> Now when I sychronize the servers I get the following error - "The merge
process could not initialize the Publisher 'ECOSYSTEM:MLEcosystem'."
> I am attaching the contents of the log file below -
>
__________________________________________________ __________________________
_____________
>
>
__________________________________________________ __________________________
_____________
>
> I have tried changing the merge agent profile's Query Timeout, Login
Timeout parameter and quite a few parameters to solve this problem as these
two servers synchronize over the Internet.
> The MSmerge_genhistory at the subscriber has 7000 rows and the one at the
publisher has around 8000 rows.
> Can someone please advise as to how to synchronize these servers?
> Thank you in advance.
> Regards,
> Manish
>
>
>
|||Hi Paul, Yuan & Hillary,
I just wanted to thank you all for helping me fix this problem.
It was more of a bandwidth problem I guess. Once all the employees in my company left for the day, I tried to sync the servers, it synchronized without any problem.
This problem occured as the synchronization didn't happen for nearly 18 hours and there was too much data to synchronize at once.
How do I make sure that this problem does not happen again?
Thank you all again!
Regards,
Manish Buttan
|||Manish,
To be honest based on the error message I'm still not sure that this is the problem, but if it is you could try limiting the number of concurrent merge processes or schedule synchronization of the merge agents so as not to overlap (I'm assuming you have m
ultiple subscribers).
HTH,
Paul Ibison
|||Hi Paul,
Thank you once again!
I have only one subscriber. So I dont think it can be because of multiple merge agents running at the same time.
Also, it would really help if you can point me to some URL or if you yourself can give me some tips to configure the merge agent for an unreliable/slow connection.
Thank you.
Regards,
Manish
|||Manish,
have a look at the properties of the merge agent profile. In particular the
QueryTimeout needs maximising. You can use the Slow Link Profile as a model
then increase this parameter.
Profile parameters:
http://msdn.microsoft.com/library/de...lmerg_4y2h.asp
http://msdn.microsoft.com/library/de...plmon_5vqd.asp
Regards,
Paul Ibison
|||Hi Manish,
I also include the followiing articles for your reference.
315521 INF: How to Troubleshoot SQL Server Merge Replication Problems
http://support.microsoft.com/?id=315521
315642 INF: Information that PSS needs to troubleshoot SQL Server
replication
http://support.microsoft.com/?id=315642
Please feel free to let me know if you need further assistance on this
issue.
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
|||Hi Yuan/Paul,
Thank you for all the help you have provided.
Regards,
Manish
Labels:
database,
error,
initialize,
merge,
microsoft,
mysql,
oracle,
partiucular,
publisher,
replication,
server,
sp3,
sql,
synchronizing,
table
Subscribe to:
Posts (Atom)