Hi,
When I execute an Insert form a select, SQL Server return the following
message
Server: Msg 8623, Level 16, State 1, Line 109
Internal Query Processor Error: The query processor could not produce a
query plan. Contact your primary support provider for more information.
I have search on technet and find the following article
(http://support.microsoft.com/defaul...kb;en-us;832412). It said to
put the FLAG 9136 on SQL Server.
I have search on Internet and don't find any information about this flag.
Procurei na internet e no encontrei informaes sobre este FLAG.
Does someone know any information about this error or about this flag?I found several KB's associated with that error such as this one:
http://support.microsoft.com/defaul...4&Product=sql2k
But it depends on what your doing. In any case I feel it's a bug and you
should contact MS PSS.
http://support.microsoft.com/defaul...id=fh;EN-US;sql SQL Support
http://www.mssqlserver.com/faq/general-pss.asp MS PSS
Andrew J. Kelly
SQL Server MVP
"Thiago Campos Pereira" <tpereira@.attps.com.br> wrote in message
news:%23sH0wnkQEHA.2716@.tk2msftngp13.phx.gbl...
> Hi,
> When I execute an Insert form a select, SQL Server return the following
> message
> Server: Msg 8623, Level 16, State 1, Line 109
> Internal Query Processor Error: The query processor could not produce a
> query plan. Contact your primary support provider for more information.
>
> I have search on technet and find the following article
> (http://support.microsoft.com/defaul...kb;en-us;832412). It said
to
> put the FLAG 9136 on SQL Server.
> I have search on Internet and don't find any information about this flag.
> Procurei na internet e no encontrei informaes sobre este FLAG.
>
> Does someone know any information about this error or about this flag?
>
Showing posts with label insert. Show all posts
Showing posts with label insert. Show all posts
Tuesday, March 27, 2012
Error 8623
Hi,
When I execute an Insert form a select, SQL Server return the following
message
Server: Msg 8623, Level 16, State 1, Line 109
Internal Query Processor Error: The query processor could not produce a
query plan. Contact your primary support provider for more information.
I have search on TechNet and find the following article
(http://support.microsoft.com/default...b;en-us;832412). It said to
put the FLAG 9136 on SQL Server.
I have search on Internet and don't find any information about this flag.
Procurei na internet e no encontrei informaes sobre este FLAG.
Does someone know any information about this error or about this flag?
I found several KB's associated with that error such as this one:
http://support.microsoft.com/default...&Product=sql2k
But it depends on what your doing. In any case I feel it's a bug and you
should contact MS PSS.
http://support.microsoft.com/default...d=fh;EN-US;sql SQL Support
http://www.mssqlserver.com/faq/general-pss.asp MS PSS
Andrew J. Kelly
SQL Server MVP
"Thiago Campos Pereira" <tpereira@.attps.com.br> wrote in message
news:%23sH0wnkQEHA.2716@.tk2msftngp13.phx.gbl...
> Hi,
> When I execute an Insert form a select, SQL Server return the following
> message
> Server: Msg 8623, Level 16, State 1, Line 109
> Internal Query Processor Error: The query processor could not produce a
> query plan. Contact your primary support provider for more information.
>
> I have search on TechNet and find the following article
> (http://support.microsoft.com/default...b;en-us;832412). It said
to
> put the FLAG 9136 on SQL Server.
> I have search on Internet and don't find any information about this flag.
> Procurei na internet e no encontrei informaes sobre este FLAG.
>
> Does someone know any information about this error or about this flag?
>
When I execute an Insert form a select, SQL Server return the following
message
Server: Msg 8623, Level 16, State 1, Line 109
Internal Query Processor Error: The query processor could not produce a
query plan. Contact your primary support provider for more information.
I have search on TechNet and find the following article
(http://support.microsoft.com/default...b;en-us;832412). It said to
put the FLAG 9136 on SQL Server.
I have search on Internet and don't find any information about this flag.
Procurei na internet e no encontrei informaes sobre este FLAG.
Does someone know any information about this error or about this flag?
I found several KB's associated with that error such as this one:
http://support.microsoft.com/default...&Product=sql2k
But it depends on what your doing. In any case I feel it's a bug and you
should contact MS PSS.
http://support.microsoft.com/default...d=fh;EN-US;sql SQL Support
http://www.mssqlserver.com/faq/general-pss.asp MS PSS
Andrew J. Kelly
SQL Server MVP
"Thiago Campos Pereira" <tpereira@.attps.com.br> wrote in message
news:%23sH0wnkQEHA.2716@.tk2msftngp13.phx.gbl...
> Hi,
> When I execute an Insert form a select, SQL Server return the following
> message
> Server: Msg 8623, Level 16, State 1, Line 109
> Internal Query Processor Error: The query processor could not produce a
> query plan. Contact your primary support provider for more information.
>
> I have search on TechNet and find the following article
> (http://support.microsoft.com/default...b;en-us;832412). It said
to
> put the FLAG 9136 on SQL Server.
> I have search on Internet and don't find any information about this flag.
> Procurei na internet e no encontrei informaes sobre este FLAG.
>
> Does someone know any information about this error or about this flag?
>
Error 8623
Hi,
When I execute an Insert form a select, SQL Server return the following
message
Server: Msg 8623, Level 16, State 1, Line 109
Internal Query Processor Error: The query processor could not produce a
query plan. Contact your primary support provider for more information.
I have search on TechNet and find the following article
(http://support.microsoft.com/default.aspx?scid=kb;en-us;832412). It said to
put the FLAG 9136 on SQL Server.
I have search on Internet and don't find any information about this flag.
Procurei na internet e não encontrei informações sobre este FLAG.
Does someone know any information about this error or about this flag?I found several KB's associated with that error such as this one:
http://support.microsoft.com/default.aspx?scid=kb;en-us;841404&Product=sql2k
But it depends on what your doing. In any case I feel it's a bug and you
should contact MS PSS.
http://support.microsoft.com/default.aspx?scid=fh;EN-US;sql SQL Support
http://www.mssqlserver.com/faq/general-pss.asp MS PSS
--
Andrew J. Kelly
SQL Server MVP
"Thiago Campos Pereira" <tpereira@.attps.com.br> wrote in message
news:%23sH0wnkQEHA.2716@.tk2msftngp13.phx.gbl...
> Hi,
> When I execute an Insert form a select, SQL Server return the following
> message
> Server: Msg 8623, Level 16, State 1, Line 109
> Internal Query Processor Error: The query processor could not produce a
> query plan. Contact your primary support provider for more information.
>
> I have search on TechNet and find the following article
> (http://support.microsoft.com/default.aspx?scid=kb;en-us;832412). It said
to
> put the FLAG 9136 on SQL Server.
> I have search on Internet and don't find any information about this flag.
> Procurei na internet e não encontrei informações sobre este FLAG.
>
> Does someone know any information about this error or about this flag?
>
When I execute an Insert form a select, SQL Server return the following
message
Server: Msg 8623, Level 16, State 1, Line 109
Internal Query Processor Error: The query processor could not produce a
query plan. Contact your primary support provider for more information.
I have search on TechNet and find the following article
(http://support.microsoft.com/default.aspx?scid=kb;en-us;832412). It said to
put the FLAG 9136 on SQL Server.
I have search on Internet and don't find any information about this flag.
Procurei na internet e não encontrei informações sobre este FLAG.
Does someone know any information about this error or about this flag?I found several KB's associated with that error such as this one:
http://support.microsoft.com/default.aspx?scid=kb;en-us;841404&Product=sql2k
But it depends on what your doing. In any case I feel it's a bug and you
should contact MS PSS.
http://support.microsoft.com/default.aspx?scid=fh;EN-US;sql SQL Support
http://www.mssqlserver.com/faq/general-pss.asp MS PSS
--
Andrew J. Kelly
SQL Server MVP
"Thiago Campos Pereira" <tpereira@.attps.com.br> wrote in message
news:%23sH0wnkQEHA.2716@.tk2msftngp13.phx.gbl...
> Hi,
> When I execute an Insert form a select, SQL Server return the following
> message
> Server: Msg 8623, Level 16, State 1, Line 109
> Internal Query Processor Error: The query processor could not produce a
> query plan. Contact your primary support provider for more information.
>
> I have search on TechNet and find the following article
> (http://support.microsoft.com/default.aspx?scid=kb;en-us;832412). It said
to
> put the FLAG 9136 on SQL Server.
> I have search on Internet and don't find any information about this flag.
> Procurei na internet e não encontrei informações sobre este FLAG.
>
> Does someone know any information about this error or about this flag?
>
Thursday, March 22, 2012
Error 8162
We get an Error 8162 when one of our SQR programs attempt
to insert records into a table. The error is irratic
since it does not always occur. We have been unable to
determine exactly what this error means or what may be
causing it. The full error message we get is listed below:
"(SQR 5528) ODBC SQL dbexec: SQLExecute error 8162 in
cursor 18: [MICROSOFT] [ODBD SQL Server Driver] [SQL
Server] Formal parameter '@.P21' was defined as OUTPUT but
the actual parameter not declared OUTPUT."
Looks like a mismatch in procedure parameters. Have you tried dropping and
recerating the stored proc and then running it?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
to insert records into a table. The error is irratic
since it does not always occur. We have been unable to
determine exactly what this error means or what may be
causing it. The full error message we get is listed below:
"(SQR 5528) ODBC SQL dbexec: SQLExecute error 8162 in
cursor 18: [MICROSOFT] [ODBD SQL Server Driver] [SQL
Server] Formal parameter '@.P21' was defined as OUTPUT but
the actual parameter not declared OUTPUT."
Looks like a mismatch in procedure parameters. Have you tried dropping and
recerating the stored proc and then running it?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
Error 8162
We get an Error 8162 when one of our SQR programs attempt
to insert records into a table. The error is irratic
since it does not always occur. We have been unable to
determine exactly what this error means or what may be
causing it. The full error message we get is listed below:
"(SQR 5528) ODBC SQL dbexec: SQLExecute error 8162 in
cursor 18: [MICROSOFT] [ODBD SQL Server Driver] [SQL
Server] Formal parameter '@.P21' was defined as OUTPUT but
the actual parameter not declared OUTPUT."Looks like a mismatch in procedure parameters. Have you tried dropping and
recerating the stored proc and then running it?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
to insert records into a table. The error is irratic
since it does not always occur. We have been unable to
determine exactly what this error means or what may be
causing it. The full error message we get is listed below:
"(SQR 5528) ODBC SQL dbexec: SQLExecute error 8162 in
cursor 18: [MICROSOFT] [ODBD SQL Server Driver] [SQL
Server] Formal parameter '@.P21' was defined as OUTPUT but
the actual parameter not declared OUTPUT."Looks like a mismatch in procedure parameters. Have you tried dropping and
recerating the stored proc and then running it?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
Error 8162
We get an Error 8162 when one of our SQR programs attempt
to insert records into a table. The error is irratic
since it does not always occur. We have been unable to
determine exactly what this error means or what may be
causing it. The full error message we get is listed below:
"(SQR 5528) ODBC SQL dbexec: SQLExecute error 8162 in
cursor 18: [MICROSOFT] [ODBD SQL Server Driver] [SQL
Server] Formal parameter '@.P21' was defined as OUTPUT but
the actual parameter not declared OUTPUT."Looks like a mismatch in procedure parameters. Have you tried dropping and
recerating the stored proc and then running it?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.sql
to insert records into a table. The error is irratic
since it does not always occur. We have been unable to
determine exactly what this error means or what may be
causing it. The full error message we get is listed below:
"(SQR 5528) ODBC SQL dbexec: SQLExecute error 8162 in
cursor 18: [MICROSOFT] [ODBD SQL Server Driver] [SQL
Server] Formal parameter '@.P21' was defined as OUTPUT but
the actual parameter not declared OUTPUT."Looks like a mismatch in procedure parameters. Have you tried dropping and
recerating the stored proc and then running it?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.sql
Wednesday, March 21, 2012
Error 7391 for distributed transaction between SQL Server and Oracle
Hi,
I am using SQL server 2000 on Windows 2003 SP1.I am trying to insert a
row into SQL server and Oracle through a Stored Proc.
If i run the sql statement using Query Analyzer with openrowset,i am
able to insert the row fine.
But when it is done through SP it throws this error.
Server: Msg 7391, Level 16, State 1, Procedure
SP_AutoInsertIncentive_oracle, Line 19
The operation could not be performed because the OLE DB provider
'MSDAORA' was unable to begin a distributed transaction.
OLE DB error trace [OLE/DB Provider 'MSDAORA'
ITransactionJoin::JoinTransaction returned 0x8004d01b].
Thanks a lot in advance for your help.
AJHi,
You can try this
[url]http://support.microsoft.com/default.aspx?scid=kb;en-us;306212&Product=sql2k.[/url
]
Hope it helps.
Danijel Novak
<aj70000@.hotmail.com> wrote in message
news:1137444337.934408.326330@.g47g2000cwa.googlegroups.com...
> Hi,
> I am using SQL server 2000 on Windows 2003 SP1.I am trying to insert a
> row into SQL server and Oracle through a Stored Proc.
> If i run the sql statement using Query Analyzer with openrowset,i am
> able to insert the row fine.
> But when it is done through SP it throws this error.
>
> Server: Msg 7391, Level 16, State 1, Procedure
> SP_AutoInsertIncentive_oracle, Line 19
> The operation could not be performed because the OLE DB provider
> 'MSDAORA' was unable to begin a distributed transaction.
> OLE DB error trace [OLE/DB Provider 'MSDAORA'
> ITransactionJoin::JoinTransaction returned 0x8004d01b].
> Thanks a lot in advance for your help.
> AJ
>
I am using SQL server 2000 on Windows 2003 SP1.I am trying to insert a
row into SQL server and Oracle through a Stored Proc.
If i run the sql statement using Query Analyzer with openrowset,i am
able to insert the row fine.
But when it is done through SP it throws this error.
Server: Msg 7391, Level 16, State 1, Procedure
SP_AutoInsertIncentive_oracle, Line 19
The operation could not be performed because the OLE DB provider
'MSDAORA' was unable to begin a distributed transaction.
OLE DB error trace [OLE/DB Provider 'MSDAORA'
ITransactionJoin::JoinTransaction returned 0x8004d01b].
Thanks a lot in advance for your help.
AJHi,
You can try this
[url]http://support.microsoft.com/default.aspx?scid=kb;en-us;306212&Product=sql2k.[/url
]
Hope it helps.
Danijel Novak
<aj70000@.hotmail.com> wrote in message
news:1137444337.934408.326330@.g47g2000cwa.googlegroups.com...
> Hi,
> I am using SQL server 2000 on Windows 2003 SP1.I am trying to insert a
> row into SQL server and Oracle through a Stored Proc.
> If i run the sql statement using Query Analyzer with openrowset,i am
> able to insert the row fine.
> But when it is done through SP it throws this error.
>
> Server: Msg 7391, Level 16, State 1, Procedure
> SP_AutoInsertIncentive_oracle, Line 19
> The operation could not be performed because the OLE DB provider
> 'MSDAORA' was unable to begin a distributed transaction.
> OLE DB error trace [OLE/DB Provider 'MSDAORA'
> ITransactionJoin::JoinTransaction returned 0x8004d01b].
> Thanks a lot in advance for your help.
> AJ
>
Error 7391 for distributed transaction between SQL Server and Oracle
Hi,
I am using SQL server 2000 on Windows 2003 SP1.I am trying to insert a
row into SQL server and Oracle through a Stored Proc.
If i run the sql statement using Query Analyzer with openrowset,i am
able to insert the row fine.
But when it is done through SP it throws this error.
Server: Msg 7391, Level 16, State 1, Procedure
SP_AutoInsertIncentive_oracle, Line 19
The operation could not be performed because the OLE DB provider
'MSDAORA' was unable to begin a distributed transaction.
OLE DB error trace [OLE/DB Provider 'MSDAORA'
ITransactionJoin::JoinTransaction returned 0x8004d01b].
Thanks a lot in advance for your help.
AJHi,
You can try this
http://support.microsoft.com/default.aspx?scid=kb;en-us;306212&Product=sql2k.
Hope it helps.
--
Danijel Novak
<aj70000@.hotmail.com> wrote in message
news:1137444337.934408.326330@.g47g2000cwa.googlegroups.com...
> Hi,
> I am using SQL server 2000 on Windows 2003 SP1.I am trying to insert a
> row into SQL server and Oracle through a Stored Proc.
> If i run the sql statement using Query Analyzer with openrowset,i am
> able to insert the row fine.
> But when it is done through SP it throws this error.
>
> Server: Msg 7391, Level 16, State 1, Procedure
> SP_AutoInsertIncentive_oracle, Line 19
> The operation could not be performed because the OLE DB provider
> 'MSDAORA' was unable to begin a distributed transaction.
> OLE DB error trace [OLE/DB Provider 'MSDAORA'
> ITransactionJoin::JoinTransaction returned 0x8004d01b].
> Thanks a lot in advance for your help.
> AJ
>
I am using SQL server 2000 on Windows 2003 SP1.I am trying to insert a
row into SQL server and Oracle through a Stored Proc.
If i run the sql statement using Query Analyzer with openrowset,i am
able to insert the row fine.
But when it is done through SP it throws this error.
Server: Msg 7391, Level 16, State 1, Procedure
SP_AutoInsertIncentive_oracle, Line 19
The operation could not be performed because the OLE DB provider
'MSDAORA' was unable to begin a distributed transaction.
OLE DB error trace [OLE/DB Provider 'MSDAORA'
ITransactionJoin::JoinTransaction returned 0x8004d01b].
Thanks a lot in advance for your help.
AJHi,
You can try this
http://support.microsoft.com/default.aspx?scid=kb;en-us;306212&Product=sql2k.
Hope it helps.
--
Danijel Novak
<aj70000@.hotmail.com> wrote in message
news:1137444337.934408.326330@.g47g2000cwa.googlegroups.com...
> Hi,
> I am using SQL server 2000 on Windows 2003 SP1.I am trying to insert a
> row into SQL server and Oracle through a Stored Proc.
> If i run the sql statement using Query Analyzer with openrowset,i am
> able to insert the row fine.
> But when it is done through SP it throws this error.
>
> Server: Msg 7391, Level 16, State 1, Procedure
> SP_AutoInsertIncentive_oracle, Line 19
> The operation could not be performed because the OLE DB provider
> 'MSDAORA' was unable to begin a distributed transaction.
> OLE DB error trace [OLE/DB Provider 'MSDAORA'
> ITransactionJoin::JoinTransaction returned 0x8004d01b].
> Thanks a lot in advance for your help.
> AJ
>
Error 7391 for distributed transaction between SQL Server and Oracle
Hi,
I am using SQL server 2000 on Windows 2003 SP1.I am trying to insert a
row into SQL server and Oracle through a Stored Proc.
If i run the sql statement using Query Analyzer with openrowset,i am
able to insert the row fine.
But when it is done through SP it throws this error.
Server: Msg 7391, Level 16, State 1, Procedure
SP_AutoInsertIncentive_oracle, Line 19
The operation could not be performed because the OLE DB provider
'MSDAORA' was unable to begin a distributed transaction.
OLE DB error trace [OLE/DB Provider 'MSDAORA'
ITransactionJoin::JoinTransaction returned 0x8004d01b].
Thanks a lot in advance for your help.
AJ
Hi,
You can try this
http://support.microsoft.com/default...Product=sql2k.
Hope it helps.
Danijel Novak
<aj70000@.hotmail.com> wrote in message
news:1137444337.934408.326330@.g47g2000cwa.googlegr oups.com...
> Hi,
> I am using SQL server 2000 on Windows 2003 SP1.I am trying to insert a
> row into SQL server and Oracle through a Stored Proc.
> If i run the sql statement using Query Analyzer with openrowset,i am
> able to insert the row fine.
> But when it is done through SP it throws this error.
>
> Server: Msg 7391, Level 16, State 1, Procedure
> SP_AutoInsertIncentive_oracle, Line 19
> The operation could not be performed because the OLE DB provider
> 'MSDAORA' was unable to begin a distributed transaction.
> OLE DB error trace [OLE/DB Provider 'MSDAORA'
> ITransactionJoin::JoinTransaction returned 0x8004d01b].
> Thanks a lot in advance for your help.
> AJ
>
I am using SQL server 2000 on Windows 2003 SP1.I am trying to insert a
row into SQL server and Oracle through a Stored Proc.
If i run the sql statement using Query Analyzer with openrowset,i am
able to insert the row fine.
But when it is done through SP it throws this error.
Server: Msg 7391, Level 16, State 1, Procedure
SP_AutoInsertIncentive_oracle, Line 19
The operation could not be performed because the OLE DB provider
'MSDAORA' was unable to begin a distributed transaction.
OLE DB error trace [OLE/DB Provider 'MSDAORA'
ITransactionJoin::JoinTransaction returned 0x8004d01b].
Thanks a lot in advance for your help.
AJ
Hi,
You can try this
http://support.microsoft.com/default...Product=sql2k.
Hope it helps.
Danijel Novak
<aj70000@.hotmail.com> wrote in message
news:1137444337.934408.326330@.g47g2000cwa.googlegr oups.com...
> Hi,
> I am using SQL server 2000 on Windows 2003 SP1.I am trying to insert a
> row into SQL server and Oracle through a Stored Proc.
> If i run the sql statement using Query Analyzer with openrowset,i am
> able to insert the row fine.
> But when it is done through SP it throws this error.
>
> Server: Msg 7391, Level 16, State 1, Procedure
> SP_AutoInsertIncentive_oracle, Line 19
> The operation could not be performed because the OLE DB provider
> 'MSDAORA' was unable to begin a distributed transaction.
> OLE DB error trace [OLE/DB Provider 'MSDAORA'
> ITransactionJoin::JoinTransaction returned 0x8004d01b].
> Thanks a lot in advance for your help.
> AJ
>
Friday, March 9, 2012
Error 515
I get this error during Merge replication
" Cannot insert the value NULL into column 'nicknames', table
'REP_Sub.dbo.MSmerge_genhistory'; column does not allow nulls. INSERT fails. "
Can anyone help
Did you register your publisher or subscriber using an IP address? There
have been reports in the past that this can cause this problem.
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
"Sesha" <Sesha@.discussions.microsoft.com> wrote in message
news:87EB3D3B-913F-4B6B-8FC7-471517A0F444@.microsoft.com...
> I get this error during Merge replication
> " Cannot insert the value NULL into column 'nicknames', table
> 'REP_Sub.dbo.MSmerge_genhistory'; column does not allow nulls. INSERT
fails. "
> Can anyone help
|||Sesha,
You must check @.@.servername on the SUBSCRIBER. This will probably return a
NULL.
Select * from sysservers
This will give you a list of local/linked/remote servers on that box. If you
returned NULL above, it's because the server has gotten confused about not
having a local named server (SRVID=0) to put in the nickname table.
If you don't have a SRVID=0 and your servername does exist in the list then
do the following:
SP_dropserver 'Servername'
go
Sp_Addserver 'Servername','local'
If it doesn't exist and you don't have SRVID=0 then just do the Add.
That should sort you out.
Good luck.
"Hilary Cotter" wrote:
> Did you register your publisher or subscriber using an IP address? There
> have been reports in the past that this can cause this problem.
> --
> 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
> "Sesha" <Sesha@.discussions.microsoft.com> wrote in message
> news:87EB3D3B-913F-4B6B-8FC7-471517A0F444@.microsoft.com...
> fails. "
>
>
" Cannot insert the value NULL into column 'nicknames', table
'REP_Sub.dbo.MSmerge_genhistory'; column does not allow nulls. INSERT fails. "
Can anyone help
Did you register your publisher or subscriber using an IP address? There
have been reports in the past that this can cause this problem.
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
"Sesha" <Sesha@.discussions.microsoft.com> wrote in message
news:87EB3D3B-913F-4B6B-8FC7-471517A0F444@.microsoft.com...
> I get this error during Merge replication
> " Cannot insert the value NULL into column 'nicknames', table
> 'REP_Sub.dbo.MSmerge_genhistory'; column does not allow nulls. INSERT
fails. "
> Can anyone help
|||Sesha,
You must check @.@.servername on the SUBSCRIBER. This will probably return a
NULL.
Select * from sysservers
This will give you a list of local/linked/remote servers on that box. If you
returned NULL above, it's because the server has gotten confused about not
having a local named server (SRVID=0) to put in the nickname table.
If you don't have a SRVID=0 and your servername does exist in the list then
do the following:
SP_dropserver 'Servername'
go
Sp_Addserver 'Servername','local'
If it doesn't exist and you don't have SRVID=0 then just do the Add.
That should sort you out.
Good luck.
"Hilary Cotter" wrote:
> Did you register your publisher or subscriber using an IP address? There
> have been reports in the past that this can cause this problem.
> --
> 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
> "Sesha" <Sesha@.discussions.microsoft.com> wrote in message
> news:87EB3D3B-913F-4B6B-8FC7-471517A0F444@.microsoft.com...
> fails. "
>
>
error 4819
I have just created a snapshot manually and started the synch manualy and I
am getting :
error 4819 - Could not bulk insert. Bulk data stream was incorrectly
specified as sorted.
Anyone point me to why this might be happening? Its a severity 16, so user
caused and supposedly user fixable.
Duncan
"Duncan" <duncanl@.mcgrath.com.au> wrote in message
news:2kflhaF1ef7jU1@.uni-berlin.de...
> I have just created a snapshot manually and started the synch manualy and
I
> am getting :
> error 4819 - Could not bulk insert. Bulk data stream was incorrectly
> specified as sorted.
> Anyone point me to why this might be happening? Its a severity 16, so
user
> caused and supposedly user fixable.
> --
>
> Duncan
>
and I have checked sp_helpsort - they are both the same.
This started happening after I made some changes to the table structure, but
for no apparent reason.
|||Duncan,
sp_helpsort returns the default collation at the server level, while this is
probably a problem at the table level. I wonder did you make some changes to
the database collation? This is potentially picked up by the applied
snapshot, and it may be incompatible with the source data. Try checking that
under the article properties you are taking the table's collation, and this
will then override the default database one.
If there's still an issue, please post back listing the table collation and
the collation of the subscriber database, and stating if you are taking the
collation or not.
HTH,
Paul Ibison
am getting :
error 4819 - Could not bulk insert. Bulk data stream was incorrectly
specified as sorted.
Anyone point me to why this might be happening? Its a severity 16, so user
caused and supposedly user fixable.
Duncan
"Duncan" <duncanl@.mcgrath.com.au> wrote in message
news:2kflhaF1ef7jU1@.uni-berlin.de...
> I have just created a snapshot manually and started the synch manualy and
I
> am getting :
> error 4819 - Could not bulk insert. Bulk data stream was incorrectly
> specified as sorted.
> Anyone point me to why this might be happening? Its a severity 16, so
user
> caused and supposedly user fixable.
> --
>
> Duncan
>
and I have checked sp_helpsort - they are both the same.
This started happening after I made some changes to the table structure, but
for no apparent reason.
|||Duncan,
sp_helpsort returns the default collation at the server level, while this is
probably a problem at the table level. I wonder did you make some changes to
the database collation? This is potentially picked up by the applied
snapshot, and it may be incompatible with the source data. Try checking that
under the article properties you are taking the table's collation, and this
will then override the default database one.
If there's still an issue, please post back listing the table collation and
the collation of the subscriber database, and stating if you are taking the
collation or not.
HTH,
Paul Ibison
Sunday, February 26, 2012
error 3520 on sql insert statement from a text file (only happens in 1 location)
I have a program that uses the Microsoft ODBC text driver Driver={Microsoft Text Driver (*.txt; *.csv)} this is used to make a connection to the database and then execute an sql insert to insert data from a flat file into an access database. The code works at hundreds of locations but for some reason it does not work at 1. I have ran an sql trace and found the error 3520 which would mean the data in the text file does not match the table that it is being inserted into but I have checked that and have tried using the same data on my computer and it works fine. I have also ran mdac compenent checker and there are no mismatched files. Any ideas on how to correct this or if anyone else has ever even seen this please help...Moving thread to Data Access Forum.
Friday, February 24, 2012
Error 2812 Could not Find Store Procedure dbo.MSmerge_expand_sp_A2F.......
Hi i am running SQL 2005 and i have a merge replication.
Sudently when i am trying to insert a new record on a table i am
getting this Error.
Error 2812 Could not Find Store Procedure
dbo.MSmerge_expand_sp_A2F......
Can anyone help please
Thanks
Savvas Christodoulou
Sounds like this proc is missing. Can you locate it on other subscribers? If
so copy it here.
Normally when you get errors like this your replication metadata is
inconsistent and it is best solved by regenerating and redistributing the
snapshot.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
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
<savvaschr@.nodalsoft.com.cy> wrote in message
news:1163094573.683827.298500@.m73g2000cwd.googlegr oups.com...
> Hi i am running SQL 2005 and i have a merge replication.
> Sudently when i am trying to insert a new record on a table i am
> getting this Error.
> Error 2812 Could not Find Store Procedure
> dbo.MSmerge_expand_sp_A2F......
> Can anyone help please
> Thanks
> Savvas Christodoulou
>
Sudently when i am trying to insert a new record on a table i am
getting this Error.
Error 2812 Could not Find Store Procedure
dbo.MSmerge_expand_sp_A2F......
Can anyone help please
Thanks
Savvas Christodoulou
Sounds like this proc is missing. Can you locate it on other subscribers? If
so copy it here.
Normally when you get errors like this your replication metadata is
inconsistent and it is best solved by regenerating and redistributing the
snapshot.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
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
<savvaschr@.nodalsoft.com.cy> wrote in message
news:1163094573.683827.298500@.m73g2000cwd.googlegr oups.com...
> Hi i am running SQL 2005 and i have a merge replication.
> Sudently when i am trying to insert a new record on a table i am
> getting this Error.
> Error 2812 Could not Find Store Procedure
> dbo.MSmerge_expand_sp_A2F......
> Can anyone help please
> Thanks
> Savvas Christodoulou
>
Friday, February 17, 2012
Error 213: Insert Error: Column name or values don't match table definition
Hello,
I have had the below procedure working and in use for some time now,
and suddently i started getting the below error:
"Eorror 213: Insert Error: Column name or number of supplied values
does not match table definition"
Thank you
CREATE PROCEDURE bat_LogData (
@.ComputerName varchar(50),
@.UserDomain varchar(50),
@.UserName varchar(50),
@.Date_Time datetime,
@.Message varchar(128),
@.SubMessage varchar(128),
@.ErrorText varchar(128),
@.ErrorCode nvarchar(15),
@.smsguid nvarchar(41),
@.locale int,
@.scriptver nvarchar(15),
@.wshver nvarchar(15)
)
AS
INSERT INTO LogonScript_data VALUES (
@.ComputerName,
@.UserName,
@.UserDomain,
GetDate(),
@.Date_Time,
@.Message,
@.SubMessage,
@.ErrorText,
@.ErrorCode,
@.smsguid,
@.locale,
@.scriptver,
@.wshver
)
SELECT @.@.IDENTITY AS 'MessageID'
GOrdixon5652@.hotmail.com wrote:
> Hello,
> I have had the below procedure working and in use for some time now,
> and suddently i started getting the below error:
> "Eorror 213: Insert Error: Column name or number of supplied values
> does not match table definition"
> Thank you
> CREATE PROCEDURE bat_LogData (
> @.ComputerName varchar(50),
> @.UserDomain varchar(50),
> @.UserName varchar(50),
> @.Date_Time datetime,
> @.Message varchar(128),
> @.SubMessage varchar(128),
> @.ErrorText varchar(128),
> @.ErrorCode nvarchar(15),
> @.smsguid nvarchar(41),
> @.locale int,
> @.scriptver nvarchar(15),
> @.wshver nvarchar(15)
> )
> AS
> INSERT INTO LogonScript_data VALUES (
> @.ComputerName,
> @.UserName,
> @.UserDomain,
> GetDate(),
> @.Date_Time,
> @.Message,
> @.SubMessage,
> @.ErrorText,
> @.ErrorCode,
> @.smsguid,
> @.locale,
> @.scriptver,
> @.wshver
> )
> SELECT @.@.IDENTITY AS 'MessageID'
> GO
I expect the table changed. Did you add or drop a column?
Always list the column names in an INSERT statement. Leaving them out
as you have done will inevitably make your code less reliable and
harder to debug. For example:
INSERT INTO LogonScript_data (
computername, username, userdomain, dt, date_time, message,
submessage,
errortext, errorcode, smsguid, locale, scriptver, wshver)
VALUES
(@.computername, @.username, @.userdomain, GETDATE(), @.date_time,
@.message,
@.submessage, @.errortext, @.errorcode, @.smsguid, @.locale, @.scriptver,
@.wshver
)
David Portas
SQL Server MVP
--
I have had the below procedure working and in use for some time now,
and suddently i started getting the below error:
"Eorror 213: Insert Error: Column name or number of supplied values
does not match table definition"
Thank you
CREATE PROCEDURE bat_LogData (
@.ComputerName varchar(50),
@.UserDomain varchar(50),
@.UserName varchar(50),
@.Date_Time datetime,
@.Message varchar(128),
@.SubMessage varchar(128),
@.ErrorText varchar(128),
@.ErrorCode nvarchar(15),
@.smsguid nvarchar(41),
@.locale int,
@.scriptver nvarchar(15),
@.wshver nvarchar(15)
)
AS
INSERT INTO LogonScript_data VALUES (
@.ComputerName,
@.UserName,
@.UserDomain,
GetDate(),
@.Date_Time,
@.Message,
@.SubMessage,
@.ErrorText,
@.ErrorCode,
@.smsguid,
@.locale,
@.scriptver,
@.wshver
)
SELECT @.@.IDENTITY AS 'MessageID'
GOrdixon5652@.hotmail.com wrote:
> Hello,
> I have had the below procedure working and in use for some time now,
> and suddently i started getting the below error:
> "Eorror 213: Insert Error: Column name or number of supplied values
> does not match table definition"
> Thank you
> CREATE PROCEDURE bat_LogData (
> @.ComputerName varchar(50),
> @.UserDomain varchar(50),
> @.UserName varchar(50),
> @.Date_Time datetime,
> @.Message varchar(128),
> @.SubMessage varchar(128),
> @.ErrorText varchar(128),
> @.ErrorCode nvarchar(15),
> @.smsguid nvarchar(41),
> @.locale int,
> @.scriptver nvarchar(15),
> @.wshver nvarchar(15)
> )
> AS
> INSERT INTO LogonScript_data VALUES (
> @.ComputerName,
> @.UserName,
> @.UserDomain,
> GetDate(),
> @.Date_Time,
> @.Message,
> @.SubMessage,
> @.ErrorText,
> @.ErrorCode,
> @.smsguid,
> @.locale,
> @.scriptver,
> @.wshver
> )
> SELECT @.@.IDENTITY AS 'MessageID'
> GO
I expect the table changed. Did you add or drop a column?
Always list the column names in an INSERT statement. Leaving them out
as you have done will inevitably make your code less reliable and
harder to debug. For example:
INSERT INTO LogonScript_data (
computername, username, userdomain, dt, date_time, message,
submessage,
errortext, errorcode, smsguid, locale, scriptver, wshver)
VALUES
(@.computername, @.username, @.userdomain, GETDATE(), @.date_time,
@.message,
@.submessage, @.errortext, @.errorcode, @.smsguid, @.locale, @.scriptver,
@.wshver
)
David Portas
SQL Server MVP
--
Subscribe to:
Posts (Atom)