Showing posts with label message. Show all posts
Showing posts with label message. Show all posts

Sunday, March 25, 2012

connecto to Database

Hello

i was tring to a connecto to a database but i have always this erros

Message 4 Impossible to find the informations the element for the schema 'http://schemas.microsoft.com/.NetConfiguration/v2.0:add'.

Message 2 Impossible to find the informations the element for the schemat 'http://schemas.microsoft.com/.NetConfiguration/v2.0:appSettings'.

Message 3 Impossible to find the informations the element for the schema 'http://schemas.microsoft.com/.NetConfiguration/v2.0:connectionStrings'.

Message 4 Impossible to find the informations the element for the schema 'http://schemas.microsoft.com/.NetConfiguration/v2.0:add'.


my code

<?xml version="1.0"?>
<configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0">
<appSettings/>
<connectionStrings>
<add name="DatabaseConnection" connectionString="Persist Security Info=False;Integrated Security=SSPI;database=MyDatabase;server=(localhost);" providerName="System.Data.SqlClient"/>
</connectionStrings>
<system.web>
<compilation debug="true"/>
<authentication mode="Windows"/>
-->
</system.web>
</configuration>

using System;
using System.Data;
using System.Configuration;
using System.Collections;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;

public partial class application : System.Web.UI.MasterPage
{
protected void Page_Load(object sender, EventArgs e)
{
Connect_to_bdd();
}

protected void Connect_to_bdd()
{
ConnectionStringSettings settings;
settings = ConfigurationManager.ConnectionStrings["DatabaseConnection"];
if (settings != null)
{
Console.WriteLine(settings.ConnectionString);
}
else
{
try
{
SqlConnection oConnection = new SqlConnection(settings);
oConnection.Open();
Console.WriteLine("Etal de la connection" + oConnection.State);
oConnection.Close();
}
catch (Exception e)
{

Console.WriteLine("L'erreur suivante a été rencontrée:" + e.Message);
}
}
}
}

Thanks for help

Hi Bolo,

It seems that your IIS settings hasn't been updated to version 2.0 .

You may enter the folderC:\WINDOWS\Microsoft.NET\Framework\v2.0.50215 in DOS mode and run "aspnet_regiis.exe -i ".

If this does not answer your question, pls feel free to reply. Thanks!

|||

Hello,

i tested but i have always same message :(

regards

Thursday, March 22, 2012

Connectivity issues

Hi,

I get the following error message trying to connect locally to sql server 2005 dev edition on xp sp2 machine.

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 SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (.Net SqlClient Data Provider)

I have enabled all protocols , the sql browser is running , sql agent and sql database engine not running. All other services like reporting etc are running.

The server is set up to run under local system account. Logging in as administrator, .

This server is installed as default instance . ( I do have sql exp and sql server 200 dev edition installed as named instances)

Beginning to pull my hair out.

Any help would be greatly appreciated.

Regards,

Well, you said the database engine is NOT running? From the looks of things that's what you're trying to connect to...I'll assume a typo maybe? The DB Engine service must be running if you're trying to connect to the SQL engine...

|||

Thank you Chad for the illuminating response.

The problem is precisely that the database engine will not start , I understand that the engine must running order for me to connect to a database , however I have made no mention of trying to connect to a database.

If you have any helpful suggestions I would really appreciate it.

Thank you

Andy

|||

Hi Andy...honestly, everything you wrote in your initial posting was indicating that you were having trouble trying to connect to the server...per your initial post:

"I get the following error message trying to connect locally to sql server 2005 dev edition on xp sp2 machine."

Then, the error message you posted indicates that you are indeed trying to connect to the server from an application:

"An error has occurred while establishing a connection to the server...."

And, it even describes a connection level provider (named pipes)...

So, given your original posting, it seems you are having trouble connecting to the instance, not getting it running. Myself and others would be more than happy to help you debug why you are having trouble getting the engine to start, but we'd need entirely different information.

If you'd like help with why the engine is not able to start, please post any error messages you notice in the application log, sql server error log, and system log related to the SQL Server instance, that's what we'd need to see to help you understand why the engine will not start.

On a final note, bear in mind that folks on the forums are trying to help you, not trying to insult you, and you'll always get more help if you treat myself and others with respect, not by being smart with us. You may notice that I am an administrator of these SQL forums, so please keep posts as civil as possible.

Regards

|||

HI Chad,

My apologies for coming across so curt , having re-read my response it does seem as though I was being rude , not my intention. Perhaps a bit of frustration creeping in, the problem is that my vocabulary and knowledge is lacking and expressing myself in a meaningful way is difficult and perhaps to some one with your knowledge, confusing.

If I am getting an error as described above when trying to get an instance started (i.e. the error is generated when I try and get the engine started) through Management Studio then I assume that error is relevant and that is what I will report on. Having read your second post it is now obvious that the error describes a connection problem rather than an issue regarding the instance running.( which obviously is as result of the engine not running.)

I checked the error log and found a network error which I googled , it seems as though if the via protocol is the culprit , having disabled this protocol the engine started .

The network error in the log:

TDSSNIClient initialization failed with error 0x7e, status code 0x60.

Thank you and my apologies once again.

|||

No worries, I definately understand frustation, we're all quite accustomed to that unfortunately. Glad you were able to get things working,

Regards,

sqlsql

Connectivity from Client to Server

Hai,

I am often getting the message

"SQL Server does not exist or access denied (Connection Open (Connect())"

when connecting from the client sql 2000 to the server and at sometimes it gets connected and it still exists/persists for some time.

though i checked the user rights, client server network utility where tcp/ip is the first protocol.

Give a (me) way to connect to the server, though the user iam trying to connect works in the Query Analyser in the Server

here,
vijayanand.gI know this a post from a previous post. I would try sql profiler and monitor the connections to see if the server is rejecting you or are you not getting there at all. You can use vnc or terminal services to connect to the server (for a good connection) and monitor your connection status.

Let me know.|||Hai,

Though i connect from the profiler the Server gives an error


here,
vijayanand.g|||Is the server behind any firewall?
Originally posted by g_vijayanand
Hai,

Though i connect from the profiler the Server gives an error


here,
vijayanand.g|||You need to execute the profiler either on the sql server or through a remote connection (using vnc or terminal services). Then try to connect on your machine and see what the profiler shows.|||Sorry - I just received your emails - I only have access to my email at home. Basically, you will need to find a machine that has access to the sql server (or login to the actual sql server) and run the profiler and see if at least the server sees that you are attempting to hit it.|||Hai,

The profiler does not connect and trace the required samples.

here,
vijayanand.g|||Hai,

I tried to connect from other machine in sql enterprise manager and query analyser for the specified user, it connects - but through my login in the domain it does not connect.

For the past 1 week iam trying to connect from a XP Machine , it does not connect, i tried to connect from a Windows 98 machine it connects, from a machine that has been logged as an administrator it connects, now i've changed my machines OS to Windows NT Server - now also not connecting .

here,
vijayanand.g|||Hai,

Connected to the Server. It was due to the entry that did not exist for the specified machine in the Hosts file or LmHosts file for the specified machine name.

The connectivity came when the connection was tested with the server by registering the Client by giving the ip address of the machine.

here,
vijayanand.g

connectivity error while registering a new group

While registering sqlserver group I am getting the following
error message
"You must upgrade your SQL Enterprise Manager and SQL DMO (SQL-OLE) to SQL server (SQL DMO) to connect to server."
Can any one please guide me how to overcome this proble.
thanx regardsLook at Knowledge Base Article:

HOW TO: Administer Different Versions of SQL Server by Using SQL Server Enterprise Manager (http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/Q225/5/45.asp&NoWebContent=1)sqlsql

ConnectionString property not initialized

I am getting an error message that says that my connection string has not been intialized I have initialized it.

Dim AirliquidiConnAsNew SqlClient.SqlConnection(ConfigurationManager.AppSettings("AirliquidiDatabase"))

Any suggestions??

Check out this article on using the connectionStrings element in the configuration file. Good luck!

http://weblogs.asp.net/jgaylord/archive/2005/05/12/406639.aspx

|||

with that line you've only created a connection instance, but have not initialized it. You'll need to actually use it before it will work now.

here's what you need to do. You need to add a "using" statement to the code and handle the data retrieval inside of it.

Dim connString As String = _
ConfigurationManager.ConnectionStrings(connStringName).ConnectionString

'Create a SqlConnection instance
Using myConnection As New SqlConnection(connString)
'Specify the SQL query
Const sql As String = "SELECT * FROM Customers"

'Create a SqlCommand instance
Dim myCommand As New SqlCommand(sql, myConnection)

'Get back a DataSet
Dim myDataSet As New DataSet

'Create a SqlDataAdapter instance
Dim myAdapter As New SqlDataAdapter(myCommand)
myAdapter.Fill(myDataSet)

'Bind the DataSet to the GridView
gvCustomers.DataSource = myDataSet
gvCustomers.DataBind()

'Close the connection
myConnection.Close()
End Using

You can visit http://aspnet.4guysfromrolla.com/articles/110905-1.aspx for a more thorough explanation (the page I got this code from)

|||I have this information in my web.config|||

This is what I have. Would I be putting a using statement in the Page_Load?

ProtectedSub Button1_Click(ByVal senderAsObject,ByVal eAs System.EventArgs)Handles Button1.Click

Dim connAirliquidiAsNew SqlClient.SqlConnection(ConfigurationManager.AppSettings("AirliquidiDatabase"))

Dim cmdInsertLoginAsNew SqlClient.SqlCommand("Insert into Logins(ID, Username, LoginDate) values (@.ID, @.Username,@.LoginDate)", connAirliquidi)

Dim activeUserAsString

Dim IDAs Guid = System.Guid.NewGuid

Dim cmdCheckUserCredentialsAsNew SqlClient.SqlCommand("select * From Usernames where(username=@.username and password=@.password)", connAirliquidi)

'If user did not fill in a username or password

If txtUsername.Text =""Or txtPassword.Text =""Then

Message("Please fill in a username/password")

Else

Try

connAirliquidi.Open()

cmdCheckUserCredentials.Parameters.AddWithValue("@.Username", Trim(txtUsername.Text))

cmdCheckUserCredentials.Parameters.AddWithValue("@.password", Trim(txtPassword.Text))

SelectCase activeUser

CaseTrue

cmdInsertLogin.Parameters.AddWithValue("@.ID", ID)

cmdInsertLogin.Parameters.AddWithValue("@.Username", Trim(txtUsername.Text))

cmdInsertLogin.Parameters.AddWithValue("@.LoginDate",Date.Now())

Session("Username") = Trim(txtUsername.Text)

FormsAuthentication.SetAuthCookie(txtUsername.Text,False)

Session("ID") = ID.ToString

Response.Redirect("ALSI.aspx?ID={" & ID.ToString &"}")

CaseFalse

Message("Inactive user")

CaseElse

Message("Invalid Username and/or Password")

EndSelect

Catch exAs Exception

Message("Error authenticating user. Please try again.")

Finally

connAirliquidi.Close()

EndTry

EndIf

EndSub

|||

you have to open the connection before you use the sql command. moveconnAirliquidi.Open() directly below this line

Dim connAirliquidiAsNew SqlClient.SqlConnection(ConfigurationManager.AppSettings("AirliquidiDatabase"))

which also means you'll have to move the connAirliquidi.close() down to directly above the End Sub line.

|||

I did that and I am still getting the same error message.

|||Can you post a snap from your web.config file where you've actually declared the connection string ?|||<configuration>

<appSettings>

<addkey="customerservice"value="abetha@.airsep.com"/>

<addkey="smtpserver"value=""/>

<addkey="AirliquidiConn"value="Airliquidi id=**;data source=SEPSQL;persist security info=True;initial catalog=Usernames;password=****"/>

</appSettings>

<connectionStrings>

<addname="AirliquidiConn"connectionString="Data Source=SEPSQL;Database=Airliquidi;User ID=**;Password=*****"

providerName="System.Data.SqlClient" />

</connectionStrings>

|||

Correct me if I'm wrong but in your earlier posts you've written the name of your connection string to be "AirliquidiDatabase" and you've set it to be used from appSettings. Now, the snap you've posted is not having a connection string with the name you might be using in your code. Both the connection strings that you've set in your config file are named "AirliquidiConn".

|||

Thank you for catching that. I have changed it to AirliquidiConn and I am still getting the same error.

Sunday, March 11, 2012

Connection to SQL2005 Database Engine

On one server I connect to I always get this message when I try to launch object explorer.
TITLE: Microsoft SQL Server Management Studio
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
Insert Error :column name or number of supplied values doesn't match.. Error:213.

Sometimes I can run refresh, and it will eventually connect.

Is the version of sql server you're connecting to the same as the one that was installed where you're launching SSMS? If not, and depending on the versions, underlying procs that SSMS depend on may be different between the two versions.
|||The server is SQL Standard Sept. release, and I installed the same version, workstation only on my station. I eventually get the browser to work. Other server is a June release std and it doesn't do this. I reinstalled every workstation component, and now I have SSIS working but still getting the browser error looking at objects on this server. BTW this server has been installed a couple of times .|||I found out that I had some possible old components in the install dir, so I started over again with fresh Sept install. When I did that , I noticed again my SQL2000 Ent Mgr quit working as I uninstalled. Prev. I had repatched SQL sp4 then reran setup of 2005. This time I left it alone , finished up install, and lo and behold the object browser works AND SQL 2000 Ent. MGr. What I am trying to deduce is the sqldmo dll might be involved . Does SQL2005 install replace that in the Windows directory , and it happens to have backwards compatibility so the 2000 still can use it ? Here is a link to the article. All is right for the moment, I shall cherish it at least the SQL2005 world a bit better.

http://www.aspfaq.com/sql2005/show.asp?id=4

Thursday, March 8, 2012

Connection to Server Failed - Analysis Services

Hi,
For some unknown reason, we are getting the following "Connection to Server
Failed" error message when we attempt to register our local server using MS
Analysis Services:
"Errors occurred while connecting to '<localservername>'. Cannot open
connection to Analysis server '<localservername>'. Cannot connect to the
server '<localservername>'. The server is either not started or too busy. Do
you still want to register the server?
Please note that we are running the Developer versions of MS SQL Server 2000
and MS Analysis Services with SP3 installed for both components on Windows X
P
Professional.
Also note that we ARE ABLE TO REGISTER A REMOTE SERVER successfully using
Analysis Manager, but we aren't able to either register or connect to a loca
l
server because we get the message above.
We are uttterly confused by this error message and would GREATLY APPRECIATE
any help in resolving this confusing issue as soon as possible.
Thanks,
Raj C.Is the Analysis services service started on the local machine?
Simon Worth
Raj C. wrote:
> Hi,
> For some unknown reason, we are getting the following "Connection to Serve
r
> Failed" error message when we attempt to register our local server using M
S
> Analysis Services:
> "Errors occurred while connecting to '<localservername>'. Cannot open
> connection to Analysis server '<localservername>'. Cannot connect to the
> server '<localservername>'. The server is either not started or too busy.
Do
> you still want to register the server?
> Please note that we are running the Developer versions of MS SQL Server 20
00
> and MS Analysis Services with SP3 installed for both components on Windows
XP
> Professional.
> Also note that we ARE ABLE TO REGISTER A REMOTE SERVER successfully using
> Analysis Manager, but we aren't able to either register or connect to a lo
cal
> server because we get the message above.
> We are uttterly confused by this error message and would GREATLY APPRECIAT
E
> any help in resolving this confusing issue as soon as possible.
> Thanks,
> Raj C.|||If you mean did we launch Analysis Manager on the local machine - than yes.
But for some unknown reason, we can't register the local server but we can
register a remote server on the network. FYI - Our login name is a member o
f
the OLAP admin group.
Please HELP!
Raj C.
"Simon Worth" wrote:

> Is the Analysis services service started on the local machine?
> Simon Worth
> Raj C. wrote:
>|||No, I mean, is the actual Analysis Services Service running on the machine?
To start Microsoft? SQL Server? 2000 Analysis Services, follow these step
s:
Open Control Panel.
If your computer's operating system is Windows? 2000, open the
Administrative Tools folder, and then double-click Services.
If your computer's operating system is Windows NT? 4.0, double-click
Services.
Select MSSQLServerOLAPService, and then on the Action menu click Start.
Simon Worth
Raj C. wrote:[vbcol=seagreen]
> If you mean did we launch Analysis Manager on the local machine - than yes
.
> But for some unknown reason, we can't register the local server but we can
> register a remote server on the network. FYI - Our login name is a member
of
> the OLAP admin group.
> Please HELP!
> Raj C.
> "Simon Worth" wrote:
>|||Yes we are running bot SQL 2000 Enterprise Manager and Analysis Services on
the local machine.
"Simon Worth" wrote:

> No, I mean, is the actual Analysis Services Service running on the machine
?
> To start Microsoft? SQL Server? 2000 Analysis Services, follow these st
eps:
> Open Control Panel.
>
> If your computer's operating system is Windows? 2000, open the
> Administrative Tools folder, and then double-click Services.
> If your computer's operating system is Windows NT? 4.0, double-click
> Services.
> Select MSSQLServerOLAPService, and then on the Action menu click Start.
>
>
> Simon Worth
> Raj C. wrote:
>|||But is the service started? When you view the service in control panel
> services, is the MSSQLServerOLAPService service in a started state?
You can have it installed on the machine, but it doesn't do anything if
you don't actually start the service.
Simon Worth
Raj C. wrote:[vbcol=seagreen]
> Yes we are running bot SQL 2000 Enterprise Manager and Analysis Services o
n
> the local machine.
>
> "Simon Worth" wrote:
>

Connection to Server Failed - Analysis Services

Hi,
For some unknown reason, we are getting the following "Connection to Server
Failed" error message when we attempt to register our local server using MS
Analysis Services:
"Errors occurred while connecting to '<localservername>'. Cannot open
connection to Analysis server '<localservername>'. Cannot connect to the
server '<localservername>'. The server is either not started or too busy. Do
you still want to register the server?
Please note that we are running the Developer versions of MS SQL Server 2000
and MS Analysis Services with SP3 installed for both components on Windows XP
Professional.
Also note that we ARE ABLE TO REGISTER A REMOTE SERVER successfully using
Analysis Manager, but we aren't able to either register or connect to a local
server because we get the message above.
We are uttterly confused by this error message and would GREATLY APPRECIATE
any help in resolving this confusing issue as soon as possible.
Thanks,
Raj C.
Is the Analysis services service started on the local machine?
Simon Worth
Raj C. wrote:
> Hi,
> For some unknown reason, we are getting the following "Connection to Server
> Failed" error message when we attempt to register our local server using MS
> Analysis Services:
> "Errors occurred while connecting to '<localservername>'. Cannot open
> connection to Analysis server '<localservername>'. Cannot connect to the
> server '<localservername>'. The server is either not started or too busy. Do
> you still want to register the server?
> Please note that we are running the Developer versions of MS SQL Server 2000
> and MS Analysis Services with SP3 installed for both components on Windows XP
> Professional.
> Also note that we ARE ABLE TO REGISTER A REMOTE SERVER successfully using
> Analysis Manager, but we aren't able to either register or connect to a local
> server because we get the message above.
> We are uttterly confused by this error message and would GREATLY APPRECIATE
> any help in resolving this confusing issue as soon as possible.
> Thanks,
> Raj C.
|||If you mean did we launch Analysis Manager on the local machine - than yes.
But for some unknown reason, we can't register the local server but we can
register a remote server on the network. FYI - Our login name is a member of
the OLAP admin group.
Please HELP!
Raj C.
"Simon Worth" wrote:

> Is the Analysis services service started on the local machine?
> Simon Worth
> Raj C. wrote:
>
|||No, I mean, is the actual Analysis Services Service running on the machine?
To start Microsoft? SQL Server? 2000 Analysis Services, follow these steps:
Open Control Panel.
If your computer's operating system is Windows? 2000, open the
Administrative Tools folder, and then double-click Services.
If your computer's operating system is Windows NT? 4.0, double-click
Services.
Select MSSQLServerOLAPService, and then on the Action menu click Start.
Simon Worth
Raj C. wrote:[vbcol=seagreen]
> If you mean did we launch Analysis Manager on the local machine - than yes.
> But for some unknown reason, we can't register the local server but we can
> register a remote server on the network. FYI - Our login name is a member of
> the OLAP admin group.
> Please HELP!
> Raj C.
> "Simon Worth" wrote:
>
|||Yes we are running bot SQL 2000 Enterprise Manager and Analysis Services on
the local machine.
"Simon Worth" wrote:

> No, I mean, is the actual Analysis Services Service running on the machine?
> To start Microsoft? SQL Server? 2000 Analysis Services, follow these steps:
> Open Control Panel.
>
> If your computer's operating system is Windows? 2000, open the
> Administrative Tools folder, and then double-click Services.
> If your computer's operating system is Windows NT? 4.0, double-click
> Services.
> Select MSSQLServerOLAPService, and then on the Action menu click Start.
>
>
> Simon Worth
> Raj C. wrote:
>
|||But is the service started? When you view the service in control panel
> services, is the MSSQLServerOLAPService service in a started state?
You can have it installed on the machine, but it doesn't do anything if
you don't actually start the service.
Simon Worth
Raj C. wrote:[vbcol=seagreen]
> Yes we are running bot SQL 2000 Enterprise Manager and Analysis Services on
> the local machine.
>
> "Simon Worth" wrote:
>

Connection to Oracle10g

(Hope this is the right forum to post this message. If not, could someone please tell me the right one?)


I'm trying to connect to oracle 10g from sql server 2000.
Oracle client tools 10g is installed on the same server as sql server.
MDAC 2.8 installed.
Tnsnames.ora file is correct. (checked with the oracle dba..).
But I still can't connect. Error message is:

Error source: Microsoft Ole Db provider for ODBC drivers
Error Description: [Microsoft][ODBC driver for Oracle][Microsoft]

Tried both odbc and oledb provider connections within dts package...

(And: cannot connect to old oracle (still running) version 9i...)

Connecting via sql*plus to old oracle working fine... but not to new
oracle server.
Tnsping to both servers working fine...

Anybody who has an idea?

Regards Jan

The Microsoft ODBC driver only provides full support for Oracle 7, and some limited support for Oracle 8 through emulation. It is unsupported for Orcale 9. You can see the roadmap for our data components via: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/Dnmdac/html/data_mdacroadmap.asp. Please contact Oracle for their ODBC driver. Thanks|||

Thanks, should do it, i hope ;-)

Jan

Saturday, February 25, 2012

Connection Timed Out Error

hello all,
can any one explain sql State HYT00
im getting this as a part of the connection timed out message, while connecting from my node to sql server 2000 instance running on windows 2000 server.
thanks in advancepresume the connection is there and you can ping the other server?

How are you attempting to connect?

Has it just stopped? Have you ever had connection? have you checked that the correct protocols are enabled on the target server?

Jim|||YES JIM

I CAN PING THE MACHINE

IVE CONFIGURED THE CLIENT NETWORK UTILITY TO USE TCP

PROTOCOL TO LISTEN TO THE DEFAULT PORT 1433. THE SERVER

NETWORK UTILITY IS ALSO CONFIGURED

I COULD CONNECT TO THE SERVER BEFORE, BUT IT DROPS ALL OF A
SUDDEN,AND DISPLAYS THE 'CONNECTION TIMED OUT' MESSAGE

IM GETTING THIS MESSAGE WHILE ATTEMTPTING AN ODBC CREATION.|||http://vyaskn.tripod.com/sql_odbc_timeout_expired.htm to resolve the issue.

HTH

'Connection terminated' errors in C/S application...

Client workstations getting 'conection terminated' message through the client
app.
Happens sporadically and we can't seem to make it happen. Sometimes the
users get error messages from SQL Srvr and sometimes just the 'con term'
message. I've checked the switch, the wire, the patch level, the clients
(2000, xp pro, 98se), drivers, apps, nics, power, phases of the moon...
Have an open case w/microsoft for over a month! No help... Updated mdac,
jet, SQL, keep alives, max ports, wait time... Using named pipes and tcp.
Have done limited net monitoring (through MS worthless net monitor prog,
doing ethereal next) and can't come up with any definitive 'ah hah' and alas
a fix.
Anyone with an opinion, possible fix? This has gotten VERY old. Some days,
up to a week, no errs. Other days up to 5 or 6 an hour! YIKES!
Clients are 98se, 2k, XP Pro.
Server 2003 SBS SP1 throughout
SQL Server 2000 SP3a
Hi
I assume there is no information in the Windows Event log or SQL Server log
to help you?
Have you tried running the client on the server (with and without shared
memory)?
You may want to try setting up a separate (small) test environment to see if
it still happens with other hardware on a standalone network.
John
"drkc" wrote:

> Client workstations getting 'conection terminated' message through the client
> app.
> Happens sporadically and we can't seem to make it happen. Sometimes the
> users get error messages from SQL Srvr and sometimes just the 'con term'
> message. I've checked the switch, the wire, the patch level, the clients
> (2000, xp pro, 98se), drivers, apps, nics, power, phases of the moon...
> Have an open case w/microsoft for over a month! No help... Updated mdac,
> jet, SQL, keep alives, max ports, wait time... Using named pipes and tcp.
> Have done limited net monitoring (through MS worthless net monitor prog,
> doing ethereal next) and can't come up with any definitive 'ah hah' and alas
> a fix.
> Anyone with an opinion, possible fix? This has gotten VERY old. Some days,
> up to a week, no errs. Other days up to 5 or 6 an hour! YIKES!
> Clients are 98se, 2k, XP Pro.
> Server 2003 SBS SP1 throughout
> SQL Server 2000 SP3a
>

'Connection terminated' errors in C/S application...

Client workstations getting 'conection terminated' message through the clien
t
app.
Happens sporadically and we can't seem to make it happen. Sometimes the
users get error messages from SQL Srvr and sometimes just the 'con term'
message. I've checked the switch, the wire, the patch level, the clients
(2000, xp pro, 98se), drivers, apps, nics, power, phases of the moon...
Have an open case w/microsoft for over a month! No help... Updated mdac,
jet, SQL, keep alives, max ports, wait time... Using named pipes and tcp.
Have done limited net monitoring (through MS worthless net monitor prog,
doing ethereal next) and can't come up with any definitive 'ah hah' and alas
a fix.
Anyone with an opinion, possible fix? This has gotten VERY old. Some days,
up to a week, no errs. Other days up to 5 or 6 an hour! YIKES!
Clients are 98se, 2k, XP Pro.
Server 2003 SBS SP1 throughout
SQL Server 2000 SP3aHi
I assume there is no information in the Windows Event log or SQL Server log
to help you?
Have you tried running the client on the server (with and without shared
memory)?
You may want to try setting up a separate (small) test environment to see if
it still happens with other hardware on a standalone network.
John
"drkc" wrote:

> Client workstations getting 'conection terminated' message through the cli
ent
> app.
> Happens sporadically and we can't seem to make it happen. Sometimes the
> users get error messages from SQL Srvr and sometimes just the 'con term'
> message. I've checked the switch, the wire, the patch level, the clients
> (2000, xp pro, 98se), drivers, apps, nics, power, phases of the moon...
> Have an open case w/microsoft for over a month! No help... Updated mdac,
> jet, SQL, keep alives, max ports, wait time... Using named pipes and tcp.
> Have done limited net monitoring (through MS worthless net monitor prog,
> doing ethereal next) and can't come up with any definitive 'ah hah' and al
as
> a fix.
> Anyone with an opinion, possible fix? This has gotten VERY old. Some days,
> up to a week, no errs. Other days up to 5 or 6 an hour! YIKES!
> Clients are 98se, 2k, XP Pro.
> Server 2003 SBS SP1 throughout
> SQL Server 2000 SP3a
>

'Connection terminated' errors in C/S application...

Client workstations getting 'conection terminated' message through the client
app.
Happens sporadically and we can't seem to make it happen. Sometimes the
users get error messages from SQL Srvr and sometimes just the 'con term'
message. I've checked the switch, the wire, the patch level, the clients
(2000, xp pro, 98se), drivers, apps, nics, power, phases of the moon...
Have an open case w/microsoft for over a month! No help... Updated mdac,
jet, SQL, keep alives, max ports, wait time... Using named pipes and tcp.
Have done limited net monitoring (through MS worthless net monitor prog,
doing ethereal next) and can't come up with any definitive 'ah hah' and alas
a fix.
Anyone with an opinion, possible fix? This has gotten VERY old. Some days,
up to a week, no errs. Other days up to 5 or 6 an hour! YIKES!
Clients are 98se, 2k, XP Pro.
Server 2003 SBS SP1 throughout
SQL Server 2000 SP3aHi
I assume there is no information in the Windows Event log or SQL Server log
to help you?
Have you tried running the client on the server (with and without shared
memory)?
You may want to try setting up a separate (small) test environment to see if
it still happens with other hardware on a standalone network.
John
"drkc" wrote:
> Client workstations getting 'conection terminated' message through the client
> app.
> Happens sporadically and we can't seem to make it happen. Sometimes the
> users get error messages from SQL Srvr and sometimes just the 'con term'
> message. I've checked the switch, the wire, the patch level, the clients
> (2000, xp pro, 98se), drivers, apps, nics, power, phases of the moon...
> Have an open case w/microsoft for over a month! No help... Updated mdac,
> jet, SQL, keep alives, max ports, wait time... Using named pipes and tcp.
> Have done limited net monitoring (through MS worthless net monitor prog,
> doing ethereal next) and can't come up with any definitive 'ah hah' and alas
> a fix.
> Anyone with an opinion, possible fix? This has gotten VERY old. Some days,
> up to a week, no errs. Other days up to 5 or 6 an hour! YIKES!
> Clients are 98se, 2k, XP Pro.
> Server 2003 SBS SP1 throughout
> SQL Server 2000 SP3a
>

Tuesday, February 14, 2012

Connection string

Hi
Can someone advise where I locate the connection string in SQL server 2000.
I keep getting a "Server does not exist" message when trying to connect to
another SQLserver computer (although the server is running).
TIA
cdsHere is a excellent source for all possible connection strings:
http://www.able-consulting.com/ADO_Conn.htm.
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com
"cds" <cdsaus2001@.yahoo.com.au> wrote in message
news:416902cd$0$20130$afc38c87@.news.optusnet.com.au...
> Hi
> Can someone advise where I locate the connection string in SQL server
2000.
> I keep getting a "Server does not exist" message when trying to connect to
> another SQLserver computer (although the server is running).
> TIA
> cds
>

Connection string

Hi
Can someone advise where I locate the connection string in SQL server 2000.
I keep getting a "Server does not exist" message when trying to connect to
another SQLserver computer (although the server is running).
TIA
cds
Here is a excellent source for all possible connection strings:
http://www.able-consulting.com/ADO_Conn.htm.
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com
"cds" <cdsaus2001@.yahoo.com.au> wrote in message
news:416902cd$0$20130$afc38c87@.news.optusnet.com.a u...
> Hi
> Can someone advise where I locate the connection string in SQL server
2000.
> I keep getting a "Server does not exist" message when trying to connect to
> another SQLserver computer (although the server is running).
> TIA
> cds
>

Sunday, February 12, 2012

Connection problems

Basically I am getting this message every now and again: "Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached." But the weirdest thing is I am closing all my connections, and using a single connection string to my SQL Server database. Here is a typical function to prove this:

Public Shared Function GetTheMenu() As SqlDataReader


Dim connection As New SqlConnection(dbconnection.connString)
Dim command As New SqlCommand("SP_GetTheMenu", connection)


command.CommandType = CommandType.StoredProcedure
connection.Open()


Return command.ExecuteReader(CommandBehavior.CloseConnection)


End Function

When I go into SQL i just see loads of open connections to the database with references to the stored procedure that has been executed - surely this should not be the case if the stored procedure is a simple Select statement that is pases a value to to a datareader, and is (supposedly) automatically closed?

Can anyone suggest reasons why this is happening?

Thanks.

I have seen this error before. Have you tried calling Close() manually on the connection object?

Andy.Smile

|||Yes and it makes no differenceTongue Tied|||Also make sure to close all DataReaders after finishing using them. You can also try Dispose() connections after using them.|||Is there anything I can do at the database level to make sure the connection closes?|||

You can check the master..sysprocesses to find out current connections on the SQL Server. Please take a look at this post:

http://forums.asp.net/thread/1400183.aspx

Friday, February 10, 2012

Connection problem

I am trying to connect a GridView to an SqlDataSource control and am getting the following error message: Following error occurred while getting connection string information from configuration. "Cannot get web application service" I added a connection successfully. I previously had Beta 2 installed and it worked. Now I am getting this error. Please help.I'm having the same issue, but did NOT have Beta 2 installed (in case someone considers that a factor)
Thanks,
Chris|||

Actually, chalk this one up to the Bizzarre Department:

I had manually created 2 data connections to 2 SSE databases on the same box as the VS2005 Pro. No problem. I usually deal with my data connections and access by hand and not by control, so this was my natural first step in order to be able to work with the database though the VS IDE.

When I dropped the SQLDataSource control onto the page and attempted to deal with the connection attributes, I received the above message.

So I removed both dB connections from the server browser and opened a new ASP.NET web project. I dropped the SQLDataSource control to the blank, pristine DEFAULT.ASPX page. When I clicked on the link to configure the properties, it worked perfectly fine.

I THEN went back to the original project, now with NO data connections in the server explorer. I dropped the SQLDataSource control onto the page where I had been having the issues before, and it worked fine. I deleted the control and re-added the data connection via the server explorer, and re-added the control. Again, no error. Even when I re-added the OTHER connection via the server explorer, I was able to drop the control and access it without issue. In fact, the config wizard picked up both data connections as expected.

It seems that because I had defined the items in the server browser BEFORE I tried the SQLDataSource control, it had issues. When they were removed, the control worked fine, even after adding the connections back in via the server browser.

The ONLY other thing that was different was that the web.config file for the original project that was throwing errors had a value for the <ConnectionString> which pointed to one of the two original data connections defined via the server explorer. I had removed the connection string info...but didn't actually re-format the XML properly for an empty element (my bad). My second project had a correctly formatted web.config file, and the success on the original project seemed to come after I went and properly formatted the web.config file.

Hope some of this rambling helps!

Chris

Connection Problem

Hi,
I'm facing on my local machine (Windows 2000 advance server + SQL Server 7.0). its a site in asp.net. sometimes i recieve the message that connection timedout. When i check the number of connections in Performance Monitor, they had reached the max size of 100.

I think my problem lies in connections that remain open after the page is loaded. For example whenever I run a particular page(that shows a complex report), 14 more connections are added to User Connections in Performance Monitor.
Can anyone tell me why the connections remain open even after the page is executed? Shouldn't they be closed once the page is loaded and returned to the connection pool to be reused?

Any help/suggestion will be highly appreciated.

ThanksThey should. Can you show us the connection string you use? Also are you closing the command when you are finished? I use Microsoft Data Access Application Blocks to handle this, and most of the closing etc. is taken care of in that code.|||thanks for the quick response.

Here is the connection string that i have in my web.config file:

<appSettings>
<add key="DB" value="server='P4'; user id='sa'; password=''; database='myDB'" /
I'm not closing the command but i'm closing the connections:

MyCommand.Connection.Close()

what do you think?|||Hi,

I added the following to my connection string "pooling=false" and it seems to have solved the problem. Performance Monitor shows that connections to database are freed when a new request is recieved by the server.

But I have read that "pooling=false" is not recommended by microsoft!!! Can someone please shed some light on this.

Thanks|||I know I've set pooling to false for one application, and it has not been a problem. This is an intranet application and I had to do this because the application was failing occaisionally. Turning pooling off turned out to be the simplest way to fix it.

I think scalability is the reason that microsoft does not recommend this. Since our application is admin app that's only going to be used by maximum 10 people, that's not an issue. HTH|||Thanks for the information. Can you give me some link to any resource related to the use of connection pooling since my application is suppose to be used by users all over the world.