SQL 2005 SP1
Windows Server 2003 SP1
Exchange 2000
I am getting this error sending a Maintenance Plans report to an email
recipient. It only happens sending to an external email address.
The mail could not be sent to the recipients because of the mail server
failure. (Sending Mail using Account 2 (2007-02-06T08:01:25). Exception
Message: Cannot send mails to mail server. (Mailbox unavailable. The server
response was: 5.7.1 Unable to relay for myaddress@.domain.com).
)
This is an issue correct-able at your SMTP server; it has nothing to do with
database mail (unless you have a more open internal SMTP server available,
that you could use instead).
A
"John Oberlin" <JohnOberlin@.discussions.microsoft.com> wrote in message
news:A35C82BD-00DA-414F-8071-2DD5F11EF010@.microsoft.com...
> SQL 2005 SP1
> Windows Server 2003 SP1
> Exchange 2000
> I am getting this error sending a Maintenance Plans report to an email
> recipient. It only happens sending to an external email address.
> The mail could not be sent to the recipients because of the mail server
> failure. (Sending Mail using Account 2 (2007-02-06T08:01:25). Exception
> Message: Cannot send mails to mail server. (Mailbox unavailable. The
> server
> response was: 5.7.1 Unable to relay for myaddress@.domain.com).
> )
|||Thanks for the reply. So what do I have to do on Exchange to correct this?
|||Well, you could open up external SMTP relay from the IP address of your SQL
Server(s). I am not an Exchange administrator. So for more specific
details, if you don't get a quick enough response here, you'll ghave better
luck in an Exchange newsgroup.
If you have a simple SMTP server running on an IIS box somewhere inside your
network, that you can use for this, I can help with specific instructions
there. Database Mail does not require Exchange, and depending on your
requirements, you may not want to mix the two.
A
"John Oberlin" <JohnOberlin@.discussions.microsoft.com> wrote in message
news:D989979C-3692-4C0D-9BA9-87523863ED45@.microsoft.com...
> Thanks for the reply. So what do I have to do on Exchange to correct
> this?
sql
Showing posts with label error. Show all posts
Showing posts with label error. Show all posts
Friday, March 30, 2012
Relay Error Using Database Mail
SQL 2005 SP1
Windows Server 2003 SP1
Exchange 2000
I am getting this error sending a Maintenance Plans report to an email
recipient. It only happens sending to an external email address.
The mail could not be sent to the recipients because of the mail server
failure. (Sending Mail using Account 2 (2007-02-06T08:01:25). Exception
Message: Cannot send mails to mail server. (Mailbox unavailable. The server
response was: 5.7.1 Unable to relay for myaddress@.domain.com).
)This is an issue correct-able at your SMTP server; it has nothing to do with
database mail (unless you have a more open internal SMTP server available,
that you could use instead).
A
"John Oberlin" <JohnOberlin@.discussions.microsoft.com> wrote in message
news:A35C82BD-00DA-414F-8071-2DD5F11EF010@.microsoft.com...
> SQL 2005 SP1
> Windows Server 2003 SP1
> Exchange 2000
> I am getting this error sending a Maintenance Plans report to an email
> recipient. It only happens sending to an external email address.
> The mail could not be sent to the recipients because of the mail server
> failure. (Sending Mail using Account 2 (2007-02-06T08:01:25). Exception
> Message: Cannot send mails to mail server. (Mailbox unavailable. The
> server
> response was: 5.7.1 Unable to relay for myaddress@.domain.com).
> )|||Thanks for the reply. So what do I have to do on Exchange to correct this?|||Well, you could open up external SMTP relay from the IP address of your SQL
Server(s). I am not an Exchange administrator. So for more specific
details, if you don't get a quick enough response here, you'll ghave better
luck in an Exchange newsgroup.
If you have a simple SMTP server running on an IIS box somewhere inside your
network, that you can use for this, I can help with specific instructions
there. Database Mail does not require Exchange, and depending on your
requirements, you may not want to mix the two.
A
"John Oberlin" <JohnOberlin@.discussions.microsoft.com> wrote in message
news:D989979C-3692-4C0D-9BA9-87523863ED45@.microsoft.com...
> Thanks for the reply. So what do I have to do on Exchange to correct
> this?
Windows Server 2003 SP1
Exchange 2000
I am getting this error sending a Maintenance Plans report to an email
recipient. It only happens sending to an external email address.
The mail could not be sent to the recipients because of the mail server
failure. (Sending Mail using Account 2 (2007-02-06T08:01:25). Exception
Message: Cannot send mails to mail server. (Mailbox unavailable. The server
response was: 5.7.1 Unable to relay for myaddress@.domain.com).
)This is an issue correct-able at your SMTP server; it has nothing to do with
database mail (unless you have a more open internal SMTP server available,
that you could use instead).
A
"John Oberlin" <JohnOberlin@.discussions.microsoft.com> wrote in message
news:A35C82BD-00DA-414F-8071-2DD5F11EF010@.microsoft.com...
> SQL 2005 SP1
> Windows Server 2003 SP1
> Exchange 2000
> I am getting this error sending a Maintenance Plans report to an email
> recipient. It only happens sending to an external email address.
> The mail could not be sent to the recipients because of the mail server
> failure. (Sending Mail using Account 2 (2007-02-06T08:01:25). Exception
> Message: Cannot send mails to mail server. (Mailbox unavailable. The
> server
> response was: 5.7.1 Unable to relay for myaddress@.domain.com).
> )|||Thanks for the reply. So what do I have to do on Exchange to correct this?|||Well, you could open up external SMTP relay from the IP address of your SQL
Server(s). I am not an Exchange administrator. So for more specific
details, if you don't get a quick enough response here, you'll ghave better
luck in an Exchange newsgroup.
If you have a simple SMTP server running on an IIS box somewhere inside your
network, that you can use for this, I can help with specific instructions
there. Database Mail does not require Exchange, and depending on your
requirements, you may not want to mix the two.
A
"John Oberlin" <JohnOberlin@.discussions.microsoft.com> wrote in message
news:D989979C-3692-4C0D-9BA9-87523863ED45@.microsoft.com...
> Thanks for the reply. So what do I have to do on Exchange to correct
> this?
Relay Error Using Database Mail
SQL 2005 SP1
Windows Server 2003 SP1
Exchange 2000
I am getting this error sending a Maintenance Plans report to an email
recipient. It only happens sending to an external email address.
The mail could not be sent to the recipients because of the mail server
failure. (Sending Mail using Account 2 (2007-02-06T08:01:25). Exception
Message: Cannot send mails to mail server. (Mailbox unavailable. The server
response was: 5.7.1 Unable to relay for myaddress@.domain.com).
)This is an issue correct-able at your SMTP server; it has nothing to do with
database mail (unless you have a more open internal SMTP server available,
that you could use instead).
A
"John Oberlin" <JohnOberlin@.discussions.microsoft.com> wrote in message
news:A35C82BD-00DA-414F-8071-2DD5F11EF010@.microsoft.com...
> SQL 2005 SP1
> Windows Server 2003 SP1
> Exchange 2000
> I am getting this error sending a Maintenance Plans report to an email
> recipient. It only happens sending to an external email address.
> The mail could not be sent to the recipients because of the mail server
> failure. (Sending Mail using Account 2 (2007-02-06T08:01:25). Exception
> Message: Cannot send mails to mail server. (Mailbox unavailable. The
> server
> response was: 5.7.1 Unable to relay for myaddress@.domain.com).
> )|||Thanks for the reply. So what do I have to do on Exchange to correct this?|||Well, you could open up external SMTP relay from the IP address of your SQL
Server(s). I am not an Exchange administrator. So for more specific
details, if you don't get a quick enough response here, you'll ghave better
luck in an Exchange newsgroup.
If you have a simple SMTP server running on an IIS box somewhere inside your
network, that you can use for this, I can help with specific instructions
there. Database Mail does not require Exchange, and depending on your
requirements, you may not want to mix the two.
A
"John Oberlin" <JohnOberlin@.discussions.microsoft.com> wrote in message
news:D989979C-3692-4C0D-9BA9-87523863ED45@.microsoft.com...
> Thanks for the reply. So what do I have to do on Exchange to correct
> this?
Windows Server 2003 SP1
Exchange 2000
I am getting this error sending a Maintenance Plans report to an email
recipient. It only happens sending to an external email address.
The mail could not be sent to the recipients because of the mail server
failure. (Sending Mail using Account 2 (2007-02-06T08:01:25). Exception
Message: Cannot send mails to mail server. (Mailbox unavailable. The server
response was: 5.7.1 Unable to relay for myaddress@.domain.com).
)This is an issue correct-able at your SMTP server; it has nothing to do with
database mail (unless you have a more open internal SMTP server available,
that you could use instead).
A
"John Oberlin" <JohnOberlin@.discussions.microsoft.com> wrote in message
news:A35C82BD-00DA-414F-8071-2DD5F11EF010@.microsoft.com...
> SQL 2005 SP1
> Windows Server 2003 SP1
> Exchange 2000
> I am getting this error sending a Maintenance Plans report to an email
> recipient. It only happens sending to an external email address.
> The mail could not be sent to the recipients because of the mail server
> failure. (Sending Mail using Account 2 (2007-02-06T08:01:25). Exception
> Message: Cannot send mails to mail server. (Mailbox unavailable. The
> server
> response was: 5.7.1 Unable to relay for myaddress@.domain.com).
> )|||Thanks for the reply. So what do I have to do on Exchange to correct this?|||Well, you could open up external SMTP relay from the IP address of your SQL
Server(s). I am not an Exchange administrator. So for more specific
details, if you don't get a quick enough response here, you'll ghave better
luck in an Exchange newsgroup.
If you have a simple SMTP server running on an IIS box somewhere inside your
network, that you can use for this, I can help with specific instructions
there. Database Mail does not require Exchange, and depending on your
requirements, you may not want to mix the two.
A
"John Oberlin" <JohnOberlin@.discussions.microsoft.com> wrote in message
news:D989979C-3692-4C0D-9BA9-87523863ED45@.microsoft.com...
> Thanks for the reply. So what do I have to do on Exchange to correct
> this?
Relative Dates
When attempting to use the 'relative dates' functionality of the Report Builder component, I'm getting an error that states "The report may not be valid or the server could not process the data" then in the detail section it says that the field I'm using (an obvious date field) is being interpreted as an integer. If I use an absolute date, it works just fine, just errors out when I use a relative date.
My questions...has anyone else come accross this error? Is it a known issue? Is there a way around it that anyone knows of? I suspect it's a glitch in this new product but really need to know for sure.
Any references to MS topics on this would be hugely appreciated as well.
Thanks...Ooogy
I’m not aware of any known issues like the one you describe. Can yougive more precise repro steps?
Wednesday, March 28, 2012
Relationship between Error Numbers and books Online URls?
Hi,
Is there any relationship between a sql server error number and the naming
convention used in SqlServer Books Online documentation error documentation
files?
Example:
The file name for Error # 207 in books Online ends with "_1_1qyf.htm",
in the msdn version of books online it ends with "_1_1qyf.asp"
The file name for error # 208 ends with "_1_1qyg.asp"
My goal: to programtically generate urls that point to each error's
documentation in books online (sqlException's "Number" property contains the
error number value, so the idea is to programatically set the helplink
property to the correct url by evaluating the number value and running it
through some operation to create the correct url).
I know the error numbers refer to the error id column value in
master.dbo.sysmessages -- but i want to be able to derive urls to books
online from the error number b/c those files have more complete information.
Any suggestions?> Is there any relationship between a sql server error number and the naming
> convention used in SqlServer Books Online documentation error
> documentation
> files?
> My goal: to programtically generate urls that point to each error's
> documentation in books online (sqlException's "Number" property contains
> the
> error number value, so the idea is to programatically set the helplink
> property to the correct url by evaluating the number value and running it
> through some operation to create the correct url).
Sorry, there is no intentional relationship between an error message number
and the filename of the corresponding topic in BOL. Nor is there a way to
predict the filename based on the error number. The filenames for Books
Online topics are auto-generated by the authoring system we use. At best
you can know that the topics for system error messages will have a filename
that starts with "tr_reslsyserr_%" , but the numbering sequence used to
create a unique filename (for example, tr_reslsyserr_1_2a0j.htm) is not
predictable.
Gail Erickson [MS]
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rights
"Chris Mohan" <ChrisMohan@.discussions.microsoft.com> wrote in message
news:86009ACC-4B0E-4308-B642-4BCA8D9E12E9@.microsoft.com...
> Hi,
> Is there any relationship between a sql server error number and the naming
> convention used in SqlServer Books Online documentation error
> documentation
> files?
> Example:
> The file name for Error # 207 in books Online ends with "_1_1qyf.htm",
> in the msdn version of books online it ends with "_1_1qyf.asp"
> The file name for error # 208 ends with "_1_1qyg.asp"
> My goal: to programtically generate urls that point to each error's
> documentation in books online (sqlException's "Number" property contains
> the
> error number value, so the idea is to programatically set the helplink
> property to the correct url by evaluating the number value and running it
> through some operation to create the correct url).
> I know the error numbers refer to the error id column value in
> master.dbo.sysmessages -- but i want to be able to derive urls to books
> online from the error number b/c those files have more complete
> information.
> Any suggestions?
Is there any relationship between a sql server error number and the naming
convention used in SqlServer Books Online documentation error documentation
files?
Example:
The file name for Error # 207 in books Online ends with "_1_1qyf.htm",
in the msdn version of books online it ends with "_1_1qyf.asp"
The file name for error # 208 ends with "_1_1qyg.asp"
My goal: to programtically generate urls that point to each error's
documentation in books online (sqlException's "Number" property contains the
error number value, so the idea is to programatically set the helplink
property to the correct url by evaluating the number value and running it
through some operation to create the correct url).
I know the error numbers refer to the error id column value in
master.dbo.sysmessages -- but i want to be able to derive urls to books
online from the error number b/c those files have more complete information.
Any suggestions?> Is there any relationship between a sql server error number and the naming
> convention used in SqlServer Books Online documentation error
> documentation
> files?
> My goal: to programtically generate urls that point to each error's
> documentation in books online (sqlException's "Number" property contains
> the
> error number value, so the idea is to programatically set the helplink
> property to the correct url by evaluating the number value and running it
> through some operation to create the correct url).
Sorry, there is no intentional relationship between an error message number
and the filename of the corresponding topic in BOL. Nor is there a way to
predict the filename based on the error number. The filenames for Books
Online topics are auto-generated by the authoring system we use. At best
you can know that the topics for system error messages will have a filename
that starts with "tr_reslsyserr_%" , but the numbering sequence used to
create a unique filename (for example, tr_reslsyserr_1_2a0j.htm) is not
predictable.
Gail Erickson [MS]
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rights
"Chris Mohan" <ChrisMohan@.discussions.microsoft.com> wrote in message
news:86009ACC-4B0E-4308-B642-4BCA8D9E12E9@.microsoft.com...
> Hi,
> Is there any relationship between a sql server error number and the naming
> convention used in SqlServer Books Online documentation error
> documentation
> files?
> Example:
> The file name for Error # 207 in books Online ends with "_1_1qyf.htm",
> in the msdn version of books online it ends with "_1_1qyf.asp"
> The file name for error # 208 ends with "_1_1qyg.asp"
> My goal: to programtically generate urls that point to each error's
> documentation in books online (sqlException's "Number" property contains
> the
> error number value, so the idea is to programatically set the helplink
> property to the correct url by evaluating the number value and running it
> through some operation to create the correct url).
> I know the error numbers refer to the error id column value in
> master.dbo.sysmessages -- but i want to be able to derive urls to books
> online from the error number b/c those files have more complete
> information.
> Any suggestions?
Relationship between Error Numbers and books Online URls?
Hi,
Is there any relationship between a sql server error number and the naming
convention used in SqlServer Books Online documentation error documentation
files?
Example:
The file name for Error # 207 in books Online ends with "_1_1qyf.htm",
in the msdn version of books online it ends with "_1_1qyf.asp"
The file name for error # 208 ends with "_1_1qyg.asp"
My goal: to programtically generate urls that point to each error's
documentation in books online (sqlException's "Number" property contains the
error number value, so the idea is to programatically set the helplink
property to the correct url by evaluating the number value and running it
through some operation to create the correct url).
I know the error numbers refer to the error id column value in
master.dbo.sysmessages -- but i want to be able to derive urls to books
online from the error number b/c those files have more complete information.
Any suggestions?
> Is there any relationship between a sql server error number and the naming
> convention used in SqlServer Books Online documentation error
> documentation
> files?
> My goal: to programtically generate urls that point to each error's
> documentation in books online (sqlException's "Number" property contains
> the
> error number value, so the idea is to programatically set the helplink
> property to the correct url by evaluating the number value and running it
> through some operation to create the correct url).
Sorry, there is no intentional relationship between an error message number
and the filename of the corresponding topic in BOL. Nor is there a way to
predict the filename based on the error number. The filenames for Books
Online topics are auto-generated by the authoring system we use. At best
you can know that the topics for system error messages will have a filename
that starts with "tr_reslsyserr_%" , but the numbering sequence used to
create a unique filename (for example, tr_reslsyserr_1_2a0j.htm) is not
predictable.
Gail Erickson [MS]
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rights
"Chris Mohan" <ChrisMohan@.discussions.microsoft.com> wrote in message
news:86009ACC-4B0E-4308-B642-4BCA8D9E12E9@.microsoft.com...
> Hi,
> Is there any relationship between a sql server error number and the naming
> convention used in SqlServer Books Online documentation error
> documentation
> files?
> Example:
> The file name for Error # 207 in books Online ends with "_1_1qyf.htm",
> in the msdn version of books online it ends with "_1_1qyf.asp"
> The file name for error # 208 ends with "_1_1qyg.asp"
> My goal: to programtically generate urls that point to each error's
> documentation in books online (sqlException's "Number" property contains
> the
> error number value, so the idea is to programatically set the helplink
> property to the correct url by evaluating the number value and running it
> through some operation to create the correct url).
> I know the error numbers refer to the error id column value in
> master.dbo.sysmessages -- but i want to be able to derive urls to books
> online from the error number b/c those files have more complete
> information.
> Any suggestions?
Is there any relationship between a sql server error number and the naming
convention used in SqlServer Books Online documentation error documentation
files?
Example:
The file name for Error # 207 in books Online ends with "_1_1qyf.htm",
in the msdn version of books online it ends with "_1_1qyf.asp"
The file name for error # 208 ends with "_1_1qyg.asp"
My goal: to programtically generate urls that point to each error's
documentation in books online (sqlException's "Number" property contains the
error number value, so the idea is to programatically set the helplink
property to the correct url by evaluating the number value and running it
through some operation to create the correct url).
I know the error numbers refer to the error id column value in
master.dbo.sysmessages -- but i want to be able to derive urls to books
online from the error number b/c those files have more complete information.
Any suggestions?
> Is there any relationship between a sql server error number and the naming
> convention used in SqlServer Books Online documentation error
> documentation
> files?
> My goal: to programtically generate urls that point to each error's
> documentation in books online (sqlException's "Number" property contains
> the
> error number value, so the idea is to programatically set the helplink
> property to the correct url by evaluating the number value and running it
> through some operation to create the correct url).
Sorry, there is no intentional relationship between an error message number
and the filename of the corresponding topic in BOL. Nor is there a way to
predict the filename based on the error number. The filenames for Books
Online topics are auto-generated by the authoring system we use. At best
you can know that the topics for system error messages will have a filename
that starts with "tr_reslsyserr_%" , but the numbering sequence used to
create a unique filename (for example, tr_reslsyserr_1_2a0j.htm) is not
predictable.
Gail Erickson [MS]
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rights
"Chris Mohan" <ChrisMohan@.discussions.microsoft.com> wrote in message
news:86009ACC-4B0E-4308-B642-4BCA8D9E12E9@.microsoft.com...
> Hi,
> Is there any relationship between a sql server error number and the naming
> convention used in SqlServer Books Online documentation error
> documentation
> files?
> Example:
> The file name for Error # 207 in books Online ends with "_1_1qyf.htm",
> in the msdn version of books online it ends with "_1_1qyf.asp"
> The file name for error # 208 ends with "_1_1qyg.asp"
> My goal: to programtically generate urls that point to each error's
> documentation in books online (sqlException's "Number" property contains
> the
> error number value, so the idea is to programatically set the helplink
> property to the correct url by evaluating the number value and running it
> through some operation to create the correct url).
> I know the error numbers refer to the error id column value in
> master.dbo.sysmessages -- but i want to be able to derive urls to books
> online from the error number b/c those files have more complete
> information.
> Any suggestions?
Monday, March 26, 2012
Relationship between Error Numbers and books Online URls?
Hi,
Is there any relationship between a sql server error number and the naming
convention used in SqlServer Books Online documentation error documentation
files?
Example:
The file name for Error # 207 in books Online ends with "_1_1qyf.htm",
in the msdn version of books online it ends with "_1_1qyf.asp"
The file name for error # 208 ends with "_1_1qyg.asp"
My goal: to programtically generate urls that point to each error's
documentation in books online (sqlException's "Number" property contains the
error number value, so the idea is to programatically set the helplink
property to the correct url by evaluating the number value and running it
through some operation to create the correct url).
I know the error numbers refer to the error id column value in
master.dbo.sysmessages -- but i want to be able to derive urls to books
online from the error number b/c those files have more complete information.
Any suggestions?> Is there any relationship between a sql server error number and the naming
> convention used in SqlServer Books Online documentation error
> documentation
> files?
> My goal: to programtically generate urls that point to each error's
> documentation in books online (sqlException's "Number" property contains
> the
> error number value, so the idea is to programatically set the helplink
> property to the correct url by evaluating the number value and running it
> through some operation to create the correct url).
Sorry, there is no intentional relationship between an error message number
and the filename of the corresponding topic in BOL. Nor is there a way to
predict the filename based on the error number. The filenames for Books
Online topics are auto-generated by the authoring system we use. At best
you can know that the topics for system error messages will have a filename
that starts with "tr_reslsyserr_%" , but the numbering sequence used to
create a unique filename (for example, tr_reslsyserr_1_2a0j.htm) is not
predictable.
--
Gail Erickson [MS]
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rights
"Chris Mohan" <ChrisMohan@.discussions.microsoft.com> wrote in message
news:86009ACC-4B0E-4308-B642-4BCA8D9E12E9@.microsoft.com...
> Hi,
> Is there any relationship between a sql server error number and the naming
> convention used in SqlServer Books Online documentation error
> documentation
> files?
> Example:
> The file name for Error # 207 in books Online ends with "_1_1qyf.htm",
> in the msdn version of books online it ends with "_1_1qyf.asp"
> The file name for error # 208 ends with "_1_1qyg.asp"
> My goal: to programtically generate urls that point to each error's
> documentation in books online (sqlException's "Number" property contains
> the
> error number value, so the idea is to programatically set the helplink
> property to the correct url by evaluating the number value and running it
> through some operation to create the correct url).
> I know the error numbers refer to the error id column value in
> master.dbo.sysmessages -- but i want to be able to derive urls to books
> online from the error number b/c those files have more complete
> information.
> Any suggestions?
Is there any relationship between a sql server error number and the naming
convention used in SqlServer Books Online documentation error documentation
files?
Example:
The file name for Error # 207 in books Online ends with "_1_1qyf.htm",
in the msdn version of books online it ends with "_1_1qyf.asp"
The file name for error # 208 ends with "_1_1qyg.asp"
My goal: to programtically generate urls that point to each error's
documentation in books online (sqlException's "Number" property contains the
error number value, so the idea is to programatically set the helplink
property to the correct url by evaluating the number value and running it
through some operation to create the correct url).
I know the error numbers refer to the error id column value in
master.dbo.sysmessages -- but i want to be able to derive urls to books
online from the error number b/c those files have more complete information.
Any suggestions?> Is there any relationship between a sql server error number and the naming
> convention used in SqlServer Books Online documentation error
> documentation
> files?
> My goal: to programtically generate urls that point to each error's
> documentation in books online (sqlException's "Number" property contains
> the
> error number value, so the idea is to programatically set the helplink
> property to the correct url by evaluating the number value and running it
> through some operation to create the correct url).
Sorry, there is no intentional relationship between an error message number
and the filename of the corresponding topic in BOL. Nor is there a way to
predict the filename based on the error number. The filenames for Books
Online topics are auto-generated by the authoring system we use. At best
you can know that the topics for system error messages will have a filename
that starts with "tr_reslsyserr_%" , but the numbering sequence used to
create a unique filename (for example, tr_reslsyserr_1_2a0j.htm) is not
predictable.
--
Gail Erickson [MS]
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rights
"Chris Mohan" <ChrisMohan@.discussions.microsoft.com> wrote in message
news:86009ACC-4B0E-4308-B642-4BCA8D9E12E9@.microsoft.com...
> Hi,
> Is there any relationship between a sql server error number and the naming
> convention used in SqlServer Books Online documentation error
> documentation
> files?
> Example:
> The file name for Error # 207 in books Online ends with "_1_1qyf.htm",
> in the msdn version of books online it ends with "_1_1qyf.asp"
> The file name for error # 208 ends with "_1_1qyg.asp"
> My goal: to programtically generate urls that point to each error's
> documentation in books online (sqlException's "Number" property contains
> the
> error number value, so the idea is to programatically set the helplink
> property to the correct url by evaluating the number value and running it
> through some operation to create the correct url).
> I know the error numbers refer to the error id column value in
> master.dbo.sysmessages -- but i want to be able to derive urls to books
> online from the error number b/c those files have more complete
> information.
> Any suggestions?
Relations Error -
Dim verilaDataAdapter1 As SqlCeDataAdapter
Dim verilaDataAdapter2 As SqlCeDataAdapter
Dim iliski As DataRelation
Dim Sorgu1 As String
Dim Sorgu2 As String
Dim A1Dataset As DataSet
Dim parametre1 As SqlCeParameter
Dim parametre2 As SqlCeParameter
Dim ssceconn As New SqlCeConnection("Data Source =\Program Files\AtisoftDA\atisoft.sdf")
ssceconn.Open()
Dim sqlInsertRow As SqlCeCommand = ssceconn.CreateCommand()
Sorgu1 = "SELECT * FROM StokKartTbl WHERE StokGrupKodu like @.StokGrupKodu Order By Stokismi ASC;"
Sorgu2 = "SELECT * FROM SarzKartTbl WHERE SarzID like @.Sarzid"
A1Dataset = New DataSet
verilaDataAdapter1 = New SqlCeDataAdapter(Sorgu1, ssceconn) 'StokkartTbl
parametre1 = New SqlCeParameter("@.StokGrupKodu", SqlDbType.NText, 25)
parametre1.Value = Trim(Mid(CBStGrupAciklama.Text, 1, 6)) + "%"
verilaDataAdapter1.SelectCommand.Parameters.Add(parametre1)
verilaDataAdapter1.Fill(A1Dataset, "StokKartTbl")
verilaDataAdapter2 = New SqlCeDataAdapter(Sorgu2, ssceconn) 'SarzKartTbl
parametre2 = New SqlCeParameter("@.Sarzid", SqlDbType.NText, 50)
parametre2.Value = Trim(Mid(CBSarzID.Text, 1, 25)) + "%"
verilaDataAdapter2.SelectCommand.Parameters.Add(parametre2)
verilaDataAdapter2.Fill(A1Dataset, "SarzKartTbl")
Dim p As DataColumn
Dim c As DataColumn
p = A1Dataset.Tables("StokKartTbl").Columns("StokID")
c = A1Dataset.Tables("SarzKartTbl").Columns("StokID")
iliski = New DataRelation("Elemanlar", p, c)
A1Dataset.Relations.Add(iliski)
DataGridStokKartTbl.DataSource = A1Dataset.Tables("StokKartTbl")
'Error
System.ArgumentException was unhandled
Message="Hata iletisi i?eren iste?e ba?l? bir kaynak derlemesi bulunamad???ndan bir hata iletisi g?rüntülenemiyor"
StackTrace:
System.Data.ConstraintCollection.AddForeignKeyConstraint()
System.Data.ConstraintCollection.Add()
System.Data.ConstraintCollection.Add()
at DataSetRelationCollection.AddCore()
System.Data.DataRelationCollection.Add()
AtisoftDA.siparis.Button2_Click()
System.Windows.Forms.Control.OnClick()
System.Windows.Forms.Button.OnClick()
System.Windows.Forms.ButtonBase.WnProc()
System.Windows.Forms.Control._InternalWnProc()
Microsoft.AGL.Forms.EVL.EnterMainLoop()
System.Windows.Forms.Application.Run()
AtisoftDA.siparis.Main()
Hi AtiSoft,
Looks like the community did not really understand your problem or the post semantics made them to show less interest in this thread. If you are still facing the problem, I would request you to post a new query with a detailed problem description than just the program dump!
Thanks,
SQL Server Mobile/Everywhere Forum Moderator
Friday, March 23, 2012
Relability? [part 2, 0xC0202093 error]
In my previous thread, we established that my system does not have SP1 applied. Apparently packaging of SQL Server SP1 is not so easy and while SQL Engine was updated SSIS is still in RTM.
Anyway, after months(!) of running we hit following:
An error occurred while initializing the flat file parser.
The PrimeOutput method on component "Flat File Source" (27679) returned error code 0xC0202093. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing.
Thread "SourceThread0" has exited with error code 0xC0047038.
Thread "WorkThread0" received a shutdown signal and is terminating. The user requested a shutdown, or an error in another thread is causing the pipeline to shutdown.
Thread "WorkThread0" has exited with error code 0xC0047039.
I could not find anything regarding 0xC0202093, but re-starting SQL & IS services cured the problem. I am putting it here, so others learn from our experience. Probably re-starting IS engine would be enough.
Someone may say that re-starting of the service is a piece of cake. In the developers enviroment - it is. In the enterprise production system, where corporate rules are applied - it is a nightmare: it has to be approved, it has to be documented ("Can you prove that re-starting will cure the problem?") and it has to be done by a DBA - and that together cost real money.
Googling 0xC0202093 comes up with hits, (http://wiki.sqlis.com/default.aspx/SQLISWiki/0xC0202093.html), and the base error message is "An error occurred while initializing the flat file parser." So it relates to the Flat File source you are using, but above that no more infomation is documented, so not entirely helpfull.
Is this a specific file that causes the issue, or perhaps the size of the file? To be honest I would be tempted to open a PSS case, that is just a poor message, and unless there are any other messages from that packag ethat hint at why, it seems like a serious issue. The parser should not just stop working.
|||Is this a specific file that causes the issue, or perhaps the size of the file? To be honest I would be tempted to open a PSS case, that is just a poor message, and unless there are any other messages from that packag ethat hint at why, it seems like a serious issue. The parser should not just stop working.
Thanks. It is not related to the size (the one of the files has 200 2-column rows) and all packages using flat file connection were affected. Unfortunatelly, I cannot reproduce the problem. Another thing was that files were on the server files. The same packages, reading from the local driver were fine. [We use dynamic connections where file location is read from the database]. So it might be that flat file parser had problems with networking - don't know.
sqlWednesday, March 21, 2012
re-install SQL Server 2000 SP3
Hi,
I 've re-installSQL Server 2000 SP3 just to change password
And while installation I got an error that the instillation fails the message as the following:
" setup Failed to configure the server, refer to the server error logs and setup error logs for more information. "
Any idea,
sql
Reinstall ODBC Components
I'm getting the following error on my XP machine:
The ODBC resource DLL c:\windows\system32\odbcint.dll is a different version
than the ODBC setup dll c:\windows\system32\odbccp32.dll reinstall the ODBC
components to ensure proper operation.
I've reinstalled SQL 7.0 several times, how do I reinstall the ODBC
components?
Thank youReinstall MDAC. Reinstalling SQL Server 7 won't update MDAC
as XP is on a higher version. You can also check your
current MDAC installation with component checker
You can find the MDAC downloads and component checker at:
http://msdn.microsoft.com/data/mdac/default.aspx
-Sue
On Wed, 10 Nov 2004 16:24:01 -0800, "Michelle"
<Michelle@.discussions.microsoft.com> wrote:
>I'm getting the following error on my XP machine:
>The ODBC resource DLL c:\windows\system32\odbcint.dll is a different versio
n
>than the ODBC setup dll c:\windows\system32\odbccp32.dll reinstall the ODBC
>components to ensure proper operation.
>I've reinstalled SQL 7.0 several times, how do I reinstall the ODBC
>components?
>Thank you
The ODBC resource DLL c:\windows\system32\odbcint.dll is a different version
than the ODBC setup dll c:\windows\system32\odbccp32.dll reinstall the ODBC
components to ensure proper operation.
I've reinstalled SQL 7.0 several times, how do I reinstall the ODBC
components?
Thank youReinstall MDAC. Reinstalling SQL Server 7 won't update MDAC
as XP is on a higher version. You can also check your
current MDAC installation with component checker
You can find the MDAC downloads and component checker at:
http://msdn.microsoft.com/data/mdac/default.aspx
-Sue
On Wed, 10 Nov 2004 16:24:01 -0800, "Michelle"
<Michelle@.discussions.microsoft.com> wrote:
>I'm getting the following error on my XP machine:
>The ODBC resource DLL c:\windows\system32\odbcint.dll is a different versio
n
>than the ODBC setup dll c:\windows\system32\odbccp32.dll reinstall the ODBC
>components to ensure proper operation.
>I've reinstalled SQL 7.0 several times, how do I reinstall the ODBC
>components?
>Thank you
Reinstall ODBC Components
I'm getting the following error on my XP machine:
The ODBC resource DLL c:\windows\system32\odbcint.dll is a different version
than the ODBC setup dll c:\windows\system32\odbccp32.dll reinstall the ODBC
components to ensure proper operation.
I've reinstalled SQL 7.0 several times, how do I reinstall the ODBC
components?
Thank you
Reinstall MDAC. Reinstalling SQL Server 7 won't update MDAC
as XP is on a higher version. You can also check your
current MDAC installation with component checker
You can find the MDAC downloads and component checker at:
http://msdn.microsoft.com/data/mdac/default.aspx
-Sue
On Wed, 10 Nov 2004 16:24:01 -0800, "Michelle"
<Michelle@.discussions.microsoft.com> wrote:
>I'm getting the following error on my XP machine:
>The ODBC resource DLL c:\windows\system32\odbcint.dll is a different version
>than the ODBC setup dll c:\windows\system32\odbccp32.dll reinstall the ODBC
>components to ensure proper operation.
>I've reinstalled SQL 7.0 several times, how do I reinstall the ODBC
>components?
>Thank you
The ODBC resource DLL c:\windows\system32\odbcint.dll is a different version
than the ODBC setup dll c:\windows\system32\odbccp32.dll reinstall the ODBC
components to ensure proper operation.
I've reinstalled SQL 7.0 several times, how do I reinstall the ODBC
components?
Thank you
Reinstall MDAC. Reinstalling SQL Server 7 won't update MDAC
as XP is on a higher version. You can also check your
current MDAC installation with component checker
You can find the MDAC downloads and component checker at:
http://msdn.microsoft.com/data/mdac/default.aspx
-Sue
On Wed, 10 Nov 2004 16:24:01 -0800, "Michelle"
<Michelle@.discussions.microsoft.com> wrote:
>I'm getting the following error on my XP machine:
>The ODBC resource DLL c:\windows\system32\odbcint.dll is a different version
>than the ODBC setup dll c:\windows\system32\odbccp32.dll reinstall the ODBC
>components to ensure proper operation.
>I've reinstalled SQL 7.0 several times, how do I reinstall the ODBC
>components?
>Thank you
Tuesday, March 20, 2012
Re-initializing an anonymous subscription from the server - error
Hi,
I'm trying to force an anonymous subscription to re-intialize on it's next sync attempt. I can do this from the subscriber no problems, and from the publisher using 'Re-initalize All Subscriptions', but I can't seem to re-intialize only a single subscription from the publisher.
To do this I'm trying to execute sp_reinitmergesubscription using the subscriber details found in the sysmergesubscriptions table. This executes ok and when the subscriber starts to sync it does try to re-initialize starting with generating a new snapshot, but after processing for a while it throws the following error messages:
Error messages:
The merge process could not allocate memory for an operation; your system may be running low on virtual memory. Restart the Merge Agent. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147198720)
Get help: http://help/MSSQL_REPL-2147198720
An error occurred while reading the .bcp data file for the 'CDP_TableDates' article. If the .bcp file is corrupt, you must regenerate the snapshot before initializing the Subscriber. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199428)
Get help: http://help/MSSQL_REPL-2147199428
The merge process was unable to deliver the snapshot to the Subscriber. If using Web synchronization, the merge process may have been unable to create or write to the message file. When troubleshooting, restart the synchronization with verbose history logging and specify an output file to which to write. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201001)
There doesn't appear to be any shortage of memory on the server. There is no problem regenerating the snapshot from the publisher, and there's no problem with syncing through the web using delta syncs or re-initializing from the subscriber, so I can't see any obvious cause from those error messages.
I'm using SQL Server 2005 SP2 on the publisher, and SQL ServerCE 3.1 on the subscriber.
Any ideas or alternatives?
Cheers
With an anonymous subscription the publisher is unable to connect to the subsciber so I would guess that actions like forcing a re-init cannot be done from the publisher.
Your root message is saying that the process could not deliver the snapshot to the subscriber. It is trying to connect to the subscriber but cannot as it is anonymous.
Martin
|||Thanks for the response.I thought that SQL Server 2005 was supposed to remove a lot of the limitations of anonymous subscribers. In this case, as the subscriber can receive the snapshot when the re-init is initiated on the subscriber, I don't understand why it can't receive it when intiated on the publisher. The client obviously recognises that a re-init is required, surely from then the process should be the same?
Any other ideas?
|||
Has anybody successfully forced an anonymous subscriber to re-initiliaze from the publisher? I would have thought this was a fairly common requirement.
|||Are you using push or pull subscription? If you are using push, can you try to use pull instead and see if that would work for you?
Regards,
Gary
I'm using a pull subscription. As far as I know, SQL Server CE only supports anonymous pull subscriptions.
I've since been advised from a support engineer (via MSC) that SQL Server 2005 can't re-initialise anonymous subscribers from the publisher, only from the subscriber. I can't see why this limitation would be in place, but it is consistent with the errors I'm getting.
The workaround will be to build into the application a pre-sync check which connects to the publisher and checks a re-init flag, then re-inits from the subscriber based on that flag.
If anyone else can suggest an alterantive (or challenge the assertion that anonymous subscriptions can't be re-init from the publisher) I'm keen to hear it.
Thanks
|||Steve, you should be able to reinitialize your mobile subscriber from the publisher.
exec pubdb..sp_reinitmergesubscription '<PublicationName>', @.subscriber='mysubscriber - aaaaaaaaaaaa', @.subscriber_db='D:\myPathToMobileDatabase.sdf'
I got the subscriber and subscriber_db from the publisher server's sysmergesubscriptions.
I executed the above at the publisher and the subscriber upon next sync was able to reinitialize.
Let me know if you are not seeing this and I would be interested to find out what issue you are encountering.
Note that I tried this on a desktop installation of mobile.
|||I am using the same process. I grabbed the details out of the sysmergesubscriptions table and then executed the sp_reinitmergesubscription procedure. When the subscriber starts to sync, it recognises that a re-init is necessary and begins that process. If an up-to-date snapshot is not available it generates one otherwise it immediatly starts to transfer the data. At this point it stops with the following error messages:
The merge process could not allocate memory for an operation; your system may be running low on virtual memory. Restart the Merge Agent. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147198720)
Get help: http://help/MSSQL_REPL-2147198720
An error occurred while reading the .bcp data file for the 'CDP_TableDates' article. If the .bcp file is corrupt, you must regenerate the snapshot before initializing the Subscriber. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199428)
Get help: http://help/MSSQL_REPL-2147199428
The merge process was unable to deliver the snapshot to the Subscriber. If using Web synchronization, the merge process may have been unable to create or write to the message file. When troubleshooting, restart the synchronization with verbose history logging and specify an output file to which to write. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201001)
The set up I'm using is SQL Server 2005 on Windows Server 2003 and SQL CE 3.1 on Windows XP (ie not mobile). The desktop is our target setup (although most clients are on Windows 2000).
I've also tried doing this in different combinations ie with both the SQL CE and the SQL Server 2005 databases on the Windows 2003 server, and with both running on the win xp desktop, but all get the same errors. In none of these situations is re-initialising from the subscriber an issue.
Any ideas on how to progress this?
|||Further testing has uncovered an interesting way to get this work. For some reason if I validate all subscribers after using sp_reinitmergesubscription to re-intialise a single subscriber, the subscriber syncs and reinitialises fine. This is obviously not ideal, as forcing all subscribers to validate creates unnecassary overhead, but the result is that I don't get errors from the subscriber re-initialisation.
So my current steps are:
exec sp_reinitmergesubscription
kick off the dynamic snapshot job for the subscriber
exec sp_validatemergepublication
Re-initializing an anonymous subscription from the server - error
Hi,
I'm trying to force an anonymous subscription to re-intialize on it's next sync attempt. I can do this from the subscriber no problems, and from the publisher using 'Re-initalize All Subscriptions', but I can't seem to re-intialize only a single subscription from the publisher.
To do this I'm trying to execute sp_reinitmergesubscription using the subscriber details found in the sysmergesubscriptions table. This executes ok and when the subscriber starts to sync it does try to re-initialize starting with generating a new snapshot, but after processing for a while it throws the following error messages:
Error messages:
The merge process could not allocate memory for an operation; your system may be running low on virtual memory. Restart the Merge Agent. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147198720)
Get help: http://help/MSSQL_REPL-2147198720
An error occurred while reading the .bcp data file for the 'CDP_TableDates' article. If the .bcp file is corrupt, you must regenerate the snapshot before initializing the Subscriber. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199428)
Get help: http://help/MSSQL_REPL-2147199428
The merge process was unable to deliver the snapshot to the Subscriber. If using Web synchronization, the merge process may have been unable to create or write to the message file. When troubleshooting, restart the synchronization with verbose history logging and specify an output file to which to write. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201001)
There doesn't appear to be any shortage of memory on the server. There is no problem regenerating the snapshot from the publisher, and there's no problem with syncing through the web using delta syncs or re-initializing from the subscriber, so I can't see any obvious cause from those error messages.
I'm using SQL Server 2005 SP2 on the publisher, and SQL ServerCE 3.1 on the subscriber.
Any ideas or alternatives?
Cheers
With an anonymous subscription the publisher is unable to connect to the subsciber so I would guess that actions like forcing a re-init cannot be done from the publisher.
Your root message is saying that the process could not deliver the snapshot to the subscriber. It is trying to connect to the subscriber but cannot as it is anonymous.
Martin
|||Thanks for the response.I thought that SQL Server 2005 was supposed to remove a lot of the limitations of anonymous subscribers. In this case, as the subscriber can receive the snapshot when the re-init is initiated on the subscriber, I don't understand why it can't receive it when intiated on the publisher. The client obviously recognises that a re-init is required, surely from then the process should be the same?
Any other ideas?
|||
Has anybody successfully forced an anonymous subscriber to re-initiliaze from the publisher? I would have thought this was a fairly common requirement.
|||Are you using push or pull subscription? If you are using push, can you try to use pull instead and see if that would work for you?
Regards,
Gary
I'm using a pull subscription. As far as I know, SQL Server CE only supports anonymous pull subscriptions.
I've since been advised from a support engineer (via MSC) that SQL Server 2005 can't re-initialise anonymous subscribers from the publisher, only from the subscriber. I can't see why this limitation would be in place, but it is consistent with the errors I'm getting.
The workaround will be to build into the application a pre-sync check which connects to the publisher and checks a re-init flag, then re-inits from the subscriber based on that flag.
If anyone else can suggest an alterantive (or challenge the assertion that anonymous subscriptions can't be re-init from the publisher) I'm keen to hear it.
Thanks
|||Steve, you should be able to reinitialize your mobile subscriber from the publisher.
exec pubdb..sp_reinitmergesubscription '<PublicationName>', @.subscriber='mysubscriber - aaaaaaaaaaaa', @.subscriber_db='D:\myPathToMobileDatabase.sdf'
I got the subscriber and subscriber_db from the publisher server's sysmergesubscriptions.
I executed the above at the publisher and the subscriber upon next sync was able to reinitialize.
Let me know if you are not seeing this and I would be interested to find out what issue you are encountering.
Note that I tried this on a desktop installation of mobile.
|||I am using the same process. I grabbed the details out of the sysmergesubscriptions table and then executed the sp_reinitmergesubscription procedure. When the subscriber starts to sync, it recognises that a re-init is necessary and begins that process. If an up-to-date snapshot is not available it generates one otherwise it immediatly starts to transfer the data. At this point it stops with the following error messages:
The merge process could not allocate memory for an operation; your system may be running low on virtual memory. Restart the Merge Agent. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147198720)
Get help: http://help/MSSQL_REPL-2147198720
An error occurred while reading the .bcp data file for the 'CDP_TableDates' article. If the .bcp file is corrupt, you must regenerate the snapshot before initializing the Subscriber. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199428)
Get help: http://help/MSSQL_REPL-2147199428
The merge process was unable to deliver the snapshot to the Subscriber. If using Web synchronization, the merge process may have been unable to create or write to the message file. When troubleshooting, restart the synchronization with verbose history logging and specify an output file to which to write. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201001)
The set up I'm using is SQL Server 2005 on Windows Server 2003 and SQL CE 3.1 on Windows XP (ie not mobile). The desktop is our target setup (although most clients are on Windows 2000).
I've also tried doing this in different combinations ie with both the SQL CE and the SQL Server 2005 databases on the Windows 2003 server, and with both running on the win xp desktop, but all get the same errors. In none of these situations is re-initialising from the subscriber an issue.
Any ideas on how to progress this?
|||Further testing has uncovered an interesting way to get this work. For some reason if I validate all subscribers after using sp_reinitmergesubscription to re-intialise a single subscriber, the subscriber syncs and reinitialises fine. This is obviously not ideal, as forcing all subscribers to validate creates unnecassary overhead, but the result is that I don't get errors from the subscriber re-initialisation.
So my current steps are:
exec sp_reinitmergesubscription
kick off the dynamic snapshot job for the subscriber
exec sp_validatemergepublication
Re-initializing an anonymous subscription from the server - error
Hi,
I'm trying to force an anonymous subscription to re-intialize on it's next sync attempt. I can do this from the subscriber no problems, and from the publisher using 'Re-initalize All Subscriptions', but I can't seem to re-intialize only a single subscription from the publisher.
To do this I'm trying to execute sp_reinitmergesubscription using the subscriber details found in the sysmergesubscriptions table. This executes ok and when the subscriber starts to sync it does try to re-initialize starting with generating a new snapshot, but after processing for a while it throws the following error messages:
Error messages:
The merge process could not allocate memory for an operation; your system may be running low on virtual memory. Restart the Merge Agent. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147198720)
Get help: http://help/MSSQL_REPL-2147198720
An error occurred while reading the .bcp data file for the 'CDP_TableDates' article. If the .bcp file is corrupt, you must regenerate the snapshot before initializing the Subscriber. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199428)
Get help: http://help/MSSQL_REPL-2147199428
The merge process was unable to deliver the snapshot to the Subscriber. If using Web synchronization, the merge process may have been unable to create or write to the message file. When troubleshooting, restart the synchronization with verbose history logging and specify an output file to which to write. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201001)
There doesn't appear to be any shortage of memory on the server. There is no problem regenerating the snapshot from the publisher, and there's no problem with syncing through the web using delta syncs or re-initializing from the subscriber, so I can't see any obvious cause from those error messages.
I'm using SQL Server 2005 SP2 on the publisher, and SQL ServerCE 3.1 on the subscriber.
Any ideas or alternatives?
Cheers
With an anonymous subscription the publisher is unable to connect to the subsciber so I would guess that actions like forcing a re-init cannot be done from the publisher.
Your root message is saying that the process could not deliver the snapshot to the subscriber. It is trying to connect to the subscriber but cannot as it is anonymous.
Martin
|||Thanks for the response.I thought that SQL Server 2005 was supposed to remove a lot of the limitations of anonymous subscribers. In this case, as the subscriber can receive the snapshot when the re-init is initiated on the subscriber, I don't understand why it can't receive it when intiated on the publisher. The client obviously recognises that a re-init is required, surely from then the process should be the same?
Any other ideas?
|||
Has anybody successfully forced an anonymous subscriber to re-initiliaze from the publisher? I would have thought this was a fairly common requirement.
|||Are you using push or pull subscription? If you are using push, can you try to use pull instead and see if that would work for you?
Regards,
Gary
I'm using a pull subscription. As far as I know, SQL Server CE only supports anonymous pull subscriptions.
I've since been advised from a support engineer (via MSC) that SQL Server 2005 can't re-initialise anonymous subscribers from the publisher, only from the subscriber. I can't see why this limitation would be in place, but it is consistent with the errors I'm getting.
The workaround will be to build into the application a pre-sync check which connects to the publisher and checks a re-init flag, then re-inits from the subscriber based on that flag.
If anyone else can suggest an alterantive (or challenge the assertion that anonymous subscriptions can't be re-init from the publisher) I'm keen to hear it.
Thanks
|||Steve, you should be able to reinitialize your mobile subscriber from the publisher.
exec pubdb..sp_reinitmergesubscription '<PublicationName>', @.subscriber='mysubscriber - aaaaaaaaaaaa', @.subscriber_db='D:\myPathToMobileDatabase.sdf'
I got the subscriber and subscriber_db from the publisher server's sysmergesubscriptions.
I executed the above at the publisher and the subscriber upon next sync was able to reinitialize.
Let me know if you are not seeing this and I would be interested to find out what issue you are encountering.
Note that I tried this on a desktop installation of mobile.
|||I am using the same process. I grabbed the details out of the sysmergesubscriptions table and then executed the sp_reinitmergesubscription procedure. When the subscriber starts to sync, it recognises that a re-init is necessary and begins that process. If an up-to-date snapshot is not available it generates one otherwise it immediatly starts to transfer the data. At this point it stops with the following error messages:
The merge process could not allocate memory for an operation; your system may be running low on virtual memory. Restart the Merge Agent. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147198720)
Get help: http://help/MSSQL_REPL-2147198720
An error occurred while reading the .bcp data file for the 'CDP_TableDates' article. If the .bcp file is corrupt, you must regenerate the snapshot before initializing the Subscriber. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199428)
Get help: http://help/MSSQL_REPL-2147199428
The merge process was unable to deliver the snapshot to the Subscriber. If using Web synchronization, the merge process may have been unable to create or write to the message file. When troubleshooting, restart the synchronization with verbose history logging and specify an output file to which to write. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201001)
The set up I'm using is SQL Server 2005 on Windows Server 2003 and SQL CE 3.1 on Windows XP (ie not mobile). The desktop is our target setup (although most clients are on Windows 2000).
I've also tried doing this in different combinations ie with both the SQL CE and the SQL Server 2005 databases on the Windows 2003 server, and with both running on the win xp desktop, but all get the same errors. In none of these situations is re-initialising from the subscriber an issue.
Any ideas on how to progress this?
|||Further testing has uncovered an interesting way to get this work. For some reason if I validate all subscribers after using sp_reinitmergesubscription to re-intialise a single subscriber, the subscriber syncs and reinitialises fine. This is obviously not ideal, as forcing all subscribers to validate creates unnecassary overhead, but the result is that I don't get errors from the subscriber re-initialisation.
So my current steps are:
exec sp_reinitmergesubscription
kick off the dynamic snapshot job for the subscriber
exec sp_validatemergepublication
Re-initializing an anonymous subscription from the server - error
Hi,
I'm trying to force an anonymous subscription to re-intialize on it's next sync attempt. I can do this from the subscriber no problems, and from the publisher using 'Re-initalize All Subscriptions', but I can't seem to re-intialize only a single subscription from the publisher.
To do this I'm trying to execute sp_reinitmergesubscription using the subscriber details found in the sysmergesubscriptions table. This executes ok and when the subscriber starts to sync it does try to re-initialize starting with generating a new snapshot, but after processing for a while it throws the following error messages:
Error messages:
The merge process could not allocate memory for an operation; your system may be running low on virtual memory. Restart the Merge Agent. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147198720)
Get help: http://help/MSSQL_REPL-2147198720
An error occurred while reading the .bcp data file for the 'CDP_TableDates' article. If the .bcp file is corrupt, you must regenerate the snapshot before initializing the Subscriber. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199428)
Get help: http://help/MSSQL_REPL-2147199428
The merge process was unable to deliver the snapshot to the Subscriber. If using Web synchronization, the merge process may have been unable to create or write to the message file. When troubleshooting, restart the synchronization with verbose history logging and specify an output file to which to write. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201001)
There doesn't appear to be any shortage of memory on the server. There is no problem regenerating the snapshot from the publisher, and there's no problem with syncing through the web using delta syncs or re-initializing from the subscriber, so I can't see any obvious cause from those error messages.
I'm using SQL Server 2005 SP2 on the publisher, and SQL ServerCE 3.1 on the subscriber.
Any ideas or alternatives?
Cheers
With an anonymous subscription the publisher is unable to connect to the subsciber so I would guess that actions like forcing a re-init cannot be done from the publisher.
Your root message is saying that the process could not deliver the snapshot to the subscriber. It is trying to connect to the subscriber but cannot as it is anonymous.
Martin
|||Thanks for the response.I thought that SQL Server 2005 was supposed to remove a lot of the limitations of anonymous subscribers. In this case, as the subscriber can receive the snapshot when the re-init is initiated on the subscriber, I don't understand why it can't receive it when intiated on the publisher. The client obviously recognises that a re-init is required, surely from then the process should be the same?
Any other ideas?
|||
Has anybody successfully forced an anonymous subscriber to re-initiliaze from the publisher? I would have thought this was a fairly common requirement.
|||Are you using push or pull subscription? If you are using push, can you try to use pull instead and see if that would work for you?
Regards,
Gary
I'm using a pull subscription. As far as I know, SQL Server CE only supports anonymous pull subscriptions.
I've since been advised from a support engineer (via MSC) that SQL Server 2005 can't re-initialise anonymous subscribers from the publisher, only from the subscriber. I can't see why this limitation would be in place, but it is consistent with the errors I'm getting.
The workaround will be to build into the application a pre-sync check which connects to the publisher and checks a re-init flag, then re-inits from the subscriber based on that flag.
If anyone else can suggest an alterantive (or challenge the assertion that anonymous subscriptions can't be re-init from the publisher) I'm keen to hear it.
Thanks
|||Steve, you should be able to reinitialize your mobile subscriber from the publisher.
exec pubdb..sp_reinitmergesubscription '<PublicationName>', @.subscriber='mysubscriber - aaaaaaaaaaaa', @.subscriber_db='D:\myPathToMobileDatabase.sdf'
I got the subscriber and subscriber_db from the publisher server's sysmergesubscriptions.
I executed the above at the publisher and the subscriber upon next sync was able to reinitialize.
Let me know if you are not seeing this and I would be interested to find out what issue you are encountering.
Note that I tried this on a desktop installation of mobile.
|||I am using the same process. I grabbed the details out of the sysmergesubscriptions table and then executed the sp_reinitmergesubscription procedure. When the subscriber starts to sync, it recognises that a re-init is necessary and begins that process. If an up-to-date snapshot is not available it generates one otherwise it immediatly starts to transfer the data. At this point it stops with the following error messages:
The merge process could not allocate memory for an operation; your system may be running low on virtual memory. Restart the Merge Agent. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147198720)
Get help: http://help/MSSQL_REPL-2147198720
An error occurred while reading the .bcp data file for the 'CDP_TableDates' article. If the .bcp file is corrupt, you must regenerate the snapshot before initializing the Subscriber. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199428)
Get help: http://help/MSSQL_REPL-2147199428
The merge process was unable to deliver the snapshot to the Subscriber. If using Web synchronization, the merge process may have been unable to create or write to the message file. When troubleshooting, restart the synchronization with verbose history logging and specify an output file to which to write. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201001)
The set up I'm using is SQL Server 2005 on Windows Server 2003 and SQL CE 3.1 on Windows XP (ie not mobile). The desktop is our target setup (although most clients are on Windows 2000).
I've also tried doing this in different combinations ie with both the SQL CE and the SQL Server 2005 databases on the Windows 2003 server, and with both running on the win xp desktop, but all get the same errors. In none of these situations is re-initialising from the subscriber an issue.
Any ideas on how to progress this?
|||Further testing has uncovered an interesting way to get this work. For some reason if I validate all subscribers after using sp_reinitmergesubscription to re-intialise a single subscriber, the subscriber syncs and reinitialises fine. This is obviously not ideal, as forcing all subscribers to validate creates unnecassary overhead, but the result is that I don't get errors from the subscriber re-initialisation.
So my current steps are:
exec sp_reinitmergesubscription
kick off the dynamic snapshot job for the subscriber
exec sp_validatemergepublication
Re-initializing an anonymous subscription from the server - error
Hi,
I'm trying to force an anonymous subscription to re-intialize on it's next sync attempt. I can do this from the subscriber no problems, and from the publisher using 'Re-initalize All Subscriptions', but I can't seem to re-intialize only a single subscription from the publisher.
To do this I'm trying to execute sp_reinitmergesubscription using the subscriber details found in the sysmergesubscriptions table. This executes ok and when the subscriber starts to sync it does try to re-initialize starting with generating a new snapshot, but after processing for a while it throws the following error messages:
Error messages:
The merge process could not allocate memory for an operation; your system may be running low on virtual memory. Restart the Merge Agent. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147198720)
Get help: http://help/MSSQL_REPL-2147198720
An error occurred while reading the .bcp data file for the 'CDP_TableDates' article. If the .bcp file is corrupt, you must regenerate the snapshot before initializing the Subscriber. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199428)
Get help: http://help/MSSQL_REPL-2147199428
The merge process was unable to deliver the snapshot to the Subscriber. If using Web synchronization, the merge process may have been unable to create or write to the message file. When troubleshooting, restart the synchronization with verbose history logging and specify an output file to which to write. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201001)
There doesn't appear to be any shortage of memory on the server. There is no problem regenerating the snapshot from the publisher, and there's no problem with syncing through the web using delta syncs or re-initializing from the subscriber, so I can't see any obvious cause from those error messages.
I'm using SQL Server 2005 SP2 on the publisher, and SQL ServerCE 3.1 on the subscriber.
Any ideas or alternatives?
Cheers
With an anonymous subscription the publisher is unable to connect to the subsciber so I would guess that actions like forcing a re-init cannot be done from the publisher.
Your root message is saying that the process could not deliver the snapshot to the subscriber. It is trying to connect to the subscriber but cannot as it is anonymous.
Martin
|||Thanks for the response.I thought that SQL Server 2005 was supposed to remove a lot of the limitations of anonymous subscribers. In this case, as the subscriber can receive the snapshot when the re-init is initiated on the subscriber, I don't understand why it can't receive it when intiated on the publisher. The client obviously recognises that a re-init is required, surely from then the process should be the same?
Any other ideas?
|||
Has anybody successfully forced an anonymous subscriber to re-initiliaze from the publisher? I would have thought this was a fairly common requirement.
|||Are you using push or pull subscription? If you are using push, can you try to use pull instead and see if that would work for you?
Regards,
Gary
I'm using a pull subscription. As far as I know, SQL Server CE only supports anonymous pull subscriptions.
I've since been advised from a support engineer (via MSC) that SQL Server 2005 can't re-initialise anonymous subscribers from the publisher, only from the subscriber. I can't see why this limitation would be in place, but it is consistent with the errors I'm getting.
The workaround will be to build into the application a pre-sync check which connects to the publisher and checks a re-init flag, then re-inits from the subscriber based on that flag.
If anyone else can suggest an alterantive (or challenge the assertion that anonymous subscriptions can't be re-init from the publisher) I'm keen to hear it.
Thanks
|||Steve, you should be able to reinitialize your mobile subscriber from the publisher.
exec pubdb..sp_reinitmergesubscription '<PublicationName>', @.subscriber='mysubscriber - aaaaaaaaaaaa', @.subscriber_db='D:\myPathToMobileDatabase.sdf'
I got the subscriber and subscriber_db from the publisher server's sysmergesubscriptions.
I executed the above at the publisher and the subscriber upon next sync was able to reinitialize.
Let me know if you are not seeing this and I would be interested to find out what issue you are encountering.
Note that I tried this on a desktop installation of mobile.
|||I am using the same process. I grabbed the details out of the sysmergesubscriptions table and then executed the sp_reinitmergesubscription procedure. When the subscriber starts to sync, it recognises that a re-init is necessary and begins that process. If an up-to-date snapshot is not available it generates one otherwise it immediatly starts to transfer the data. At this point it stops with the following error messages:
The merge process could not allocate memory for an operation; your system may be running low on virtual memory. Restart the Merge Agent. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147198720)
Get help: http://help/MSSQL_REPL-2147198720
An error occurred while reading the .bcp data file for the 'CDP_TableDates' article. If the .bcp file is corrupt, you must regenerate the snapshot before initializing the Subscriber. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199428)
Get help: http://help/MSSQL_REPL-2147199428
The merge process was unable to deliver the snapshot to the Subscriber. If using Web synchronization, the merge process may have been unable to create or write to the message file. When troubleshooting, restart the synchronization with verbose history logging and specify an output file to which to write. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201001)
The set up I'm using is SQL Server 2005 on Windows Server 2003 and SQL CE 3.1 on Windows XP (ie not mobile). The desktop is our target setup (although most clients are on Windows 2000).
I've also tried doing this in different combinations ie with both the SQL CE and the SQL Server 2005 databases on the Windows 2003 server, and with both running on the win xp desktop, but all get the same errors. In none of these situations is re-initialising from the subscriber an issue.
Any ideas on how to progress this?
|||Further testing has uncovered an interesting way to get this work. For some reason if I validate all subscribers after using sp_reinitmergesubscription to re-intialise a single subscriber, the subscriber syncs and reinitialises fine. This is obviously not ideal, as forcing all subscribers to validate creates unnecassary overhead, but the result is that I don't get errors from the subscriber re-initialisation.
So my current steps are:
exec sp_reinitmergesubscription
kick off the dynamic snapshot job for the subscriber
exec sp_validatemergepublication
Re-initializing an anonymous subscription from the server - error
Hi,
I'm trying to force an anonymous subscription to re-intialize on it's next sync attempt. I can do this from the subscriber no problems, and from the publisher using 'Re-initalize All Subscriptions', but I can't seem to re-intialize only a single subscription from the publisher.
To do this I'm trying to execute sp_reinitmergesubscription using the subscriber details found in the sysmergesubscriptions table. This executes ok and when the subscriber starts to sync it does try to re-initialize starting with generating a new snapshot, but after processing for a while it throws the following error messages:
Error messages:
The merge process could not allocate memory for an operation; your system may be running low on virtual memory. Restart the Merge Agent. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147198720)
Get help: http://help/MSSQL_REPL-2147198720
An error occurred while reading the .bcp data file for the 'CDP_TableDates' article. If the .bcp file is corrupt, you must regenerate the snapshot before initializing the Subscriber. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199428)
Get help: http://help/MSSQL_REPL-2147199428
The merge process was unable to deliver the snapshot to the Subscriber. If using Web synchronization, the merge process may have been unable to create or write to the message file. When troubleshooting, restart the synchronization with verbose history logging and specify an output file to which to write. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201001)
There doesn't appear to be any shortage of memory on the server. There is no problem regenerating the snapshot from the publisher, and there's no problem with syncing through the web using delta syncs or re-initializing from the subscriber, so I can't see any obvious cause from those error messages.
I'm using SQL Server 2005 SP2 on the publisher, and SQL ServerCE 3.1 on the subscriber.
Any ideas or alternatives?
Cheers
With an anonymous subscription the publisher is unable to connect to the subsciber so I would guess that actions like forcing a re-init cannot be done from the publisher.
Your root message is saying that the process could not deliver the snapshot to the subscriber. It is trying to connect to the subscriber but cannot as it is anonymous.
Martin
|||Thanks for the response.I thought that SQL Server 2005 was supposed to remove a lot of the limitations of anonymous subscribers. In this case, as the subscriber can receive the snapshot when the re-init is initiated on the subscriber, I don't understand why it can't receive it when intiated on the publisher. The client obviously recognises that a re-init is required, surely from then the process should be the same?
Any other ideas?
|||
Has anybody successfully forced an anonymous subscriber to re-initiliaze from the publisher? I would have thought this was a fairly common requirement.
|||Are you using push or pull subscription? If you are using push, can you try to use pull instead and see if that would work for you?
Regards,
Gary
I'm using a pull subscription. As far as I know, SQL Server CE only supports anonymous pull subscriptions.
I've since been advised from a support engineer (via MSC) that SQL Server 2005 can't re-initialise anonymous subscribers from the publisher, only from the subscriber. I can't see why this limitation would be in place, but it is consistent with the errors I'm getting.
The workaround will be to build into the application a pre-sync check which connects to the publisher and checks a re-init flag, then re-inits from the subscriber based on that flag.
If anyone else can suggest an alterantive (or challenge the assertion that anonymous subscriptions can't be re-init from the publisher) I'm keen to hear it.
Thanks
|||Steve, you should be able to reinitialize your mobile subscriber from the publisher.
exec pubdb..sp_reinitmergesubscription '<PublicationName>', @.subscriber='mysubscriber - aaaaaaaaaaaa', @.subscriber_db='D:\myPathToMobileDatabase.sdf'
I got the subscriber and subscriber_db from the publisher server's sysmergesubscriptions.
I executed the above at the publisher and the subscriber upon next sync was able to reinitialize.
Let me know if you are not seeing this and I would be interested to find out what issue you are encountering.
Note that I tried this on a desktop installation of mobile.
|||I am using the same process. I grabbed the details out of the sysmergesubscriptions table and then executed the sp_reinitmergesubscription procedure. When the subscriber starts to sync, it recognises that a re-init is necessary and begins that process. If an up-to-date snapshot is not available it generates one otherwise it immediatly starts to transfer the data. At this point it stops with the following error messages:
The merge process could not allocate memory for an operation; your system may be running low on virtual memory. Restart the Merge Agent. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147198720)
Get help: http://help/MSSQL_REPL-2147198720
An error occurred while reading the .bcp data file for the 'CDP_TableDates' article. If the .bcp file is corrupt, you must regenerate the snapshot before initializing the Subscriber. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199428)
Get help: http://help/MSSQL_REPL-2147199428
The merge process was unable to deliver the snapshot to the Subscriber. If using Web synchronization, the merge process may have been unable to create or write to the message file. When troubleshooting, restart the synchronization with verbose history logging and specify an output file to which to write. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201001)
The set up I'm using is SQL Server 2005 on Windows Server 2003 and SQL CE 3.1 on Windows XP (ie not mobile). The desktop is our target setup (although most clients are on Windows 2000).
I've also tried doing this in different combinations ie with both the SQL CE and the SQL Server 2005 databases on the Windows 2003 server, and with both running on the win xp desktop, but all get the same errors. In none of these situations is re-initialising from the subscriber an issue.
Any ideas on how to progress this?
|||Further testing has uncovered an interesting way to get this work. For some reason if I validate all subscribers after using sp_reinitmergesubscription to re-intialise a single subscriber, the subscriber syncs and reinitialises fine. This is obviously not ideal, as forcing all subscribers to validate creates unnecassary overhead, but the result is that I don't get errors from the subscriber re-initialisation.
So my current steps are:
exec sp_reinitmergesubscription
kick off the dynamic snapshot job for the subscriber
exec sp_validatemergepublication
Re-initializing an anonymous subscription from the server - error
Hi,
I'm trying to force an anonymous subscription to re-intialize on it's next sync attempt. I can do this from the subscriber no problems, and from the publisher using 'Re-initalize All Subscriptions', but I can't seem to re-intialize only a single subscription from the publisher.
To do this I'm trying to execute sp_reinitmergesubscription using the subscriber details found in the sysmergesubscriptions table. This executes ok and when the subscriber starts to sync it does try to re-initialize starting with generating a new snapshot, but after processing for a while it throws the following error messages:
Error messages:
The merge process could not allocate memory for an operation; your system may be running low on virtual memory. Restart the Merge Agent. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147198720)
Get help: http://help/MSSQL_REPL-2147198720
An error occurred while reading the .bcp data file for the 'CDP_TableDates' article. If the .bcp file is corrupt, you must regenerate the snapshot before initializing the Subscriber. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199428)
Get help: http://help/MSSQL_REPL-2147199428
The merge process was unable to deliver the snapshot to the Subscriber. If using Web synchronization, the merge process may have been unable to create or write to the message file. When troubleshooting, restart the synchronization with verbose history logging and specify an output file to which to write. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201001)
There doesn't appear to be any shortage of memory on the server. There is no problem regenerating the snapshot from the publisher, and there's no problem with syncing through the web using delta syncs or re-initializing from the subscriber, so I can't see any obvious cause from those error messages.
I'm using SQL Server 2005 SP2 on the publisher, and SQL ServerCE 3.1 on the subscriber.
Any ideas or alternatives?
Cheers
With an anonymous subscription the publisher is unable to connect to the subsciber so I would guess that actions like forcing a re-init cannot be done from the publisher.
Your root message is saying that the process could not deliver the snapshot to the subscriber. It is trying to connect to the subscriber but cannot as it is anonymous.
Martin
|||Thanks for the response.I thought that SQL Server 2005 was supposed to remove a lot of the limitations of anonymous subscribers. In this case, as the subscriber can receive the snapshot when the re-init is initiated on the subscriber, I don't understand why it can't receive it when intiated on the publisher. The client obviously recognises that a re-init is required, surely from then the process should be the same?
Any other ideas?
|||
Has anybody successfully forced an anonymous subscriber to re-initiliaze from the publisher? I would have thought this was a fairly common requirement.
|||Are you using push or pull subscription? If you are using push, can you try to use pull instead and see if that would work for you?
Regards,
Gary
I'm using a pull subscription. As far as I know, SQL Server CE only supports anonymous pull subscriptions.
I've since been advised from a support engineer (via MSC) that SQL Server 2005 can't re-initialise anonymous subscribers from the publisher, only from the subscriber. I can't see why this limitation would be in place, but it is consistent with the errors I'm getting.
The workaround will be to build into the application a pre-sync check which connects to the publisher and checks a re-init flag, then re-inits from the subscriber based on that flag.
If anyone else can suggest an alterantive (or challenge the assertion that anonymous subscriptions can't be re-init from the publisher) I'm keen to hear it.
Thanks
|||Steve, you should be able to reinitialize your mobile subscriber from the publisher.
exec pubdb..sp_reinitmergesubscription '<PublicationName>', @.subscriber='mysubscriber - aaaaaaaaaaaa', @.subscriber_db='D:\myPathToMobileDatabase.sdf'
I got the subscriber and subscriber_db from the publisher server's sysmergesubscriptions.
I executed the above at the publisher and the subscriber upon next sync was able to reinitialize.
Let me know if you are not seeing this and I would be interested to find out what issue you are encountering.
Note that I tried this on a desktop installation of mobile.
|||I am using the same process. I grabbed the details out of the sysmergesubscriptions table and then executed the sp_reinitmergesubscription procedure. When the subscriber starts to sync, it recognises that a re-init is necessary and begins that process. If an up-to-date snapshot is not available it generates one otherwise it immediatly starts to transfer the data. At this point it stops with the following error messages:
The merge process could not allocate memory for an operation; your system may be running low on virtual memory. Restart the Merge Agent. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147198720)
Get help: http://help/MSSQL_REPL-2147198720
An error occurred while reading the .bcp data file for the 'CDP_TableDates' article. If the .bcp file is corrupt, you must regenerate the snapshot before initializing the Subscriber. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199428)
Get help: http://help/MSSQL_REPL-2147199428
The merge process was unable to deliver the snapshot to the Subscriber. If using Web synchronization, the merge process may have been unable to create or write to the message file. When troubleshooting, restart the synchronization with verbose history logging and specify an output file to which to write. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201001)
The set up I'm using is SQL Server 2005 on Windows Server 2003 and SQL CE 3.1 on Windows XP (ie not mobile). The desktop is our target setup (although most clients are on Windows 2000).
I've also tried doing this in different combinations ie with both the SQL CE and the SQL Server 2005 databases on the Windows 2003 server, and with both running on the win xp desktop, but all get the same errors. In none of these situations is re-initialising from the subscriber an issue.
Any ideas on how to progress this?
|||Further testing has uncovered an interesting way to get this work. For some reason if I validate all subscribers after using sp_reinitmergesubscription to re-intialise a single subscriber, the subscriber syncs and reinitialises fine. This is obviously not ideal, as forcing all subscribers to validate creates unnecassary overhead, but the result is that I don't get errors from the subscriber re-initialisation.
So my current steps are:
exec sp_reinitmergesubscription
kick off the dynamic snapshot job for the subscriber
exec sp_validatemergepublication
reinitialized subscription - more info
Running - Win 2K / SQL 2K
I am constantly, once a week or so,getting an error on a
transactional publication that I have...
The subscription(s) have been marked inactive and must be
reinitialized. NoSync subscriptions will need to be
dropped and recreated.
This publication is set up to be continious and is
checked daily to verify it is running. I will come in
one morning and there will be an error. There are 15
remote locations using a transactional/continous
publication to move data to the main office.
How can I prevent this from happening?
What is causing this?
Is there some logging option I can turn on to see more
info about the transactions?
Larry....
By default is a publisher and subscriber have not "talked to" each other for
14 days the subscriber is marked inactive and the subscription may be
dropped. You must reinitialize, regenerate and redistribute the snapshot to
clear this condition.
You can set the interval by right clicking on your publication, selecting
properties and in the subscription expiration section, set a long expiration
value.
I normally run scripts that detect whether the distribution agent has
replicated a transaction to the subscriber in the last 24 hours, and if not,
it raises an alert which causes operations to be paged.
This raises the visibility of these errors.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"larry..." <anonymous@.discussions.microsoft.com> wrote in message
news:9b3601c43446$63f03c20$a401280a@.phx.gbl...
> Running - Win 2K / SQL 2K
> I am constantly, once a week or so,getting an error on a
> transactional publication that I have...
> The subscription(s) have been marked inactive and must be
> reinitialized. NoSync subscriptions will need to be
> dropped and recreated.
> This publication is set up to be continious and is
> checked daily to verify it is running. I will come in
> one morning and there will be an error. There are 15
> remote locations using a transactional/continous
> publication to move data to the main office.
> How can I prevent this from happening?
> What is causing this?
> Is there some logging option I can turn on to see more
> info about the transactions?
> Larry....
>
I am constantly, once a week or so,getting an error on a
transactional publication that I have...
The subscription(s) have been marked inactive and must be
reinitialized. NoSync subscriptions will need to be
dropped and recreated.
This publication is set up to be continious and is
checked daily to verify it is running. I will come in
one morning and there will be an error. There are 15
remote locations using a transactional/continous
publication to move data to the main office.
How can I prevent this from happening?
What is causing this?
Is there some logging option I can turn on to see more
info about the transactions?
Larry....
By default is a publisher and subscriber have not "talked to" each other for
14 days the subscriber is marked inactive and the subscription may be
dropped. You must reinitialize, regenerate and redistribute the snapshot to
clear this condition.
You can set the interval by right clicking on your publication, selecting
properties and in the subscription expiration section, set a long expiration
value.
I normally run scripts that detect whether the distribution agent has
replicated a transaction to the subscriber in the last 24 hours, and if not,
it raises an alert which causes operations to be paged.
This raises the visibility of these errors.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"larry..." <anonymous@.discussions.microsoft.com> wrote in message
news:9b3601c43446$63f03c20$a401280a@.phx.gbl...
> Running - Win 2K / SQL 2K
> I am constantly, once a week or so,getting an error on a
> transactional publication that I have...
> The subscription(s) have been marked inactive and must be
> reinitialized. NoSync subscriptions will need to be
> dropped and recreated.
> This publication is set up to be continious and is
> checked daily to verify it is running. I will come in
> one morning and there will be an error. There are 15
> remote locations using a transactional/continous
> publication to move data to the main office.
> How can I prevent this from happening?
> What is causing this?
> Is there some logging option I can turn on to see more
> info about the transactions?
> Larry....
>
Subscribe to:
Posts (Atom)