Error 8623

Hi,
After some changes in my database when I try to execute following statement:
delete from dbo.PrzychodH
i received this error:
Server: Msg 8623, Level 16, State 1, Line 1
Internal Query Processor Error:
The query processor could not produce a query plan.
Contact your primary support provider for more information.
When I dropped all changes this error does NOT disappeared.
Sql2000 SP4 on WinServ2003 SP1.
Is this SQL2k SP4 new bug?
MarekMarek,
Not sure what you're doing but might take a look at:
http://support.microsoft.com/search...>
ast=3&mode=a
There are quite a few references to the error code in here.
Also, might perform a DBCC CHECKTABLE on przychodH just to rule that out as
a possible cause.
HTH
Jerry
"Marek" <marlie@.wp.pl> wrote in message
news:OcbJYr2wFHA.3124@.TK2MSFTNGP12.phx.gbl...
> Hi,
>
> After some changes in my database when I try to execute following
> statement:
>
> delete from dbo.PrzychodH
>
> i received this error:
>
> Server: Msg 8623, Level 16, State 1, Line 1
> Internal Query Processor Error:
> The query processor could not produce a query plan.
> Contact your primary support provider for more information.
>
> When I dropped all changes this error does NOT disappeared.
>
> Sql2000 SP4 on WinServ2003 SP1.
>
> Is this SQL2k SP4 new bug?
>
> Marek
>
>sql

Error 8623

Hi,
After some changes in my database when I try to execute following statement:
delete from dbo.PrzychodH
i received this error:
Server: Msg 8623, Level 16, State 1, Line 1
Internal Query Processor Error:
The query processor could not produce a query plan.
Contact your primary support provider for more information.
When I dropped all changes this error does NOT disappeared.
Sql2000 SP4 on WinServ2003 SP1.
Is this SQL2k SP4 new bug?
Marek
Marek,
Not sure what you're doing but might take a look at:
http://support.microsoft.com/search/...2&ast=3&mode=a
There are quite a few references to the error code in here.
Also, might perform a DBCC CHECKTABLE on przychodH just to rule that out as
a possible cause.
HTH
Jerry
"Marek" <marlie@.wp.pl> wrote in message
news:OcbJYr2wFHA.3124@.TK2MSFTNGP12.phx.gbl...
> Hi,
>
> After some changes in my database when I try to execute following
> statement:
>
> delete from dbo.PrzychodH
>
> i received this error:
>
> Server: Msg 8623, Level 16, State 1, Line 1
> Internal Query Processor Error:
> The query processor could not produce a query plan.
> Contact your primary support provider for more information.
>
> When I dropped all changes this error does NOT disappeared.
>
> Sql2000 SP4 on WinServ2003 SP1.
>
> Is this SQL2k SP4 new bug?
>
> Marek
>
>

Error 8623

Hi,
After some changes in my database when I try to execute following statement:
delete from dbo.PrzychodH
i received this error:
Server: Msg 8623, Level 16, State 1, Line 1
Internal Query Processor Error:
The query processor could not produce a query plan.
Contact your primary support provider for more information.
When I dropped all changes this error does NOT disappeared.
Sql2000 SP4 on WinServ2003 SP1.
Is this SQL2k SP4 new bug?
MarekMarek,
Not sure what you're doing but might take a look at:
http://support.microsoft.com/search/default.aspx?spid=2852&query=not+produce+a+query+plan&catalog=LCID%3D1033&pwt=false&title=false&kt=ALL&mdt=0&comm=1&ast=1&ast=2&ast=3&mode=a
There are quite a few references to the error code in here.
Also, might perform a DBCC CHECKTABLE on przychodH just to rule that out as
a possible cause.
HTH
Jerry
"Marek" <marlie@.wp.pl> wrote in message
news:OcbJYr2wFHA.3124@.TK2MSFTNGP12.phx.gbl...
> Hi,
>
> After some changes in my database when I try to execute following
> statement:
>
> delete from dbo.PrzychodH
>
> i received this error:
>
> Server: Msg 8623, Level 16, State 1, Line 1
> Internal Query Processor Error:
> The query processor could not produce a query plan.
> Contact your primary support provider for more information.
>
> When I dropped all changes this error does NOT disappeared.
>
> Sql2000 SP4 on WinServ2003 SP1.
>
> Is this SQL2k SP4 new bug?
>
> Marek
>
>

Error 7306 when trying to do an update on a linked server

Here is my query run on one server against a Linked server:
UPDATE [Linked-Name].dbname.dbo.[Table name]
SET TimeStamp = '1900-01-01 00:00:00'
WHERE ISDATE(TimeStamp) = 0
I get the following error message:
Could not open table '"dbname"."dbo"."Table name"' from OLE DB provider
'SQLOLEDB'. The provider could not support a row lookup position. The
provider indicates that conflicts occurred with other properties or
requirements.
[OLE/DB provider returned message: Multiple-step OLE DB operation
generated errors. Check each OLE DB status value, if available. No work
was done.]
OLE DB error trace [OLE/DB Provider 'SQLOLEDB' IOpenRowset::OpenRowset
returned 0x80040e21: [PROPID=DBPROP_BOOKMARKS VALUE=True
STATUS=DBPROPSTATUS_CONFLICTING], [PROPID=DBPROP_COMMANDTIMEOUT
VALUE=600 STATUS=DBPROPSTATUS_OK], [PROPID=Unknown PropertyID
VALUE=True STATUS=DBPROPSTATUS_OK], [PROPID=DBPROP_IRowsetLocate
VALUE=True STATUS=DBPROPSTATUS_CONFLICTING],
[PROPID=DBPROP_IRowsetChange VA...
Please help!
Thanks.What platform is the linked server?
<ryan_willow@.hotmail.com> wrote in message
news:1150831576.021477.128570@.p79g2000cwp.googlegroups.com...
> Here is my query run on one server against a Linked server:
> UPDATE [Linked-Name].dbname.dbo.[Table name]
> SET TimeStamp = '1900-01-01 00:00:00'
> WHERE ISDATE(TimeStamp) = 0
> I get the following error message:
> Could not open table '"dbname"."dbo"."Table name"' from OLE DB provider
> 'SQLOLEDB'. The provider could not support a row lookup position. The
> provider indicates that conflicts occurred with other properties or
> requirements.
> [OLE/DB provider returned message: Multiple-step OLE DB operation
> generated errors. Check each OLE DB status value, if available. No work
> was done.]
> OLE DB error trace [OLE/DB Provider 'SQLOLEDB' IOpenRowset::OpenRowset
> returned 0x80040e21: [PROPID=DBPROP_BOOKMARKS VALUE=True
> STATUS=DBPROPSTATUS_CONFLICTING], [PROPID=DBPROP_COMMANDTIMEOUT
> VALUE=600 STATUS=DBPROPSTATUS_OK], [PROPID=Unknown PropertyID
> VALUE=True STATUS=DBPROPSTATUS_OK], [PROPID=DBPROP_IRowsetLocate
> VALUE=True STATUS=DBPROPSTATUS_CONFLICTING],
> [PROPID=DBPROP_IRowsetChange VA...
> Please help!
> Thanks.
>|||SQL Server 2000.
I believe that this is the problem:
http://msdn.microsoft.com/library/d...serr_2_4gqh.asp
i.e. UPDATE, and DELETE statements are not supported on the remote
table if the table does not have a unique index defined on it.
So now I'm here:
I've done DELETEs remotely and had no problem, only errors on UPDATE.
I don't want to modify this established database by defining unique
indices.
How can I get around this?
Mike C# wrote:
> What platform is the linked server?
> <ryan_willow@.hotmail.com> wrote in message
> news:1150831576.021477.128570@.p79g2000cwp.googlegroups.com...|||ryan_willow@.hotmail.com wrote:
> SQL Server 2000.
> I believe that this is the problem:
> http://msdn.microsoft.com/library/d...serr_2_4gqh.asp
> i.e. UPDATE, and DELETE statements are not supported on the remote
> table if the table does not have a unique index defined on it.
> So now I'm here:
> I've done DELETEs remotely and had no problem, only errors on UPDATE.
> I don't want to modify this established database by defining unique
> indices.
> How can I get around this?
> Mike C# wrote:
What is version of MDAC?
and Service Pack?
We have also a problem like this and after updating to latest version
problem was solved
Regards
Amish Shah

Error 7201: Permissions problem?

Hi there

I am new to this forum and I was wondering if someone could help out.

I am marked as "dbo" on a SQL Server database. Attached to this DB is a
publication. When I right click > properties SQL Server gives me Error 7201

Any ideas as to how I can get over this? Is it permissions related?

ThanksRandall McMurphy via SQLMonster.com (forum@.nospam.SQLMonster.com) writes:
> I am new to this forum and I was wondering if someone could help out.
> I am marked as "dbo" on a SQL Server database. Attached to this DB is a
> publication. When I right click > properties SQL Server gives me Error
> 7201

That is: "Could not execute procedure on remote server '%.*ls' because SQL
Server is not configured for remote access. Ask your system administrator to
reconfigure SQL Server to allow remote access."

> Any ideas as to how I can get over this? Is it permissions related?

No, it's a configuraiton issue. I have not seen the message before, and
the message is a little strange. Which server needs to be configured? The
local server or the remote server? But since I cannot think of any
configuration on the local side, it's probably the definition of the remote
server that is wacko.

Do sp_helpserver on the linked server, and make sure that all of these
are enabled: rpc, rpc out and data access. If they are not, use
sp_serveroption to set these on.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

Error 21776: After creating new login

I run this code:
EXEC DATA0003.dbo.sp_addlogin 'test','pwd'
EXEC DATA0003.dbo.sp_grantdbaccess 'test'
EXEC DATA0003.dbo.sp_addrolemember 'Full','test'
When I go into enterprise and go to the properties of
login and to Data Access Tab and select the Data0003
(which is checked) I get this error:
Error 21776:[SQL-DMO]The name 'test' was not found in the
Users collection. If the name is a qualified name, use
[] to separte various parts of the name, and try again.
The only way I found to get rid of the error is to go to
DATA0003 and select the users and refresh the list.
Then, their is no problem.
But, I would like to not have to go refresh user
everytime I add a login.
I would appreciate any help.
Thanks in advance,
BobEM uses SQLDMO and caches a lot of the information you see. In general this
is a good thing. I don't believe there is any way to alter the behaviour in
Enterprise Manager. See this note from BOL about SQLDMO collections
"To enable more efficient processing, SQL-DMO caches much of the information
about SQL Server components referenced by objects maintained in a
collection. When component data is cached, administrative activity of
another SQL Server session is not visible to the SQL-DMO session. The
Refresh method queries the organization server, filling the collection with
the most up-to-date component information."
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Bob Haines" <bhaines@.pahousegop.com> wrote in message
news:164f901c4173c$4c0e51e0$a501280a@.phx
.gbl...
> I run this code:
> EXEC DATA0003.dbo.sp_addlogin 'test','pwd'
> EXEC DATA0003.dbo.sp_grantdbaccess 'test'
> EXEC DATA0003.dbo.sp_addrolemember 'Full','test'
> When I go into enterprise and go to the properties of
> login and to Data Access Tab and select the Data0003
> (which is checked) I get this error:
> Error 21776:[SQL-DMO]The name 'test' was not found in the
> Users collection. If the name is a qualified name, use
> [] to separte various parts of the name, and try again.
> The only way I found to get rid of the error is to go to
> DATA0003 and select the users and refresh the list.
> Then, their is no problem.
> But, I would like to not have to go refresh user
> everytime I add a login.
> I would appreciate any help.
> Thanks in advance,
> Bob|||try this
type:
use DATA0003
before :
EXEC DATA0003.dbo.sp_addlogin 'test','pwd'
EXEC DATA0003.dbo.sp_grantdbaccess 'test'
EXEC DATA0003.dbo.sp_addrolemember 'Full','test'
and execute it. this may solve the problem

quote:

---

Originally posted by Jasper Smith
EM uses SQLDMO and caches a lot of the information you see. In general this
is a good thing. I don't believe there is any way to alter the behaviour in
Enterprise Manager. See this note from BOL about SQLDMO collections
"To enable more efficient processing, SQL-DMO caches much of the information
about SQL Server components referenced by objects maintained in a
collection. When component data is cached, administrative activity of
another SQL Server session is not visible to the SQL-DMO session. The
Refresh method queries the organization server, filling the collection with
the most up-to-date component information."
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Bob Haines" <bhaines@.pahousegop.com> wrote in message
news:164f901c4173c$4c0e51e0$a501280a@.phx
.gbl...
> I run this code:
> EXEC DATA0003.dbo.sp_addlogin 'test','pwd'
> EXEC DATA0003.dbo.sp_grantdbaccess 'test'
> EXEC DATA0003.dbo.sp_addrolemember 'Full','test'
> When I go into enterprise and go to the properties of
> login and to Data Access Tab and select the Data0003
> (which is checked) I get this error:
> Error 21776:[SQL-DMO]The name 'test' was not found in the
> Users collection. If the name is a qualified name, use
> [] to separte various parts of the name, and try again.
> The only way I found to get rid of the error is to go to
> DATA0003 and select the users and refresh the list.
> Then, their is no problem.
> But, I would like to not have to go refresh user
> everytime I add a login.
> I would appreciate any help.
> Thanks in advance,
> Bob

---

Error 21776 and dbo Problem

Hello:
We recently installed a SQL 2000 version of an older
application we were running. The company took our old
Paradox data and converted it at their site and gave us a
backup to restore to a new database we created on our SQL
server.
After restoring the database, we began to get Error 15023
messages relating to the user and login that the
application uses to grant access to the database. After
some research, I used query analyzer to drop the
questionable users and logins and then re-created them
without a problem. However, we were still getting errors
when trying to connect to the database using the
application.
While troubleshooting the problem, I went to look at the
properties of the sa account and the system threw up
Error 21776-The name dbo was not found in the users
collection. If I try to add a dbo user account to the
database in question, I get Error 15023. I can't drop
and re-create the users and logins because SQL is telling
me I can't do this with a database owner. I can't use
sp_change_users_login because it involves the dbo account.
I don't know where to go from here.
Any comments or suggestions would be appreciated.
Thanks
BrennanHave you checked this article?
305711 BUG: DBO User Does Not Display in Enterprise Manager
http://support.microsoft.com/?id=305711
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.