Hi,
I have setup snapshot pull replication between SQL2000 (publisher) and
MSDE2000 (subscriber).
The following error "Invalid Descriptor Index" is occuring on the
subscriber. Would someone please tell me what this error means and how to
get around it?
Thanks
reapply sp3 on the subscriber.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"mm" <postto@.news.com> wrote in message
news:u8luytqlEHA.2492@.TK2MSFTNGP15.phx.gbl...
> Hi,
> I have setup snapshot pull replication between SQL2000 (publisher) and
> MSDE2000 (subscriber).
> The following error "Invalid Descriptor Index" is occuring on the
> subscriber. Would someone please tell me what this error means and how to
> get around it?
> Thanks
>
Showing posts with label sql2000. Show all posts
Showing posts with label sql2000. Show all posts
Monday, March 19, 2012
Monday, March 12, 2012
Invalid Connection to SQL2000 after installing SP3
After having installed SP3 on SQL 2000 server standard edition running
on Windows 2000 server, users cannot access the database whether
through Enterprise Manager, Query Analyser, or my application.
It was running fine before. Users are running Windows XP. The database
is a named instance and is used for replication. Funny enough, I may
access the database from my development machine which is running
Windows 2000 server.
Help is most welcome
PatrickPatrick,
What are the symptoms? What does "users cannot access the database"
mean? Does it time-out, do they get an error? Please paste the error
message.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Patrick wrote:
> After having installed SP3 on SQL 2000 server standard edition running
> on Windows 2000 server, users cannot access the database whether
> through Enterprise Manager, Query Analyser, or my application.
> It was running fine before. Users are running Windows XP. The database
> is a named instance and is used for replication. Funny enough, I may
> access the database from my development machine which is running
> Windows 2000 server.
> Help is most welcome
> Patrick|||Mark,
Thank you for your interest in our problem. The error message is just
"Invalid Connection". The server is running SQL server 2000 with sp3 n
Windows server 2000.
the client are running Windows XP pro.
Best Regards
Patrick
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!|||Patrick,
Connect from Query Analyzer and paste the message here, you will get
something more than "Invalid Connection".
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Patrick Menage wrote:
> Mark,
> Thank you for your interest in our problem. The error message is just
> "Invalid Connection". The server is running SQL server 2000 with sp3 n
> Windows server 2000.
> the client are running Windows XP pro.
> Best Regards
> Patrick
> *** Sent via Developersdex http://www.codecomments.com ***
> Don't just participate in USENET...get rewarded for it!|||> Thank you for your interest in our problem. The error message is just
> "Invalid Connection".
? What software is giving this "error message"?
http://www.aspfaq.com/
(Reverse address to reply.)|||I have just found the solution. There was another SQL server instance
running with the same port number. I changed it and everythings is
working fine.
Thank you for your support.
Best Regards
Patrick
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
on Windows 2000 server, users cannot access the database whether
through Enterprise Manager, Query Analyser, or my application.
It was running fine before. Users are running Windows XP. The database
is a named instance and is used for replication. Funny enough, I may
access the database from my development machine which is running
Windows 2000 server.
Help is most welcome
PatrickPatrick,
What are the symptoms? What does "users cannot access the database"
mean? Does it time-out, do they get an error? Please paste the error
message.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Patrick wrote:
> After having installed SP3 on SQL 2000 server standard edition running
> on Windows 2000 server, users cannot access the database whether
> through Enterprise Manager, Query Analyser, or my application.
> It was running fine before. Users are running Windows XP. The database
> is a named instance and is used for replication. Funny enough, I may
> access the database from my development machine which is running
> Windows 2000 server.
> Help is most welcome
> Patrick|||Mark,
Thank you for your interest in our problem. The error message is just
"Invalid Connection". The server is running SQL server 2000 with sp3 n
Windows server 2000.
the client are running Windows XP pro.
Best Regards
Patrick
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!|||Patrick,
Connect from Query Analyzer and paste the message here, you will get
something more than "Invalid Connection".
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Patrick Menage wrote:
> Mark,
> Thank you for your interest in our problem. The error message is just
> "Invalid Connection". The server is running SQL server 2000 with sp3 n
> Windows server 2000.
> the client are running Windows XP pro.
> Best Regards
> Patrick
> *** Sent via Developersdex http://www.codecomments.com ***
> Don't just participate in USENET...get rewarded for it!|||> Thank you for your interest in our problem. The error message is just
> "Invalid Connection".
? What software is giving this "error message"?
http://www.aspfaq.com/
(Reverse address to reply.)|||I have just found the solution. There was another SQL server instance
running with the same port number. I changed it and everythings is
working fine.
Thank you for your support.
Best Regards
Patrick
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
Invalid Connection to SQL2000 after installing SP3
After having installed SP3 on SQL 2000 server standard edition running
on Windows 2000 server, users cannot access the database whether
through Enterprise Manager, Query Analyser, or my application.
It was running fine before. Users are running Windows XP. The database
is a named instance and is used for replication. Funny enough, I may
access the database from my development machine which is running
Windows 2000 server.
Help is most welcome
PatrickPatrick,
What are the symptoms? What does "users cannot access the database"
mean? Does it time-out, do they get an error? Please paste the error
message.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Patrick wrote:
> After having installed SP3 on SQL 2000 server standard edition running
> on Windows 2000 server, users cannot access the database whether
> through Enterprise Manager, Query Analyser, or my application.
> It was running fine before. Users are running Windows XP. The database
> is a named instance and is used for replication. Funny enough, I may
> access the database from my development machine which is running
> Windows 2000 server.
> Help is most welcome
> Patrick
on Windows 2000 server, users cannot access the database whether
through Enterprise Manager, Query Analyser, or my application.
It was running fine before. Users are running Windows XP. The database
is a named instance and is used for replication. Funny enough, I may
access the database from my development machine which is running
Windows 2000 server.
Help is most welcome
PatrickPatrick,
What are the symptoms? What does "users cannot access the database"
mean? Does it time-out, do they get an error? Please paste the error
message.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Patrick wrote:
> After having installed SP3 on SQL 2000 server standard edition running
> on Windows 2000 server, users cannot access the database whether
> through Enterprise Manager, Query Analyser, or my application.
> It was running fine before. Users are running Windows XP. The database
> is a named instance and is used for replication. Funny enough, I may
> access the database from my development machine which is running
> Windows 2000 server.
> Help is most welcome
> Patrick
Invalid Connection to SQL2000 after installing SP3
After having installed SP3 on SQL 2000 server standard edition running
on Windows 2000 server, users cannot access the database whether
through Enterprise Manager, Query Analyser, or my application.
It was running fine before. Users are running Windows XP. The database
is a named instance and is used for replication. Funny enough, I may
access the database from my development machine which is running
Windows 2000 server.
Help is most welcome
Patrick
Patrick,
What are the symptoms? What does "users cannot access the database"
mean? Does it time-out, do they get an error? Please paste the error
message.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Patrick wrote:
> After having installed SP3 on SQL 2000 server standard edition running
> on Windows 2000 server, users cannot access the database whether
> through Enterprise Manager, Query Analyser, or my application.
> It was running fine before. Users are running Windows XP. The database
> is a named instance and is used for replication. Funny enough, I may
> access the database from my development machine which is running
> Windows 2000 server.
> Help is most welcome
> Patrick
|||Mark,
Thank you for your interest in our problem. The error message is just
"Invalid Connection". The server is running SQL server 2000 with sp3 n
Windows server 2000.
the client are running windows XP pro.
Best Regards
Patrick
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||Patrick,
Connect from Query Analyzer and paste the message here, you will get
something more than "Invalid Connection".
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Patrick Menage wrote:
> Mark,
> Thank you for your interest in our problem. The error message is just
> "Invalid Connection". The server is running SQL server 2000 with sp3 n
> Windows server 2000.
> the client are running windows XP pro.
> Best Regards
> Patrick
> *** Sent via Developersdex http://www.codecomments.com ***
> Don't just participate in USENET...get rewarded for it!
|||> Thank you for your interest in our problem. The error message is just
> "Invalid Connection".
? What software is giving this "error message"?
http://www.aspfaq.com/
(Reverse address to reply.)
|||I have just found the solution. There was another SQL server instance
running with the same port number. I changed it and everythings is
working fine.
Thank you for your support.
Best Regards
Patrick
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
on Windows 2000 server, users cannot access the database whether
through Enterprise Manager, Query Analyser, or my application.
It was running fine before. Users are running Windows XP. The database
is a named instance and is used for replication. Funny enough, I may
access the database from my development machine which is running
Windows 2000 server.
Help is most welcome
Patrick
Patrick,
What are the symptoms? What does "users cannot access the database"
mean? Does it time-out, do they get an error? Please paste the error
message.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Patrick wrote:
> After having installed SP3 on SQL 2000 server standard edition running
> on Windows 2000 server, users cannot access the database whether
> through Enterprise Manager, Query Analyser, or my application.
> It was running fine before. Users are running Windows XP. The database
> is a named instance and is used for replication. Funny enough, I may
> access the database from my development machine which is running
> Windows 2000 server.
> Help is most welcome
> Patrick
|||Mark,
Thank you for your interest in our problem. The error message is just
"Invalid Connection". The server is running SQL server 2000 with sp3 n
Windows server 2000.
the client are running windows XP pro.
Best Regards
Patrick
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||Patrick,
Connect from Query Analyzer and paste the message here, you will get
something more than "Invalid Connection".
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Patrick Menage wrote:
> Mark,
> Thank you for your interest in our problem. The error message is just
> "Invalid Connection". The server is running SQL server 2000 with sp3 n
> Windows server 2000.
> the client are running windows XP pro.
> Best Regards
> Patrick
> *** Sent via Developersdex http://www.codecomments.com ***
> Don't just participate in USENET...get rewarded for it!
|||> Thank you for your interest in our problem. The error message is just
> "Invalid Connection".
? What software is giving this "error message"?
http://www.aspfaq.com/
(Reverse address to reply.)
|||I have just found the solution. There was another SQL server instance
running with the same port number. I changed it and everythings is
working fine.
Thank you for your support.
Best Regards
Patrick
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
Sunday, February 19, 2012
Interrogating lock information...
I'm working on a PB / OLE DB / SQL2000 application architecture. Here is my requirement:
I need to find out if/how I can interrogate a SQL2000 database for its locking information, with a fairly high degree of granularity. That is to say I'd want to extract the following info:
TABLE LOCK:
--> The name of the table thats locked. (this I can get from SYS tables...)
PAGE LOCK:
--> The table and the row or range of rows that are locked.
ROW LOCK:
--> The table and the row (RId or physical key) that is locked.
My understanding is that rows that are locked as part of a page lock, or a row that is rowlocked, is managed internally within the DBMS. Any one of the three lock types will register e.g. on the SYSLOCKS table, but only specifies the name of the locked object (i.e. table name, index, etc...).
Is my only real solution to create my own custom locking info table(s)? I don't strongly favor that sort of solution, because the code to properly manage such a table would be pretty ambitious to write, and prone to corruption at some point no matter how well we build it.
Are there any inventive solutions out there?All the tools to do that are at your finguretips, - PerfMon, DBCC, Profiler, and QA. Look into sp_lock stored procedure that will point you to master.dbo.syslocks and master.dbo.syslockinfo. Look into perfmon counters as well as various profiler templates.
I need to find out if/how I can interrogate a SQL2000 database for its locking information, with a fairly high degree of granularity. That is to say I'd want to extract the following info:
TABLE LOCK:
--> The name of the table thats locked. (this I can get from SYS tables...)
PAGE LOCK:
--> The table and the row or range of rows that are locked.
ROW LOCK:
--> The table and the row (RId or physical key) that is locked.
My understanding is that rows that are locked as part of a page lock, or a row that is rowlocked, is managed internally within the DBMS. Any one of the three lock types will register e.g. on the SYSLOCKS table, but only specifies the name of the locked object (i.e. table name, index, etc...).
Is my only real solution to create my own custom locking info table(s)? I don't strongly favor that sort of solution, because the code to properly manage such a table would be pretty ambitious to write, and prone to corruption at some point no matter how well we build it.
Are there any inventive solutions out there?All the tools to do that are at your finguretips, - PerfMon, DBCC, Profiler, and QA. Look into sp_lock stored procedure that will point you to master.dbo.syslocks and master.dbo.syslockinfo. Look into perfmon counters as well as various profiler templates.
Subscribe to:
Posts (Atom)