ODBC Error

I am trying to reinstall MSQL Server 2000, but the
installation fails. The sqlstp.log has the message
below. I have reinstalled MDAC and the error persists. Can someone tell me
what is wrong and how to fix
it?
Sincerely,
Alvin
Starting Service ...
SQL_Latin1_General_CP1_CI_AS
-m -Q -T4022 -T3659
Connecting to Server ...
driver={sql
server};server=DENISPUTNAMTOSH;UID=sa;PWD=;databas e=master
[Microsoft][ODBC Driver Manager] Driver's SQLAllocHandle
on SQL_HANDLE_ENV failed
driver={sql
server};server=DENISPUTNAMTOSH;UID=sa;PWD=;databas e=master
[Microsoft][ODBC Driver Manager] Driver's SQLAllocHandle
on SQL_HANDLE_ENV failed
driver={sql
server};server=DENISPUTNAMTOSH;UID=sa;PWD=;databas e=master
[Microsoft][ODBC Driver Manager] Driver's SQLAllocHandle
on SQL_HANDLE_ENV failed
SQL Server configuration failed.Hi
What OS and Edition are you trying to install SQL Server on? Do you have
admin rights on the machine?
Regards
Mike
"Alvin" wrote:
> I am trying to reinstall MSQL Server 2000, but the
> installation fails. The sqlstp.log has the message
> below. I have reinstalled MDAC and the error persists. Can someone tell me
> what is wrong and how to fix
> it?
> Sincerely,
> Alvin
> Starting Service ...
> SQL_Latin1_General_CP1_CI_AS
> -m -Q -T4022 -T3659
> Connecting to Server ...
> driver={sql
> server};server=DENISPUTNAMTOSH;UID=sa;PWD=;databas e=master
> [Microsoft][ODBC Driver Manager] Driver's SQLAllocHandle
> on SQL_HANDLE_ENV failed
> driver={sql
> server};server=DENISPUTNAMTOSH;UID=sa;PWD=;databas e=master
> [Microsoft][ODBC Driver Manager] Driver's SQLAllocHandle
> on SQL_HANDLE_ENV failed
> driver={sql
> server};server=DENISPUTNAMTOSH;UID=sa;PWD=;databas e=master
> [Microsoft][ODBC Driver Manager] Driver's SQLAllocHandle
> on SQL_HANDLE_ENV failed
> SQL Server configuration failed.
>|||I am installing it on Server 2003 and yes, I have admin rights.
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> What OS and Edition are you trying to install SQL Server on? Do you have
> admin rights on the machine?
> Regards
> Mike
> "Alvin" wrote:
> > I am trying to reinstall MSQL Server 2000, but the
> > installation fails. The sqlstp.log has the message
> > below. I have reinstalled MDAC and the error persists. Can someone tell me
> > what is wrong and how to fix
> > it?
> >
> > Sincerely,
> > Alvin
> >
> > Starting Service ...
> >
> > SQL_Latin1_General_CP1_CI_AS
> >
> > -m -Q -T4022 -T3659
> >
> > Connecting to Server ...
> >
> > driver={sql
> > server};server=DENISPUTNAMTOSH;UID=sa;PWD=;databas e=master
> >
> > [Microsoft][ODBC Driver Manager] Driver's SQLAllocHandle
> > on SQL_HANDLE_ENV failed
> >
> > driver={sql
> > server};server=DENISPUTNAMTOSH;UID=sa;PWD=;databas e=master
> >
> > [Microsoft][ODBC Driver Manager] Driver's SQLAllocHandle
> > on SQL_HANDLE_ENV failed
> >
> > driver={sql
> > server};server=DENISPUTNAMTOSH;UID=sa;PWD=;databas e=master
> >
> > [Microsoft][ODBC Driver Manager] Driver's SQLAllocHandle
> > on SQL_HANDLE_ENV failed
> >
> > SQL Server configuration failed.
> >
> >

ODBC Error

Hi All,
I am getting the following error message when I am trying to connect to SQL 2000 Server from SQL 7 Server using BCP/OSQL/ISQL etc., Can any one help me in fixing this problem.
NULL
COULD NOT CONNECT TO SQL SERVER
NULL
SQLState: 08001 Native Error: 6
Info. Message: [Microsoft][ODBC SQL Server Driver][Named Pipes]Specified SQL server not found.
NULL
SQLState: 01000 Native Error: 53
Info. Message: [Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionOpen (CreateFile()).
Thanks & Regards
Balaji Prabhu.TBalaji,
What is the respective OS?Do you have only 'Named pipes' enabled?
--
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"Balaji Prabhu.T" <Balaji Prabhu.T@.discussions.microsoft.com> wrote in
message news:C15C3280-F0A5-418B-912B-018EE518AF14@.microsoft.com...
> Hi All,
> I am getting the following error message when I am trying to connect to
SQL 2000 Server from SQL 7 Server using BCP/OSQL/ISQL etc., Can any one help
me in fixing this problem.
> NULL
> COULD NOT CONNECT TO SQL SERVER
> NULL
> SQLState: 08001 Native Error: 6
> Info. Message: [Microsoft][ODBC SQL Server Driver][Named Pipes]Specified
SQL server not found.
> NULL
> SQLState: 01000 Native Error: 53
> Info. Message: [Microsoft][ODBC SQL Server Driver][Named
Pipes]ConnectionOpen (CreateFile()).
> Thanks & Regards
> Balaji Prabhu.T
>

ODBC Error

Does anyone have idea on how to reslove this error message
below.
Error Source 4, code 01000 10054
[microsoft][ODBC SQL SERVER Driver] [ TCP/IP Sockets]
ConnectionRead (recv())Hello!
This could be due to multiple reasons. Can you locate the ERRORLOG.* files
(found in the LOG sub-folder under the SQL Server installation folder) and
send it across? That might help establish if anything's wrong on the server
side.
Also:
- do you get this issue from all clients or is it specific to a set of
client(s)?
- do you receive this issue only when running a specific query? what are you
trying to execute when you experience this issue?
- are the client and server separated by any kind of network equipment like
a router / firewall?
- will the issue occur if you run the query locally on the server?
Thanks!
Arvind.
--
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-
This posting is provided "AS IS" with no warranties, and confers no rights.
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-
"Aboki" <hcokoli@.yahoo.com> wrote in message
news:6b8301c475a3$bfab9a70$a401280a@.phx.gbl...
> Does anyone have idea on how to reslove this error message
> below.
>
> Error Source 4, code 01000 10054
> [microsoft][ODBC SQL SERVER Driver] [ TCP/IP Sockets]
> ConnectionRead (recv())
>sql

ODBC Error

I'm getting an error message I've never seen before when I installed my
application on a client's machine.
I've got seven machines at this location that all work fine, when I install
on a new machine, I can connect through ODBC Administrator; but, when I try
to connect through the program I get this error message:
[ODBC SQL Server Driver][TCP/IP Sockets]SSL Security Error
[ODBC SQL Server Driver][TCP/IP
Sockets]ConnectionOpen(SECDoClientHandsh
ake()).
I've looked on KB and have not been able to find anything specific on this
problem.
Any ideas?
Thanks in advance.This might be the same issue reported in the KB article at the link
http://support.microsoft.com/defaul...b;en-us;Q322144
Regards,
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Regards,
Uwa Agbonile[MSFT]
"Dennis Powell" <dennis.powell@.monroe.XXXXXXXXX> wrote in message
news:OA6%23L0fYFHA.2128@.TK2MSFTNGP15.phx.gbl...
> I'm getting an error message I've never seen before when I installed my
> application on a client's machine.
> I've got seven machines at this location that all work fine, when I
install
> on a new machine, I can connect through ODBC Administrator; but, when I
try
> to connect through the program I get this error message:
> [ODBC SQL Server Driver][TCP/IP Sockets]SSL Security Error
> [ODBC SQL Server Driver][TCP/IP
> Sockets]ConnectionOpen(SECDoClientHandsh
ake()).
> I've looked on KB and have not been able to find anything specific on
this
> problem.
> Any ideas?
> Thanks in advance.
>

ODBC driver error

I am all of a sudden getting this error message on a
system, when trying to connect to sql server data:
Unable to load SQL Server ODBC driver resource DLL. The
application cannot continue.
I've reinstalled mdac (2.6 and 2.8), but this has not
helped. I need to get this system up and running asap, so
any help would be greatly appreciated.
Thank you,
Tom
PS I posted this first in the ODBC\data.odbc group, but
there doesn't appear to be too much activity there....Hi Tom,
Please check
http://mcse.ms/arch/66/2003/5/790826
http://mcse.ms/arch/66/2003/1/588214
Surely will help.
Sankar Renganathan
DBA, SPAR Group Inc.,
Please reply only to the newsgroups.
This posting is provided AS IS with no warranties, and confers no rights.
"TomT" <tomt@.tomt.com> wrote in message
news:03a901c3d8d7$8e9d5630$a101280a@.phx.gbl...

quote:

---

> I am all of a sudden getting this error message on a
> system, when trying to connect to sql server data:
> Unable to load SQL Server ODBC driver resource DLL. The
> application cannot continue.
> I've reinstalled mdac (2.6 and 2.8), but this has not
> helped. I need to get this system up and running asap, so
> any help would be greatly appreciated.
> Thank you,
> Tom
> PS I posted this first in the ODBC\data.odbc group, but
> there doesn't appear to be too much activity there....

---

|||Sankar,
Thanks for your help. I checked versions of the files,
and then replaced them since there was a mis-match.

quote:

---

>--Original Message--
>Hi Tom,
>Please check
>http://mcse.ms/arch/66/2003/5/790826
>http://mcse.ms/arch/66/2003/1/588214
>Surely will help.
>Sankar Renganathan
>DBA, SPAR Group Inc.,
>Please reply only to the newsgroups.
>This posting is provided AS IS with no warranties, and

---

confers no rights.

quote:

---

>
>"TomT" <tomt@.tomt.com> wrote in message
>news:03a901c3d8d7$8e9d5630$a101280a@.phx.gbl...
so[QUOTE]
>
>.
>

---

ODBC Connectivity problem in Sql Server2005

Hi,

I have created DSN connection with sql server authentication in Sql server 2005. There is message comes "Connection Succeeded".

After I try through my application again asking username and password for the DSN at run time. My application is developed in Powerbuilder 5.0.

The connection string as follows,

SQLCA.dbms= "ODBC"
SQLCA.dBparm = "CONNECTSTRING='DSN=ntm',APPNAME = 'ntm',uid='sa',pwd='sierra'"

Can you help me?

I'm not really sure what Powerbuilder syntax is, but did you try something like:
SQLCA.dBparm ="CONNECTSTRING='DSN=ntm;uid=sa;pwd=sierra'"|||

Thanks for your kind reply..

We have rectified that problem.

sql

ODBC Connectivity problem in Sql Server2005

Hi,

I have created DSN connection with sql server authentication in Sql server 2005. There is message comes "Connection Succeeded".

After I try through my application again asking username and password for the DSN at run time. My application is developed in Powerbuilder 5.0.

The connection string as follows,

SQLCA.dbms= "ODBC"
SQLCA.dBparm = "CONNECTSTRING='DSN=ntm',APPNAME = 'ntm',uid='sa',pwd='sierra'"

Can you help me?

I'm not really sure what Powerbuilder syntax is, but did you try something like:
SQLCA.dBparm ="CONNECTSTRING='DSN=ntm;uid=sa;pwd=sierra'"|||

Thanks for your kind reply..

We have rectified that problem.

ODBC connection to remote computer giving invalid instance() message

I am trying to set up a ODBC connection to a remote database using the ODBC data source administrator. I am getting an error message complaining of an invalid instance(). The database I am trying to connect to does have a default instance and a named instance. Do I need to specify the instance name somewhere in the connection settings? I tried specifying the server name as <Remote computer IP Address>/<Instance Name> but this didn't work. Any ideas?Hi,

make sure SQL Server Browser is running, otherwise you will have to name the port after the service name like in:

Data Source=Servername,SomePortnumber --> Data Source=SomeServer,1455 (e.g. for any non-default port settings)

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de|||

Note that it should be "<Remote computer IP Address>\<Instance Name>" rather than "<Remote computer IP Address>/<Instance Name>".

Can you connect to the default instance? What protocols are enabled? What's the actual error msg? Any firewall issue? Search firewall and browser posts on the forum would help.

|||Thanks for ideas. I think I needed to sleep on this one a bit! I looked at it again this morning and unticked the 'dynamically determine port' option in the network lib config of the ODBC connection setup and specified the port no. the instance is listening on. This worked!

ODBC Connection Problems

I'm having problems connecting to an MSDE database through ODBC.
The following message appears below:

Connection Failed:
SQL State: '01000'
SQL Server Error: 10061
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]
Connection Open (Connect())
Connection Failed:
SQL State '08001'
SQL Server Error 17
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL
Server does not exist or access denied

I've tried the following
1. Downloading the lastest version of MDAC.
2. Tried Pinging the server which was successful.
3. Setting up an ODBC connection to the server from another client which was successful.
4. Adding an entry in my hosts file to see the server.
5. Searching the archives for a solution.

Does anyone have any other ideas as I stumped?

Thanks.Are you sure you have declared the full server (and instance) name for the MSDE instance? Check services on the MSDE box, and look for MSSQL$___. The ___ is the instance name. Also, are you able to connect to the MSDE instance with any other tools (Query Analyzer, OSQL, etc.)?|||It's quite embarrassing but someone put the wrong IP address label on the server. Thanks for your help.|||As fate would have it, I am encountering a very similar problem. Everything was working fine and dandy up until two days ago when suddenly you were unable to connect to SQLServer.

At first, you were able to connect via EM but not Query Analyzer. Now suddenly you're unable to connect using either. This literally happened overnight. I'm gettign the same error message as referenced above. I'm able to ping the box just fine, but cannot isql into it or use Query Analyzer/EM.

I'm running SQL2K on SP3 / Windows 2000 Advanced Server.

ANY suggestions would be greatly appreciated.

P.S. - One of the boxes is a development box and one is a production machine. I have considered installing MDAC 8 on the dev machine to see if this does the trick. Has this worked for anyone else who was having a similar problem, and what - if any - were the side effects?

Thanks again!|||...also forgot to mention that I'm unable to create an ODBC connection to the servers as well.

Thanx

ODBC

I am getting this message in my SQL Server Agent Error
Log. What does it mean[165] ODBC Error: 11, General
network error. Check your network documentation. [SQLSTATE
08S01]I've have seen this before. It could be a time-out.

Occasional "Timeout expired" message - on SP that should take 1 second

Hi there,
I've got something kind of weird going on. I have a stored procedure that
normally takes less than one second to execute, but it has started taking
over 30 seconds from time to time.
The SP is called by an ASP page on a web server, running on a separate
machine. The database server is running SQL Server 2000. The ASP page
makes an ODBC connection, using TCP/IP and creates & sends the stored
procedure call.
From time to time, something goes haywire, and the ASP page returns
[Microsoft][ODBC SQL Server Driver]Timeout expired
Then, the ASP page will not work no matter what we do, even if we leave it a
day or two. (No locks on the database, sometimes not even any connections!)
The only way to fix it is to run the stored procedure through Query
Analyzer. It will take a little over 30 seconds, but finish successfully.
Then, if I run the exact same SP again, it will complete in 0 seconds, and
the web page will work fine again.
I've seen this before, but I cannot for the life of me remember what we did
to fix it. We tried changing the ODBC connection to Named Pipes instead of
TCP/IP but that didn't help.
Any suggestions?
BeverleyI am having the same issue and the solution provided by SQL crafter in the S
ql Server Timeout expired post is not working. Could someone help us with t
his issue?
Thanks,
Rick|||I have been struggling with a similar problem for a couple of weeks and came
to this group in search of a solution. Perhaps a pooling of information
will help.
In my situation, I have a VB interactive front-end on multiple machines
accessing a SQL2K database through ODBC over TCP/IP. It has been in service
for over 2 years and the master table now has over 750K records in it.
Recently we started receiving occasional "Timeout Expired" errors in pretty
much the same manner as you describe -- a query that would normally take
1-2 seconds would suddenly take over 90 and crap out. I ran database
integrity checks, reconstructed the indexes, created additional indexes, ran
numerous original and reconfigured queries through the Index Analyzer. And
of course spent hours trying various searches in the MS KB. I have reached
the following conclusions:
The problem (in my case, at least) originates with the Query Optimizer. A
very specific query run through the Query Analyzer will *always* select an
appropriate index or mix of indexes. The *identical* query submitted
through ODBC, however, will sometimes select a completely inappropriate
index mix, or no index at all, wind up executing full-table scans or other
time-wasting substitutes, and time out. This effect, I suspect, is a
permanent feature of MSSQL, but does not manifest on smaller tables because
the malfunction does not cause a timeout on smaller tables, just an
inexcusable waste of time.
I proved this theory by adding index hints to my ODBC-originated queries
(which Books Online says should never be necessary), and observing the
performance stabilize. Problem is, I consider this a completely hokey
solution since if I ever decide to reconfigure my indexes, I will have
dozens of coordinating code changes to perform. Also, there are several
queries in which I cannot use index hints because the query requires
column-level 'OR'-ing with which hints are incompatible.
So I am still looking for a "proper" solution from one of you out there, or
at least an acknowledgment from MS that this is a behavioral issue with
SQL2K that needs to be addressed.
- Fred
"Beverley" <ali_webitems@.hotmail.com> wrote in message
news:OpxbH$K9DHA.712@.tk2msftngp13.phx.gbl...
> Hi there,
> I've got something kind of weird going on. I have a stored procedure that
> normally takes less than one second to execute, but it has started taking
> over 30 seconds from time to time.
> The SP is called by an ASP page on a web server, running on a separate
> machine. The database server is running SQL Server 2000. The ASP page
> makes an ODBC connection, using TCP/IP and creates & sends the stored
> procedure call.
> From time to time, something goes haywire, and the ASP page returns
> [Microsoft][ODBC SQL Server Driver]Timeout expired
> Then, the ASP page will not work no matter what we do, even if we leave it
a
> day or two. (No locks on the database, sometimes not even any
connections!)
> The only way to fix it is to run the stored procedure through Query
> Analyzer. It will take a little over 30 seconds, but finish successfully.
> Then, if I run the exact same SP again, it will complete in 0 seconds, and
> the web page will work fine again.
> I've seen this before, but I cannot for the life of me remember what we
did
> to fix it. We tried changing the ODBC connection to Named Pipes instead
of
> TCP/IP but that didn't help.
> Any suggestions?
> Beverley
>|||I have been struggling with a similar problem for a couple of weeks and
came
to this group in search of a solution. Perhaps a pooling of information
will help.
In my situation, I have a VB interactive front-end on multiple machines
accessing a SQL2K database through ODBC over TCP/IP. It has been in
service
for over 2 years and the master table now has over 750K records in it.
Recently we started receiving occasional "Timeout Expired" errors in pretty
much the same manner as you describe -- a query that would normally take
1-2 seconds would suddenly take over 90 and crap out. I ran database
integrity checks, reconstructed the indexes, created additional indexes,
ran
numerous original and reconfigured queries through the Index Analyzer. And
of course spent hours trying various searches in the MS KB. I have reached
the following conclusions:
The problem (in my case, at least) originates with the Query Optimizer. A
very specific query run through the Query Analyzer will *always* select an
appropriate index or mix of indexes. The *identical* query submitted
through ODBC, however, will sometimes select a completely inappropriate
index mix, or no index at all, wind up executing full-table scans or other
time-wasting substitutes, and time out. This effect, I suspect, is a
permanent feature of MSSQL, but does not manifest on smaller tables because
the malfunction does not cause a timeout on smaller tables, just an
inexcusable waste of time.
I proved this theory by adding index hints to my ODBC-originated queries
(which Books Online says should never be necessary), and observing the
performance stabilize. Problem is, I consider this a completely hokey
solution since if I ever decide to reconfigure my indexes, I will have
dozens of coordinating code changes to perform. Also, there are several
queries in which I cannot use index hints because the query requires
column-level 'OR'-ing with which hints are incompatible.
So I am still looking for a "proper" solution from one of you out there, or
at least an acknowledgment from MS that this is a behavioral issue with
SQL2K that needs to be addressed.
- ITFred|||ITFRED, have you found a solution to your problem at all'
I have a similar problem, I also get the *occasional timeout*.
Mine is an ASP web application connected to MSDE, and the application
gets a timeout error occasionally when the ASP code tries to update
many records in a table, but smaller tables work fine.
The error message is:
> Error Number -214xxxxxx, ODBC SQL Server Driver timeout expired.
In a testing environment on a dev server, the same ASP application
connects to a SQL2K database and it has NOT encountered any problems.
My conclusion is (thanks to all your posts I have read) that it is in
ODBC connections where the MSDE engine times out.
Can anyone please come up with a solution!'
Is using a different database an option, perhaps mysql or postgreSQL?
Thanks.
huge
ITFred wrote:
> *I have been struggling with a similar problem for a couple of weeks
> and
> came
> to this group in search of a solution. Perhaps a pooling of
> information
> will help.
> In my situation, I have a VB interactive front-end on multiple
> machines
> accessing a SQL2K database through ODBC over TCP/IP. It has been in
> service
> for over 2 years and the master table now has over 750K records in
> it.
> Recently we started receiving occasional "Timeout Expired" errors in
> pretty
> much the same manner as you describe -- a query that would normally
> take
> 1-2 seconds would suddenly take over 90 and crap out. I ran
> database
> integrity checks, reconstructed the indexes, created additional
> indexes,
> ran
> numerous original and reconfigured queries through the Index
> Analyzer. And
> of course spent hours trying various searches in the MS KB. I have
> reached
> the following conclusions:
> The problem (in my case, at least) originates with the Query
> Optimizer. A
> very specific query run through the Query Analyzer will *always*
> select an
> appropriate index or mix of indexes. The *identical* query
> submitted
> through ODBC, however, will sometimes select a completely
> inappropriate
> index mix, or no index at all, wind up executing full-table scans or
> other
> time-wasting substitutes, and time out. This effect, I suspect, is
> a
> permanent feature of MSSQL, but does not manifest on smaller tables
> because
> the malfunction does not cause a timeout on smaller tables, just an
> inexcusable waste of time.
> I proved this theory by adding index hints to my ODBC-originated
> queries
> (which Books Online says should never be necessary), and observing
> the
> performance stabilize. Problem is, I consider this a completely
> hokey
> solution since if I ever decide to reconfigure my indexes, I will
> have
> dozens of coordinating code changes to perform. Also, there are
> several
> queries in which I cannot use index hints because the query requires
> column-level 'OR'-ing with which hints are incompatible.
> So I am still looking for a "proper" solution from one of you out
> there, or
> at least an acknowledgment from MS that this is a behavioral issue
> with
> SQL2K that needs to be addressed.
> - ITFred *
huge
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message397556.html

Obtaining Hotfix

We're experiencing the problem describe in MS Knowledge
Base Article - 812915 "Performance monitor shared memory
setup failed: -1" error message when you start SQL
Server. The article states there is a support hotfix
available through Microsoft Product Support Services.
We're currently evaulating SQL server so we're using the
Enterprise Evaluation Edition. We like to obtain the
hotfix ( preferably for free ), but since we have
evaluation edition we don't know how to go about this.
Can we get the hotfix?
(a) I don't think you can apply patches and hotfixes to the evaluation
edition, but I'm not 100% positive. Did you install the latest release of
the evaluation edition, or have you been running it for a while?
(b) you can't just bypass product support and download a hotfix "for
free"... if it's a bug, and you can demonstrate to PSS that you are affected
by it, then you will be provided the file and refunded the cost of the call.
http://www.aspfaq.com/
(Reverse address to reply.)
"J" <anonymous@.discussions.microsoft.com> wrote in message
news:886b01c49606$7e287f90$a501280a@.phx.gbl...
> We're experiencing the problem describe in MS Knowledge
> Base Article - 812915 "Performance monitor shared memory
> setup failed: -1" error message when you start SQL
> Server. The article states there is a support hotfix
> available through Microsoft Product Support Services.
> We're currently evaulating SQL server so we're using the
> Enterprise Evaluation Edition. We like to obtain the
> hotfix ( preferably for free ), but since we have
> evaluation edition we don't know how to go about this.
> Can we get the hotfix?

Obtained an error when performing a dbcc on an sms database

An error occurred while executing the following
query: "DBCC CHECKCATALOG([sms_055])".
SQL error number: "09E8".
SQL error message: "DBCC results for 'sms_055'.
".
Thanks for your help in advance!!It seems you didn't execute the DBCC from Query Analyzer (QA doesn't return error number in hex).
The actual error from SQL Server isn't included here, so we cannot comment on what the problem might
be. I suggest that you execute the DBCC from Query Analyzer and post the full output here. Pls add
WITH NO_INFOMSGS so you don't get all those informational messages.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Maria Garcia" <garcim@.miamidade.gov> wrote in message
news:472801c3e438$9778be40$a001280a@.phx.gbl...
> An error occurred while executing the following
> query: "DBCC CHECKCATALOG([sms_055])".
> SQL error number: "09E8".
> SQL error message: "DBCC results for 'sms_055'.
> ".
> Thanks for your help in advance!!

Obtained an error when performing a dbcc on an sms database

An error occurred while executing the following
query: "DBCC CHECKCATALOG([sms_055])".
SQL error number: "09E8".
SQL error message: "DBCC results for 'sms_055'.
".
Thanks for your help in advance!!It seems you didn't execute the DBCC from Query Analyzer (QA doesn't return
error number in hex).
The actual error from SQL Server isn't included here, so we cannot comment o
n what the problem might
be. I suggest that you execute the DBCC from Query Analyzer and post the ful
l output here. Pls add
WITH NO_INFOMSGS so you don't get all those informational messages.
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=...ls
erver
"Maria Garcia" <garcim@.miamidade.gov> wrote in message
news:472801c3e438$9778be40$a001280a@.phx.gbl...

quote:

---

> An error occurred while executing the following
> query: "DBCC CHECKCATALOG([sms_055])".
> SQL error number: "09E8".
> SQL error message: "DBCC results for 'sms_055'.
> ".
> Thanks for your help in advance!!

---