Invalid object name when trying to access sql server through vb ap

Hi,
We're in the process of migrating our live server (Windows NT Server 4.0 sql
6.5) to windows 2003 and sql server 2000.
I've setup a test server running windows 2000 and sql server 6.5, i've
copied the database across to the dev server and fixed the orphaned logins
and made sure the database is consistent which has come out fine.
when we try to acess the database with our vb app we get the error invalid
object name dbo.table name, i think this is something to do with permissions
so i granted myself select access onto the problem table but i still get the
same error, i then granted myself select access onto all the tables and i
still get the same error.
is there another permission that i need to enable?
played around with restoring the msdb database from the live server to the
dev server then going in on single user mode to restor the master from the
live server to the dev server but it all goes pear shaped and i've got to
completely re-install 6.5
any help/advice would be appreciated
thanks
lavan
hi don't worry, i've solved it, i forget to se tthe default database so the
app was going straight to master.
cheers anyway
"lavann" wrote:

> Hi,
> We're in the process of migrating our live server (Windows NT Server 4.0 sql
> 6.5) to windows 2003 and sql server 2000.
> I've setup a test server running windows 2000 and sql server 6.5, i've
> copied the database across to the dev server and fixed the orphaned logins
> and made sure the database is consistent which has come out fine.
> when we try to acess the database with our vb app we get the error invalid
> object name dbo.table name, i think this is something to do with permissions
> so i granted myself select access onto the problem table but i still get the
> same error, i then granted myself select access onto all the tables and i
> still get the same error.
> is there another permission that i need to enable?
> played around with restoring the msdb database from the live server to the
> dev server then going in on single user mode to restor the master from the
> live server to the dev server but it all goes pear shaped and i've got to
> completely re-install 6.5
> any help/advice would be appreciated
> thanks
> lavan

Invalid object name 'ctsv_F9F22D34FACE4A1BA4D2B061ADBEE5C1'

Hi,
I've a replication in a SQL Server 2000 to syncronize with a SQL CE 2.0.
When I try to update a row, I get this error: Invalid object name
'ctsv_F9F22D34FACE4A1BA4D2B061ADBEE5C1'
I get this error if I try to modify a row from enterprise manager too!
Can you help me please?
Thanks!
your merge replication metadata is out of sync. Script out your publication,
drop your publication, and then recreate it from script.
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
"Andrea Grandi" <andrea@.nospam.com> wrote in message
news:uytKvf$TFHA.1796@.TK2MSFTNGP15.phx.gbl...
> Hi,
> I've a replication in a SQL Server 2000 to syncronize with a SQL CE 2.0.
> When I try to update a row, I get this error: Invalid object name
> 'ctsv_F9F22D34FACE4A1BA4D2B061ADBEE5C1'
> I get this error if I try to modify a row from enterprise manager too!
> Can you help me please?
> Thanks!
|||Hi,

> your merge replication metadata is out of sync. Script out your publication,
> drop your publication, and then recreate it from script.
wich script? Can I drop/create from Enterprise Manager?
Anyway, now I've another problem... I exported only the 4 tables I was
interested in to another instance. I dropped the whole database and
re-imported the 4 tables. Now I cannot write on those tables
I tried to remove the rowguid column but I get this error "rowguid
column is not valid". I know it's not valid, I removed it!
Is there a way to fix my database?
Thanks!
|||Most probably some artefacts are left on you tables, such as merge replication triggers. They try to write to replication views, but views are not existing..
If triggers are not there, then we should think about something else..
Regards,
Kestutis Adomavicius
Consultant
UAB "Baltic Software Solutions"
"Andrea Grandi" <andrea@.nospam.com> wrote in message news:%23EqCibBUFHA.3076@.TK2MSFTNGP12.phx.gbl...
Hi,

> your merge replication metadata is out of sync. Script out your publication,
> drop your publication, and then recreate it from script.
wich script? Can I drop/create from Enterprise Manager?
Anyway, now I've another problem... I exported only the 4 tables I was
interested in to another instance. I dropped the whole database and
re-imported the 4 tables. Now I cannot write on those tables
I tried to remove the rowguid column but I get this error "rowguid
column is not valid". I know it's not valid, I removed it!
Is there a way to fix my database?
Thanks!

Invalid Descriptor Index problem

I've successfully set up replication on two servers, but the third one
is giving me problems. Naturally, the first two were development test
servers and the last one is the customer's server. It's a Win2000
server, with SP4. The SQL Server version is 8.00.760 (SP3). I
upgraded MDAC last night to 2.8, so the SQL Server ODBC version is
2000.85.1022.00.
I am trying to set up transactional publications between databases.
When they initialize--before the first transaction can run--I get the
Invalid Descriptor Index error. If anyone can help, please do!
(Please reply to the group, so that all who search may benefit from
your wisdom.)
I ran distrib from the command line with OutputVerboseLevel set to 2.
The command I used was:
>distrib -Publisher SQL1S -PublisherDB B_DB_Copy -Subscriber SQL1S
>-OutputVerboseLevel 2 -DistributorLogin sa -DistributorPassword
><password_removed> -SubscriberDB RC_DB_Copy -SubscriberLogin sa
>-SubscriberPassword <password_removed> -Distributor SQL1S
>-SubscriptionType 0 -SubscriptionTableName reg_geo_cfg
>-Publication B_DB_Copy
Here's the result (sanitized so the customer won't get mad):
Microsoft SQL Server Distribution Agent 8.00.760
Copyright (c) 2000 Microsoft Corporation
Connecting to Distributor 'SQL1S'
Connecting to Distributor 'SQL1S.'
[6/10/2004 10:14:50 PM]SQL1S.: exec sp_helpdistpublisher N'SQL1S'
[6/10/2004 10:14:50 PM]SQL1S.distribution: select @.@.SERVERNAME
Server: SQL1S
DBMS: Microsoft SQL Server
Version: 08.00.0760
user name: dbo
API conformance: 2
SQL conformance: 1
transaction capable: 2
read only: N
identifier quote char: "
non_nullable_columns: 1
owner usage: 31
max table name len: 128
max column name len: 128
need long data len: Y
max columns in table: 1024
max columns in index: 16
max char literal len: 524288
max statement len: 524288
max row size: 524288
[6/10/2004 10:14:50 PM]SQL1S.distribution: execute sp_server_info 18
ANSI codepage: 1
[6/10/2004 10:14:50 PM]SQL1S.distribution: select datasource, srvid
from master..sysservers where upper(srvname) = upper(N'SQL1S')
[6/10/2004 10:14:50 PM]SQL1S.distribution: {?=call
sp_MShelp_subscriber_info (N'SQL1S', N'SQL1S')}
Subscriber security mode: 0, login name: sa.
[6/10/2004 10:14:50 PM]SQL1S.distribution: select datasource, srvid
from master..sysservers where upper(srvname) = upper(N'SQL1S')
[6/10/2004 10:14:50 PM]SQL1S.distribution: {call
sp_MShelp_distribution_agentid(0, N'B_DB_Copy', N'B_DB_Copy', 0,
N'RC_DB_Copy', 0)}
Agent message code 20046. Invalid Descriptor Index
[6/10/2004 10:14:50 PM]SQL1S.distribution: {call
sp_MSadd_distribution_history(1, 6, ?, ?, 0, 0, 0.00, 0x01, 1, ?, -1,
0x01, 0x01)}
Adding alert to msdb..sysreplicationalerts: ErrorId = 3,
Transaction Seqno = 0000000000000000000000000000, Command ID = -1
Message: Replication-Replication Distribution Subsystem: agent
SQL1S-BDBCopy-B_DB_Copy-SQL1S-1 failed. Invalid Descriptor
Index[6/10/2004 10:14:50 PM]SQL1S.distribution: {call
sp_MSadd_repl_alert(3, 1, 3, 14151, ?, -1, N'SQL1S', N'B_DB_Copy',
N'SQL1S', N'RC_DB_Copy', ?)}
ErrorId = 3, SourceTypeId = 4
ErrorCode = 'S1002'
ErrorText = 'Invalid Descriptor Index'
[6/10/2004 10:14:50 PM]SQL1S.distribution: {call
sp_MSadd_repl_error(3, 0, 4, ?, N'S1002', ?)}
Category:ODBC
Source: ODBC SQL Server Driver
Number: S1002
Message: Invalid Descriptor Index
Disconnecting from Distributor History 'SQL1S'
The process finished. Use CTRL+C to close this window.
there have been reports that this problem has been solved by reapplying the
latest sp (sp3a).
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"KenRobertson" <google.nospam.roberken@.spamgourmet.com> wrote in message
news:4c25a332.0406110528.5bfd7b97@.posting.google.c om...
> I've successfully set up replication on two servers, but the third one
> is giving me problems. Naturally, the first two were development test
> servers and the last one is the customer's server. It's a Win2000
> server, with SP4. The SQL Server version is 8.00.760 (SP3). I
> upgraded MDAC last night to 2.8, so the SQL Server ODBC version is
> 2000.85.1022.00.
> I am trying to set up transactional publications between databases.
> When they initialize--before the first transaction can run--I get the
> Invalid Descriptor Index error. If anyone can help, please do!
> (Please reply to the group, so that all who search may benefit from
> your wisdom.)
> I ran distrib from the command line with OutputVerboseLevel set to 2.
> The command I used was:
> Here's the result (sanitized so the customer won't get mad):
> Microsoft SQL Server Distribution Agent 8.00.760
> Copyright (c) 2000 Microsoft Corporation
> Connecting to Distributor 'SQL1S'
> Connecting to Distributor 'SQL1S.'
> [6/10/2004 10:14:50 PM]SQL1S.: exec sp_helpdistpublisher N'SQL1S'
> [6/10/2004 10:14:50 PM]SQL1S.distribution: select @.@.SERVERNAME
> Server: SQL1S
> DBMS: Microsoft SQL Server
> Version: 08.00.0760
> user name: dbo
> API conformance: 2
> SQL conformance: 1
> transaction capable: 2
> read only: N
> identifier quote char: "
> non_nullable_columns: 1
> owner usage: 31
> max table name len: 128
> max column name len: 128
> need long data len: Y
> max columns in table: 1024
> max columns in index: 16
> max char literal len: 524288
> max statement len: 524288
> max row size: 524288
> [6/10/2004 10:14:50 PM]SQL1S.distribution: execute sp_server_info 18
> ANSI codepage: 1
> [6/10/2004 10:14:50 PM]SQL1S.distribution: select datasource, srvid
> from master..sysservers where upper(srvname) = upper(N'SQL1S')
> [6/10/2004 10:14:50 PM]SQL1S.distribution: {?=call
> sp_MShelp_subscriber_info (N'SQL1S', N'SQL1S')}
> Subscriber security mode: 0, login name: sa.
> [6/10/2004 10:14:50 PM]SQL1S.distribution: select datasource, srvid
> from master..sysservers where upper(srvname) = upper(N'SQL1S')
> [6/10/2004 10:14:50 PM]SQL1S.distribution: {call
> sp_MShelp_distribution_agentid(0, N'B_DB_Copy', N'B_DB_Copy', 0,
> N'RC_DB_Copy', 0)}
> Agent message code 20046. Invalid Descriptor Index
> [6/10/2004 10:14:50 PM]SQL1S.distribution: {call
> sp_MSadd_distribution_history(1, 6, ?, ?, 0, 0, 0.00, 0x01, 1, ?, -1,
> 0x01, 0x01)}
> Adding alert to msdb..sysreplicationalerts: ErrorId = 3,
> Transaction Seqno = 0000000000000000000000000000, Command ID = -1
> Message: Replication-Replication Distribution Subsystem: agent
> SQL1S-BDBCopy-B_DB_Copy-SQL1S-1 failed. Invalid Descriptor
> Index[6/10/2004 10:14:50 PM]SQL1S.distribution: {call
> sp_MSadd_repl_alert(3, 1, 3, 14151, ?, -1, N'SQL1S', N'B_DB_Copy',
> N'SQL1S', N'RC_DB_Copy', ?)}
> ErrorId = 3, SourceTypeId = 4
> ErrorCode = 'S1002'
> ErrorText = 'Invalid Descriptor Index'
> [6/10/2004 10:14:50 PM]SQL1S.distribution: {call
> sp_MSadd_repl_error(3, 0, 4, ?, N'S1002', ?)}
> Category:ODBC
> Source: ODBC SQL Server Driver
> Number: S1002
> Message: Invalid Descriptor Index
> Disconnecting from Distributor History 'SQL1S'
>
> The process finished. Use CTRL+C to close this window.
|||Reapplying the service pack worked. Thank you for your help!!
"Hilary Cotter" <hilaryk@.att.net> wrote in message news:<uO#U0aWUEHA.3664@.TK2MSFTNGP12.phx.gbl>...[vbcol=seagreen]
> there have been reports that this problem has been solved by reapplying the
> latest sp (sp3a).
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "KenRobertson" <google.nospam.roberken@.spamgourmet.com> wrote in message
> news:4c25a332.0406110528.5bfd7b97@.posting.google.c om...

'Invalid cursor state' error when saving table changes

I've created a small DB (one table so far, 0 records as yet). When I try to
change the table structure via Enterprise Manager, I get the following
error:
/*
05 August 2004 16:02:36
User:
Server: HYPERION
Database: TADB
Application: MS SQLEM - Data Tools
*/
'TANumbers' table
- Unable to rename column from 'AdviceNoteID' to 'AdviceNote'.
ODBC error: [Microsoft][ODBC SQL Server Driver]Invalid cursor state
The actual change I was trying to do worked, or at least it appears to have
done.
BOL suggest that this error might be due to the fact that the DB or the Tlog
is full. With no data an no transactions so far, that is unlikely. Plus EM
reports that there is 8.43 Mb free out of 10Mb!
Any ideas anyone?
Thanks
Chris
Hi CJM,
From your descriptions, I understood you could not rename your column name
by SQL Server Enterprise Manager. Have I understood you? If there is
anything I misunderstood, please feel free to let me know.
Admittedly, it is a known issue for us when using SQL Server Enterprise
Manager. You will have to use sp_rename in Query Analyzer instead. I am
sorry for the inconvenience you may encounter.
More information of how to use sp_rename could be found in BooksOnline or
MSDN Online
sp_rename
http://msdn.microsoft.com/library/de...us/tsqlref/ts_
sp_ra-rz_3ns5.asp
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!
|||Hi,
I'm just curious as to why *this* table on *this* DB suffers from this
problem?
I've never had a problem on this server before, so what is it about this DB
that is so different?
Chris
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in message
news:v5%23isS4eEHA.1060@.cpmsftngxa06.phx.gbl...
> Hi CJM,
> From your descriptions, I understood you could not rename your column name
> by SQL Server Enterprise Manager. Have I understood you? If there is
> anything I misunderstood, please feel free to let me know.
> Admittedly, it is a known issue for us when using SQL Server Enterprise
> Manager. You will have to use sp_rename in Query Analyzer instead. I am
> sorry for the inconvenience you may encounter.
> More information of how to use sp_rename could be found in BooksOnline or
> MSDN Online
> sp_rename
>
http://msdn.microsoft.com/library/de...us/tsqlref/ts_
> sp_ra-rz_3ns5.asp
>
|||Hi CJM,
This issue was reported in SP3 and higher version, it was fixed in SQL
Server 8.00.902
It is very possible that changes of columns are made successfully before
you upgrade to SQL Server SP3 .
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!
|||""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in message
news:k37x%23bDfEHA.3212@.cpmsftngxa06.phx.gbl...
> Hi CJM,
> This issue was reported in SP3 and higher version, it was fixed in SQL
> Server 8.00.902
> It is very possible that changes of columns are made successfully before
> you upgrade to SQL Server SP3 .
>
I'm a bit confused...
How do I get hold of v8.00.902? I thought I was up to date with SP3a...
Chris
|||Hi Chris,
Thanks for your prompt updates!
For 8.00.0902 or higher, a supported fix is now available from Microsoft,
but it is only intended to correct the problem that is described in this
article. Apply it only to systems that are experiencing this specific
problem.
To resolve this problem, please contact Microsoft Product Support Services
to obtain the fix. For a complete list of Microsoft Product Support
Services phone numbers and information about support costs, visit the
following Microsoft Web site:
http://support.microsoft.com/default...EN-US;CNTACTMS
Asking hotfix will be a FREE case. If PSS staff asking a KB for this issue,
please show me the link and KB No below
FIX: Profiler RPC events truncate parameters that have a text data type to
16 characters
http://support.microsoft.com/?id=839688
You will receive Build 8.00.0927 instead from PSS, based on my testing,
this hotfix could resolved the problm as you described. BTW, I cannot find
excatly Build 8.00.0902 and its relative KB internal
If you want PSS Staff be notified of this newsgroup thread, show him the
following information
Tomcat IssueID: 24064701
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!
|||Mingqing,
I've downloaded, installed & tested the patch and everything works fine now.
Thanks
Chris
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in message
news:c6mfgnofEHA.1200@.cpmsftngxa06.phx.gbl...
> Hi Chris,
> Thanks for your prompt updates!
> For 8.00.0902 or higher, a supported fix is now available from Microsoft,
> but it is only intended to correct the problem that is described in this
> article. Apply it only to systems that are experiencing this specific
> problem.
>
|||Hi Chris,
It's great to hear that you have resolved it! Thanks for your kindest reply
letting me know the status of your issue.
If you encounter any questions or difficulties using SQL Server, please
feel free to post here. We are always here to be of assistance!
Thanks again for using MSDN Managed Newsgroup!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!