Connection timed out

We are running SQL Server 2000 Version 8.00.760. We are running our
application using Java. We are frequently getting Connection Timed Out in
our appserver. Is anyone aware of such an issue this version of SQL Server
? We have similar configurations on several other servers, but only the
appserver's connected to this particular database is giving connection
timeouts. Is this a known bug ? or are we hit with a virus ?
I searched Google, but did not find any info.
-Nags
Nags,
The "application timeout" usually means that the driver or the client code
has some sort of timeout within which, if sql server doesnt execute and
return the query, then it times out. For example, I think the default at
the ODBC driver setting is 30 seconds.
That leads us to the next question - why is it taking 30 seconds or more
(I'm making the assumption here that 30 sec is your default timeout as
well). I'm also making another assumption - that the other configurations
you have are EXACTLY like this "problem server" configuation which includes
the same amt of tables, and the same amt of data in these tables. And that,
there was a time maybe when things were fine on this "problem" server.
A couple of things you'd want ot check -
1. Does this happen for any query/hit against the sql server? example, even
logging on (user name/password) results in a timeout?
2. Does it happen for a set of queries?
3. If you know the queries that are commonly executed by this application,
OR some of the queries that you've seen timeout. Take those queries in
Query analyser and see how long they run.
4. Try updating statistics on the tables.
5. Compare index structures on the tables on the 'good' db's with their
counterparts on this problem db.
Hope this helps.
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.
|||I'm facing the pro as well.
I look into error log, it said 'Server terminating due to 'Stop' request
from Service Control Manager'. The db server also using the Autogrowth
option, and everytime it growing the log file, seems like the server stop
responding.
Pls advise.
Thanks in advance.
"Vikram Jayaram [MS]" wrote:

> Nags,
> The "application timeout" usually means that the driver or the client code
> has some sort of timeout within which, if sql server doesnt execute and
> return the query, then it times out. For example, I think the default at
> the ODBC driver setting is 30 seconds.
> That leads us to the next question - why is it taking 30 seconds or more
> (I'm making the assumption here that 30 sec is your default timeout as
> well). I'm also making another assumption - that the other configurations
> you have are EXACTLY like this "problem server" configuation which includes
> the same amt of tables, and the same amt of data in these tables. And that,
> there was a time maybe when things were fine on this "problem" server.
> A couple of things you'd want ot check -
> 1. Does this happen for any query/hit against the sql server? example, even
> logging on (user name/password) results in a timeout?
> 2. Does it happen for a set of queries?
> 3. If you know the queries that are commonly executed by this application,
> OR some of the queries that you've seen timeout. Take those queries in
> Query analyser and see how long they run.
> 4. Try updating statistics on the tables.
> 5. Compare index structures on the tables on the 'good' db's with their
> counterparts on this problem db.
> Hope this helps.
> 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 timed out

We are running SQL Server 2000 Version 8.00.760. We are running our
application using Java. We are frequently getting Connection Timed Out in
our appserver. Is anyone aware of such an issue this version of SQL Server
? We have similar configurations on several other servers, but only the
appserver's connected to this particular database is giving connection
timeouts. Is this a known bug ? or are we hit with a virus ?
I searched Google, but did not find any info.
-NagsNags,
The "application timeout" usually means that the driver or the client code
has some sort of timeout within which, if sql server doesnt execute and
return the query, then it times out. For example, I think the default at
the ODBC driver setting is 30 seconds.
That leads us to the next question - why is it taking 30 seconds or more
(I'm making the assumption here that 30 sec is your default timeout as
well). I'm also making another assumption - that the other configurations
you have are EXACTLY like this "problem server" configuation which includes
the same amt of tables, and the same amt of data in these tables. And that,
there was a time maybe when things were fine on this "problem" server.
A couple of things you'd want ot check -
1. Does this happen for any query/hit against the sql server? example, even
logging on (user name/password) results in a timeout?
2. Does it happen for a set of queries?
3. If you know the queries that are commonly executed by this application,
OR some of the queries that you've seen timeout. Take those queries in
Query analyser and see how long they run.
4. Try updating statistics on the tables.
5. Compare index structures on the tables on the 'good' db's with their
counterparts on this problem db.
Hope this helps.
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.|||I'm facing the pro as well.
I look into error log, it said 'Server terminating due to 'Stop' request
from Service Control Manager'. The db server also using the Autogrowth
option, and everytime it growing the log file, seems like the server stop
responding.
Pls advise.
Thanks in advance.
"Vikram Jayaram [MS]" wrote:

> Nags,
> The "application timeout" usually means that the driver or the client code
> has some sort of timeout within which, if sql server doesnt execute and
> return the query, then it times out. For example, I think the default at
> the ODBC driver setting is 30 seconds.
> That leads us to the next question - why is it taking 30 seconds or more
> (I'm making the assumption here that 30 sec is your default timeout as
> well). I'm also making another assumption - that the other configurations
> you have are EXACTLY like this "problem server" configuation which include
s
> the same amt of tables, and the same amt of data in these tables. And that
,
> there was a time maybe when things were fine on this "problem" server.
> A couple of things you'd want ot check -
> 1. Does this happen for any query/hit against the sql server? example, eve
n
> logging on (user name/password) results in a timeout?
> 2. Does it happen for a set of queries?
> 3. If you know the queries that are commonly executed by this application,
> OR some of the queries that you've seen timeout. Take those queries in
> Query analyser and see how long they run.
> 4. Try updating statistics on the tables.
> 5. Compare index structures on the tables on the 'good' db's with their
> counterparts on this problem db.
> Hope this helps.
> 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 timed out

We are running SQL Server 2000 Version 8.00.760. We are running our
application using Java. We are frequently getting Connection Timed Out in
our appserver. Is anyone aware of such an issue this version of SQL Server
? We have similar configurations on several other servers, but only the
appserver's connected to this particular database is giving connection
timeouts. Is this a known bug ? or are we hit with a virus ?
I searched Google, but did not find any info.
-NagsNags,
The "application timeout" usually means that the driver or the client code
has some sort of timeout within which, if sql server doesnt execute and
return the query, then it times out. For example, I think the default at
the ODBC driver setting is 30 seconds.
That leads us to the next question - why is it taking 30 seconds or more
(I'm making the assumption here that 30 sec is your default timeout as
well). I'm also making another assumption - that the other configurations
you have are EXACTLY like this "problem server" configuation which includes
the same amt of tables, and the same amt of data in these tables. And that,
there was a time maybe when things were fine on this "problem" server.
A couple of things you'd want ot check -
1. Does this happen for any query/hit against the sql server? example, even
logging on (user name/password) results in a timeout?
2. Does it happen for a set of queries?
3. If you know the queries that are commonly executed by this application,
OR some of the queries that you've seen timeout. Take those queries in
Query analyser and see how long they run.
4. Try updating statistics on the tables.
5. Compare index structures on the tables on the 'good' db's with their
counterparts on this problem db.
Hope this helps.
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.|||I'm facing the pro as well.
I look into error log, it said 'Server terminating due to 'Stop' request
from Service Control Manager'. The db server also using the Autogrowth
option, and everytime it growing the log file, seems like the server stop
responding.
Pls advise.
Thanks in advance.
"Vikram Jayaram [MS]" wrote:
> Nags,
> The "application timeout" usually means that the driver or the client code
> has some sort of timeout within which, if sql server doesnt execute and
> return the query, then it times out. For example, I think the default at
> the ODBC driver setting is 30 seconds.
> That leads us to the next question - why is it taking 30 seconds or more
> (I'm making the assumption here that 30 sec is your default timeout as
> well). I'm also making another assumption - that the other configurations
> you have are EXACTLY like this "problem server" configuation which includes
> the same amt of tables, and the same amt of data in these tables. And that,
> there was a time maybe when things were fine on this "problem" server.
> A couple of things you'd want ot check -
> 1. Does this happen for any query/hit against the sql server? example, even
> logging on (user name/password) results in a timeout?
> 2. Does it happen for a set of queries?
> 3. If you know the queries that are commonly executed by this application,
> OR some of the queries that you've seen timeout. Take those queries in
> Query analyser and see how long they run.
> 4. Try updating statistics on the tables.
> 5. Compare index structures on the tables on the 'good' db's with their
> counterparts on this problem db.
> Hope this helps.
> 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 String to SQL Express on another computer

I have an XP Pro machine running a classic ASP site in IIS - the version that comes on the XP Pro CD. The site makes a connection to an MSDE database on the same machine named InControl. I have moved that database to SQL Express 2005 and want to test it with the ASP site. SQL Express 2005 is running on a separate Vista machine. I am currently using this connection string:

objConn.ConnectionString = "Provider=SQLOLEDB;Data Source=400SC;Initial Catalog=InControl;User ID=" & uid & ";Password=" & upass & ""

Where 400SC is the name of the XP Pro machine and InControl is the database. The variables uid and upass are pulled from Session when the connection string is created.

I have tried different Provider names and various combinations of server name and ip address with and without port numbers for the Data Source. All of them yield some variation of this error:

Microsoft OLE DB Provider for SQL Server (0x80004005)
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.

What should the connection string look like?

Thanks for the help.

PS - If the solution involves a port, do I need to make that port an exception in the Vista Firewall?

The sqlexpress server may have an instance name. Try changing it to "Data Source=400SC\SQLEXPRESS"

|||

This is the string I initially tried to access SQL Express on the other computer - CSC_DELL. I recieved the error message in the original post. Hard coding the User ID and Password also yeilds the same error. The User is set-up in SQL and the database.

objConn.ConnectionString = "Provider=SQLOLEDB;Data Source=CSC_DELL\SQLEXPRESS;Initial Catalog=InControl;User ID=" & uid & ";Password=" & upass & ""

|||

Create a new file on your desktop. Rename the file to "test.udl" Double-click the file, and create a connection to your database. Once the "Test Connection" succeeds, then close the dialog box and view the contents of your .udl file in notepad. This will give you a connection string to compare against.

|||

Created a .udl file, but the SQL Express server on the Vista machine was not listed in the Server drop down list. I used the SQL Configuration tool and enabled listening with TCP/IP and Named Pipes - both were disabled. Also made a 1433 port exception in the Vista firewall. Tried udl, again, and the server still did not show. Both computers are in the same workgroup on my home network. I tried typing the name of the SQL Express server in the drop down list - didn't work. Everything I try yields the "SQL Server does not exist or access denied." Still stuck.

Connection String suddenly Stops working

Hi
Odd one here, I have a local version of SQL running on my laptop for
demos, been working fine for years yet yesterday I suddenly get an
error "Invalid Conection Parameter" running a sproc using the
following connection string (Its an Access 2002 App to SQL 2000)
strConnect = "Network=DBMSSOCN;Server=" & DB_Server & ";DRIVER=SQL
Server;UID=abc;PWD=def"
Works fine if I use the server based SQL resource
So I change it to be the following and it starts working ?
strConnect = "Server=" & DB_Server & ";DRIVER=SQL
Server;UID=abc;PWD=def"
So it started not liking the 'Network=DBMSSOCN' part but both the
datbases have TCP/IP and Named Pipes setup as network protocols and
bot have not chnaged config for years
I did install SP2 for XP a few weeks ago but I'm sure I have run it
since (mind you I wish I'd never done SP2 with all the unasked for
'extras' MS dump on your PC but thats another thread)
Thanks all
shaun
Strange. It looks that both strings are correct (although I would put the
network part toward the end as a personal preference).
I often refer to http://www.connectionstrings.com/ for examples and usage of
connection strings.
Keith
"Shaun" <shaunsizen@.msn.com> wrote in message
news:4a2f9143.0502030133.5892ee76@.posting.google.c om...
> Hi
> Odd one here, I have a local version of SQL running on my laptop for
> demos, been working fine for years yet yesterday I suddenly get an
> error "Invalid Conection Parameter" running a sproc using the
> following connection string (Its an Access 2002 App to SQL 2000)
> strConnect = "Network=DBMSSOCN;Server=" & DB_Server & ";DRIVER=SQL
> Server;UID=abc;PWD=def"
> Works fine if I use the server based SQL resource
> So I change it to be the following and it starts working ?
> strConnect = "Server=" & DB_Server & ";DRIVER=SQL
> Server;UID=abc;PWD=def"
> So it started not liking the 'Network=DBMSSOCN' part but both the
> datbases have TCP/IP and Named Pipes setup as network protocols and
> bot have not chnaged config for years
> I did install SP2 for XP a few weeks ago but I'm sure I have run it
> since (mind you I wish I'd never done SP2 with all the unasked for
> 'extras' MS dump on your PC but thats another thread)
> Thanks all
> shaun
|||Thanks for the link Keith
Yep it is odd as I thought both were fine as well and the one now is
not working worked fine for months!!!
Ah well the odditiess of Microsoft
Cheers
Shaun
"Keith Kratochvil" <sqlguy.back2u@.comcast.net> wrote in message news:<uQts2dgCFHA.3908@.TK2MSFTNGP12.phx.gbl>...[vbcol=seagreen]
> Strange. It looks that both strings are correct (although I would put the
> network part toward the end as a personal preference).
> I often refer to http://www.connectionstrings.com/ for examples and usage of
> connection strings.
> --
> Keith
>
> "Shaun" <shaunsizen@.msn.com> wrote in message
> news:4a2f9143.0502030133.5892ee76@.posting.google.c om...
|||Win XP SP2 also probably updated your MDAC or exposed an MDAC vunerability
that was updated recently through Windows Updates.
Nevertheless, you are using the OLEDB for ODBC, MSADSQL? Why not just use
the SQLOLEDB directly seeing as you are not using the functionality that an
ODBC DSN would give you? If I am wrong, then it is the DRIVER=SQLSERVER
that is throwing you. That's an ODBC Only OLEDB parameter.
Sincerely,
Anthony Thomas

"Shaun" <shaunsizen@.msn.com> wrote in message
news:4a2f9143.0502030133.5892ee76@.posting.google.c om...
Hi
Odd one here, I have a local version of SQL running on my laptop for
demos, been working fine for years yet yesterday I suddenly get an
error "Invalid Conection Parameter" running a sproc using the
following connection string (Its an Access 2002 App to SQL 2000)
strConnect = "Network=DBMSSOCN;Server=" & DB_Server & ";DRIVER=SQL
Server;UID=abc;PWD=def"
Works fine if I use the server based SQL resource
So I change it to be the following and it starts working ?
strConnect = "Server=" & DB_Server & ";DRIVER=SQL
Server;UID=abc;PWD=def"
So it started not liking the 'Network=DBMSSOCN' part but both the
datbases have TCP/IP and Named Pipes setup as network protocols and
bot have not chnaged config for years
I did install SP2 for XP a few weeks ago but I'm sure I have run it
since (mind you I wish I'd never done SP2 with all the unasked for
'extras' MS dump on your PC but thats another thread)
Thanks all
shaun

Connection String suddenly Stops working

Hi
Odd one here, I have a local version of SQL running on my laptop for
demos, been working fine for years yet yesterday I suddenly get an
error "Invalid Conection Parameter" running a sproc using the
following connection string (Its an Access 2002 App to SQL 2000)
strConnect = "Network=DBMSSOCN;Server=" & DB_Server & ";DRIVER=SQL
Server;UID=abc;PWD=def"
Works fine if I use the server based SQL resource
So I change it to be the following and it starts working '
strConnect = "Server=" & DB_Server & ";DRIVER=SQL
Server;UID=abc;PWD=def"
So it started not liking the 'Network=DBMSSOCN' part but both the
datbases have TCP/IP and Named Pipes setup as network protocols and
bot have not chnaged config for years
I did install SP2 for XP a few weeks ago but I'm sure I have run it
since (mind you I wish I'd never done SP2 with all the unasked for
'extras' MS dump on your PC but thats another thread)
Thanks all
shaunStrange. It looks that both strings are correct (although I would put the
network part toward the end as a personal preference).
I often refer to http://www.connectionstrings.com/ for examples and usage of
connection strings.
--
Keith
"Shaun" <shaunsizen@.msn.com> wrote in message
news:4a2f9143.0502030133.5892ee76@.posting.google.com...
> Hi
> Odd one here, I have a local version of SQL running on my laptop for
> demos, been working fine for years yet yesterday I suddenly get an
> error "Invalid Conection Parameter" running a sproc using the
> following connection string (Its an Access 2002 App to SQL 2000)
> strConnect = "Network=DBMSSOCN;Server=" & DB_Server & ";DRIVER=SQL
> Server;UID=abc;PWD=def"
> Works fine if I use the server based SQL resource
> So I change it to be the following and it starts working '
> strConnect = "Server=" & DB_Server & ";DRIVER=SQL
> Server;UID=abc;PWD=def"
> So it started not liking the 'Network=DBMSSOCN' part but both the
> datbases have TCP/IP and Named Pipes setup as network protocols and
> bot have not chnaged config for years
> I did install SP2 for XP a few weeks ago but I'm sure I have run it
> since (mind you I wish I'd never done SP2 with all the unasked for
> 'extras' MS dump on your PC but thats another thread)
> Thanks all
> shaun|||Thanks for the link Keith
Yep it is odd as I thought both were fine as well and the one now is
not working worked fine for months!!!
Ah well the odditiess of Microsoft
Cheers
Shaun
"Keith Kratochvil" <sqlguy.back2u@.comcast.net> wrote in message news:<uQts2dgCFHA.3908@.TK2MSFTNGP12.phx.gbl>...
> Strange. It looks that both strings are correct (although I would put the
> network part toward the end as a personal preference).
> I often refer to http://www.connectionstrings.com/ for examples and usage of
> connection strings.
> --
> Keith
>
> "Shaun" <shaunsizen@.msn.com> wrote in message
> news:4a2f9143.0502030133.5892ee76@.posting.google.com...
> > Hi
> >
> > Odd one here, I have a local version of SQL running on my laptop for
> > demos, been working fine for years yet yesterday I suddenly get an
> > error "Invalid Conection Parameter" running a sproc using the
> > following connection string (Its an Access 2002 App to SQL 2000)
> >
> > strConnect = "Network=DBMSSOCN;Server=" & DB_Server & ";DRIVER=SQL
> > Server;UID=abc;PWD=def"
> >
> > Works fine if I use the server based SQL resource
> >
> > So I change it to be the following and it starts working '
> >
> > strConnect = "Server=" & DB_Server & ";DRIVER=SQL
> > Server;UID=abc;PWD=def"
> >
> > So it started not liking the 'Network=DBMSSOCN' part but both the
> > datbases have TCP/IP and Named Pipes setup as network protocols and
> > bot have not chnaged config for years
> >
> > I did install SP2 for XP a few weeks ago but I'm sure I have run it
> > since (mind you I wish I'd never done SP2 with all the unasked for
> > 'extras' MS dump on your PC but thats another thread)
> >
> > Thanks all
> > shaun|||Win XP SP2 also probably updated your MDAC or exposed an MDAC vunerability
that was updated recently through Windows Updates.
Nevertheless, you are using the OLEDB for ODBC, MSADSQL? Why not just use
the SQLOLEDB directly seeing as you are not using the functionality that an
ODBC DSN would give you? If I am wrong, then it is the DRIVER=SQLSERVER
that is throwing you. That's an ODBC Only OLEDB parameter.
Sincerely,
Anthony Thomas
"Shaun" <shaunsizen@.msn.com> wrote in message
news:4a2f9143.0502030133.5892ee76@.posting.google.com...
Hi
Odd one here, I have a local version of SQL running on my laptop for
demos, been working fine for years yet yesterday I suddenly get an
error "Invalid Conection Parameter" running a sproc using the
following connection string (Its an Access 2002 App to SQL 2000)
strConnect = "Network=DBMSSOCN;Server=" & DB_Server & ";DRIVER=SQL
Server;UID=abc;PWD=def"
Works fine if I use the server based SQL resource
So I change it to be the following and it starts working '
strConnect = "Server=" & DB_Server & ";DRIVER=SQL
Server;UID=abc;PWD=def"
So it started not liking the 'Network=DBMSSOCN' part but both the
datbases have TCP/IP and Named Pipes setup as network protocols and
bot have not chnaged config for years
I did install SP2 for XP a few weeks ago but I'm sure I have run it
since (mind you I wish I'd never done SP2 with all the unasked for
'extras' MS dump on your PC but thats another thread)
Thanks all
shaun

Connection String suddenly Stops working

Hi
Odd one here, I have a local version of SQL running on my laptop for
demos, been working fine for years yet yesterday I suddenly get an
error "Invalid Conection Parameter" running a sproc using the
following connection string (Its an Access 2002 App to SQL 2000)
strConnect = "Network=DBMSSOCN;Server=" & DB_Server & ";DRIVER=SQL
Server;UID=abc;PWD=def"
Works fine if I use the server based SQL resource
So I change it to be the following and it starts working '
strConnect = "Server=" & DB_Server & ";DRIVER=SQL
Server;UID=abc;PWD=def"
So it started not liking the 'Network=DBMSSOCN' part but both the
datbases have TCP/IP and Named Pipes setup as network protocols and
bot have not chnaged config for years
I did install SP2 for XP a few weeks ago but I'm sure I have run it
since (mind you I wish I'd never done SP2 with all the unasked for
'extras' MS dump on your PC but thats another thread)
Thanks all
shaunStrange. It looks that both strings are correct (although I would put the
network part toward the end as a personal preference).
I often refer to http://www.connectionstrings.com/ for examples and usage of
connection strings.
Keith
"Shaun" <shaunsizen@.msn.com> wrote in message
news:4a2f9143.0502030133.5892ee76@.posting.google.com...
> Hi
> Odd one here, I have a local version of SQL running on my laptop for
> demos, been working fine for years yet yesterday I suddenly get an
> error "Invalid Conection Parameter" running a sproc using the
> following connection string (Its an Access 2002 App to SQL 2000)
> strConnect = "Network=DBMSSOCN;Server=" & DB_Server & ";DRIVER=SQL
> Server;UID=abc;PWD=def"
> Works fine if I use the server based SQL resource
> So I change it to be the following and it starts working '
> strConnect = "Server=" & DB_Server & ";DRIVER=SQL
> Server;UID=abc;PWD=def"
> So it started not liking the 'Network=DBMSSOCN' part but both the
> datbases have TCP/IP and Named Pipes setup as network protocols and
> bot have not chnaged config for years
> I did install SP2 for XP a few weeks ago but I'm sure I have run it
> since (mind you I wish I'd never done SP2 with all the unasked for
> 'extras' MS dump on your PC but thats another thread)
> Thanks all
> shaun|||Thanks for the link Keith
Yep it is odd as I thought both were fine as well and the one now is
not working worked fine for months!!!
Ah well the odditiess of Microsoft
Cheers
Shaun
"Keith Kratochvil" <sqlguy.back2u@.comcast.net> wrote in message news:<uQts2dgCFHA.3908@.TK2MS
FTNGP12.phx.gbl>...[vbcol=seagreen]
> Strange. It looks that both strings are correct (although I would put the
> network part toward the end as a personal preference).
> I often refer to http://www.connectionstrings.com/ for examples and usage
of
> connection strings.
> --
> Keith
>
> "Shaun" <shaunsizen@.msn.com> wrote in message
> news:4a2f9143.0502030133.5892ee76@.posting.google.com...|||Win XP SP2 also probably updated your MDAC or exposed an MDAC vunerability
that was updated recently through Windows Updates.
Nevertheless, you are using the OLEDB for ODBC, MSADSQL? Why not just use
the SQLOLEDB directly seeing as you are not using the functionality that an
ODBC DSN would give you? If I am wrong, then it is the DRIVER=SQLSERVER
that is throwing you. That's an ODBC Only OLEDB parameter.
Sincerely,
Anthony Thomas
"Shaun" <shaunsizen@.msn.com> wrote in message
news:4a2f9143.0502030133.5892ee76@.posting.google.com...
Hi
Odd one here, I have a local version of SQL running on my laptop for
demos, been working fine for years yet yesterday I suddenly get an
error "Invalid Conection Parameter" running a sproc using the
following connection string (Its an Access 2002 App to SQL 2000)
strConnect = "Network=DBMSSOCN;Server=" & DB_Server & ";DRIVER=SQL
Server;UID=abc;PWD=def"
Works fine if I use the server based SQL resource
So I change it to be the following and it starts working '
strConnect = "Server=" & DB_Server & ";DRIVER=SQL
Server;UID=abc;PWD=def"
So it started not liking the 'Network=DBMSSOCN' part but both the
datbases have TCP/IP and Named Pipes setup as network protocols and
bot have not chnaged config for years
I did install SP2 for XP a few weeks ago but I'm sure I have run it
since (mind you I wish I'd never done SP2 with all the unasked for
'extras' MS dump on your PC but thats another thread)
Thanks all
shaun

Connection String for SQL Server not working

I have the Visual Studio 2005 Team Suite trial version and the SQL Server 2005 trial (which came with team suite) installed in my machine.

When I installed the SQL Server 2005 I installed it in the Windows Authentication mode. So every time I open SQL Server 2005 it doesnt ask for Username/Password (Its greyed out). The only thing available were:

Server Type: Database Engine

ServerName: ServerSue

Authentication: Windows Authentication.

Here is my Problem:

I created a small application in C#. In the web.config file I created the following:

<

appSettings>

<

addkey="resumecon"value="SERVER=ServerSue;database=Resume;"/>

</

appSettings>

Then in the Code behind I created the following string:

string

strResCon =ConfigurationManager.AppSettings["resumecon"].ToString();

Then in method (for a Login page) I created the connection string as follows and wrote code to insert some values into the Resume database. I called this method on a button click event.

SqlConnection

conLogin =newSqlConnection(strResCon);

When I run the page and when I click the button I get the following error:

Login failed for user ''. The user is not associated with a trusted SQL Server connection.

I think some thing is wrong in the addkey of webconfig? How do I change this?

You have set the database for Windows Authentication but the user account accessing the database does not have permission to it. You need to know thw account used to access the database, which would be the ASP.NET Process account unless you're authenticating or impersonating. Grant that account access to the database or place it in a Windows group that has access.

Or use SQL Authentication.

Jeff

|||

Thanks Jeff. I am too new to SQL Server 2005. I have been using asp.net for the last 5 months and used SQL Server 2000 before.

I didnt quite understand what you mentioned. So is it safe for me to uninstall SQL Server 2005 and install it back with server authentication with a username and password? In that way I can specify the usaname password in the string

Because in the past with SQL Server 2000, I had some virus attack in my machine.

|||

You can use SQL either way, you just need to provide the correct authentication for it. Take a look atwww.connectionstrings.com for options in connecting to SQL, and the documentation for using Windows Authentication. In many cases I would recommend reconfiguring and using SQL Authentication, especially for beginners since most examples assume it, but it's really your choice.

Jeff

|||Thanks so much Jeff. I still havent got the time to do it. I am going to do this weekend and if things go wrong, (rarely I would say), I might post a question here.|||

I am back again. I uninstalled SQL Server 2005 and tried to re install it. But got stuck. When I got the window which says Instance name, there were 2 radio buttons: default instance and named instance.

I clicked the default instance radio button. Is this correct?

In the next window, Service Account window again there are 2 radio buttons:

1. Use the built-in service account radio button. This has a drop down with Local System and Network Service.

2. Use a domain user account radio button which is asking for user name, password, and domain.

Which one should I choose? I chose the second one and gave a username and password. But didnt know what to give for Domain name. Also I got an alert window saying some thing about my user name password not correct or so.

Connection problem, please

I have a server, in datacenter, that have installed a SQL server 2000
standard version
then another PC, in company, need to connect to that SQL server through the
Enterprise Manager.
Althrough I have created both window account or SQL account, I still cannot
connect to that SQL server, it prompt me connOpen(), then access deny or the
server not exist...how to solve it?
thx a lot~Hello.
I don't have an answer to your question but I would advise
that you look at the following.
1) Does the person have access rights to the server (not
SQL) ?
2) Are you using NT Authorisation or mixed mode.
3) Can you user "see" the server though enterprise
manager ? (if not then its a network problem)
4) Does your user have access rights to the database they
are trying to connect to ?
I'm sorry I can't be of more help but there is a lot that
can go wrong.
Can you give actual error messages ?
Peter
>--Original Message--
>I have a server, in datacenter, that have installed a SQL
server 2000
>standard version
>then another PC, in company, need to connect to that SQL
server through the
>Enterprise Manager.
>Althrough I have created both window account or SQL
account, I still cannot
>connect to that SQL server, it prompt me connOpen(), then
access deny or the
>server not exist...how to solve it?
>thx a lot~
>
>.
>

Connection problem OSQL - MSDE

Hello All
I have recently installed MSDE to use with
a trial version of Visual Studio .NET 2003
I installed MSDE 2000 release A with the following command:
Setup.exe /qb+ INSTANCENAME=3D"NetSDK" DISABLENETWORKPROTOCOLS=3D1
SAPWD=3D"notthisone"
I now have to install a database to be used in exercises
that is installed through a bat file:
rem The following command line installs the Contact SQL database
osql -E -i InstContacts.Sql
osql.exe refused to connect with sqlserver. It should communicate
using shared memory but that fails.I have enabled tcp/ip and named
pipes (which are disabled by default) using the Server Network Utility
but that did not work either. It usually fails with the following
messages:
[Shared Memory]SQL Server does not exist or access denied.
[Shared Memory]ConnectionOpen (Connect()).
With tcpip enabled it gives the messages
[Shared Memory]Invalid connection.
[Shared Memory]ConnectionOpen (Invalid Instance()).
after running ther TDIMON utility (www.sysinternals.org)
I get the first error message,
TDIMON seems to screw up some tcpip related settings as I encounter
other problems connecting with ADSL with a ethernet card.
(Could this be causing confusion for OSQL?)
The messages suggest to me that it is using shared memory also
when TCPIP is available.
I have no control over the communications by OSQL,
there seem to be no switches to control it.
I tried several solutions I found in this group and on
a Microsoft site, but none worked so far.
I have one named instance NETSDK of SQL server (desktop engine)
I am running Windows 2000 with
Norton Internet Security 2002
computer/instance=3DSTARSHIP\NETSDK
instance name=3DMSSQL$NETSDK
some version info: 'SSNETLIB.DLL' version '8.0.766'.
I think I have MDAC 2.7 when looking in the registry
Does anyone has an idea what is wrong?
Martin Kramer
mkramer@.wxs.nl
http://home.wxs.nl/~mkramer/
hi Martin,
Martin Kramer wrote:
> rem The following command line installs the Contact SQL database
> osql -E -i InstContacts.Sql
please add the full instance name ...
osql -E -S(Local)\NetSDK -i InstContacts.Sql
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote:

>hi Martin,
>Martin Kramer wrote:
>please add the full instance name ...
>osql -E -S(Local)\NetSDK -i InstContacts.Sql
Thanks a lot
It certainly worked much bettert than anything I tried
There is a database created. I only have doubts about the
access rights for the ASPNET user that the selfstudy samples use.
But this was syntax from microsoft. It should have worked
as it came with the samples. Or has anything gone wrong
initially when osql searches for a database server?
There is only one on my system.
I copied the original bat file to a new one,
adding a pause statement to see the feedback,
because the original flashed away before I could have a look at it.
It seems the problem was not with TCPIP after all,
However, I can not get osql into a command promt mode with
the same syntax. Is that possible and if so, how.
Oracle and DB2 had similar functions.
Or is osql not intended/suitable for such use?
Martin Kramer
mkramer@.wxs.nl
http://home.wxs.nl/~mkramer/
|||hi Martin,
Martin Kramer wrote:
> But this was syntax from microsoft. It should have worked
> as it came with the samples. Or has anything gone wrong
> initially when osql searches for a database server?
> There is only one on my system.
without specifying the destination server, the (Local) server is assumed,
but as long you installed a named instance you have to full qualify it..

> I copied the original bat file to a new one,
> adding a pause statement to see the feedback,
> because the original flashed away before I could have a look at it.
> It seems the problem was not with TCPIP after all,
Shared Memory is used instead of network protocol(s) to connect to local
server..

> However, I can not get osql into a command promt mode with
> the same syntax. Is that possible and if so, how.
> Oracle and DB2 had similar functions.
> Or is osql not intended/suitable for such use?
are you using the one I proposed?
http://msdn.microsoft.com/library/de..._osql_1wxl.asp
http://support.microsoft.com/default...;EN-US;q325003
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote:

>hi Martin,
>Martin Kramer wrote:
>without specifying the destination server, the (Local) server is =
assumed,=20
>but as long you installed a named instance you have to full qualify it..
I understand. Having a named instance requires specifying it.
>
>Shared Memory is used instead of network protocol(s) to connect to local=
=20
>server..
OK. Seems logical as it should be efficient.
>
>are you using the one I proposed?
>http://msdn.microsoft.com/library/de...y/en-us/copro=
mpt/cp_osql_1wxl.asp
>http://support.microsoft.com/default...;EN-US;q325003
I don't understand this question, as you are proposing it only now,
but I found the links very helpful and now have osql.exe running in
command promt mode so I can try all kinds of commands.
This was what I was looking for.
You have been very helpful
Thank you.
Martin Kramer