I reinstalled sql server 2000 on Windoes server 2003 three times due to diff
errors - 1st time replication recovery did not work; 2nd time typo in the
file name ; 3rd time typo in the server name. Then when I installed it the
4th time , the installation failed with system error [TCP/IP sockets] sq
l
server does not exist or access denied. Is this possible that the problem
is related to the port conflict in the machine?
Please advise !!!
Thanks.
Wen ChangRestart ur server delete all the installation files.
HTH
from
Doller
Wen Chang wrote:
> I reinstalled sql server 2000 on Windoes server 2003 three times due to di
ff
> errors - 1st time replication recovery did not work; 2nd time typo in the
> file name ; 3rd time typo in the server name. Then when I installed it th
e
> 4th time , the installation failed with system error [TCP/IP sockets]
sql
> server does not exist or access denied. Is this possible that the proble
m
> is related to the port conflict in the machine?
> Please advise !!!
> Thanks.
> Wen Chang
Showing posts with label denied. Show all posts
Showing posts with label denied. Show all posts
Tuesday, March 20, 2012
Friday, February 24, 2012
[Help] EXECUTE permission denied on object
Microsoft OLE DB Provider for SQL Server error '80040e09'
EXECUTE permission denied on object 'wwfSpTimeAndDateSettings', database 'iobmi6_ETSasp', owner 'dbo'.
/forum/functions/functions_date_time_format.asp, line 82
What does the EXECUTE permission denied on object... line mean?It means that the object owner decided NOT to run the following statement:
grant execute on dbo.wwfSpTimeAndDateSettings to <you>|||Ok i spent time trying to figure out how to fix it bymyself... but i have no idea. I'm trying to install Iportal... so i remade sure i installed all the files completly. Looked up my database info to see that correct. Is it somthing with my database not having dbo autority? (cause then i'll need to ask my hosting for it)|||What is the User ID specified in the connection string? Issue the statement from the previous post and replace <you> with that value.|||Dude! did you read rdjabarob post? if yes, read it again .. if you still don't get it, then I suggest you do some BOL reading about "permissions-SQL Server: Managing permissions"
EXECUTE permission denied on object 'wwfSpTimeAndDateSettings', database 'iobmi6_ETSasp', owner 'dbo'.
/forum/functions/functions_date_time_format.asp, line 82
What does the EXECUTE permission denied on object... line mean?It means that the object owner decided NOT to run the following statement:
grant execute on dbo.wwfSpTimeAndDateSettings to <you>|||Ok i spent time trying to figure out how to fix it bymyself... but i have no idea. I'm trying to install Iportal... so i remade sure i installed all the files completly. Looked up my database info to see that correct. Is it somthing with my database not having dbo autority? (cause then i'll need to ask my hosting for it)|||What is the User ID specified in the connection string? Issue the statement from the previous post and replace <you> with that value.|||Dude! did you read rdjabarob post? if yes, read it again .. if you still don't get it, then I suggest you do some BOL reading about "permissions-SQL Server: Managing permissions"
Sunday, February 19, 2012
[DBNETLIB][ConnectionOpen(Connect()).]SQL Server does not exist or access denied
Hi Folks,
Lets get this out of the way first - I KNOW NOTHING ABOUT SQL SERVER, MSDE or MDAC
Sorry I don't mean to shout but I really don't know anything at all so please make your answers as simple as possible.
I have an application (Webmarshall) that has a SQL database from which certain reports are run. Whenever I try to run the reports it asks me for database details.
According to the application it is using LANCELOT\WEBMARSHALL\Webmarshall as the database
As this is all happening on one server, I presume it is local and not remote.
When I am presented with the dialogue box for the reporting module it asks for a server and a database, I have tried the following :
Server: local Auth: Windows
Server: local Auth: SQL
Server lancelot (both authorisation methods)
Server: lancelot\webmarshall (both authorisation methods)
Server: \\lancelot\webmarshall (both authorisation methods)
Each time, I get the message
[DBNETLIB][ConnectionOpen(Connect()).]SQL Server does not exist or access denied
and I can't select a database.
Can someone help me please...its a long time since I went fishing in the dark (with no net) but thats how I feel right now!!!!
Thanks
In the SQL Server menu options on your Start menu, do you have Enterprise Manager? (you may not depending on which version of SQL Server you have and which installation options were selected, but if you do things will be simpler)
When you try to connect with SQL Auth, are you using a user name and password that are known to be correct? Windows Auth may not work simply because your Windows user may not have permission to connect.
|||Hi Guys,
Thanks for the response, in the end I was so confused by it all that I got a (SQL experienced and very trusted) colleague to remote onto my server.
It turns out that it was MSDE, and that for some reason the connection details had all been lost during the upgrade process. We eventually found the user buried deep in the properties of the application, changed the password and now it all works OK
Perhaps I need to start learning more about SQL, and stop playing with exchange all day!!!!!!
Thanks again
[DBNETLIB][ConnectionOpen(Connect()).] SQL Server does not exist or access denied
ok im a CS student, installed visual studio .net, and im trying to connect to a ms sql database (Northwind), but I keep getting a error that "[DBNETLIB][ConnectionOpen(Connect()).] SQLServer does not exist or access denied" in visual studio whenever I try creating a new database connection. How do I know if SQL server is installed on my system? cuz in my systray I see SQL server service manager, is that the same thing as SQL server? or do I need to download the full version or something? also could it be that a certain port on my system is not open that SQL server requires to be open?
Thanks
Ron
The tray icon doesn't mean SQL is running, so use the tray icon to start SQL if it isn't. I do not know if SQL Express uses a tray icon, so i would assume you are using MSDE 2000. You might need to grant the user ASPNET access to the database.
SQL uses Port 1433. DTE services use ports 5000-5020, however I don't think you are using DTE.
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.
We have a classic ASP application which runs fine on NT Server, W2K Server a
nd with SQL7.0 and SQL 2000.
However, we are having problems with IIS6.0 and Windows 2003 Server when con
necting to a second Windows 2003 Server running SQL 2000 Server. IIS6.0 and
SQL on the same server works fine.
We see intermittent connection problems resulting in:
Microsoft OLE DB Provider for SQL Server error '80004005'
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or
access denied.
We have tried everything we have found trawling the web and still have no id
ea what is causing it.
One ASP script in particular that simply updates a table, fails most of the
time but does VERY rarely run successfully. The same script NEVER failed un
der NT/SQL7.0 or W2K/SQL2000.
We have increased timeout settings in IIS and the ASP scripts themselves. W
e have changed the OLEDB connection to reference the SQL Server IP address i
nstead of its name but nothing tried has made any difference.
Any suggestions would be gratefully received!
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine sup
ports Post Alerts, Ratings, and Searching.That error message is too generic to give specific information as to why it
is failing.
Have you checked for locking /blocking on the server?
You state that the ASP page is performing an update.
Otherwise, have you made network traces from the IIS box to the SQL Server?
What protocols are you using?
Can you reproduce the problem /error using SQL Query Analyser or only from
within IIS?
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||I have this EXACT same problem. My ASP app works fine on Win2000, SQL
Server 7 or 2000.
I get the same intermittent connection problem only when SQL Server
2000 is on a Win2k3 box. It doesn't seem to be restricted to ASP/IIS6
connections. I have problems with Access 2000 and Enterprise Mgr. as
well.
The ASP problem went away when I put SQL Server on the same box as
IIS6, but this can only be a temporary solution.
I've scoured the forums as well and I've seen this problem described
many times, but no solutions yet.
dcase
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message747245.html|||same here... I optimised the scripts to reduce the number of queries and
I've managed to reduce the number of errors, but I haven't been able to
eliminate them.
Windows 2000 used to work fine, but Windows 2003 on upgraded hardware
and with a tenth of the number of queries (or less) gives problems.
Sometimes the problem occurs when I'm trying to get a recordset, and
sometimes it occurs when I'm connecting to the SQL Server 2000 DB.
MUTU
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message747245.html|||We're having the same problems, except with WScript since moving a
server over to Windows 2003 Server. We are connecting to SQL Server 7
on a local network, specifying TCP/IP in the connection string.
The connection failure is intermittent, but is most easily reproduced
by performing a loop where connections are opened and closed. That
will pretty much guarantee that the error will occur at some random
spot in the loop. Sometimes it fails on the first try, sometimes on
the 415th try. It seems to be completely random.
We have eliminated network issues as a possibility by isolating the
servers onto their own switch and have been able to mitigate the
problem by re-using database connections rather than opening new ones.
Probably we will open a ticket with MS soon.
If anybody has info on a fix, it would help us out tremendously to
hear about it.
Pseudo code to reproduce issue...
begin loop
open database connection
execute a sql statement
close database connection
destroy connection
end loop
MUTU <MUTU.18f155@.mail.mcse.ms> wrote in message news:<MUTU.18f155@.mail.mcse.ms>...agreen">
> same here... I optimised the scripts to reduce the number of queries and
> I've managed to reduce the number of errors, but I haven't been able to
> eliminate them.
> Windows 2000 used to work fine, but Windows 2003 on upgraded hardware
> and with a tenth of the number of queries (or less) gives problems.
> Sometimes the problem occurs when I'm trying to get a recordset, and
> sometimes it occurs when I'm connecting to the SQL Server 2000 DB.|||SqlJunkies User wrote:
> *We have a classic ASP application which runs fine on NT Server, W2K
> Server and with SQL7.0 and SQL 2000.
> However, we are having problems with IIS6.0 and Windows 2003 Server
> when connecting to a second Windows 2003 Server running SQL 2000
> Server. IIS6.0 and SQL on the same server works fine.
> We see intermittent connection problems resulting in:
> Microsoft OLE DB Provider for SQL Server error '80004005'
> [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist o
r
> access denied.
> We have tried everything we have found trawling the web and still
> have no idea what is causing it.
> One ASP script in particular that simply updates a table, fails most
> of the time but does VERY rarely run successfully. The same script
> NEVER failed under NT/SQL7.0 or W2K/SQL2000.
> We have increased timeout settings in IIS and the ASP scripts
> themselves. We have changed the OLEDB connection to reference the
> SQL Server IP address instead of its name but nothing tried has made
> any difference.
> Any suggestions would be gratefully received!
> --
> Posted using Wimdows.net NntpNews Component -
> Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup
> engine supports Post Alerts, Ratings, and Searching. *
jmrosseau
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message747245.html|||In case you haven't been told this already....
The intermittant failures smack strongly of TCP/IP ports being
blocked.
A named instance of a server will begin hunting for a TCP/IP Port
between 1025 to 5000. Many of these ports are typical Trojan ports.
You may have read the following:
http://support.microsoft.com/?id=287932
http://support.microsoft.com/default.aspx?kbid=814130
Lou Arnold
Ottawa Canada
On 28 Jun 2004 07:54:29 -0700, jjimenez1984@.yahoo.com (Joel) wrote:
[vbcol=seagreen]
>We're having the same problems, except with WScript since moving a
>server over to Windows 2003 Server. We are connecting to SQL Server 7
>on a local network, specifying TCP/IP in the connection string.
>The connection failure is intermittent, but is most easily reproduced
>by performing a loop where connections are opened and closed. That
>will pretty much guarantee that the error will occur at some random
>spot in the loop. Sometimes it fails on the first try, sometimes on
>the 415th try. It seems to be completely random.
>We have eliminated network issues as a possibility by isolating the
>servers onto their own switch and have been able to mitigate the
>problem by re-using database connections rather than opening new ones.
>Probably we will open a ticket with MS soon.
>If anybody has info on a fix, it would help us out tremendously to
>hear about it.
>Pseudo code to reproduce issue...
>--
>begin loop
>open database connection
>execute a sql statement
>close database connection
>destroy connection
>end loop
>--
>
>
>MUTU <MUTU.18f155@.mail.mcse.ms> wrote in message news:<MUTU.18f155@.mail.mcs
e.ms>...|||Here are our findings on this issue whereby we were attempting to update a t
able within a loop.
When we run the script, around 2 minutes into the execution, we would receiv
e the error.
Our original code where we saw this problem was as follows:
Dataconnection.open "Provider=SQLOLEDB; Data Source=sourcename; Initial Cata
log=catalogname; User Id=userid; Password=password"
SQLrep = "Select * from rep where deletedflag = 0 order by id"
Set objRSrep = Dataconnection.Execute(SQLrep)
We changed the connection and the opening of our recordsets to:
Set Dataconnection = Server.Createobject ("ADODB.Connection")
Dataconnection.ConnectionTimeout = 300
Dataconnection.open "DRIVER={SQL Server};SERVER=sourcename;DATABASE=dat
abasename;UID=userid;PWD=password"
Dataconnection.CommandTimeout = 300
Set objRSrep = Server.CreateObject("ADODB.Recordset")
objRSrep.Open SQLrep, Dataconnection, , AdLockOptimistic
We have found that this solution works but it takes about 4 times longer to
execute.
We have also found that by simply using:
Dataconnection.ConnectionTimeout = 300
Dataconnection.CommandTimeout = 300
with our original code also does the trick. At the point around 2 minutes w
here it previously failed, there is a stutter in execution of upto 19 second
s but it does manage to continue now. Well 6 successes out of 6 isn't bad w
hen previously it would hav
e been 1 success out of 20!
Hope this helps someone.
Neil H
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine sup
ports Post Alerts, Ratings, and Searching.|||Hi,
I encountered this problem recently out of sudden. The app used to work
fine and sound. However, this happens after a simple function was
deployed. Even we reverted to the previous state the app still
encounters the same problem.
All existing report generation functions which access database thru udl
are not working accordingly. However, other types of report generation
functions which access db thru crystal report are not affected. In
addition, the newly deployed function which access the db thru udl also
working fine.It's very weird.
If the database server is not accessible, why are the rest of functions
which also access db like search functions can work well.
Can somebody enlighten me?
Thanks a lots.
Rgds,
DBfaq
*** Sent via Devdex http://www.devdex.com ***
Don't just participate in USENET...get rewarded for it!|||Did anyone ever find a solution for this?
I have the exact same problem, access denied on a sql connect. Worked fine i
n iis 5.
Thank you...
nd with SQL7.0 and SQL 2000.
However, we are having problems with IIS6.0 and Windows 2003 Server when con
necting to a second Windows 2003 Server running SQL 2000 Server. IIS6.0 and
SQL on the same server works fine.
We see intermittent connection problems resulting in:
Microsoft OLE DB Provider for SQL Server error '80004005'
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or
access denied.
We have tried everything we have found trawling the web and still have no id
ea what is causing it.
One ASP script in particular that simply updates a table, fails most of the
time but does VERY rarely run successfully. The same script NEVER failed un
der NT/SQL7.0 or W2K/SQL2000.
We have increased timeout settings in IIS and the ASP scripts themselves. W
e have changed the OLEDB connection to reference the SQL Server IP address i
nstead of its name but nothing tried has made any difference.
Any suggestions would be gratefully received!
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine sup
ports Post Alerts, Ratings, and Searching.That error message is too generic to give specific information as to why it
is failing.
Have you checked for locking /blocking on the server?
You state that the ASP page is performing an update.
Otherwise, have you made network traces from the IIS box to the SQL Server?
What protocols are you using?
Can you reproduce the problem /error using SQL Query Analyser or only from
within IIS?
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||I have this EXACT same problem. My ASP app works fine on Win2000, SQL
Server 7 or 2000.
I get the same intermittent connection problem only when SQL Server
2000 is on a Win2k3 box. It doesn't seem to be restricted to ASP/IIS6
connections. I have problems with Access 2000 and Enterprise Mgr. as
well.
The ASP problem went away when I put SQL Server on the same box as
IIS6, but this can only be a temporary solution.
I've scoured the forums as well and I've seen this problem described
many times, but no solutions yet.
dcase
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message747245.html|||same here... I optimised the scripts to reduce the number of queries and
I've managed to reduce the number of errors, but I haven't been able to
eliminate them.
Windows 2000 used to work fine, but Windows 2003 on upgraded hardware
and with a tenth of the number of queries (or less) gives problems.
Sometimes the problem occurs when I'm trying to get a recordset, and
sometimes it occurs when I'm connecting to the SQL Server 2000 DB.
MUTU
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message747245.html|||We're having the same problems, except with WScript since moving a
server over to Windows 2003 Server. We are connecting to SQL Server 7
on a local network, specifying TCP/IP in the connection string.
The connection failure is intermittent, but is most easily reproduced
by performing a loop where connections are opened and closed. That
will pretty much guarantee that the error will occur at some random
spot in the loop. Sometimes it fails on the first try, sometimes on
the 415th try. It seems to be completely random.
We have eliminated network issues as a possibility by isolating the
servers onto their own switch and have been able to mitigate the
problem by re-using database connections rather than opening new ones.
Probably we will open a ticket with MS soon.
If anybody has info on a fix, it would help us out tremendously to
hear about it.
Pseudo code to reproduce issue...
begin loop
open database connection
execute a sql statement
close database connection
destroy connection
end loop
MUTU <MUTU.18f155@.mail.mcse.ms> wrote in message news:<MUTU.18f155@.mail.mcse.ms>...agreen">
> same here... I optimised the scripts to reduce the number of queries and
> I've managed to reduce the number of errors, but I haven't been able to
> eliminate them.
> Windows 2000 used to work fine, but Windows 2003 on upgraded hardware
> and with a tenth of the number of queries (or less) gives problems.
> Sometimes the problem occurs when I'm trying to get a recordset, and
> sometimes it occurs when I'm connecting to the SQL Server 2000 DB.|||SqlJunkies User wrote:
> *We have a classic ASP application which runs fine on NT Server, W2K
> Server and with SQL7.0 and SQL 2000.
> However, we are having problems with IIS6.0 and Windows 2003 Server
> when connecting to a second Windows 2003 Server running SQL 2000
> Server. IIS6.0 and SQL on the same server works fine.
> We see intermittent connection problems resulting in:
> Microsoft OLE DB Provider for SQL Server error '80004005'
> [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist o
r
> access denied.
> We have tried everything we have found trawling the web and still
> have no idea what is causing it.
> One ASP script in particular that simply updates a table, fails most
> of the time but does VERY rarely run successfully. The same script
> NEVER failed under NT/SQL7.0 or W2K/SQL2000.
> We have increased timeout settings in IIS and the ASP scripts
> themselves. We have changed the OLEDB connection to reference the
> SQL Server IP address instead of its name but nothing tried has made
> any difference.
> Any suggestions would be gratefully received!
> --
> Posted using Wimdows.net NntpNews Component -
> Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup
> engine supports Post Alerts, Ratings, and Searching. *
jmrosseau
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message747245.html|||In case you haven't been told this already....
The intermittant failures smack strongly of TCP/IP ports being
blocked.
A named instance of a server will begin hunting for a TCP/IP Port
between 1025 to 5000. Many of these ports are typical Trojan ports.
You may have read the following:
http://support.microsoft.com/?id=287932
http://support.microsoft.com/default.aspx?kbid=814130
Lou Arnold
Ottawa Canada
On 28 Jun 2004 07:54:29 -0700, jjimenez1984@.yahoo.com (Joel) wrote:
[vbcol=seagreen]
>We're having the same problems, except with WScript since moving a
>server over to Windows 2003 Server. We are connecting to SQL Server 7
>on a local network, specifying TCP/IP in the connection string.
>The connection failure is intermittent, but is most easily reproduced
>by performing a loop where connections are opened and closed. That
>will pretty much guarantee that the error will occur at some random
>spot in the loop. Sometimes it fails on the first try, sometimes on
>the 415th try. It seems to be completely random.
>We have eliminated network issues as a possibility by isolating the
>servers onto their own switch and have been able to mitigate the
>problem by re-using database connections rather than opening new ones.
>Probably we will open a ticket with MS soon.
>If anybody has info on a fix, it would help us out tremendously to
>hear about it.
>Pseudo code to reproduce issue...
>--
>begin loop
>open database connection
>execute a sql statement
>close database connection
>destroy connection
>end loop
>--
>
>
>MUTU <MUTU.18f155@.mail.mcse.ms> wrote in message news:<MUTU.18f155@.mail.mcs
e.ms>...|||Here are our findings on this issue whereby we were attempting to update a t
able within a loop.
When we run the script, around 2 minutes into the execution, we would receiv
e the error.
Our original code where we saw this problem was as follows:
Dataconnection.open "Provider=SQLOLEDB; Data Source=sourcename; Initial Cata
log=catalogname; User Id=userid; Password=password"
SQLrep = "Select * from rep where deletedflag = 0 order by id"
Set objRSrep = Dataconnection.Execute(SQLrep)
We changed the connection and the opening of our recordsets to:
Set Dataconnection = Server.Createobject ("ADODB.Connection")
Dataconnection.ConnectionTimeout = 300
Dataconnection.open "DRIVER={SQL Server};SERVER=sourcename;DATABASE=dat
abasename;UID=userid;PWD=password"
Dataconnection.CommandTimeout = 300
Set objRSrep = Server.CreateObject("ADODB.Recordset")
objRSrep.Open SQLrep, Dataconnection, , AdLockOptimistic
We have found that this solution works but it takes about 4 times longer to
execute.
We have also found that by simply using:
Dataconnection.ConnectionTimeout = 300
Dataconnection.CommandTimeout = 300
with our original code also does the trick. At the point around 2 minutes w
here it previously failed, there is a stutter in execution of upto 19 second
s but it does manage to continue now. Well 6 successes out of 6 isn't bad w
hen previously it would hav
e been 1 success out of 20!
Hope this helps someone.
Neil H
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine sup
ports Post Alerts, Ratings, and Searching.|||Hi,
I encountered this problem recently out of sudden. The app used to work
fine and sound. However, this happens after a simple function was
deployed. Even we reverted to the previous state the app still
encounters the same problem.
All existing report generation functions which access database thru udl
are not working accordingly. However, other types of report generation
functions which access db thru crystal report are not affected. In
addition, the newly deployed function which access the db thru udl also
working fine.It's very weird.
If the database server is not accessible, why are the rest of functions
which also access db like search functions can work well.
Can somebody enlighten me?
Thanks a lots.
Rgds,
DBfaq
*** Sent via Devdex http://www.devdex.com ***
Don't just participate in USENET...get rewarded for it!|||Did anyone ever find a solution for this?
I have the exact same problem, access denied on a sql connect. Worked fine i
n iis 5.
Thank you...
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.
I installed the SQL SERVER , Oracleclient on my computer, and I can connect to remote SQL server,oracle databases using wizards , however when I try to run application iam getting this error.Server Error in '/shiva/datagrd' Application.
Source File:e:\shiva\datagrd\webform1.aspx.cs Line:42
Version Information: Microsoft .NET Framework Version:1.1.4322.573; ASP.NET Version:1.1.4322.573
Server Error in '/shiva/datagrd' Application.
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.
Description:An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.Exception Details:System.Data.OleDb.OleDbException: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.
Source Error:
Line 40: //SqlDataAdapter da=new SqlDataAdapter("select * from sms",con);
Line 41: DataSet ds=new DataSet();
Line 42: da.Fill(ds,"tab");
Line 43: DataGrid1.DataSource=ds.Tables[0].DefaultView;
Line 44: DataGrid1.DataBind();Source File:e:\shiva\datagrd\webform1.aspx.cs Line:42
Stack Trace:
[OleDbException (0x80004005): [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.]
System.Data.OleDb.OleDbConnection.ProcessResults(Int32 hr)
System.Data.OleDb.OleDbConnection.InitializeProvider()
System.Data.OleDb.OleDbConnection.Open()
System.Data.Common.DbDataAdapter.QuietOpen(IDbConnection connection, ConnectionState& originalState)
System.Data.Common.DbDataAdapter.FillFromCommand(Object data, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, String srcTable)
datagrd.WebForm1.Page_Load(Object sender, EventArgs e) in e:\shiva\datagrd\webform1.aspx.cs:42
System.Web.UI.Control.OnLoad(EventArgs e)
System.Web.UI.Control.LoadRecursive()
System.Web.UI.Page.ProcessRequestMain()
Version Information: Microsoft .NET Framework Version:1.1.4322.573; ASP.NET Version:1.1.4322.573
please provide the solution.
What is your sql connection string in your web application?
|||string strCon="Provider=SQLOLEDB.1;User ID=sa;Initial Catalog=Anjali;Data Source=MIPL0121;Persist Security Info=False"; //my connection string
and it is existing i am able to see the data through microsoft sql server --> enterprise manager
and i am able to get the data for my windows applications but not for web application why?
|||You would have to use:
String strCon = "Server=MIPL0121;Database=Anjali;User ID=myuser;password=mypassword;"
|||still problem is like that only
i think problem with some other one not with connection string
https://secure.experts-exchange.com/register.jsp?srid=m6c%2BKpauvxfudZgRmo%2Fm6A%3D%3D&rsid=20&viewQuestionRedirectURL=%2FDatabase%2FOracle%2FQ_20402341.html%3Fqid%3D20402341%26qid%3D20402341&submit=
my problem is exact as this
Hi,
This is definately a security issue. In you connection string, you're using the Windows integrated authentication to connection to the server.
You can do this in the VS.NET because it is using your windows identity(Running under your account). However, the ASP.NET app is running under the ASPNET account, which doesn't have that previlege.
To resolve this, you can either give the ASPNET account proper permission to access the database, or use other accounts for accessing the database.
|||but i am able to get the data from remote server using same connection string in vs2005 but not in 2003 why?|||at the same time i am not able to get the data from ORACLE also and the connection string and code is perfectly executing on my neighbor system.|||at the same time i am not able to get the data from ORACLE also andthe connection string and code is perfectly executing on my neighborsystem with the same setting|||Hi,
I'd like to know if you're connecting from VS.NET IDE using this connection string. Or you're using this connection string in your ASP.NET application.
Because in different scenarios, it holds different user credentials. Also, please check if you have used the correct OleDb driver to do the connection to SQL Server.
|||ya i am using this connection string in asp.net application
but i tryied by using vs.net IDE(using Wizards) also its givng the same error when i am connecting throw wizards it is connecting and showing the database contents(mean if a select a tabe it
showing the discription of that table ) but when i am running the application it giving the above error
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.
We have a classic ASP application which runs fine on NT Server, W2K Server and with SQL7.0 and SQL 2000.
However, we are having problems with IIS6.0 and Windows 2003 Server when connecting to a second Windows 2003 Server running SQL 2000 Server. IIS6.0 and SQL on the same server works fine.
We see intermittent connection problems resulting in:
Microsoft OLE DB Provider for SQL Server error '80004005'
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.
We have tried everything we have found trawling the web and still have no idea what is causing it.
One ASP script in particular that simply updates a table, fails most of the time but does VERY rarely run successfully. The same script NEVER failed under NT/SQL7.0 or W2K/SQL2000.
We have increased timeout settings in IIS and the ASP scripts themselves. We have changed the OLEDB connection to reference the SQL Server IP address instead of its name but nothing tried has made any difference.
Any suggestions would be gratefully received!
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.
That error message is too generic to give specific information as to why it
is failing.
Have you checked for locking /blocking on the server?
You state that the ASP page is performing an update.
Otherwise, have you made network traces from the IIS box to the SQL Server?
What protocols are you using?
Can you reproduce the problem /error using SQL Query Analyser or only from
within IIS?
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
|||I have this EXACT same problem. My ASP app works fine on Win2000, SQL Server 7 or 2000.
I get the same intermittent connection problem only when SQL Server 2000 is on a Win2k3 box. It doesn't seem to be restricted to ASP/IIS6 connections. I have problems with Access 2000 and Enterprise Mgr. as well.
The ASP problem went away when I put SQL Server on the same box as IIS6, but this can only be a temporary solution.
I've scoured the forums as well and I've seen this problem described many times, but no solutions yet.|||same here... I optimised the scripts to reduce the number of queries and I've managed to reduce the number of errors, but I haven't been able to eliminate them.
Windows 2000 used to work fine, but Windows 2003 on upgraded hardware and with a tenth of the number of queries (or less) gives problems.
Sometimes the problem occurs when I'm trying to get a recordset, and sometimes it occurs when I'm connecting to the SQL Server 2000 DB.|||We're having the same problems, except with WScript since moving a
server over to Windows 2003 Server. We are connecting to SQL Server 7
on a local network, specifying TCP/IP in the connection string.
The connection failure is intermittent, but is most easily reproduced
by performing a loop where connections are opened and closed. That
will pretty much guarantee that the error will occur at some random
spot in the loop. Sometimes it fails on the first try, sometimes on
the 415th try. It seems to be completely random.
We have eliminated network issues as a possibility by isolating the
servers onto their own switch and have been able to mitigate the
problem by re-using database connections rather than opening new ones.
Probably we will open a ticket with MS soon.
If anybody has info on a fix, it would help us out tremendously to
hear about it.
Pseudo code to reproduce issue...
begin loop
open database connection
execute a sql statement
close database connection
destroy connection
end loop
MUTU <MUTU.18f155@.mail.mcse.ms> wrote in message news:<MUTU.18f155@.mail.mcse.ms>...
> same here... I optimised the scripts to reduce the number of queries and
> I've managed to reduce the number of errors, but I haven't been able to
> eliminate them.
> Windows 2000 used to work fine, but Windows 2003 on upgraded hardware
> and with a tenth of the number of queries (or less) gives problems.
> Sometimes the problem occurs when I'm trying to get a recordset, and
> sometimes it occurs when I'm connecting to the SQL Server 2000 DB.
|||We're having the same problems, except with WScript since moving a
server over to Windows 2003 Server. We are connecting to SQL Server 7
on a local network, specifying TCP/IP in the connection string.
The connection failure is intermittent, but is most easily reproduced
by performing a loop where connections are opened and closed. That
will pretty much guarantee that the error will occur at some random
spot in the loop. Sometimes it fails on the first try, sometimes on
the 415th try. It seems to be completely random.
We have eliminated network issues as a possibility by isolating the
servers onto their own switch and have been able to mitigate the
problem by re-using database connections rather than opening new ones.
Probably we will open a ticket with MS soon.
If anybody has info on a fix, it would help us out tremendously to
hear about it.
Pseudo code to reproduce issue...
begin loop
open database connection
execute a sql statement
close database connection
destroy connection
end loop
MUTU <MUTU.18f155@.mail.mcse.ms> wrote in message news:<MUTU.18f155@.mail.mcse.ms>...
> same here... I optimised the scripts to reduce the number of queries and
> I've managed to reduce the number of errors, but I haven't been able to
> eliminate them.
> Windows 2000 used to work fine, but Windows 2003 on upgraded hardware
> and with a tenth of the number of queries (or less) gives problems.
> Sometimes the problem occurs when I'm trying to get a recordset, and
> sometimes it occurs when I'm connecting to the SQL Server 2000 DB.
|||Originally posted by SqlJunkies User
We have a classic ASP application which runs fine on NT Server, W2K Server and with SQL7.0 and SQL 2000.
However, we are having problems with IIS6.0 and Windows 2003 Server when connecting to a second Windows 2003 Server running SQL 2000 Server. IIS6.0 and SQL on the same server works fine.
We see intermittent connection problems resulting in:
Microsoft OLE DB Provider for SQL Server error '80004005'
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.
We have tried everything we have found trawling the web and still have no idea what is causing it.
One ASP script in particular that simply updates a table, fails most of the time but does VERY rarely run successfully. The same script NEVER failed under NT/SQL7.0 or W2K/SQL2000.
We have increased timeout settings in IIS and the ASP scripts themselves. We have changed the OLEDB connection to reference the SQL Server IP address instead of its name but nothing tried has made any difference.
Any suggestions would be gratefully received!
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching. Originally posted by jmrosseau
I got my information through the microsoft website: http://support.microsoft.com/default...b;EN-US;328383
Here is what helped me:
Specify the protocol in your connection string. For example: "DSN=DSNName;SERVER=servername;DATABASE=YourDataBa seName;Network=DBMSSOCN;Address=IP_Address,1433;UI D=YourUID;PWD=YourPassword;"
In this example, you specify the network protocol as "DBMSSOCN", which means that you want to use the TCP/IP protocol. If you specify the protocol inside your connection string, Dbnetlib only uses the specified protocol and does not try any other protocol. Similarly, to enable Named Pipe protocol only, use a connection string similar to this: "DSN=DSNName;SERVER=servername;DATABASE=YourDataBa seName;Network=DBNMPNTW;Address=\\.\pipe\sql\query ;UID=YourUID;PWD=YourPassword;"|||In case you haven't been told this already....
The intermittant failures smack strongly of TCP/IP ports being
blocked.
A named instance of a server will begin hunting for a TCP/IP Port
between 1025 to 5000. Many of these ports are typical Trojan ports.
You may have read the following:
http://support.microsoft.com/?id=287932
http://support.microsoft.com/default.aspx?kbid=814130
Lou Arnold
Ottawa Canada
On 28 Jun 2004 07:54:29 -0700, jjimenez1984@.yahoo.com (Joel) wrote:
[vbcol=seagreen]
>We're having the same problems, except with WScript since moving a
>server over to Windows 2003 Server. We are connecting to SQL Server 7
>on a local network, specifying TCP/IP in the connection string.
>The connection failure is intermittent, but is most easily reproduced
>by performing a loop where connections are opened and closed. That
>will pretty much guarantee that the error will occur at some random
>spot in the loop. Sometimes it fails on the first try, sometimes on
>the 415th try. It seems to be completely random.
>We have eliminated network issues as a possibility by isolating the
>servers onto their own switch and have been able to mitigate the
>problem by re-using database connections rather than opening new ones.
>Probably we will open a ticket with MS soon.
>If anybody has info on a fix, it would help us out tremendously to
>hear about it.
>Pseudo code to reproduce issue...
>--
>begin loop
>open database connection
>execute a sql statement
>close database connection
>destroy connection
>end loop
>--
>
>
>MUTU <MUTU.18f155@.mail.mcse.ms> wrote in message news:<MUTU.18f155@.mail.mcse.ms>...
|||In case you haven't been told this already....
The intermittant failures smack strongly of TCP/IP ports being
blocked.
A named instance of a server will begin hunting for a TCP/IP Port
between 1025 to 5000. Many of these ports are typical Trojan ports.
You may have read the following:
http://support.microsoft.com/?id=287932
http://support.microsoft.com/default.aspx?kbid=814130
Lou Arnold
Ottawa Canada
On 28 Jun 2004 07:54:29 -0700, jjimenez1984@.yahoo.com (Joel) wrote:
[vbcol=seagreen]
>We're having the same problems, except with WScript since moving a
>server over to Windows 2003 Server. We are connecting to SQL Server 7
>on a local network, specifying TCP/IP in the connection string.
>The connection failure is intermittent, but is most easily reproduced
>by performing a loop where connections are opened and closed. That
>will pretty much guarantee that the error will occur at some random
>spot in the loop. Sometimes it fails on the first try, sometimes on
>the 415th try. It seems to be completely random.
>We have eliminated network issues as a possibility by isolating the
>servers onto their own switch and have been able to mitigate the
>problem by re-using database connections rather than opening new ones.
>Probably we will open a ticket with MS soon.
>If anybody has info on a fix, it would help us out tremendously to
>hear about it.
>Pseudo code to reproduce issue...
>--
>begin loop
>open database connection
>execute a sql statement
>close database connection
>destroy connection
>end loop
>--
>
>
>MUTU <MUTU.18f155@.mail.mcse.ms> wrote in message news:<MUTU.18f155@.mail.mcse.ms>...
However, we are having problems with IIS6.0 and Windows 2003 Server when connecting to a second Windows 2003 Server running SQL 2000 Server. IIS6.0 and SQL on the same server works fine.
We see intermittent connection problems resulting in:
Microsoft OLE DB Provider for SQL Server error '80004005'
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.
We have tried everything we have found trawling the web and still have no idea what is causing it.
One ASP script in particular that simply updates a table, fails most of the time but does VERY rarely run successfully. The same script NEVER failed under NT/SQL7.0 or W2K/SQL2000.
We have increased timeout settings in IIS and the ASP scripts themselves. We have changed the OLEDB connection to reference the SQL Server IP address instead of its name but nothing tried has made any difference.
Any suggestions would be gratefully received!
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.
That error message is too generic to give specific information as to why it
is failing.
Have you checked for locking /blocking on the server?
You state that the ASP page is performing an update.
Otherwise, have you made network traces from the IIS box to the SQL Server?
What protocols are you using?
Can you reproduce the problem /error using SQL Query Analyser or only from
within IIS?
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
|||I have this EXACT same problem. My ASP app works fine on Win2000, SQL Server 7 or 2000.
I get the same intermittent connection problem only when SQL Server 2000 is on a Win2k3 box. It doesn't seem to be restricted to ASP/IIS6 connections. I have problems with Access 2000 and Enterprise Mgr. as well.
The ASP problem went away when I put SQL Server on the same box as IIS6, but this can only be a temporary solution.
I've scoured the forums as well and I've seen this problem described many times, but no solutions yet.|||same here... I optimised the scripts to reduce the number of queries and I've managed to reduce the number of errors, but I haven't been able to eliminate them.
Windows 2000 used to work fine, but Windows 2003 on upgraded hardware and with a tenth of the number of queries (or less) gives problems.
Sometimes the problem occurs when I'm trying to get a recordset, and sometimes it occurs when I'm connecting to the SQL Server 2000 DB.|||We're having the same problems, except with WScript since moving a
server over to Windows 2003 Server. We are connecting to SQL Server 7
on a local network, specifying TCP/IP in the connection string.
The connection failure is intermittent, but is most easily reproduced
by performing a loop where connections are opened and closed. That
will pretty much guarantee that the error will occur at some random
spot in the loop. Sometimes it fails on the first try, sometimes on
the 415th try. It seems to be completely random.
We have eliminated network issues as a possibility by isolating the
servers onto their own switch and have been able to mitigate the
problem by re-using database connections rather than opening new ones.
Probably we will open a ticket with MS soon.
If anybody has info on a fix, it would help us out tremendously to
hear about it.
Pseudo code to reproduce issue...
begin loop
open database connection
execute a sql statement
close database connection
destroy connection
end loop
MUTU <MUTU.18f155@.mail.mcse.ms> wrote in message news:<MUTU.18f155@.mail.mcse.ms>...
> same here... I optimised the scripts to reduce the number of queries and
> I've managed to reduce the number of errors, but I haven't been able to
> eliminate them.
> Windows 2000 used to work fine, but Windows 2003 on upgraded hardware
> and with a tenth of the number of queries (or less) gives problems.
> Sometimes the problem occurs when I'm trying to get a recordset, and
> sometimes it occurs when I'm connecting to the SQL Server 2000 DB.
|||We're having the same problems, except with WScript since moving a
server over to Windows 2003 Server. We are connecting to SQL Server 7
on a local network, specifying TCP/IP in the connection string.
The connection failure is intermittent, but is most easily reproduced
by performing a loop where connections are opened and closed. That
will pretty much guarantee that the error will occur at some random
spot in the loop. Sometimes it fails on the first try, sometimes on
the 415th try. It seems to be completely random.
We have eliminated network issues as a possibility by isolating the
servers onto their own switch and have been able to mitigate the
problem by re-using database connections rather than opening new ones.
Probably we will open a ticket with MS soon.
If anybody has info on a fix, it would help us out tremendously to
hear about it.
Pseudo code to reproduce issue...
begin loop
open database connection
execute a sql statement
close database connection
destroy connection
end loop
MUTU <MUTU.18f155@.mail.mcse.ms> wrote in message news:<MUTU.18f155@.mail.mcse.ms>...
> same here... I optimised the scripts to reduce the number of queries and
> I've managed to reduce the number of errors, but I haven't been able to
> eliminate them.
> Windows 2000 used to work fine, but Windows 2003 on upgraded hardware
> and with a tenth of the number of queries (or less) gives problems.
> Sometimes the problem occurs when I'm trying to get a recordset, and
> sometimes it occurs when I'm connecting to the SQL Server 2000 DB.
|||
Quote:
We have a classic ASP application which runs fine on NT Server, W2K Server and with SQL7.0 and SQL 2000.
However, we are having problems with IIS6.0 and Windows 2003 Server when connecting to a second Windows 2003 Server running SQL 2000 Server. IIS6.0 and SQL on the same server works fine.
We see intermittent connection problems resulting in:
Microsoft OLE DB Provider for SQL Server error '80004005'
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.
We have tried everything we have found trawling the web and still have no idea what is causing it.
One ASP script in particular that simply updates a table, fails most of the time but does VERY rarely run successfully. The same script NEVER failed under NT/SQL7.0 or W2K/SQL2000.
We have increased timeout settings in IIS and the ASP scripts themselves. We have changed the OLEDB connection to reference the SQL Server IP address instead of its name but nothing tried has made any difference.
Any suggestions would be gratefully received!
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.
Quote:
I got my information through the microsoft website: http://support.microsoft.com/default...b;EN-US;328383
Here is what helped me:
Specify the protocol in your connection string. For example: "DSN=DSNName;SERVER=servername;DATABASE=YourDataBa seName;Network=DBMSSOCN;Address=IP_Address,1433;UI D=YourUID;PWD=YourPassword;"
In this example, you specify the network protocol as "DBMSSOCN", which means that you want to use the TCP/IP protocol. If you specify the protocol inside your connection string, Dbnetlib only uses the specified protocol and does not try any other protocol. Similarly, to enable Named Pipe protocol only, use a connection string similar to this: "DSN=DSNName;SERVER=servername;DATABASE=YourDataBa seName;Network=DBNMPNTW;Address=\\.\pipe\sql\query ;UID=YourUID;PWD=YourPassword;"|||In case you haven't been told this already....
The intermittant failures smack strongly of TCP/IP ports being
blocked.
A named instance of a server will begin hunting for a TCP/IP Port
between 1025 to 5000. Many of these ports are typical Trojan ports.
You may have read the following:
http://support.microsoft.com/?id=287932
http://support.microsoft.com/default.aspx?kbid=814130
Lou Arnold
Ottawa Canada
On 28 Jun 2004 07:54:29 -0700, jjimenez1984@.yahoo.com (Joel) wrote:
[vbcol=seagreen]
>We're having the same problems, except with WScript since moving a
>server over to Windows 2003 Server. We are connecting to SQL Server 7
>on a local network, specifying TCP/IP in the connection string.
>The connection failure is intermittent, but is most easily reproduced
>by performing a loop where connections are opened and closed. That
>will pretty much guarantee that the error will occur at some random
>spot in the loop. Sometimes it fails on the first try, sometimes on
>the 415th try. It seems to be completely random.
>We have eliminated network issues as a possibility by isolating the
>servers onto their own switch and have been able to mitigate the
>problem by re-using database connections rather than opening new ones.
>Probably we will open a ticket with MS soon.
>If anybody has info on a fix, it would help us out tremendously to
>hear about it.
>Pseudo code to reproduce issue...
>--
>begin loop
>open database connection
>execute a sql statement
>close database connection
>destroy connection
>end loop
>--
>
>
>MUTU <MUTU.18f155@.mail.mcse.ms> wrote in message news:<MUTU.18f155@.mail.mcse.ms>...
|||In case you haven't been told this already....
The intermittant failures smack strongly of TCP/IP ports being
blocked.
A named instance of a server will begin hunting for a TCP/IP Port
between 1025 to 5000. Many of these ports are typical Trojan ports.
You may have read the following:
http://support.microsoft.com/?id=287932
http://support.microsoft.com/default.aspx?kbid=814130
Lou Arnold
Ottawa Canada
On 28 Jun 2004 07:54:29 -0700, jjimenez1984@.yahoo.com (Joel) wrote:
[vbcol=seagreen]
>We're having the same problems, except with WScript since moving a
>server over to Windows 2003 Server. We are connecting to SQL Server 7
>on a local network, specifying TCP/IP in the connection string.
>The connection failure is intermittent, but is most easily reproduced
>by performing a loop where connections are opened and closed. That
>will pretty much guarantee that the error will occur at some random
>spot in the loop. Sometimes it fails on the first try, sometimes on
>the 415th try. It seems to be completely random.
>We have eliminated network issues as a possibility by isolating the
>servers onto their own switch and have been able to mitigate the
>problem by re-using database connections rather than opening new ones.
>Probably we will open a ticket with MS soon.
>If anybody has info on a fix, it would help us out tremendously to
>hear about it.
>Pseudo code to reproduce issue...
>--
>begin loop
>open database connection
>execute a sql statement
>close database connection
>destroy connection
>end loop
>--
>
>
>MUTU <MUTU.18f155@.mail.mcse.ms> wrote in message news:<MUTU.18f155@.mail.mcse.ms>...
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied - PLEASE
Hi have created an application in asp.net to connect to a sql database.
The reason why I am sooooo very confused is because the connection to the database works if i keep the project on my local machine and connect to the database on the server, but as soon as I upload the project to the server, I get the following error when I try to connect to the database:
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied
Can anyone tell me why this is happenning? - PLEASE - Any help will be appreciated
Thanks,
Danielle
you might want to check your connection string and make sure its pointing to the rigtht database server.
The reason why I am sooooo very confused is because the connection to the database works if i keep the project on my local machine and connect to the database on the server, but as soon as I upload the project to the server, I get the following error when I try to connect to the database:
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied
Can anyone tell me why this is happenning? - PLEASE - Any help will be appreciated
Thanks,
Danielle
you might want to check your connection string and make sure its pointing to the rigtht database server.
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied
Server : W2K
Workstations : XP, W2K
Web apllication locks up with 8-12 users on this error
We can unlock everything with IISRESET
Server machine has all SQL SP and latest MDAC version
Server : W2K
Workstations : XP, W2K
Web apllication locks up with 8-12 users on this error
We can unlock everything with IISRESET
Server machine has all SQL SP and latest MDAC version
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or
access denied
Server : W2K
Workstations : XP, W2K
Web apllication locks up with 8-12 users on this error
We can unlock everything with IISRESETServer machine has all SQL SP and latest MDAC version
access denied
Server : W2K
Workstations : XP, W2K
Web apllication locks up with 8-12 users on this error
We can unlock everything with IISRESETServer machine has all SQL SP and latest MDAC version
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied
hello,
I hope someone can help me with the problem I am having, I get the following error:
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied
I am trying to connect to my SQLServer 2000 db via asp.net. The aspx file uses a DataGrid, the aspx.vbcode behind file gets the connection string from the web.config file. Itested my connection via ODBC, or SQL Query Analyzer just fine so Iknow the userid/password is correct.
this is the snipplet code from the aspx.vb code-behind file:
Private Sub Page_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) _
Handles MyBase.Load
Dim dbConn As OleDbConnection
Dim dCmd As OleDbCommand
Dim dReader As OleDbDataReader
Dim strConnection As String
Dim strSQL As String
If (Not Page.IsPostBack) Then
Try
'get the connection string from web.config and open a connection
'to the database
strConnection = ConfigurationSettings.AppSettings("dbConnectionString")
dbConn = New OleDb.OleDbConnection(strConnection)
dbConn.Open()
'build the query string and get the data from the database
strSQL = "SELECT Title, ISBN, Publisher " & _
"FROM Book " & _
"ORDER BY Title"
dCmd = New OleDbCommand(strSQL, dbConn)
dReader = dCmd.ExecuteReader()
'set the source of the data for the datagrid control and bind it
dgQuick.DataSource = dReader
dgQuick.DataBind()
Finally
'cleanup
If (Not IsNothing(dReader)) Then
dReader.Close()
End If
If (Not IsNothing(dbConn)) Then
dbConn.Close()
End If
End Try
End If
End Sub 'Page_Load
End Class
this is the connection string inside the web.config file:
<!--add key="dbConnectionString"value="Provider=SQLOLEDB;Data Source=localhost;InitialCatalog=myDBName;UID=myUserID;PWD=myUserPssd" /-->
<!--addkey="sqlConnectionString" value="Data Source=localhost;InitialCatalog=myDBName;UID=myUserID;PWD=myUserPssd;persist securityinfo=False;" /-->
thanks,
arlena
I hope someone can help me with the problem I am having, I get the following error:
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied
I am trying to connect to my SQLServer 2000 db via asp.net. The aspx file uses a DataGrid, the aspx.vbcode behind file gets the connection string from the web.config file. Itested my connection via ODBC, or SQL Query Analyzer just fine so Iknow the userid/password is correct.
this is the snipplet code from the aspx.vb code-behind file:
Private Sub Page_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) _
Handles MyBase.Load
Dim dbConn As OleDbConnection
Dim dCmd As OleDbCommand
Dim dReader As OleDbDataReader
Dim strConnection As String
Dim strSQL As String
If (Not Page.IsPostBack) Then
Try
'get the connection string from web.config and open a connection
'to the database
strConnection = ConfigurationSettings.AppSettings("dbConnectionString")
dbConn = New OleDb.OleDbConnection(strConnection)
dbConn.Open()
'build the query string and get the data from the database
strSQL = "SELECT Title, ISBN, Publisher " & _
"FROM Book " & _
"ORDER BY Title"
dCmd = New OleDbCommand(strSQL, dbConn)
dReader = dCmd.ExecuteReader()
'set the source of the data for the datagrid control and bind it
dgQuick.DataSource = dReader
dgQuick.DataBind()
Finally
'cleanup
If (Not IsNothing(dReader)) Then
dReader.Close()
End If
If (Not IsNothing(dbConn)) Then
dbConn.Close()
End If
End Try
End If
End Sub 'Page_Load
End Class
this is the connection string inside the web.config file:
<!--add key="dbConnectionString"value="Provider=SQLOLEDB;Data Source=localhost;InitialCatalog=myDBName;UID=myUserID;PWD=myUserPssd" /-->
<!--addkey="sqlConnectionString" value="Data Source=localhost;InitialCatalog=myDBName;UID=myUserID;PWD=myUserPssd;persist securityinfo=False;" /-->
thanks,
arlena
Try these urls, it is permissions related see if your database setup meets what is in that site in PUBs. I see you are using OLEDB instead of ADO.NET, OLEDB is for none SQL Server and DTS packages. Hope this helps.
http://duhnetnuke2.net/Default.aspx?tabid=64
http://duhnetnuke.net/DesktopDefault.aspx?tabid=40
Subscribe to:
Posts (Atom)