error from trasational repl

Hi all,
i found an error in my transactional replication, from the MSrepl_errors table, one of the error_text is "{CALL
sp_MSins_MisFlightScheduleSector (N'KUL', N'CHI', N'KUL;SIN;CHI', 2004-12-29 04:03:00)}", when i run this query in the query
analyzer with the subscriber's database, it show me this error "[Microsoft][ODBC SQL Server Driver]Invalid character value for cast
specification", can anyone tell me some hints or I can't do this action directly as i want to find what error about this query.
Thx
Hi,
Thanks for your posting!
From your descriptions, I understood that you encountered error message
"Invalid character value for cast specification"
First of all, Please know that replication issues might tend to be very
complex and hard to troubleshoot in newsgroups. I recommend that you open a
Support incident with Microsoft Product Support Services (PSS) so that a
dedicated Support Professional can work with you in a more timely and
efficient manner. If you need any help in this regard, please let me know.
For a complete list of Microsoft Product Support Services phone numbers,
please go to the following address on the World Wide Web:
http://support.microsoft.com/directory/overview.asp
Secondly, I noticed there is an Knowledge Base article that mentioned this
error message
FIX: Merge Agent may fail with an "Invalid character value for cast
specification" error message
http://support.microsoft.com/kb/867880
Note that it will be a FREE incident asking the hotfix and this hotfix has
been scheduled to be included in SP4
Thirdly, does your replication works as your expected? Is it possible for
you to provide more information about your scenario, such as how do you
create the replication. Does the same steps work well in other client? Is
is possible for you to show me a detailed description, with which I could
reproduce it on my side?
Thank you for your patience and corporation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
Get Secure! - http://www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!
|||The interpretation of '2004-12-29 04:03:00' as a valid date format depends
on the language employed. This works for English, but not British English
(we're always awkward ). So, I wonder if you are using a login which has a
different default language on the publisher and subscriber?
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||if the language is different, will the first time snapshot replication success and then transactional replication is fail? Since the
snapshot replication is success. thanks
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message news:uuUeVMq7EHA.3236@.TK2MSFTNGP15.phx.gbl...
> The interpretation of '2004-12-29 04:03:00' as a valid date format depends
> on the language employed. This works for English, but not British English
> (we're always awkward ). So, I wonder if you are using a login which has a
> different default language on the publisher and subscriber?
> Rgds,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||The snapshot runs using BCP text files which is an entirely different
mechanism to the synchronization using stored procedures. If it still
exists, please have a look at the format of the date values in the relevant
file to see if this is on the right track.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||thx Paul
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message news:%230p4bZ27EHA.3076@.TK2MSFTNGP15.phx.gbl...
> The snapshot runs using BCP text files which is an entirely different
> mechanism to the synchronization using stored procedures. If it still
> exists, please have a look at the format of the date values in the relevant
> file to see if this is on the right track.
> Rgds,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
sql