Invalid XML Elements found inside cync block

I'm receiving the following error when attempting to execute an
updategram using SQL 2005 and SQLXML 4.0
FrostingModel.Tests.Artist.InvalidConcurrencyUpdate :
Microsoft.Data.SqlXml.SqlXmlException : HRESULT="0x80004005"
Description="Invalid XML elements found inside sync block"
Here is my updategram.
<u>
<updg:sync mapping-schema=".\Schemata\Artist.xsd" nullvalue="NULL"
xmlns:updg="urn:schemas-microsoft-com:xml-updategram">
<updg:before>
<ns1:Artist updg:id="0" ArtistID="1716"
UpdateStamp="AAAAAAAADUw=" xmlns:ns1="urn:Frosting" />
</updg:before>
<updg:after>
<ns1:Artist updg:id="0" ArtistID="1716" Name="Blah Blah Update"
xmlns:ns1="urn:Frosting" />
</updg:after>
</updg:sync>
</u>
And here is the accompanying schema:
<xsd:complexType name="Artist">
<xsd:attribute name="ArtistID" type="xsd:int" use="required"
sql:identity="ignore" sql:datatype="int" />
<xsd:attribute name="Name" type="xsd:string" use="optional"
sql:datatype="nvarchar" />
<xsd:attribute name="UpdateStamp" use="optional" dt:type="bin.hex"
sql:datatype="timestamp" sql2:concurrency="UseValue" />
</xsd:complexType>
It should be noted that if I use concurrency on the Name attribute, it
works as expected. However I would prefer to use a timestamp - it's
the timestamp that seems to be the big proverbial pain in the arse.
I can't seem to find any solutions online regarding this problem... any
takers?
- ryan.Okay...
I changed my UpdateStamp value to be something like 0x000000000000101A
and the updategram worked as expected. However this doesn't make any
sense, because SQL 2005's FOR XML EXPLICIT returns the timestamp value
in a 12 character format such as "AAAAAAAADUw=", not in the above
format.
Am I missing something, or is this a bug in SQLXML 4.0 / SQL 2005? How
is it that SQL 2005 can emit a timestamp value in that "AAA..." format,
but it can't accept it? Do I have to do some type of conversion on my
client side after I receive the timestamp value from sql server?
Any help would be appreciated,
- cranley
cranley wrote:
> I'm receiving the following error when attempting to execute an
> updategram using SQL 2005 and SQLXML 4.0
> FrostingModel.Tests.Artist.InvalidConcurrencyUpdate :
> Microsoft.Data.SqlXml.SqlXmlException : HRESULT="0x80004005"
> Description="Invalid XML elements found inside sync block"
> Here is my updategram.
> <u>
> <updg:sync mapping-schema=".\Schemata\Artist.xsd" nullvalue="NULL"
> xmlns:updg="urn:schemas-microsoft-com:xml-updategram">
> <updg:before>
> <ns1:Artist updg:id="0" ArtistID="1716"
> UpdateStamp="AAAAAAAADUw=" xmlns:ns1="urn:Frosting" />
> </updg:before>
> <updg:after>
> <ns1:Artist updg:id="0" ArtistID="1716" Name="Blah Blah Update"
> xmlns:ns1="urn:Frosting" />
> </updg:after>
> </updg:sync>
> </u>
> And here is the accompanying schema:
> <xsd:complexType name="Artist">
> <xsd:attribute name="ArtistID" type="xsd:int" use="required"
> sql:identity="ignore" sql:datatype="int" />
> <xsd:attribute name="Name" type="xsd:string" use="optional"
> sql:datatype="nvarchar" />
> <xsd:attribute name="UpdateStamp" use="optional" dt:type="bin.hex"
> sql:datatype="timestamp" sql2:concurrency="UseValue" />
> </xsd:complexType>
> It should be noted that if I use concurrency on the Name attribute, it
> works as expected. However I would prefer to use a timestamp - it's
> the timestamp that seems to be the big proverbial pain in the arse.
> I can't seem to find any solutions online regarding this problem... any
> takers?
> - ryan.

Invalid object name 'dbo.MSreplication_queue'.

I am attemption to update a record in a SQL 2005 table that is trans.
replicated with updates and I am receiving the following message...
Msg 208, Level 16, State 1, Procedure sp_MSsendtosqlqueue, Line 40
Invalid object name 'dbo.MSreplication_queue'.
Any ideas?
AHIA,
Larry...
Does the table dbo.MSreplication_queue exist in the subscribing database ?
In updatable scription scenerio, SQL Server fires ins/upd/del triggers which
will insert information into that table when a DML command is executed on the
replicated tables. So this table is one of the critical tables for the queue
replication to work.
I can think of only 2 reasons why you might be running into this error :
1. The table dbo.MSreplication_queue has been deleted. To see if the table
was dropped, take a look at the default trace report for the database "Schema
Changes Histroy" in the Management Studio.
or
2. The snapshot did not get applied to the subscriber successfully. Check
the distribution agents histroy to see if there has been any failures.
"LPR-3rd" wrote:

> I am attemption to update a record in a SQL 2005 table that is trans.
> replicated with updates and I am receiving the following message...
> Msg 208, Level 16, State 1, Procedure sp_MSsendtosqlqueue, Line 40
> Invalid object name 'dbo.MSreplication_queue'.
>
> Any ideas?
> AHIA,
> Larry...
>
|||What is the compatibility level of this database?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"LPR-3rd" <lreames@.gmail.com> wrote in message
news:1168541651.977581.286190@.i56g2000hsf.googlegr oups.com...
>I am attemption to update a record in a SQL 2005 table that is trans.
> replicated with updates and I am receiving the following message...
> Msg 208, Level 16, State 1, Procedure sp_MSsendtosqlqueue, Line 40
> Invalid object name 'dbo.MSreplication_queue'.
>
> Any ideas?
> AHIA,
> Larry...
>

Invalid connection string attribute

We have a development team that is having intermittant problems with
connecting to a server. They are receiving the following error:
Microsoft OLE DB Provider for SQL Server ... Error Message: Invalid
connection string attribute
for the following connection string:
Provider=SQLOLEDB;Data Source=SNLSQLDBD01;Initial
Catalog=WINTER;Trusted_Connection=Yes;DateFormat=m dy
I'd appreciate any insight - as I said the error is intermittant (love
those). I can't find any examples of DateFormat being used in a SQLOLEDB
provider so I am wondering about that.
thanks
Peter
We now think that the message was misleading - there may be something in the
conection string that it didn't like (DateFormat=mdy ?) but was able to
cope with. The job ran fine when scheduled to start at a different time when
there was lower activity.
"Peter Feakins" wrote:

> We have a development team that is having intermittant problems with
> connecting to a server. They are receiving the following error:
> Microsoft OLE DB Provider for SQL Server ... Error Message: Invalid
> connection string attribute
> for the following connection string:
> Provider=SQLOLEDB;Data Source=SNLSQLDBD01;Initial
> Catalog=WINTER;Trusted_Connection=Yes;DateFormat=m dy
> I'd appreciate any insight - as I said the error is intermittant (love
> those). I can't find any examples of DateFormat being used in a SQLOLEDB
> provider so I am wondering about that.
> thanks
> Peter
>
>
>
>
|||I couldn't find any reference in the docs on the provider
for the attribute DateFormat. I found some posts were a few
others were using it but they had the value in double quotes
and used formats such as "YYYY-MM-DD". DateFormat = mdy
looks more like a T-SQL thing. You may want to just execute
a set dateformat SQL statement if that's what you want to
set the format for the client entering datetime data.
-Sue
On Thu, 9 Sep 2004 14:59:13 -0700, "Peter Feakins"
<PeterFeakins@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>We now think that the message was misleading - there may be something in the
>conection string that it didn't like (DateFormat=mdy ?) but was able to
>cope with. The job ran fine when scheduled to start at a different time when
>there was lower activity.
>"Peter Feakins" wrote:

Invalid @owner_login_name and subscriptions

I've been trying to create subscriptions on a new server and have been
receiving errors on the login name. After researching it, I see that can be
as a result of a server name change, and indeed, the new server was renamed
after SQL installation. However, I've done the drop servername, add
servername thing, restarted and even rebooted. The new @.@.Servername value is
correct. But I still get the same error (even after updating sysjobs
originating server). Anybody have any suggestions? If I have to reinstall, I
can, but would that be SQL or SQL RS or both?
--
Thanks,
CGWAh, just had to reconfigure... RSConfig
--
Thanks,
CGW
"CGW" wrote:
> I've been trying to create subscriptions on a new server and have been
> receiving errors on the login name. After researching it, I see that can be
> as a result of a server name change, and indeed, the new server was renamed
> after SQL installation. However, I've done the drop servername, add
> servername thing, restarted and even rebooted. The new @.@.Servername value is
> correct. But I still get the same error (even after updating sysjobs
> originating server). Anybody have any suggestions? If I have to reinstall, I
> can, but would that be SQL or SQL RS or both?
> --
> Thanks,
> CGW