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 access. Show all posts
Showing posts with label access. Show all posts
Tuesday, March 20, 2012
Monday, March 19, 2012
[SQL2005] Profiler Trace Security Issue
With SQL Server 2005 there is an option to grant a person access to Profiler for tracing SQL. This is done with the "GRANT ALTER TRACE" statement. The statement has to be executed at server level i.e. the master database.
The user in question only has access to certain databases on that server. The security problem that arises is that with the Profiler rights active, he can see the sql commands that are executed on the databases he has no rights for. Those SQL commands are executed by others users.
How do I configure security rules so that the person in question can use Profiler, but can only see the SQL statements that are executed on the databases he has the rights for? TIA!
Unfortunately there is no such level of granularity in SQL Server 2005 permission model, and ALTER TRACE is considered an elevated permission because of the reasons you mentioned.
Hopefully somebody may be able to reply back with a good workaround.
-Raul Garcia
SDE/T
SQL Server Engine[SQL Server 2000] How to Interpret Server Trace / How to Get More Details?
Hello all,
An application that i wrote (that interacts with SQL Server 2000) is causing deadlocks on the server. i have no direct access to the server, but the user have sent me a server trace.
The relevant part of the trace is:
Code Snippet
2007-04-04 11:29:13.01 spid4 End deadlock search 296 ... a deadlock was found.
2007-04-04 11:29:13.01 spid4
2007-04-04 11:29:13.01 spid4 ResType:LockOwner Stype:'OR' Mode: S SPID:116 ECID:0 Ec:(0xC62A54F8) Value:0x80
2007-04-04 11:29:13.01 spid4 Victim Resource Owner:
2007-04-04 11:29:13.01 spid4 ResType:LockOwner Stype:'OR' Mode: IX SPID:122 ECID:0 Ec:(0xC61DF4F8) Value:0xa
2007-04-04 11:29:13.01 spid4 Requested By:
2007-04-04 11:29:13.01 spid4 Input Buf: RPC Event: sp_execute;1
2007-04-04 11:29:13.01 spid4 SPID: 116 ECID: 0 Statement Type: UPDATE Line #: 1
2007-04-04 11:29:13.01 spid4 Owner:0x8849cba0 Mode: X Flg:0x0 Ref:2 Life:02000000 SPID:116 ECID:0
2007-04-04 11:29:13.01 spid4 Grant List 0::
2007-04-04 11:29:13.01 spid4 PAG: 12:1:42176 CleanCnt:2 Mode: X Flags: 0x2
2007-04-04 11:29:13.01 spid4 Node:2
2007-04-04 11:29:13.01 spid4
2007-04-04 11:29:13.01 spid4 ResType:LockOwner Stype:'OR' Mode: S SPID:116 ECID:0 Ec:(0xC62A54F8) Value:0x80
2007-04-04 11:29:13.01 spid4 Requested By:
2007-04-04 11:29:13.01 spid4 Input Buf: RPC Event: sp_execute;1
2007-04-04 11:29:13.01 spid4 SPID: 122 ECID: 0 Statement Type: INSERT Line #: 1
2007-04-04 11:29:13.01 spid4 Owner:0x800936e0 Mode: IX Flg:0x0 Ref:0 Life:02000000 SPID:122 ECID:0
2007-04-04 11:29:13.01 spid4 Grant List 2::
2007-04-04 11:29:13.01 spid4 PAG: 12:1:42157 CleanCnt:2 Mode: IX Flags: 0x0
2007-04-04 11:29:13.01 spid4 Node:1
2007-04-04 11:29:13.01 spid4
2007-04-04 11:29:13.01 spid4 Wait-for graph
2007-04-04 11:29:13.01 spid4
2007-04-04 11:29:13.01 spid4 ...
2007-04-04 11:29:13.01 spid4
2007-04-04 11:29:13.01 spid4 Cycle: ResType:LockOwner Stype:'OR' Mode: S SPID:116 ECID:0 Ec:(0xC62A54F8) Va
2007-04-04 11:29:13.01 spid4 Node:2 ResType:LockOwner Stype:'OR' Mode: IX SPID:122 ECID:0 Ec:(0xC61DF4F8) V
2007-04-04 11:29:13.01 spid4 Node:1 ResType:LockOwner Stype:'OR' Mode: S SPID:116 ECID:0 Ec:(0xC62A54F8) Va
2007-04-04 11:29:13.01 spid4 Deadlock cycle was encountered .... verifying cycle
2007-04-04 11:29:13.01 spid4
2007-04-04 11:29:13.01 spid4
2007-04-04 11:29:13.01 spid4 Cycle: ResType:LockOwner Stype:'OR' Mode: S SPID:116 ECID:0 Ec:(0xC62A54F8) Va
2007-04-04 11:29:13.01 spid4 Node:2 ResType:LockOwner Stype:'OR' Mode: IX SPID:122 ECID:0 Ec:(0xC61DF4F8) V
2007-04-04 11:29:13.01 spid4 Node:1 ResType:LockOwner Stype:'OR' Mode: S SPID:116 ECID:0 Ec:(0xC62A54F8) Va
2007-04-04 11:29:13.01 spid4 ResType:LockOwner Stype:'OR' Mode: S SPID:116 ECID:0 Ec:(0xC62A54F8) Value:0x80
2007-04-04 11:29:13.01 spid4 Target Resource Owner:
2007-04-04 11:29:13.01 spid4 Starting deadlock search 296
Having very little experience with SQL Server 2000, all that i learn from the trace is that, well, there is a deadlock, but i had already known that beforehand.
What other useful details can be interpreted from the trace above?
How can i obtain information like the specific statement(s) which cause the deadlock, etc?
Thanks in Advance,
Edwin
Not sure if you have the complete information in your snippet...having a running Profiler trace that captures the relevant time period can be helpful. That will be the only way to see the specific statements.
SPIDs 116 and 122 deadlocked with each other. 116 was running an UPDATE and 122 was trying to INSERT. 122 was chosen as the victim (SQL will generally choose the SPID with the fewest resources to minimize rollback time). Your app should detect and trap error 1205 and re-submit the deadlocked query.
Minimizing deadlocks from within the database will almost always come down to tweaking your indexes. It is hard to comment further without knowing your schema for the table in question. Your open transactions should be kept as short as possible too.
-MichaelSunday, March 11, 2012
[SBS2003 Premium R2] Reporting services problem
Hi!
When I try configure report data source to connect to database on another
SQL Server 200 i receive message:
The feature: "Remote access to report data sources and/or the report server
database" is not supported in this edition of Reporting Services.
What can I do with thiss message?
Please help me
Best regards
AdamOn Jun 29, 1:57 am, "Adam Kobylinski" <akobylin@.NO_SPAM.op.pl> wrote:
> Hi!
> When I try configure report data source to connect to database on another
> SQL Server 200 i receive message:
> The feature: "Remote access to report data sources and/or the report server
> database" is not supported in this edition of Reporting Services.
> What can I do with thiss message?
> Please help me
> Best regards
> Adam
If you are running SQL Server 2005 Express Edition (w/Advanced
Services), this is one of the limitations. Otherwise, you will want to
open the local SQL Server Surface Area Configuration tool and select
Surface Area Configuration for Services and Connections -> View by
Instance -> MSSQLSERVER (or the local instance name) -> Database
Engine -> Remote Connections and make sure that it is set to: Local
and remote connections. Hope this helps.
Regards,
Enrique Martinez
Sr. Software Consultant|||User "EMartinez" <emartinez.pr1@.gmail.com>
> On Jun 29, 1:57 am, "Adam Kobylinski" <akobylin@.NO_SPAM.op.pl> wrote:
>> Hi!
>> When I try configure report data source to connect to database on another
>> SQL Server 200 i receive message:
>> The feature: "Remote access to report data sources and/or the report
>> server
>> database" is not supported in this edition of Reporting Services.
>> What can I do with thiss message?
>> Please help me
>> Best regards
>> Adam
>
> If you are running SQL Server 2005 Express Edition (w/Advanced
> Services), this is one of the limitations. Otherwise, you will want to
> open the local SQL Server Surface Area Configuration tool and select
> Surface Area Configuration for Services and Connections -> View by
> Instance -> MSSQLSERVER (or the local instance name) -> Database
> Engine -> Remote Connections and make sure that it is set to: Local
> and remote connections. Hope this helps.
>
Unfortunately it doesn't work, i already have remote connections selected,
SQL server 2000 on other computer is Standard Edition and i can connect
remotely from other applications.
Have you any idea?
Regards
Adam
When I try configure report data source to connect to database on another
SQL Server 200 i receive message:
The feature: "Remote access to report data sources and/or the report server
database" is not supported in this edition of Reporting Services.
What can I do with thiss message?
Please help me
Best regards
AdamOn Jun 29, 1:57 am, "Adam Kobylinski" <akobylin@.NO_SPAM.op.pl> wrote:
> Hi!
> When I try configure report data source to connect to database on another
> SQL Server 200 i receive message:
> The feature: "Remote access to report data sources and/or the report server
> database" is not supported in this edition of Reporting Services.
> What can I do with thiss message?
> Please help me
> Best regards
> Adam
If you are running SQL Server 2005 Express Edition (w/Advanced
Services), this is one of the limitations. Otherwise, you will want to
open the local SQL Server Surface Area Configuration tool and select
Surface Area Configuration for Services and Connections -> View by
Instance -> MSSQLSERVER (or the local instance name) -> Database
Engine -> Remote Connections and make sure that it is set to: Local
and remote connections. Hope this helps.
Regards,
Enrique Martinez
Sr. Software Consultant|||User "EMartinez" <emartinez.pr1@.gmail.com>
> On Jun 29, 1:57 am, "Adam Kobylinski" <akobylin@.NO_SPAM.op.pl> wrote:
>> Hi!
>> When I try configure report data source to connect to database on another
>> SQL Server 200 i receive message:
>> The feature: "Remote access to report data sources and/or the report
>> server
>> database" is not supported in this edition of Reporting Services.
>> What can I do with thiss message?
>> Please help me
>> Best regards
>> Adam
>
> If you are running SQL Server 2005 Express Edition (w/Advanced
> Services), this is one of the limitations. Otherwise, you will want to
> open the local SQL Server Surface Area Configuration tool and select
> Surface Area Configuration for Services and Connections -> View by
> Instance -> MSSQLSERVER (or the local instance name) -> Database
> Engine -> Remote Connections and make sure that it is set to: Local
> and remote connections. Hope this helps.
>
Unfortunately it doesn't work, i already have remote connections selected,
SQL server 2000 on other computer is Standard Edition and i can connect
remotely from other applications.
Have you any idea?
Regards
Adam
Tuesday, March 6, 2012
[Microsoft][ODBC Text Driver] In the file specification '...', the Col1 option is invalid.
I'm trying to connect to a tab-delimited text file using the ODBC data access. I set it up using Administrative Tools - Data Sources (ODBC) from the start menu, and clicked the 'Guess' button under Define Format.
The schema it created looks like this:
[cims_output_data.txt]
ColNameHeader=True
Format=TabDelimited
MaxScanRows=0
CharacterSet=OEM
Col1=SIMNAME
Col2=TIMESTAMP
Col3=SIMTYPE
Col4=REGION
Col5=SECTOR
....etc.
It looks OK, but if I go back to Define in Administrative Tools and try to review it, I get a similar error message:
Ini File (or Registry) C:\Program Files\CIMS\schema.ini is corrupt.
Section: cims_output_data.txt, Key: Col1.
Has anyone seen this before? There is nothing on MSDN as far as I could find. I read on another forum that if you replace the label 'Col1' with 'Col' the problem is solved but it still reports that the schema is corrupt when I try to open it in Administrative Tools.
Bill.
Hi Bill,
Could you try specifying the types of your columns in the schema (i.e. Col1=SIMNAME string...)?
I hope this helps,
John Gordon (MSFT)
|||John
thanks, I tried that. The funny thing is switching the "Col1" label to "Col" really does solve the problem so I am just going with this solution and ignoring the fact that the ODBC configuration editor says the schema is corrupt.
Bill.
[Microsoft][ODBC Text Driver] In the file specification '...', the Col1 option is invalid.
I'm trying to connect to a tab-delimited text file using the ODBC data access. I set it up using Administrative Tools - Data Sources (ODBC) from the start menu, and clicked the 'Guess' button under Define Format.
The schema it created looks like this:
[cims_output_data.txt]
ColNameHeader=True
Format=TabDelimited
MaxScanRows=0
CharacterSet=OEM
Col1=SIMNAME
Col2=TIMESTAMP
Col3=SIMTYPE
Col4=REGION
Col5=SECTOR
....etc.
It looks OK, but if I go back to Define in Administrative Tools and try to review it, I get a similar error message:
Ini File (or Registry) C:\Program Files\CIMS\schema.ini is corrupt.
Section: cims_output_data.txt, Key: Col1.
Has anyone seen this before? There is nothing on MSDN as far as I could find. I read on another forum that if you replace the label 'Col1' with 'Col' the problem is solved but it still reports that the schema is corrupt when I try to open it in Administrative Tools.
Bill.
Hi Bill,
Could you try specifying the types of your columns in the schema (i.e. Col1=SIMNAME string...)?
I hope this helps,
John Gordon (MSFT)
|||John
thanks, I tried that. The funny thing is switching the "Col1" label to "Col" really does solve the problem so I am just going with this solution and ignoring the fact that the ODBC configuration editor says the schema is corrupt.
Bill.
Saturday, February 25, 2012
[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name
I have a ms sqlserver 2000 database installed on my Windows NT4 PC.
I want to access this database from a java program using JDBC - ODBC
Here are the relavent lines of code from my java source code file.
Note : I am attempting to access the sample database "Northwind Traders" that came with the installation.
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver").newInstance();
datasource = "NORTHDS";
url = "jdbc:odbc:" + datasource;
con = DriverManager.getConnection(url,username,password) ;
query = "SELECT * from " + datasource + "." + username + "." + tablename;
ResultSet rs = stmt.executeQuery(query);
The connection succeeds but the query fails with :
java.sql.SQLException: [Microsoft][ODBC SQL Server Driver][SQL
Server]Invalid object name 'NORTHDS.username.Customers'.
Using the program "Microsoft Access" I was able to verify that the "Customers" table is intact.
Any ideas ?Take a look at the following:
In your select statement there are a couple of potential problems that you need to verify.
select * from datasource.username.table ... which is returning 'NORTHDS.username.Customers'
should be
select * from Northwind.dbo.Customers ... (unless you renamed the database ...)
In other words, check to make sure your are referencing the correct database/owner/table in your select statement. It appears that the variables you are using are incorrect. tablename appears to be ok, but the username variable is returning username. Also, the datasource variable may not be your database name.
I want to access this database from a java program using JDBC - ODBC
Here are the relavent lines of code from my java source code file.
Note : I am attempting to access the sample database "Northwind Traders" that came with the installation.
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver").newInstance();
datasource = "NORTHDS";
url = "jdbc:odbc:" + datasource;
con = DriverManager.getConnection(url,username,password) ;
query = "SELECT * from " + datasource + "." + username + "." + tablename;
ResultSet rs = stmt.executeQuery(query);
The connection succeeds but the query fails with :
java.sql.SQLException: [Microsoft][ODBC SQL Server Driver][SQL
Server]Invalid object name 'NORTHDS.username.Customers'.
Using the program "Microsoft Access" I was able to verify that the "Customers" table is intact.
Any ideas ?Take a look at the following:
In your select statement there are a couple of potential problems that you need to verify.
select * from datasource.username.table ... which is returning 'NORTHDS.username.Customers'
should be
select * from Northwind.dbo.Customers ... (unless you renamed the database ...)
In other words, check to make sure your are referencing the correct database/owner/table in your select statement. It appears that the variables you are using are incorrect. tablename appears to be ok, but the username variable is returning username. Also, the datasource variable may not be your database name.
[Microsoft][ODBC SQL Server Driver] Invalid Descriptor Index
Hi,
I am using MFC ODBC classes in my VC++ application for database accesss (on
a SQL Server/Access Database).
Some times after opening a Recordset (containing bound columns generated
using the ClassWizard) I have to use the
CRecordset::GetFieldValue( LPCTSTR lpszName, CDBVariant& varValue, short
nFieldType = DEFAULT_FIELD_TYPE )
method of the CRecordset object to obtain field values. The above method
works fine with ODBC drivers for Jet but when I use ODBC for SQL Server it
throws the following exception
State:S1002,Native:0,Origin:[Microsoft][
ODBC SQL Server Driver] Invalid
Descriptor Index
I don't understand why the Microsoft SQL Server ODBC Driver is throwing this
exception.
Please help me!
SameerHi Sameer,
Thanks for posting in the community.
From your description, I understand that when you use the CRecordset::GetFie
ldValue
method t oobtain the field values after opening a binding columns recordset,
you will
receive the exception of Invalid Descriptor Index for ODBC SQL Server Driver
. However, the
problem doesn't occur with ODBC drivers for Jet.
Before we start, please notice that the issue is related to MFC programming
which is
gracefully handling in this queue. However, it's my pleasure to let me see i
f I can address
your problem and give some solutions. For quickly and efficiently solve your
problem, it's
better to post this issue in the corresponding queues such as ADO/VC/VC++ ne
wsgroup.
I'm not 100% sure why the exception was genereted when using ODBC SQL Server
Drivers.
Based on my research, per the ODBC docs SQLGetData throws that error if it's
called and
all the columns are already bound when it is generated using the ClassWizard
.
So the bottom line is that if you're using a CRecordset that was created wit
h
the AppWizard, don't use GetFieldValue. Instead, go to the record that you
want and then look at the data member of the recordset to get the field valu
e.
Please apply my suggestions above and let me know if this helps resolve your
problem. If
there is anything more I can do to assist you, please feel free to post it i
n the group.
If the problem still persists and you'd like to get the most qualified pool
of respondents,
please repost this issue to the corresponding queues I mentioned above. Addi
tionally,
other partners who read the newsgroups regularly can either share their know
ledge or learn
from your interaction with us. I hope the problem can be resolved quickly.
Best regards,
Billy Yao
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.
I am using MFC ODBC classes in my VC++ application for database accesss (on
a SQL Server/Access Database).
Some times after opening a Recordset (containing bound columns generated
using the ClassWizard) I have to use the
CRecordset::GetFieldValue( LPCTSTR lpszName, CDBVariant& varValue, short
nFieldType = DEFAULT_FIELD_TYPE )
method of the CRecordset object to obtain field values. The above method
works fine with ODBC drivers for Jet but when I use ODBC for SQL Server it
throws the following exception
State:S1002,Native:0,Origin:[Microsoft][
ODBC SQL Server Driver] Invalid
Descriptor Index
I don't understand why the Microsoft SQL Server ODBC Driver is throwing this
exception.
Please help me!
SameerHi Sameer,
Thanks for posting in the community.
From your description, I understand that when you use the CRecordset::GetFie
ldValue
method t oobtain the field values after opening a binding columns recordset,
you will
receive the exception of Invalid Descriptor Index for ODBC SQL Server Driver
. However, the
problem doesn't occur with ODBC drivers for Jet.
Before we start, please notice that the issue is related to MFC programming
which is
gracefully handling in this queue. However, it's my pleasure to let me see i
f I can address
your problem and give some solutions. For quickly and efficiently solve your
problem, it's
better to post this issue in the corresponding queues such as ADO/VC/VC++ ne
wsgroup.
I'm not 100% sure why the exception was genereted when using ODBC SQL Server
Drivers.
Based on my research, per the ODBC docs SQLGetData throws that error if it's
called and
all the columns are already bound when it is generated using the ClassWizard
.
So the bottom line is that if you're using a CRecordset that was created wit
h
the AppWizard, don't use GetFieldValue. Instead, go to the record that you
want and then look at the data member of the recordset to get the field valu
e.
Please apply my suggestions above and let me know if this helps resolve your
problem. If
there is anything more I can do to assist you, please feel free to post it i
n the group.
If the problem still persists and you'd like to get the most qualified pool
of respondents,
please repost this issue to the corresponding queues I mentioned above. Addi
tionally,
other partners who read the newsgroups regularly can either share their know
ledge or learn
from your interaction with us. I hope the problem can be resolved quickly.
Best regards,
Billy Yao
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.
[Microsoft][ODBC Microsoft Access Driver] Too few parameters. Expected 2
Heres my code:
<%
'Dimension variables
Dim adoCon 'Holds the Database Connection Object
Dim rsAddLinks 'Holds the recordset for the new record to be added
Dim strSQL 'Holds the SQL query to query the database
'Create an ADO connection object
Set adoCon = Server.CreateObject("ADODB.Connection")
'Set an active connection to the Connection object using a DSN-less connection
adoCon.Open "DRIVER={Microsoft Access Driver (*.mdb)}; DBQ=" & Server.MapPath("links.mdb")
'Create an ADO recordset object
Set rsAddLinks = Server.CreateObject("ADODB.Recordset")
'Initialise the strSQL variable with an SQL statement to query the database
strSQL = "SELECT tblLinks.URL, tblLinks.Description FROM tblLinks;"
'Set the cursor type we are using so we can navigate through the recordset
rsAddLinks.CursorType = 2
'Set the lock type so that the record is locked by ADO when it is updated
rsAddLinks.LockType = 3
'Open the recordset with the SQL query
rsAddLinks.Open strSQL, adoCon
'Tell the recordset we are adding a new record to it
rsAddLinks.AddNew
'Add a new record to the recordset
rsAddLinks.Fields("URL") = Request.Form("url")
rsAddLinks.Fields("Description") = Request.Form("description")
'Write the updated recordset to the database
rsAddLinks.Update
'Reset server objects
rsAddLinks.Close
Set rsAddLinks = Nothing
Set adoCon = Nothing
'Redirect to the guestbook.asp page
Response.Redirect "links.asp"
%>
When i run the code I get: [Microsoft][ODBC Microsoft Access Driver] Too few parameters. Expected 2
Can someone please help?
--NickTry replacing % in place of *.|||Ok, thanks, but now it says
[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
Can you help me on this?
--Nick
PS: If your wondering, im reletively new at asp thats why I havent been able to figure this out myself.|||By all means refer to this KBA (http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/Q169/3/77.asp&NoWebContent=1) to get rid of the issues and follwup.|||That really didn't help me much.|||thanks for all your help. I figured it out! i was linking to the page directly when i should have been using the page b4 it that links to it...
if that makes any scence
<%
'Dimension variables
Dim adoCon 'Holds the Database Connection Object
Dim rsAddLinks 'Holds the recordset for the new record to be added
Dim strSQL 'Holds the SQL query to query the database
'Create an ADO connection object
Set adoCon = Server.CreateObject("ADODB.Connection")
'Set an active connection to the Connection object using a DSN-less connection
adoCon.Open "DRIVER={Microsoft Access Driver (*.mdb)}; DBQ=" & Server.MapPath("links.mdb")
'Create an ADO recordset object
Set rsAddLinks = Server.CreateObject("ADODB.Recordset")
'Initialise the strSQL variable with an SQL statement to query the database
strSQL = "SELECT tblLinks.URL, tblLinks.Description FROM tblLinks;"
'Set the cursor type we are using so we can navigate through the recordset
rsAddLinks.CursorType = 2
'Set the lock type so that the record is locked by ADO when it is updated
rsAddLinks.LockType = 3
'Open the recordset with the SQL query
rsAddLinks.Open strSQL, adoCon
'Tell the recordset we are adding a new record to it
rsAddLinks.AddNew
'Add a new record to the recordset
rsAddLinks.Fields("URL") = Request.Form("url")
rsAddLinks.Fields("Description") = Request.Form("description")
'Write the updated recordset to the database
rsAddLinks.Update
'Reset server objects
rsAddLinks.Close
Set rsAddLinks = Nothing
Set adoCon = Nothing
'Redirect to the guestbook.asp page
Response.Redirect "links.asp"
%>
When i run the code I get: [Microsoft][ODBC Microsoft Access Driver] Too few parameters. Expected 2
Can someone please help?
--NickTry replacing % in place of *.|||Ok, thanks, but now it says
[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
Can you help me on this?
--Nick
PS: If your wondering, im reletively new at asp thats why I havent been able to figure this out myself.|||By all means refer to this KBA (http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/Q169/3/77.asp&NoWebContent=1) to get rid of the issues and follwup.|||That really didn't help me much.|||thanks for all your help. I figured it out! i was linking to the page directly when i should have been using the page b4 it that links to it...
if that makes any scence
[Microsoft][ODBC Microsoft Access Driver] System resource exceeded
odbc_pconnect() [function.odbc-p
we got the error with access 2000 database and PHP as prog. language .
we created dsn for the connection.
reboot solves the problem. but we need another solution better than this.
You might be running a query that is returning too many records.
Try limiting the query by usng the WHERE clause. Try adding more memory to your computer
Also shifting to SQL Server 2005 for larger databases would improve performance.
Regards,
http://www.Designing-Systems.com
|||You might also want to check out that you do not keep creating new connections instead of reusing existing ones. Check your PSP settings(if you haven't already) and see whether you have pooling support from PHP or ODBC driver manager.|||
Hi there,
we solved this problem after converting access db to mysql. It solves problem for this.
thanks
|||If the problem is any of the problems suggested by the above posters, then shifting underlying database representation will just defer the problem until your database gets larger. While your current solution has clearly reduced the pressure to fix the problem, looking into reducing query load, connection usage, and memory overhead on the client side will certainly be beneficial for building a strategy to grow your database.
Hope this helps,
John (MSFT)
|||We solved this issue. Please close this thread.
Thank you
Jitendra Chavan
[Microsoft][ODBC Microsoft Access Driver] System resource exceeded
odbc_pconnect() [function.odbc-p
we got the error with access 2000 database and PHP as prog. language .
we created dsn for the connection.
reboot solves the problem. but we need another solution better than this.
You might be running a query that is returning too many records.
Try limiting the query by usng the WHERE clause. Try adding more memory to your computer
Also shifting to SQL Server 2005 for larger databases would improve performance.
Regards,
http://www.Designing-Systems.com
|||You might also want to check out that you do not keep creating new connections instead of reusing existing ones. Check your PSP settings(if you haven't already) and see whether you have pooling support from PHP or ODBC driver manager.|||
Hi there,
we solved this problem after converting access db to mysql. It solves problem for this.
thanks
|||If the problem is any of the problems suggested by the above posters, then shifting underlying database representation will just defer the problem until your database gets larger. While your current solution has clearly reduced the pressure to fix the problem, looking into reducing query load, connection usage, and memory overhead on the client side will certainly be beneficial for building a strategy to grow your database.
Hope this helps,
John (MSFT)
|||We solved this issue. Please close this thread.
Thank you
Jitendra Chavan
[Microsoft][ODBC Microsoft Access Driver] System resource exceeded
odbc_pconnect() [function.odbc-p
we got the error with access 2000 database and PHP as prog. language .
we created dsn for the connection.
reboot solves the problem. but we need another solution better than this.
You might be running a query that is returning too many records.
Try limiting the query by usng the WHERE clause. Try adding more memory to your computer
Also shifting to SQL Server 2005 for larger databases would improve performance.
Regards,
http://www.Designing-Systems.com
|||You might also want to check out that you do not keep creating new connections instead of reusing existing ones. Check your PSP settings(if you haven't already) and see whether you have pooling support from PHP or ODBC driver manager.|||
Hi there,
we solved this problem after converting access db to mysql. It solves problem for this.
thanks
|||If the problem is any of the problems suggested by the above posters, then shifting underlying database representation will just defer the problem until your database gets larger. While your current solution has clearly reduced the pressure to fix the problem, looking into reducing query load, connection usage, and memory overhead on the client side will certainly be beneficial for building a strategy to grow your database.
Hope this helps,
John (MSFT)
|||We solved this issue. Please close this thread.
Thank you
Jitendra Chavan
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
Subscribe to:
Posts (Atom)