connection problem

Hi.
I have installed Microsoft SQL Server Desktop on Windows XP Pro. I can
connect to database from remote machines with Windows 98Se, but i can't
connect from machines with Windows XP.
ChrisI think that it is a problem with not having the 'correct' client network
utilities installed.
On the Start menu, select [All Programs], [Microsoft SQL Server], th
en
[Client Network Utility].
In the [Enabled Protocols] window, you should have both TCP/IP and Named
Pipes.
If one is missing, select the missing protocol from the list on the left
side, and click the [Enable] button.
Hopefully, if my memory is correct, that will take care of the problem.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Krzysztof" <colinkj@.poczta.onet.pl> wrote in message
news:eb0a61$jov$1@.nemesis.news.tpi.pl...
> Hi.
> I have installed Microsoft SQL Server Desktop on Windows XP Pro. I can
> connect to database from remote machines with Windows 98Se, but i can't
> connect from machines with Windows XP.
> Chris
>
>|||Have you tried temporarily disabling the firewall on the XP machines?
John Opincar
john.opincar@.sundesksoftware.com
"Krzysztof" <colinkj@.poczta.onet.pl> wrote in message
news:eb0a61$jov$1@.nemesis.news.tpi.pl...
> Hi.
> I have installed Microsoft SQL Server Desktop on Windows XP Pro. I can
> connect to database from remote machines with Windows 98Se, but i can't
> connect from machines with Windows XP.
> Chris
>
>

connection problem

I am a newbie to SQL server. I have installed SQL server on my PC. I have created a local server on my machine. When i go to the SQL server wizard to register my server and it gives me the option to connect i am getting the message: SQL server does not exist or access denied. Now i was told that this may be due to my firewall. I have turned these off..and am still getting the message.
Please help
JohnHi John,
What was the authentication mode that you selected while installing the SQL
Server ?
If you have created in Mixed mode, What is the SA Password ?
Is it blank ?
Did you create a named instance or is it the default instance ?
If you have created a named instance, what is the name that you
have assigned to this new instance ?
Just a step by step info, in case you have missed one.
1. "Select a Server" Step
If your instllation is the default installation, then
type your computer name for the "Available Servers" and click on
Add.
If your installation is the Named instance, then
type the server name as "Computername\InstanceName" for the
"Available Servers" and click on ADD.
2. "Select an Authentication Mode" step
If you have selected Mixed Mode authentication, then select
"The SQL Server Login information that was assigned to me by
the system administrator"
3. If you select SQL Server login, you get this additional step "Select
Connection Option"
select first option "Login Automatically using my SQL Server account
information"
Login Name : SA
Password : <The password that you have set> or leave it
blank, if you had set it blank.
4. "Select SQL Server Group" step
select "Add the SQL Server(s) to an existing SQL Server Group".
5. Click on Finish, to get connected to the SQL Server.
With this simple steps you should be able to register the SQL Server in
Enterprise Manager.
HTH
Ashish
This posting is provided "AS IS" with no warranties, and confers no rights.

connection problem

I am a newbie to SQL server. I have installed SQL server on my PC. I have created a local server on my machine. When i go to the SQL server wizard to register my server and it gives me the option to connect i am getting the message: SQL server does not ex
ist or access denied. Now i was told that this may be due to my firewall. I have turned these off..and am still getting the message.
Please help?
John
Hi John,
What was the authentication mode that you selected while installing the SQL
Server ?
If you have created in Mixed mode, What is the SA Password ?
Is it blank ?
Did you create a named instance or is it the default instance ?
If you have created a named instance, what is the name that you
have assigned to this new instance ?
Just a step by step info, in case you have missed one.
1. "Select a Server" Step
If your instllation is the default installation, then
type your computer name for the "Available Servers" and click on
Add.
If your installation is the Named instance, then
type the server name as "Computername\InstanceName" for the
"Available Servers" and click on ADD.
2. "Select an Authentication Mode" step
If you have selected Mixed Mode authentication, then select
"The SQL Server Login information that was assigned to me by
the system administrator"
3. If you select SQL Server login, you get this additional step "Select
Connection Option"
select first option "Login Automatically using my SQL Server account
information"
Login Name : SA
Password : <The password that you have set> or leave it
blank, if you had set it blank.
4. "Select SQL Server Group" step
select "Add the SQL Server(s) to an existing SQL Server Group".
5. Click on Finish, to get connected to the SQL Server.
With this simple steps you should be able to register the SQL Server in
Enterprise Manager.
HTH
Ashish
This posting is provided "AS IS" with no warranties, and confers no rights.

connection problem

I am a newbie to SQL server. I have installed SQL server on my PC. I have cr
eated a local server on my machine. When i go to the SQL server wizard to re
gister my server and it gives me the option to connect i am getting the mess
age: SQL server does not ex
ist or access denied. Now i was told that this may be due to my firewall. I
have turned these off..and am still getting the message.
Please help?
JohnHi John,
What was the authentication mode that you selected while installing the SQL
Server ?
If you have created in Mixed mode, What is the SA Password ?
Is it blank ?
Did you create a named instance or is it the default instance ?
If you have created a named instance, what is the name that you
have assigned to this new instance ?
Just a step by step info, in case you have missed one.
1. "Select a Server" Step
If your instllation is the default installation, then
type your computer name for the "Available Servers" and click on
Add.
If your installation is the Named instance, then
type the server name as "Computername\InstanceName" for the
"Available Servers" and click on ADD.
2. "Select an Authentication Mode" step
If you have selected Mixed Mode authentication, then select
"The SQL Server Login information that was assigned to me by
the system administrator"
3. If you select SQL Server login, you get this additional step "Select
Connection Option"
select first option "Login Automatically using my SQL Server account
information"
Login Name : SA
Password : <The password that you have set> or leave it
blank, if you had set it blank.
4. "Select SQL Server Group" step
select "Add the SQL Server(s) to an existing SQL Server Group".
5. Click on Finish, to get connected to the SQL Server.
With this simple steps you should be able to register the SQL Server in
Enterprise Manager.
HTH
Ashish
This posting is provided "AS IS" with no warranties, and confers no rights.

Connection over VPN

I have MSDE server installed on a pc at work. This PC runs Windows XP and
runs as a VPN server as well.
I have SQL Server Enterpise Manager on my laptop, and need to be able to
manage the MSDE server when connected to work from home, using a VPN.
When I try to add the server in Enterprise Manager, it says access is denied
or server is unavailable. I have read a lot of posts about using named
pipes, opening port 1723 but none of these have worked for me.
Any ideas please?
Tom
I suspect your actual error message was "sql server does not exist or
access denied". There are many potential causes as outlined in this article:
328306 INF: Potential Causes of the "SQL Server Does Not Exist or Access
http://support.microsoft.com/?id=328306
If the problem is only with VPNs I would probably concentrate on ports that
are blocked for VPN connections or permissions that are different for VPN
connections.
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.

Connection over VPN

I have MSDE server installed on a pc at work. This PC runs Windows XP and
runs as a VPN server as well.
I have SQL Server Enterpise Manager on my laptop, and need to be able to
manage the MSDE server when connected to work from home, using a VPN.
When I try to add the server in Enterprise Manager, it says access is denied
or server is unavailable. I have read a lot of posts about using named
pipes, opening port 1723 but none of these have worked for me.
Any ideas please?
TomI suspect your actual error message was "sql server does not exist or
access denied". There are many potential causes as outlined in this article:
328306 INF: Potential Causes of the "SQL Server Does Not Exist or Access
http://support.microsoft.com/?id=328306
If the problem is only with VPNs I would probably concentrate on ports that
are blocked for VPN connections or permissions that are different for VPN
connections.
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.

Connection Managers not installed?

apologies if this is the wrong group ..

whenever I create an Integrated Services project and attempt to add a Connection Manager I get the error

Connection Manager 'blah' is not properly installed on this computer.

(Microsoft.DataTransformationServices.Design)

This happens with all menu options except New Connection..

I have uninstalled and reinstalled both Visual Studio 2005 and SQL Server 2005 and made sure I have selected everything in each case

what am I missing?

Thanks

Chris

seems this has happened to others

see Jason Lodice thread for solution

Chris

Connection Issues To Report Services

Hello all,

I just installed the SQL 2k5 standard suite of services on a w2k3 enterprise edition server. All went well except for the connection to the reporting server. I get the error below.

"No connection could be made because the target machine actively refused it"

I can't seem to find any information on this error and have no clue where to even start. I've done 10+ installations of this software on various machines and have not encountered this error on any of them.

I have uninstalled, then reinstalled the reporting services and still no solution. All connection attempts are being made on the actual server, not from a desktop. sp1 for sql 2k5 is also installed, if that helps.

Windows Firewall is off.

What web searches I've done have turned up nothing useful. I'm pretty good at figuring this stuff out but this error provides very little of any use.

Anyone out there have any ideas?

Thanks in advance,

Greg

Have you seen this page: http://www.sqljunkies.com/WebLog/edwardm/ ?|||

First, thanks for the link. I'll make note of the ports used by SSAS and some of the other information in there.

I did figure this out, though. Not a very scientific approach so I'll have to run into this problem again to verify but, at a minimum, backing up the encryption key from within Reporting Services Configuration seemed to do the trick. I had a few other things out of whack, too.

At one point, the Backup option was disabled, but disabling "Web Server and HTTP Access" via SQL Server Surface Area Configuration -> Surface Area Configuration for Feature -> Reporting Services enabled the Backup button (kind of a round-about way of making that happen).

After backing up the encryption key, I enabled that option and could connect after that. Problem Solved!

This was further complicated by the fact that the reporting services install didn't conform to some "default" system configuration and performed only a "files-only" install. I really didn't pay that much attention during the install and the difference never really registered in my mind. So, I had to manually configure the reporting server (web directories, db connections, dbs and all).

So, chalk this up to experience and I'll know the next time I run into this.

Other things I addressed, but I'm not sure were relevant were:

the state of the IIS Admin and WWW publishing services (these were stopped and in manual mode during the install - I would think the install would start these if needed)

The execution permissions and application protection modes of the reporting server virtual directories (these were different on the problem installation than a "default" installation - an install on another machine that did work fine)

I don't think I needed to do the reporting services re-install.

When creating the databases manually, I ended up having to do that with scripts. For some reason, the database creation was timing out. The creation of the two databases was ok, but the reporting server temp db did not have any objects in it (no tables, views, etc).

There are a myriad of other things, but I'm almost certain these weren't relevant. All-in-all, a hassle.

Greg

|||Greg: Thanks for your post. I have a problem getting SSRS to work on one of my servers, too. I posted on Sunday:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1215786&SiteID=1
but no one answered. In my case, the local SSRS does not even appear in the list of servers to initialize, within the RS Config Manager. When I installed SSRS, I got the message "Reporting Services was installed, but not configured". This was on a reinstall of SQL05 needed to place the files on a drive other than C:

I will see if backing up the key fixes my problem, next time I'm at that site.|||I'm back at the server with the problem. When I run RS Config Mgr, the button to back up the encryption key is disabled. The only enabled buttons on that page are the 'Restore' button, and the 'Delete' (delete encrypted content) button.

I tried disabling HTTP and Web Access using the Surface Area tool, but the 'Backup' button is still disabled.

Any ideas on how to diagnose and fix this?|||

Hmm. That's what I did. One other thing you might try is deleting the encrypted content. At some point in my troubleshooting process, I pressed that button. I would assume that if encrypted content did exist, and you didn't have the proper encryption key to restore from, the encrypted content would be un-accessible (that's rather obvious). I was comfortable deleting encrypted content because the installation was new and there was nothing to lose.

After doing that, you could then go throught the HTTP and Web Access routine again.

|||No luck for me. Could not get the 'Backup' button enabled on the Encryption Key page. I found in the event log I'm getting EventID 7000 from the RS Service saying "...cannot connect to the report server database". I tried scripting out the DB creation and running that separately. The script ran without errors, but I still get the connection failure event.

I tried running "rsconfig.exe -t -c -d SSRS -a windows -s mssqlserver", where SSRS is my RS db name and mssqlserver is the SQL Server instance name (the default instance), and it came back with "The command completed successfully"

Now since running rsconfig, in the GUI version, RS Configuration Mgr, I'm getting error popups saying it can't connect to SQL Server at all. The popups say it was trying to connect using named pipes. I went to the Surface Area tool and enabled named pipes on remote connections, but RS Config Mgr still can't connect.

It seems like my installation is hosed. I thought Crystal Enterprise was hard to use, but this SSRS is worse! I'm open to suggestions. Does anyone know a reliable way to configure the db connection for Reporting Services?|||I uninstalled and reinstalled the Reporting Services components. This at least allowed RS Config Mgr to connect to SQL Server. However, when I attempt to create a new database for RS, each step succeeds except the last one. For the "Setting Connection Info for the Reporting Server" task, there

was a yellow '!', with the explanation, "Although saving the database

connection succeeded, the report server cannot access internal

information about this deployment to determine if the current

configuration is valid for this edition. ..." The RS Service is still logging errors in the event log saying it cannot connect. I give up.

connection issue from our developer

Hi,
SQL 2005 EE is installed on W2k3 box and firewall is off in this server.
From my client machine, my window account and that developer window account
all can login into this server with ODBC, sql client, telent to 1433 or VS
connection. But, this developer can't login to SQL server from him machine
with any appliction. He is in the same domain as server and my machine. I
don't know what's the reason to cause this issue now.
Please advise. Thank you.
Lynn
Best Regards,
Lynn
What is the exact error message and error number he gets
when he tries to log into SQL Server?
-Sue
On Thu, 22 Mar 2007 10:33:45 -0700, Lynn
<Lynn@.discussions.microsoft.com> wrote:

>Hi,
>SQL 2005 EE is installed on W2k3 box and firewall is off in this server.
>From my client machine, my window account and that developer window account
>all can login into this server with ODBC, sql client, telent to 1433 or VS
>connection. But, this developer can't login to SQL server from him machine
>with any appliction. He is in the same domain as server and my machine. I
>don't know what's the reason to cause this issue now.
>Please advise. Thank you.
>Lynn
|||We only enable Shared Memory and TCP/IP protocal in server side. And, those
are the error they are getting.
osql -- SQL server doesn't exist or access denied
Query Analyzer -- General network error. Check your network documentation
VS 2005 -- (without specifing TCP protocal in connection) A connection was
succssfully established with the server, but then an error occured during the
pre-login handshake. When connecting ....(provider: Named Pipes provider,
error: 0 - No process is on the ther end of the pipe)
VS 2005 -- (specify TCP protocal in connection) An error has occurred while
establishing a connection to the server. When connecting to SQL server 2005,
this failure may be caused by the fact that under the default settings ...
(provider: TCP provider: 0 -- A connection attempt failed because the
connected party didn't not properly respond after a period of tiem, or
established connection failed because connected host has failed to respond.)
Again, this developer is able to login by using my machine with his WIN
account.
After I enable Named Pipes in server. This developer is able to connect to
server on his machine by using Named Pipe.
Firewall is off in the server, so I can't think of the issue for TCP
connection on developer's machine.
Please advise. Thank you.
Best Regards,
Lynn
"Sue Hoegemeier" wrote:

> What is the exact error message and error number he gets
> when he tries to log into SQL Server?
> -Sue
> On Thu, 22 Mar 2007 10:33:45 -0700, Lynn
> <Lynn@.discussions.microsoft.com> wrote:
>
>
|||Check the following article in Books Online:
http://msdn2.microsoft.com/en-us/library/ms175496.aspx
-Sue
On Fri, 23 Mar 2007 09:15:08 -0700, Lynn
<Lynn@.discussions.microsoft.com> wrote:

>We only enable Shared Memory and TCP/IP protocal in server side. And, those
>are the error they are getting.
>osql -- SQL server doesn't exist or access denied
>Query Analyzer -- General network error. Check your network documentation
>VS 2005 -- (without specifing TCP protocal in connection) A connection was
>succssfully established with the server, but then an error occured during the
>pre-login handshake. When connecting ....(provider: Named Pipes provider,
>error: 0 - No process is on the ther end of the pipe)
>VS 2005 -- (specify TCP protocal in connection) An error has occurred while
>establishing a connection to the server. When connecting to SQL server 2005,
>this failure may be caused by the fact that under the default settings ...
>(provider: TCP provider: 0 -- A connection attempt failed because the
>connected party didn't not properly respond after a period of tiem, or
>established connection failed because connected host has failed to respond.)
>Again, this developer is able to login by using my machine with his WIN
>account.
>After I enable Named Pipes in server. This developer is able to connect to
>server on his machine by using Named Pipe.
>Firewall is off in the server, so I can't think of the issue for TCP
>connection on developer's machine.
>Please advise. Thank you.
|||Sue,
The developer's client protocol order is TCP and NP. We didn't enable Named
Pipe in server at the beginning, that's why the first message is NP message
due to client will try to connect in the protocol order in the client. As I
menetioned, after I turn on Named Pipes in server, user's machine is able to
connect to server. But, the issue our developers had is that they couldn't
connect with TCP protocol from their machine. (I can connect by TCP protocol
from my machine. The developer login to my machine and his win account can
connect to the server as well). His machine is able to connect to our SQL
2000 with TCP protocol, but just can't connect to 2005 with TCP protocol. I
was thinging is firewall in server to caused this issue, but firewall didn't
enable in the server at all. So, I don't know what cause the issue.
Please advise.
Best Regards,
Lynn
"Sue Hoegemeier" wrote:

> Check the following article in Books Online:
> http://msdn2.microsoft.com/en-us/library/ms175496.aspx
> -Sue
> On Fri, 23 Mar 2007 09:15:08 -0700, Lynn
> <Lynn@.discussions.microsoft.com> wrote:
>
>
|||When you get symptoms like this where it only affects the
user on a particular PC then you need to look at that PC.
You'd probably start by testing basic connectivity to the
server from the PC: Can the user ping the server by name,
can the user ping the server by IP, what network related
issues are found in the Event logs on the PC, can the user
connect to the server using sqlcmd, etc. Also, have you
tried logging in from that users PC?
If you find that the issue is comes up only with Management
Studio, have the user increase the connect timeout in SSMS:
When logging on, click on the options button in the Connect
to Server window and increase the connection timeout to
something greater than the 15 second default.
It would also be worth checking the users MDAC installation
using the component checker. You can download this from:
http://msdn2.microsoft.com/en-us/data/aa937730.aspx
You may also want to look at applying the latest SQL Server
service pack to the client on that PC having problems.
-Sue
On Thu, 29 Mar 2007 15:38:05 -0700, Lynn
<Lynn@.discussions.microsoft.com> wrote:

>Sue,
>The developer's client protocol order is TCP and NP. We didn't enable Named
>Pipe in server at the beginning, that's why the first message is NP message
>due to client will try to connect in the protocol order in the client. As I
>menetioned, after I turn on Named Pipes in server, user's machine is able to
>connect to server. But, the issue our developers had is that they couldn't
>connect with TCP protocol from their machine. (I can connect by TCP protocol
>from my machine. The developer login to my machine and his win account can
>connect to the server as well). His machine is able to connect to our SQL
>2000 with TCP protocol, but just can't connect to 2005 with TCP protocol. I
>was thinging is firewall in server to caused this issue, but firewall didn't
>enable in the server at all. So, I don't know what cause the issue.
>Please advise.
|||Sue,
Thank you again. Definitely, we already checked the network connect from
those developers machine. The connection issue happens to all related
developers. The developers were able to ping the server by name and IP from
their machine. But, the issue only happened on connecting to SQL 2005 with
TCP protocol. We tested through ODBC (with TCP/IP), osql, telnet to 1433
port, VS, but all connection were failed.
One developer already reinstall SQL 2005 client, but the problem is still
resisted. Will ask them to update to sp2 and go from there.
Best Regards,
Lynn
"Sue Hoegemeier" wrote:

> When you get symptoms like this where it only affects the
> user on a particular PC then you need to look at that PC.
> You'd probably start by testing basic connectivity to the
> server from the PC: Can the user ping the server by name,
> can the user ping the server by IP, what network related
> issues are found in the Event logs on the PC, can the user
> connect to the server using sqlcmd, etc. Also, have you
> tried logging in from that users PC?
> If you find that the issue is comes up only with Management
> Studio, have the user increase the connect timeout in SSMS:
> When logging on, click on the options button in the Connect
> to Server window and increase the connection timeout to
> something greater than the 15 second default.
> It would also be worth checking the users MDAC installation
> using the component checker. You can download this from:
> http://msdn2.microsoft.com/en-us/data/aa937730.aspx
> You may also want to look at applying the latest SQL Server
> service pack to the client on that PC having problems.
> -Sue

Connection Issue

I am a novice and have SQL 2k5 installed on my server running windows SBS 2003. I am able to connect to the database from my workstation and I am able to view all the fields of the database but I am not able to view any of the records contained in the database. Can someone please guide me. I need to be able to view add and delete records using Access as a front end program to SQL. Thank you.

How are you connecting to the server? What 'client tool' are you using? (Visual Studio, SSMS, QA, etc.)

|||I am connecting to the server via an intranet enviroment and I am logged on with administrator properties.|||

The most important thing to note is how you are connecting, like windows Authentication or with a SQL username and password.

If you can connect to the SQL Server and see some of the fields, and schema, then depending on the way you are connecting it could be that the user does not have access to SELECT from the tables.

If you are using Access to connect, you should be able to do what you want to do if you are using the appropriate permissions inside SQL for your tables.

Ben Miller

|||

Thank you!

I reset all the ODBC connections and I was able to view the data. Your response was very helpful. Thank you once more.

connection going to sleep?

Ok, here's the scenario. On a Windows 2003 Server I have MSSQL 2000
installed. On another test server I have Windows 2003 server, IIS 6 and
Coldfusion installed. There has been an account created in SQL and assigned
permissions. My coldfusion web site makes multiple calls to the database
server using the account created. All is wonderful. Then, all of a sudden
I start getting connection problems (SQL STATE: HTY00). My web site cannot
connect using that account. I can still ping the SQL server from the
development server so I know thats not the problem. So I tried creating an
ODBC connection using that account. Same error. Sometimes resetting the
password in SQL works. A few days ago, however, I had to reboot the SQL
server and now everything is fine again, until the next time. Can anyone
explain to me why that user account seems to "goes to sleep" every few
days' There have been occasions when it's been fine for a week or two
but sooner or later, it will always do this!when you're dealing with connection problems it helps to do things like:
* try the connection from a different client
* check to see if you can connect from other accounts
* check to see if you can connect from a Windows and/or SQL authenticated
account
* check the SQL Server error logs for messages....
--
Brian Moran
Principal Mentor
Solid Quality Learning
SQL Server MVP
http://www.solidqualitylearning.com
"Steve" <StephenGL@.sabian.ca> wrote in message
news:5Lovb.33154$R13.985896@.ursa-nb00s0.nbnet.nb.ca...
> Ok, here's the scenario. On a Windows 2003 Server I have MSSQL 2000
> installed. On another test server I have Windows 2003 server, IIS 6 and
> Coldfusion installed. There has been an account created in SQL and
assigned
> permissions. My coldfusion web site makes multiple calls to the database
> server using the account created. All is wonderful. Then, all of a
sudden
> I start getting connection problems (SQL STATE: HTY00). My web site
cannot
> connect using that account. I can still ping the SQL server from the
> development server so I know thats not the problem. So I tried creating
an
> ODBC connection using that account. Same error. Sometimes resetting the
> password in SQL works. A few days ago, however, I had to reboot the SQL
> server and now everything is fine again, until the next time. Can anyone
> explain to me why that user account seems to "goes to sleep" every few
> days' There have been occasions when it's been fine for a week or two
> but sooner or later, it will always do this!
>

connection from the pool

I build an asp.net 2.0 (VS 2005) web application and put it on the server. The installed SQL server is SQL server 2003. I get this error message when i keep the application running for 10 or 15 mins. "Timeout expired. The timeout period elapsed prior obtaining a connection from the pool. This may have occure because all pooled connections were in use and max pool size was reached."

I made the server timeout unlimited but the error keeps coming up after some time of openning the application. The application session time out redirects the user to the login page and doesn't throw an error like the one i mentioned above.

Any idea. Thanks in advance.

designstudio,

try increasing the number of connections in the pool. in your connection string, here is an example

conn.ConnectionString = "integratedsecurity=SSPI;SERVER=YOUR_SERVER;DATABASE=YOUR_DB_NAME;Min Pool Size=5;Max PoolSize=60;Connect Timeout=2;";

see where it says max pool size = ...have you tried that?

hope this helps -- jp

|||

Thanks jdingo,

I haven't tried that. I think it will work.

I'll let you know if it doesn't work.

|||

Thanks jdingo,

I haven't tried that. I think it will work.

I'll let you know if it doesn't work.

|||

You might also want to ensure that you really are closing all connections. The best way to ensure this is to use the 'using' statement in C#, or a try-finally combination where you explicitly close the connection in the finally block.

string connectionString = GetConnectionString(); // Gets the connection string in some way defined by youusing (SqlConnection connection =new SqlConnection(connectionString)){ connection.Open();// Do whatever needs to be doing. When the using-block is exited, the connection // objects Dispose() method will be called, ensure that the connection is returned // to the pool. Even if an exception occurs.}

Connection failure on MSDE 2000/XP installation

We have installed MSDE 2000 on XP For Tablet PC. All
applications that use ODBC to connect to the database work
well, however those applications that use either DBLIB or
E/SQL (embedded SQL built on top of DBLIB) return a "Failed
to get DBPROCESS" error. MSDE was installed with
SQL-Authentication and all apps are started locally on the
server running MSDE. All applications run succesfully under
SQL 2000. Using SQL Profiler to trace application-activity
results in NO events being logged/traced, suggesting that
no SQL commands ever reach the server. Any ideas ?
If they are connecting via tcp/ip, do you have an exception in the firewall
(presuming XP SP2 is installed)?
Is the protocol they are connecting on enabled? (see svrnetcn.exe).
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Fintan" <anonymous@.discussions.microsoft.com> wrote in message
news:074001c5356f$36253fe0$a401280a@.phx.gbl...
> We have installed MSDE 2000 on XP For Tablet PC. All
> applications that use ODBC to connect to the database work
> well, however those applications that use either DBLIB or
> E/SQL (embedded SQL built on top of DBLIB) return a "Failed
> to get DBPROCESS" error. MSDE was installed with
> SQL-Authentication and all apps are started locally on the
> server running MSDE. All applications run succesfully under
> SQL 2000. Using SQL Profiler to trace application-activity
> results in NO events being logged/traced, suggesting that
> no SQL commands ever reach the server. Any ideas ?
>

connection failure

Hi all,
Everything is fine until today.
I have two instances(both msde databases, but I have enterprise manager and
analyser installed) on my computer one instance is mssql and the other is
mssql$netsdk (asp.net starter kit database)
somehow the connection to mssql$netsdk is failed which display in enterprise
manager.
So I removed the origianl server registration and start a new one, I type
"BETTYPC\NETSDK" as server and using windows authentication when doing the
registration, but the message display at the last step:
sql server registration failed because of connection failure displayed
below:sqldumpexceptionhandler :process 53 generated a fatal exception
c0000005 EXCEPTION_ACCESS_VIOLATION, sql server is terminating this process.
what's the problem?
Can you help and I am desperated
Betty
Hi Bettys,
Welcome to use MSDN Managed Newsgroup!
From your descriptions, I understood you are not able to connect the SQL
Server named instance NETSDK with error message EXCEPTION_ACCESS_VIOLATION.
If I have misunderstood your concern, please feel free to point it out.
AV errors could be caused by various reasons, please perform the steps
below and let me know the result
1. Check the log file of NETSDK instance, make sure whether the instance
was started correctly.
Defautly, the log will be located at C:\Program Files\Microsoft SQL
Server\MSSQL$NETSDK\log, you may paste them here or send to me directly
v-mingqc@.ONLINEmicrosoft.com if you have concerns on security. (Note that
REMOVE ONLINE in my email address before you click SEND)
2. Is it possible to connect the instance via OSQL and Query Analyzer?
3. Is it possible for you to connect via SQL Authentication?
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
================================================== ====
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Hi Michael,
Thank you, this is the first post on this forum. I didn't know what went
wrong. The only thing I can do is googling. Then it came to my mind that I
can stop the mssql@.netsdk sql server then and I restarted. It just started
and stopped again somehow. And then I have to restart the computer. After
that I saw both instances have sqlservr.exe process. This time I register the
server again and it looks fine. Connection is OK.
(I didn't try to use osql and did try to use sql authentication, but when I
supplied one userID and password to this server, this password is set up to a
database on this server, it should be OK right? it didn't work either.)
If you can tell what was going on, that will be great.
Here is the paste from errorLog:
2006-02-02 13:12:54.28 server Microsoft SQL Server 2000 - 8.00.760
(Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 1)
2006-02-02 13:12:54.28 server Copyright (C) 1988-2002 Microsoft
Corporation.
2006-02-02 13:12:54.28 server All rights reserved.
2006-02-02 13:12:54.28 server Server Process ID is 2988.
2006-02-02 13:12:54.28 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL$NETSDK\LOG\ERRORLOG'.
2006-02-02 13:12:54.32 server SQL Server is starting at priority class
'normal'(2 CPUs detected).
2006-02-02 13:12:54.50 server SQL Server configured for thread mode
processing.
2006-02-02 13:12:54.50 server Using dynamic lock allocation. [500] Lock
Blocks, [1000] Lock Owner Blocks.
2006-02-02 13:12:54.52 spid4 Starting up database 'master'.
2006-02-02 13:12:54.57 server Using 'SSNETLIB.DLL' version '8.0.766'.
2006-02-02 13:12:54.57 spid5 Starting up database 'model'.
2006-02-02 13:12:54.57 spid4 Server name is 'BETTYPC\NETSDK'.
2006-02-02 13:12:54.57 spid4 Skipping startup of clean database id 4
2006-02-02 13:12:54.57 spid4 Skipping startup of clean database id 5
2006-02-02 13:12:54.57 spid4 Skipping startup of clean database id 6
2006-02-02 13:12:54.57 spid4 Skipping startup of clean database id 7
2006-02-02 13:12:54.57 spid4 Skipping startup of clean database id 8
2006-02-02 13:12:54.57 spid4 Skipping startup of clean database id 9
2006-02-02 13:12:54.57 spid4 Skipping startup of clean database id 10
2006-02-02 13:12:54.57 spid4 Skipping startup of clean database id 11
2006-02-02 13:12:54.57 spid4 Starting up database 'subway'.
2006-02-02 13:12:54.66 spid5 Clearing tempdb database.
2006-02-02 13:12:55.72 server SQL server listening on .
2006-02-02 13:12:55.72 server Error: 17826, Severity: 18, State: 1
2006-02-02 13:12:55.72 server Could not set up Net-Library 'SSNETLIB'..
2006-02-02 13:12:55.72 server Unable to load any netlibs.
2006-02-02 13:12:55.72 server SQL Server could not spawn FRunCM thread.
Here is the sqldump file
================================================== ===================
BugCheck Dump
================================================== ===================
This file is generated by Microsoft SQL Server 8.00.760
upon detection of fatal unexpected error. Please return this file,
the query or program that produced the bugcheck, the database and
the error log, and any other pertinent information with a Service Request.
Betty
"Michael Cheng [MSFT]" wrote:

> Hi Bettys,
> Welcome to use MSDN Managed Newsgroup!
> From your descriptions, I understood you are not able to connect the SQL
> Server named instance NETSDK with error message EXCEPTION_ACCESS_VIOLATION.
> If I have misunderstood your concern, please feel free to point it out.
> AV errors could be caused by various reasons, please perform the steps
> below and let me know the result
> 1. Check the log file of NETSDK instance, make sure whether the instance
> was started correctly.
> Defautly, the log will be located at C:\Program Files\Microsoft SQL
> Server\MSSQL$NETSDK\log, you may paste them here or send to me directly
>if you have concerns on security. (Note that
> REMOVE ONLINE in my email address before you click SEND)
> 2. Is it possible to connect the instance via OSQL and Query Analyzer?
> 3. Is it possible for you to connect via SQL Authentication?
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> ================================================== ====
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
|||Hi Betty,
It seems your SQL Server is not stable. From the startup log, I believe
something internal is wrong. We may noticed "netlibs" is not loaded and
Dump file were also generated.
Although you could register SQL Server now, I would recommend you backup
all the data in this instnace and perform a reinstallation of NETSDK
instance. You may follow the link below to perform a complete uninstall
How to manually remove SQL Server 2000 default, named, or virtual instance
http://support.microsoft.com/kb/290991
If you have any questions or concerns, don't hesitate to let me know. We
are always here to be of assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
================================================== ====
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.

connection failure

Hi,
We have just installed sql server 8
while using the enterprise manager, as we clicked on the
server icon the following error was issued:
"An error 1069 (the service did not start due to a logon
failure) ocurred while performing this service operation
on then MSSQL Server Service." In a related dialog we
found out that its default login procedure is by means of
the windows login. Another option was to
provide 'independent' login/password. In older versions I
was always able to login using sa as login with empty
password...
Which one should we use? what is missing?
tia
paco
tia,
FranciscoYour problem is not the login from EM to SQL Server. The problem is that SQL Server didn't event
start. Check out the Service Account for the SQL Server service, and the password specified for
this.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Francisco" <anonymous@.discussions.microsoft.com> wrote in message
news:09dd01c3aec7$002f4a50$a001280a@.phx.gbl...
> Hi,
> We have just installed sql server 8
> while using the enterprise manager, as we clicked on the
> server icon the following error was issued:
> "An error 1069 (the service did not start due to a logon
> failure) ocurred while performing this service operation
> on then MSSQL Server Service." In a related dialog we
> found out that its default login procedure is by means of
> the windows login. Another option was to
> provide 'independent' login/password. In older versions I
> was always able to login using sa as login with empty
> password...
> Which one should we use? what is missing?
> tia
> paco
>
> tia,
> Francisco
>

Connection fails SQL 2000

One of our customers has SQl server 2000 installed
This has been working perfectly untill last Friday.
At this point various databases began to return errors
when querries were run on the data.
There appeasr to be no pattern to which databases still
work as I have two backup copies of the main databse they
use. The main one and one of the backups produce errors
yet the other backup, taken on the same day does not.
Looking at the error log (attached) there seems to be a
lot of "corrupt" entires.
Any suggestions
Date Source Message
---
--
---
--...
004 DC771 Module(sqlservr+000DC771) (ExecuteSql
(class CParamExchange *,class CXVariant *,
004 A9DE2 Module(sqlservr+000A9DE2)
(CXteHashMatch::ExecCompile(class CExecCompContext *)
004 A9E93 Module(sqlservr+000A9E93)
(CXteHashMatch::ExecCompile(class CExecCompContext *)
004 A70B6 Module(sqlservr+000A70B6)
(CXteHashMatch::IntermediateCompile(class IMemObj *,c
004 A8B35 Module(sqlservr+000A8B35)
(CXteHashMatch::CreateBailoutPlan(class CRemapContext
0041 F796 Module(sqlservr+0001F796)
(CSQLObject::FTransform(class CParamExchange *)+00000
0041 FDDD Module(sqlservr+0001FDDD)
(CSQLObject::FTransform2(class CSQLComment *,class CP
00415080 Module(sqlservr+00015080)
(CSQLSource::FTransform(class CParamExchange *)
+0000037C)
0041534 F Module(sqlservr+0001534F)
(CSQLSource::Execute(class CParamExchange *)+00000176
00415410 Module(sqlservr+00015410)
(CSQLSource::Execute(class CParamExchange *)
+00000343)
00415765 Module(sqlservr+00015765)
(CMsqlExecContext::Execute(class CCompPlan *,class
CParamExchange *)+000001C7)
004160 DB Module(sqlservr+000160DB)
(CMsqlExecContext::ExecuteStmts(class ExecutionContex
0041767 E Module(sqlservr+0001767E) (process_commands
(struct srv_proc *)+000001E7)
0043 B7EF Module(sqlservr+0003B7EF) (execute_rpc
(struct srv_proc *)+00000019)
00447078 Module(sqlservr+00047078)
(CCompPlan::FCompileStep(class CAlgStmt *,class
CStatement * *)+00000AE7)
004510 FE Module(sqlservr+000510FE)
(CProchdr::FCompile(class CCompPlan *,class CParamExc
0049 CB9F Module(sqlservr+0009CB9F)
(CStmtExec::XretExecute(class CMsqlExecContext *)cons
0049 CD0A Module(sqlservr+0009CD0A)
(CStmtExec::XretLocalExec(class CMsqlExecContext *,un
0049 C6F4 Module(sqlservr+0009C6F4)
(CSQLObject::FGetFromDisk(class CParamExchange *)+000
0049 DA48 Module(sqlservr+0009DA48)
(CStmtSelect::Init(class CAlgStmt *,class CCompPlan *
00563 F78 Module(sqlservr+00163F78)
(CStmtQuery::InitQuery(class CAlgStmt *,class CCompPl
00564019 Module(sqlservr+00164019)
(BuildQueryFromTree(class TREE *,class IMemObj
*,class IMemObj *,class IQueryOb
005642 CD Module(sqlservr+001642CD)
(CCvtTree::PqryFromTree(class TREE *,class IMemObj *,
0056701 F Module(sqlservr+0016701F)
(CBndOutputs::RemapValrefs(class CRemapContext *,int)
00567536 Module(sqlservr+00167536)
(CXte::ExecCompile(class CExecCompContext *)
+000000B7)
00567536 Module(sqlservr+00167536)
(CXte::ExecCompile(class CExecCompContext *)
+000000B7)
005688 A4 Module(sqlservr+001688A4) (CQuery::Prepare
(void)+00000116)
0061 DDB6 Module(sqlservr+0021DDB6)
(CSpecProc::Execute(class CParamExchange *)+00000092)
0061 DA3E Module(sqlservr+0021DA3E)
(CSpecProc::ExecuteSpecial(class CParamExchange *,uns
0063 C71D Module(sqlservr+0023C71D) (execrpc(struct
srv_proc *)+000004A8)
00703 A1C Module(sqlservr+00303A1C)
(CXteHashMatch::CreateInputScan(class IMemObj *,class
2003-11-05 12:36:10.29 server Microsoft SQL Server
2000 - 8.00.194 (Intel X86) ...
2003-11-05 12:36:10.54 server Logging SQL Server
messages in file 'd:\Program Files\Microsoft SQL
Server\MSSQ
2003-11-05 12:36:10.54 server Server Process ID is 1700.
2003-11-05 12:36:10.54 server All rights reserved.
2003-11-05 12:36:10.54 server Copyright (C) 1988-2000
Microsoft Corporation.
2003-11-05 12:36:10.99 server SQL Server is starting at
priority class 'normal'(4 CPUs detected).
2003-11-05 12:36:13.00 server SQL Server configured for
thread mode processing.
2003-11-05 12:36:13.23 server Using dynamic lock
allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks.
2003-11-05 12:36:13.62 server Attempting to initialize
Distributed Transaction Coordinator.
2003-11-05 12:36:19.92 spid2 Starting up
database 'master'.
2003-11-05 12:36:27.70 spid5 Starting up
database 'model'.
2003-11-05 12:36:27.70 server Using 'SSNETLIB.DLL'
version '8.0.194'.
2003-11-05 12:36:27.73 spid2 Server name is 'WRLW2S002'.
2003-11-05 12:36:27.79 spid12 Starting up
database 'powerway'.
2003-11-05 12:36:27.79 spid11 Starting up
database 'dbWheelset_Live'.
2003-11-05 12:36:27.79 spid10 Starting up
database 'Northwind'.
2003-11-05 12:36:27.79 spid9 Starting up
database 'pubs'.
2003-11-05 12:36:27.79 spid8 Starting up
database 'msdb'.
2003-11-05 12:36:27.81 spid14 Starting up
database 'dbWheelSets_LIVE'.
2003-11-05 12:36:27.81 spid13 Starting up
database 'dbWheelSets_TEST'.
2003-11-05 12:36:27.89 spid16 Starting up
database 'dbWheelsets_ARCH_TEST'.
2003-11-05 12:36:27.89 spid15 Starting up
database 'dbWheelsets_BACKUP'.
2003-11-05 12:36:27.98 spid17 Starting up
database 'dbWheelsets_DATA_TEST'.
2003-11-05 12:36:28.43 spid5 Clearing tempdb database.
2003-11-05 12:36:28.51 spid11 Analysis of
database 'dbWheelset_Live' (7) is 100% complete
(approximately 0 mo
2003-11-05 12:36:28.65 spid12 Analysis of
database 'powerway' (8) is 100% complete (approximately 0
more seco
2003-11-05 12:36:28.87 server SQL Server is ready for
client connections
2003-11-05 12:36:28.87 server SQL server listening on
172.20.120.23:1433, 127.0.0.1:1433.
2003-11-05 12:36:28.87 server SQL server listening on
TCP, Shared Memory, Named Pipes.
2003-11-05 12:36:29.76 spid13 Analysis of
database 'dbWheelSets_TEST' (9) is 100% complete
(approximately 0 m
2003-11-05 12:36:38.67 spid5 Starting up
database 'tempdb'.
2003-11-05 12:36:41.85 spid2 Recovery complete.
2003-11-05 12:36:49.51 spid51 Using 'xpsqlbot.dll'
version '2000.80.194' to execute extended stored procedure
2003-11-05 12:36:51.96 spid51 Using 'xpstar.dll'
version '2000.80.194' to execute extended stored
procedure '
2003-11-05 13:15:27.45 spid55 Using 'sqlimage.dll'
version '4.0.5'...
2003-11-05 13:15:27.46 spid55 SqlDumpExceptionHandler:
Process 55 generated fatal exception c0000005 EXCEPTIO
2003-11-05 13:15:27.46 spid55 Error: 0, Severity: 19,
State: 0
410735 D0 Module(UMS+000035D0) (ProcessWorkRequests
(class UmsWorkQueue *)+00000264)
4107382 C Module(UMS+0000382C) (ThreadStartRoutine
(void *)+000000BC)
7 C57B382 Module(KERNEL32+0000B382)
(lstrcmpiW+000000B7)
78008454 Module(MSVCRT+00008454)
(_endthread+000000C1)Have you tried running DBCC CHECKDB
--
HTH
Ryan Waight, MCDBA, MCSE
"john kinghorn" <anonymous@.discussions.microsoft.com> wrote in message
news:076a01c3a787$7e28ea20$a401280a@.phx.gbl...
> One of our customers has SQl server 2000 installed
> This has been working perfectly untill last Friday.
> At this point various databases began to return errors
> when querries were run on the data.
> There appeasr to be no pattern to which databases still
> work as I have two backup copies of the main databse they
> use. The main one and one of the backups produce errors
> yet the other backup, taken on the same day does not.
> Looking at the error log (attached) there seems to be a
> lot of "corrupt" entires.
> Any suggestions
>
> Date Source Message
> ---
> --
> ---
> --...
> 004 DC771 Module(sqlservr+000DC771) (ExecuteSql
> (class CParamExchange *,class CXVariant *,
> 004 A9DE2 Module(sqlservr+000A9DE2)
> (CXteHashMatch::ExecCompile(class CExecCompContext *)
> 004 A9E93 Module(sqlservr+000A9E93)
> (CXteHashMatch::ExecCompile(class CExecCompContext *)
> 004 A70B6 Module(sqlservr+000A70B6)
> (CXteHashMatch::IntermediateCompile(class IMemObj *,c
> 004 A8B35 Module(sqlservr+000A8B35)
> (CXteHashMatch::CreateBailoutPlan(class CRemapContext
> 0041 F796 Module(sqlservr+0001F796)
> (CSQLObject::FTransform(class CParamExchange *)+00000
> 0041 FDDD Module(sqlservr+0001FDDD)
> (CSQLObject::FTransform2(class CSQLComment *,class CP
> 00415080 Module(sqlservr+00015080)
> (CSQLSource::FTransform(class CParamExchange *)
> +0000037C)
> 0041534 F Module(sqlservr+0001534F)
> (CSQLSource::Execute(class CParamExchange *)+00000176
> 00415410 Module(sqlservr+00015410)
> (CSQLSource::Execute(class CParamExchange *)
> +00000343)
> 00415765 Module(sqlservr+00015765)
> (CMsqlExecContext::Execute(class CCompPlan *,class
> CParamExchange *)+000001C7)
> 004160 DB Module(sqlservr+000160DB)
> (CMsqlExecContext::ExecuteStmts(class ExecutionContex
> 0041767 E Module(sqlservr+0001767E) (process_commands
> (struct srv_proc *)+000001E7)
> 0043 B7EF Module(sqlservr+0003B7EF) (execute_rpc
> (struct srv_proc *)+00000019)
> 00447078 Module(sqlservr+00047078)
> (CCompPlan::FCompileStep(class CAlgStmt *,class
> CStatement * *)+00000AE7)
> 004510 FE Module(sqlservr+000510FE)
> (CProchdr::FCompile(class CCompPlan *,class CParamExc
> 0049 CB9F Module(sqlservr+0009CB9F)
> (CStmtExec::XretExecute(class CMsqlExecContext *)cons
> 0049 CD0A Module(sqlservr+0009CD0A)
> (CStmtExec::XretLocalExec(class CMsqlExecContext *,un
> 0049 C6F4 Module(sqlservr+0009C6F4)
> (CSQLObject::FGetFromDisk(class CParamExchange *)+000
> 0049 DA48 Module(sqlservr+0009DA48)
> (CStmtSelect::Init(class CAlgStmt *,class CCompPlan *
> 00563 F78 Module(sqlservr+00163F78)
> (CStmtQuery::InitQuery(class CAlgStmt *,class CCompPl
> 00564019 Module(sqlservr+00164019)
> (BuildQueryFromTree(class TREE *,class IMemObj
> *,class IMemObj *,class IQueryOb
> 005642 CD Module(sqlservr+001642CD)
> (CCvtTree::PqryFromTree(class TREE *,class IMemObj *,
> 0056701 F Module(sqlservr+0016701F)
> (CBndOutputs::RemapValrefs(class CRemapContext *,int)
> 00567536 Module(sqlservr+00167536)
> (CXte::ExecCompile(class CExecCompContext *)
> +000000B7)
> 00567536 Module(sqlservr+00167536)
> (CXte::ExecCompile(class CExecCompContext *)
> +000000B7)
> 005688 A4 Module(sqlservr+001688A4) (CQuery::Prepare
> (void)+00000116)
> 0061 DDB6 Module(sqlservr+0021DDB6)
> (CSpecProc::Execute(class CParamExchange *)+00000092)
> 0061 DA3E Module(sqlservr+0021DA3E)
> (CSpecProc::ExecuteSpecial(class CParamExchange *,uns
> 0063 C71D Module(sqlservr+0023C71D) (execrpc(struct
> srv_proc *)+000004A8)
> 00703 A1C Module(sqlservr+00303A1C)
> (CXteHashMatch::CreateInputScan(class IMemObj *,class
> 2003-11-05 12:36:10.29 server Microsoft SQL Server
> 2000 - 8.00.194 (Intel X86) ...
> 2003-11-05 12:36:10.54 server Logging SQL Server
> messages in file 'd:\Program Files\Microsoft SQL
> Server\MSSQ
> 2003-11-05 12:36:10.54 server Server Process ID is 1700.
> 2003-11-05 12:36:10.54 server All rights reserved.
> 2003-11-05 12:36:10.54 server Copyright (C) 1988-2000
> Microsoft Corporation.
> 2003-11-05 12:36:10.99 server SQL Server is starting at
> priority class 'normal'(4 CPUs detected).
> 2003-11-05 12:36:13.00 server SQL Server configured for
> thread mode processing.
> 2003-11-05 12:36:13.23 server Using dynamic lock
> allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks.
> 2003-11-05 12:36:13.62 server Attempting to initialize
> Distributed Transaction Coordinator.
> 2003-11-05 12:36:19.92 spid2 Starting up
> database 'master'.
> 2003-11-05 12:36:27.70 spid5 Starting up
> database 'model'.
> 2003-11-05 12:36:27.70 server Using 'SSNETLIB.DLL'
> version '8.0.194'.
> 2003-11-05 12:36:27.73 spid2 Server name is 'WRLW2S002'.
> 2003-11-05 12:36:27.79 spid12 Starting up
> database 'powerway'.
> 2003-11-05 12:36:27.79 spid11 Starting up
> database 'dbWheelset_Live'.
> 2003-11-05 12:36:27.79 spid10 Starting up
> database 'Northwind'.
> 2003-11-05 12:36:27.79 spid9 Starting up
> database 'pubs'.
> 2003-11-05 12:36:27.79 spid8 Starting up
> database 'msdb'.
> 2003-11-05 12:36:27.81 spid14 Starting up
> database 'dbWheelSets_LIVE'.
> 2003-11-05 12:36:27.81 spid13 Starting up
> database 'dbWheelSets_TEST'.
> 2003-11-05 12:36:27.89 spid16 Starting up
> database 'dbWheelsets_ARCH_TEST'.
> 2003-11-05 12:36:27.89 spid15 Starting up
> database 'dbWheelsets_BACKUP'.
> 2003-11-05 12:36:27.98 spid17 Starting up
> database 'dbWheelsets_DATA_TEST'.
> 2003-11-05 12:36:28.43 spid5 Clearing tempdb database.
> 2003-11-05 12:36:28.51 spid11 Analysis of
> database 'dbWheelset_Live' (7) is 100% complete
> (approximately 0 mo
> 2003-11-05 12:36:28.65 spid12 Analysis of
> database 'powerway' (8) is 100% complete (approximately 0
> more seco
> 2003-11-05 12:36:28.87 server SQL Server is ready for
> client connections
> 2003-11-05 12:36:28.87 server SQL server listening on
> 172.20.120.23:1433, 127.0.0.1:1433.
> 2003-11-05 12:36:28.87 server SQL server listening on
> TCP, Shared Memory, Named Pipes.
> 2003-11-05 12:36:29.76 spid13 Analysis of
> database 'dbWheelSets_TEST' (9) is 100% complete
> (approximately 0 m
> 2003-11-05 12:36:38.67 spid5 Starting up
> database 'tempdb'.
> 2003-11-05 12:36:41.85 spid2 Recovery complete.
> 2003-11-05 12:36:49.51 spid51 Using 'xpsqlbot.dll'
> version '2000.80.194' to execute extended stored procedure
> 2003-11-05 12:36:51.96 spid51 Using 'xpstar.dll'
> version '2000.80.194' to execute extended stored
> procedure '
> 2003-11-05 13:15:27.45 spid55 Using 'sqlimage.dll'
> version '4.0.5'...
> 2003-11-05 13:15:27.46 spid55 SqlDumpExceptionHandler:
> Process 55 generated fatal exception c0000005 EXCEPTIO
> 2003-11-05 13:15:27.46 spid55 Error: 0, Severity: 19,
> State: 0
> 410735 D0 Module(UMS+000035D0) (ProcessWorkRequests
> (class UmsWorkQueue *)+00000264)
> 4107382 C Module(UMS+0000382C) (ThreadStartRoutine
> (void *)+000000BC)
> 7 C57B382 Module(KERNEL32+0000B382)
> (lstrcmpiW+000000B7)
> 78008454 Module(MSVCRT+00008454)
> (_endthread+000000C1)
>

Connection fails and currupt log

One of our customers has SQL server 2000 installed
This has been working perfectly for over a year
Now various databases have started to return errors when queries are
run on the data from VB or Query Analyser.
A typical error is:
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData
(CheckForData()).
Server: Msg 11, Level 16, State 1, Line 0
General Network Error. Check your network documentation
Connection broken
Not all the database produce errors but there appears to be no pattern
to which databases still work.
I have two backup copies of the main database they use. The main
database its self and one of the backups produce errors yet the other
backup, taken on the same day does not.
Looking at the error log (attached) there seems to be a lot of
"corrupt" entires.
Any suggestions* If you see corruption, then --
1. Check system and app event logs for details on any hardware corruption.
2. contact your hardware vendors to run some tests, diagnostics, etc and
also check for firmware upgrades.
3. Only then, RESTORE from your last healthy SQL Backup.
4. If you dont have a backup, then you could try to "Repair" the database
using "dbcc checkdb".
Thanks,
Vikram
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.

connection failed: SQLstate: 28000

I have SQL 2000 installed in my windows 2003 server with mixed mode authentication. When I login to the server and open the SQL server manager under my windows name everything works. And if I try to create an odbc connection from one of the client pc's or from the server itself using windows authentication still everything works. Now I opened the SQL enterprise manager and in the Security section, there is a user group called BUILTIN\Administrators, I was asked to deny access to this group in SQL. So I did that and added my windows login name in the security -> Login section. Now still if I try to open the enterprise manager and and login to sql under my windows login name it works. But if I try to create an odbc connection to the sql server either from the server itself or from the client work station I get the following error:

connection failed:
SQLstate: '28000'
SQL Server Error: 18456
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'PROD\pchelin'

If I go to the security -> Login and enable BUILT\Aministrators group, everything works. But I would like to know how to disable that group and add my own windows group or login id in SQL server and connect using ODBC.

Your valuable feedback is greatly appriciated.

Hi,

I do not know which user you use to connect to SQL server except your login, and I have no idea if you are a member of built\Administrators group, but I know that if you deny Access to server for group even if user itself had rights to access server this DENY will prevent user to log into SQL Server.

I hope that it helps

JPazgier

|||

You are correct. The moment I deleted the BUILT/Administrators group it started to work. Are there any disadvantages in deleting this group?

|||

If it was windows group it is not safe to delete it. It will be good practice to create another group like SQLAdministrators and give its users rights to be admins on SQL server. The only problem can be that administrators have by default rights to SQL server so you have to just remove this rights to SQL server but do not set Deny access.

JPazgier

Connection failed between PC

Hello, i ahve a problem to connect a pc to another with MSDE installed.
The response message of this failure is:
'Server not exists'

Can help me?

Thanks!Hai,

I dont exactly trap 'What u mentaioned is the os server or sql
server.

Any way if you want to access a machine from u r machine , the
followings must exits.

1. Network among them.
2. if , so u can access other machines from u r command prompt(run).

like, \\node-x\e$

..if it does not work , share the other machine's drives

Raghu|||alessandro_chiodo@.hotmail.com (Alex) wrote in message news:<c7bf0032.0312040727.29186bc9@.posting.google.com>...
> Hello, i ahve a problem to connect a pc to another with MSDE installed.
> The response message of this failure is:
> 'Server not exists'
> Can help me?
> Thanks!

One possibility is that you're using the wrong authentication method:

http://support.microsoft.com/defaul...0&Product=sql2k

Another possibility is that it's MSDE SP3a, which disables network
access to MSDE by default:

http://support.microsoft.com/defaul...for _msde_d3jb

Simon

Connection fail in analysis service

I got an error when I try to connect my SQL server Analysis service. I have
installed SQL Server Analysis Service in my WinXP PC. When I try to open
Analysis Manager to connect my pc, I got the error "Unable to connect to
registry on the server (COMPUTERNAME), or you are not a member of OLAP
Administrators group on this server."
HOW COME...PLS HELP!!!Check two things:
- is the user a member of Windows local OLAP Administrators group
- do you have SP3a for Analysis Services installed (latest hotfixes for XP
disable accessto the AS is it is not patched).
--
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com
"Grey" <erickwyum@.i-cable.com> wrote in message
news:%23WSCGGoiEHA.3536@.TK2MSFTNGP12.phx.gbl...
> I got an error when I try to connect my SQL server Analysis service. I
have
> installed SQL Server Analysis Service in my WinXP PC. When I try to open
> Analysis Manager to connect my pc, I got the error "Unable to connect to
> registry on the server (COMPUTERNAME), or you are not a member of OLAP
> Administrators group on this server."
> HOW COME...PLS HELP!!!
>