ok yesterday i crunched my head against the wall, after trying MSDE
installation (MSDE rel.A and MSDE SP4) on a brand new WXPPSP2 laptop.
Today it worked, in this way:
#Prerequisites
1.removed any MSDE installation (control panel > Remove Applications)
2.removed any MSDE directory (eg. "C:\programmi\Microsoft SQL Server") and
subdirs
3.removed any MSSQL regKey (Regedit.exe > HKLM\Software\Microsoft, keys
named "Microsoft SQL Server" or "MSDE", i browsed by intuition)
#Installation
i used following installation parameters:
BLANKSAPWD=1 (testing purposes only, next i'll check SAPWD="strongpwd")
INSTANCENAME ="theinstance"
DATADIR = "c:\Program Files\Microsoft SQL Server\MSSQL$theinstance\data\"
(notice the final backslash)
/L*v "C:\msde.log"
#Connection
$ osql -S (local)\theinstance -E
using -U sa with no input as password i get the error "Access denied for
"sa" user. Reason: not associated with a trusted SQL Server connection"
since i installed with blank sa pwd. (In theory sa should gain access with
no password specified)
actually, if you install MSDE without specificating the authentication mode,
the installation sets the login authentication to Windows authentication
mode, not the integrated one, hence you cannot access with builtin users
login.
See http://support.microsoft.com/default...;EN-US;Q285097
for further infos.
> #Connection
> $ osql -S (local)\theinstance -E
> using -U sa with no input as password i get the error "Access denied for
> "sa" user. Reason: not associated with a trusted SQL Server connection"
> since i installed with blank sa pwd. (In theory sa should gain access with
> no password specified)
Showing posts with label connect. Show all posts
Showing posts with label connect. Show all posts
Tuesday, March 20, 2012
[strange] date format issue: 2 servers, one query, 2 different results.
I'm running 2 WIN2K SP4 servers with MSSQL Server (v 7.00.1077). Both NT servers seems to have the same setup. I use the ADODB object to connect to MSSQL via OLE DB and notice that the following query generates an error on one server, not the other:
SELECT DATA FROM TABLE_1 WHERE ((TRANSACTION_DATE >='13/11/2003') AND (TRANSACTIONS_DATE <='20/11/2003')) [dates are DD/MM/YYYY]
Query on server_1:
- using OLE DB: correct
- using ODBC: correct
- using Query Analyzer: error <The conversion of a char data type to a datetime data type resulted in an out-of-range datetime value>
On server_2:
- using OLE DB: error <The conversion of a char data type to a datetime data type resulted in an out-of-range datetime value>
- using ODBC: correct
- using Query Analyzer: error <The conversion of a char data type to a datetime data type resulted in an out-of-range datetime value>
Both servers have MDAC 2.8 RTM installed and a <select @.@.language> returns <us_english> via query analyzer and <franais> via ODBC.
I'd like to setup Server 2 so that queries can be executed the same as on server 1.
Any ideas are welcomed!There's a problem with 20/11/2003 in us_english format. Default is: MDY, so it's reading 20th as month, which is why you're getting that error.
Here's an article I found: http://members.lycos.nl/digispy/C2/P56/C2P56A1806.htm
G'luck!
Meera|||Possible there is something to do with locale settings of windows, check the "Region Options" in Control Panel for both servers.|||I'd say the languages are different...and accordingingly each date format is different
Di SELECT * FROM master..syslanguages
I think English is the only one that mdy|||(D/M/Y is a French date format).
I just had to set <French> to user's default language instead of <US_ENGLISH>. This means ODBC settings override the default SQL Server settings as OLE DB uses the default SQL Server setting.sql
SELECT DATA FROM TABLE_1 WHERE ((TRANSACTION_DATE >='13/11/2003') AND (TRANSACTIONS_DATE <='20/11/2003')) [dates are DD/MM/YYYY]
Query on server_1:
- using OLE DB: correct
- using ODBC: correct
- using Query Analyzer: error <The conversion of a char data type to a datetime data type resulted in an out-of-range datetime value>
On server_2:
- using OLE DB: error <The conversion of a char data type to a datetime data type resulted in an out-of-range datetime value>
- using ODBC: correct
- using Query Analyzer: error <The conversion of a char data type to a datetime data type resulted in an out-of-range datetime value>
Both servers have MDAC 2.8 RTM installed and a <select @.@.language> returns <us_english> via query analyzer and <franais> via ODBC.
I'd like to setup Server 2 so that queries can be executed the same as on server 1.
Any ideas are welcomed!There's a problem with 20/11/2003 in us_english format. Default is: MDY, so it's reading 20th as month, which is why you're getting that error.
Here's an article I found: http://members.lycos.nl/digispy/C2/P56/C2P56A1806.htm
G'luck!
Meera|||Possible there is something to do with locale settings of windows, check the "Region Options" in Control Panel for both servers.|||I'd say the languages are different...and accordingingly each date format is different
Di SELECT * FROM master..syslanguages
I think English is the only one that mdy|||(D/M/Y is a French date format).
I just had to set <French> to user's default language instead of <US_ENGLISH>. This means ODBC settings override the default SQL Server settings as OLE DB uses the default SQL Server setting.sql
Sunday, 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
Thursday, March 8, 2012
[Q]Problems related to the MySQL linked Server.
Dear everyone.
I have two questions about the linked server for the MySQL.
I need to connect to the mysql DB from the my SQLServer 2000 SP4 on the
Windows 2000 standard Edition(MDAC 2.8)
So, I made a linked server at the SQLServer. I worked well, but I faced with
some problem.
1. Query method
I need to query some data in the mysql with dynamic parameter.
ex) select @.v_intUserNo = uno
from tb_test
where userid = 'testid'
*input of the userid is changed everytime by the user.
so, I cannot use the OPENQUERY or OPENROWSET.
I want to query above like this,
select @.v_intUserNo = uno
from [linked server name].[catalog name].[schema name].[ta
ble name]
where userid = 'testid'
When I used above syntax at the linked server of the SQLServer, it worked
well.
But, it did not worked with the mysql DB.
(unfortunately, I cannot remember the exact error message.T.T)
2. Not killable SPID.
After #1 step, I tried many method to solve the problem.
As one trial, I set the catalog at the linked server's property.
After that, I tried query as followings
---
select @.v_intUserNo = uno
from [linked server name].[catalog name].[schema name].[ta
ble name]
where userid = 'testid'
or select @.v_intUserNo = uno
from OPENQUERY('TEST_DB', 'select * from test_tbl where userid =
''testid''')
---
It doesn't returned any error or result, so, I killed the session.
but it was not cleared promptly, only return the following message.
SPID 70: transaction rollback in progress. Estimated rollback completion:
100%. Estimated time remaining: 0 seconds.
After restarting the SQLServer, they were cleared.
I wish to know the all the experiencies for managing the linked server to
the mysql DB at the SQLServer.
Thank you in advanceFurther information of my environment.
1. I used the mysql ODBC Ver 3.51
2. The error messge when I query data with following SQL.
select @.v_intUserNo = uno
from [linked server name].[catalog name].[schema name].[ta
ble name]
where userid = 'testid'
Server: Msg 7313, Level 16, State 1, Line 1
Invalid schema or catalog specified for provider 'MSDASQL'.
OLE DB error trace [Non-interface error: Invalid schema or catalog
specified for the provider.].
**Following query also doesn't work.
select @.v_intUserNo = uno
from [linked server name].[catalog name].[table name]
where userid = 'testid'
select @.v_intUserNo = uno
from [linked server name].[schema name].[table name]
where userid = 'testid'
select @.v_intUserNo = uno
from [linked server name].[table name]
where userid = 'testid'
Thank you.
"?" <dialup@.nownuri.net> wrote in message
news:ObJWtpObGHA.3992@.TK2MSFTNGP05.phx.gbl...
> Dear everyone.
> I have two questions about the linked server for the MySQL.
> I need to connect to the mysql DB from the my SQLServer 2000 SP4 on the
> Windows 2000 standard Edition(MDAC 2.8)
> So, I made a linked server at the SQLServer. I worked well, but I faced
with
> some problem.
> 1. Query method
> I need to query some data in the mysql with dynamic parameter.
> ex) select @.v_intUserNo = uno
> from tb_test
> where userid = 'testid'
> *input of the userid is changed everytime by the user.
> so, I cannot use the OPENQUERY or OPENROWSET.
> I want to query above like this,
> select @.v_intUserNo = uno
> from [linked server name].[catalog name].[schema name].[
table name]
> where userid = 'testid'
> When I used above syntax at the linked server of the SQLServer, it worked
> well.
> But, it did not worked with the mysql DB.
> (unfortunately, I cannot remember the exact error message.T.T)
> 2. Not killable SPID.
> After #1 step, I tried many method to solve the problem.
> As one trial, I set the catalog at the linked server's property.
> After that, I tried query as followings
> ---
> select @.v_intUserNo = uno
> from [linked server name].[catalog name].[schema name].[
table name]
> where userid = 'testid'
> or select @.v_intUserNo = uno
> from OPENQUERY('TEST_DB', 'select * from test_tbl where userid =
> ''testid''')
> ---
> It doesn't returned any error or result, so, I killed the session.
> but it was not cleared promptly, only return the following message.
> SPID 70: transaction rollback in progress. Estimated rollback completion:
> 100%. Estimated time remaining: 0 seconds.
> After restarting the SQLServer, they were cleared.
> I wish to know the all the experiencies for managing the linked server to
> the mysql DB at the SQLServer.
> Thank you in advance
>
>
I have two questions about the linked server for the MySQL.
I need to connect to the mysql DB from the my SQLServer 2000 SP4 on the
Windows 2000 standard Edition(MDAC 2.8)
So, I made a linked server at the SQLServer. I worked well, but I faced with
some problem.
1. Query method
I need to query some data in the mysql with dynamic parameter.
ex) select @.v_intUserNo = uno
from tb_test
where userid = 'testid'
*input of the userid is changed everytime by the user.
so, I cannot use the OPENQUERY or OPENROWSET.
I want to query above like this,
select @.v_intUserNo = uno
from [linked server name].[catalog name].[schema name].[ta
ble name]
where userid = 'testid'
When I used above syntax at the linked server of the SQLServer, it worked
well.
But, it did not worked with the mysql DB.
(unfortunately, I cannot remember the exact error message.T.T)
2. Not killable SPID.
After #1 step, I tried many method to solve the problem.
As one trial, I set the catalog at the linked server's property.
After that, I tried query as followings
---
select @.v_intUserNo = uno
from [linked server name].[catalog name].[schema name].[ta
ble name]
where userid = 'testid'
or select @.v_intUserNo = uno
from OPENQUERY('TEST_DB', 'select * from test_tbl where userid =
''testid''')
---
It doesn't returned any error or result, so, I killed the session.
but it was not cleared promptly, only return the following message.
SPID 70: transaction rollback in progress. Estimated rollback completion:
100%. Estimated time remaining: 0 seconds.
After restarting the SQLServer, they were cleared.
I wish to know the all the experiencies for managing the linked server to
the mysql DB at the SQLServer.
Thank you in advanceFurther information of my environment.
1. I used the mysql ODBC Ver 3.51
2. The error messge when I query data with following SQL.
select @.v_intUserNo = uno
from [linked server name].[catalog name].[schema name].[ta
ble name]
where userid = 'testid'
Server: Msg 7313, Level 16, State 1, Line 1
Invalid schema or catalog specified for provider 'MSDASQL'.
OLE DB error trace [Non-interface error: Invalid schema or catalog
specified for the provider.].
**Following query also doesn't work.
select @.v_intUserNo = uno
from [linked server name].[catalog name].[table name]
where userid = 'testid'
select @.v_intUserNo = uno
from [linked server name].[schema name].[table name]
where userid = 'testid'
select @.v_intUserNo = uno
from [linked server name].[table name]
where userid = 'testid'
Thank you.
"?" <dialup@.nownuri.net> wrote in message
news:ObJWtpObGHA.3992@.TK2MSFTNGP05.phx.gbl...
> Dear everyone.
> I have two questions about the linked server for the MySQL.
> I need to connect to the mysql DB from the my SQLServer 2000 SP4 on the
> Windows 2000 standard Edition(MDAC 2.8)
> So, I made a linked server at the SQLServer. I worked well, but I faced
with
> some problem.
> 1. Query method
> I need to query some data in the mysql with dynamic parameter.
> ex) select @.v_intUserNo = uno
> from tb_test
> where userid = 'testid'
> *input of the userid is changed everytime by the user.
> so, I cannot use the OPENQUERY or OPENROWSET.
> I want to query above like this,
> select @.v_intUserNo = uno
> from [linked server name].[catalog name].[schema name].[
table name]
> where userid = 'testid'
> When I used above syntax at the linked server of the SQLServer, it worked
> well.
> But, it did not worked with the mysql DB.
> (unfortunately, I cannot remember the exact error message.T.T)
> 2. Not killable SPID.
> After #1 step, I tried many method to solve the problem.
> As one trial, I set the catalog at the linked server's property.
> After that, I tried query as followings
> ---
> select @.v_intUserNo = uno
> from [linked server name].[catalog name].[schema name].[
table name]
> where userid = 'testid'
> or select @.v_intUserNo = uno
> from OPENQUERY('TEST_DB', 'select * from test_tbl where userid =
> ''testid''')
> ---
> It doesn't returned any error or result, so, I killed the session.
> but it was not cleared promptly, only return the following message.
> SPID 70: transaction rollback in progress. Estimated rollback completion:
> 100%. Estimated time remaining: 0 seconds.
> After restarting the SQLServer, they were cleared.
> I wish to know the all the experiencies for managing the linked server to
> the mysql DB at the SQLServer.
> Thank you in advance
>
>
Tuesday, March 6, 2012
[Microsoft][SQLServer 2000 Driver for JDBC]The requested instance is either invalid or not
I have this instance running, on a server. I can connect to it using SQL
Query Analyzer as well as SQL Enterprise Manager.
But when I try to connect to it using SQL Server JDBC it gives error,
[Microsoft][SQLServer 2000 Driver for JDBC]The requested instance is either
invalid or not running.
I havent changed anything in Java code it is still the same. It was working
fine earlier. Can any one help?
I had similar problem with SQL Analyzer too but I could fix it using
cliconfg utility provided by MS.
| From: "Developers@.Enzigma" <developers@.enzigma.com>
| Subject: [Microsoft][SQLServer 2000 Driver for JDBC]The requested
instance is either invalid or not running.
| Date: Thu, 20 May 2004 16:29:47 +0530
| Lines: 14
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
| Message-ID: <eIISfmlPEHA.1340@.TK2MSFTNGP12.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.jdbcdriver
| NNTP-Posting-Host: 203.123.162.162
| Path:
cpmsftngxa10.phx.gbl!TK2MSFTFEED01.phx.gbl!TK2MSFT NGP08.phx.gbl!TK2MSFTNGP12
.phx.gbl
| Xref: cpmsftngxa10.phx.gbl microsoft.public.sqlserver.jdbcdriver:6044
| X-Tomcat-NG: microsoft.public.sqlserver.jdbcdriver
|
| I have this instance running, on a server. I can connect to it using SQL
| Query Analyzer as well as SQL Enterprise Manager.
|
| But when I try to connect to it using SQL Server JDBC it gives error,
| [Microsoft][SQLServer 2000 Driver for JDBC]The requested instance is
either
| invalid or not running.
|
| I havent changed anything in Java code it is still the same. It was
working
| fine earlier. Can any one help?
|
| I had similar problem with SQL Analyzer too but I could fix it using
| cliconfg utility provided by MS.
|
|
|
With JDBC SP2, I can only reproduce this behavior if I have incorrectly
specified the instance name in my code. What is the name of your instance,
and can you post the code snippet that reproduces the problem? You
mentioned using cliconfg.exe to fix a similar problem with Query Analyzer.
Please run this tool again and verify that there are no aliases that point
to an invalid instance name as well.
Carb Simien, MCSE MCDBA MCAD
Microsoft Developer Support - Web Data
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.
Query Analyzer as well as SQL Enterprise Manager.
But when I try to connect to it using SQL Server JDBC it gives error,
[Microsoft][SQLServer 2000 Driver for JDBC]The requested instance is either
invalid or not running.
I havent changed anything in Java code it is still the same. It was working
fine earlier. Can any one help?
I had similar problem with SQL Analyzer too but I could fix it using
cliconfg utility provided by MS.
| From: "Developers@.Enzigma" <developers@.enzigma.com>
| Subject: [Microsoft][SQLServer 2000 Driver for JDBC]The requested
instance is either invalid or not running.
| Date: Thu, 20 May 2004 16:29:47 +0530
| Lines: 14
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
| Message-ID: <eIISfmlPEHA.1340@.TK2MSFTNGP12.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.jdbcdriver
| NNTP-Posting-Host: 203.123.162.162
| Path:
cpmsftngxa10.phx.gbl!TK2MSFTFEED01.phx.gbl!TK2MSFT NGP08.phx.gbl!TK2MSFTNGP12
.phx.gbl
| Xref: cpmsftngxa10.phx.gbl microsoft.public.sqlserver.jdbcdriver:6044
| X-Tomcat-NG: microsoft.public.sqlserver.jdbcdriver
|
| I have this instance running, on a server. I can connect to it using SQL
| Query Analyzer as well as SQL Enterprise Manager.
|
| But when I try to connect to it using SQL Server JDBC it gives error,
| [Microsoft][SQLServer 2000 Driver for JDBC]The requested instance is
either
| invalid or not running.
|
| I havent changed anything in Java code it is still the same. It was
working
| fine earlier. Can any one help?
|
| I had similar problem with SQL Analyzer too but I could fix it using
| cliconfg utility provided by MS.
|
|
|
With JDBC SP2, I can only reproduce this behavior if I have incorrectly
specified the instance name in my code. What is the name of your instance,
and can you post the code snippet that reproduces the problem? You
mentioned using cliconfg.exe to fix a similar problem with Query Analyzer.
Please run this tool again and verify that there are no aliases that point
to an invalid instance name as well.
Carb Simien, MCSE MCDBA MCAD
Microsoft Developer Support - Web Data
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.
[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.
[Microsoft][ODBC SQL Server Driver]Timeout expired
Hi:
I am getting this error when the .asp page tries to connect to the DB server.
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC SQL Server Driver]Timeout expired
The web server is Windows 2000 Advanced Server, Dual CPU with
Hyperthreading, P4 with 2 GB RAM. The database is SQL 2000 Standard Edition
with SP3 and Cumulative Patch for Microsoft SQL Server (815495)MS03-031
installed on a remote server with the same config. I have also tried all the
possible variations like increasing the VBscript timeout in IIS from 90 to
300 and Global transaction timeout in COM+ applications from 60 to 300. This
however is not helping either. When I check the anonymous concurrent sessions
I find atleast 950 connections at any given time. Also installed MDAC 2.7
Refresh on both the servers.
Can any one help me on this please.
Mitul Z.
Hi Mitul,
This error message is somewhat a generic error message for ODBC. Here are
some ideas for troubleshooting the issue.
1. From the server hosting your web server, can you connect to the SQL
Server using Query Analyzer? If you do not have Query Analyzer available,
you can test connectivity by creating a test ODBC DSN and using the test
facility. Can you connect to the SQL Server with these techniques?
2. If you can connect using Query Analyzer or an ODBC test DSN, then the
issue is with the asp page itself. If you cannot connect to the SQL Server
using these tests, the problem is with ODBC configuration or a network
level problem is at play.
If you suspect a network problem is at play, Network Monitor traces will be
very helpful for your troubleshooting. That will at least allow you to
know if your connection request is reaching the SQL Server.
Please let me know if this information helps.
Thank you.
Gary
This posting is provided "AS IS" with no warranties, and confers no rights.
I am getting this error when the .asp page tries to connect to the DB server.
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC SQL Server Driver]Timeout expired
The web server is Windows 2000 Advanced Server, Dual CPU with
Hyperthreading, P4 with 2 GB RAM. The database is SQL 2000 Standard Edition
with SP3 and Cumulative Patch for Microsoft SQL Server (815495)MS03-031
installed on a remote server with the same config. I have also tried all the
possible variations like increasing the VBscript timeout in IIS from 90 to
300 and Global transaction timeout in COM+ applications from 60 to 300. This
however is not helping either. When I check the anonymous concurrent sessions
I find atleast 950 connections at any given time. Also installed MDAC 2.7
Refresh on both the servers.
Can any one help me on this please.
Mitul Z.
Hi Mitul,
This error message is somewhat a generic error message for ODBC. Here are
some ideas for troubleshooting the issue.
1. From the server hosting your web server, can you connect to the SQL
Server using Query Analyzer? If you do not have Query Analyzer available,
you can test connectivity by creating a test ODBC DSN and using the test
facility. Can you connect to the SQL Server with these techniques?
2. If you can connect using Query Analyzer or an ODBC test DSN, then the
issue is with the asp page itself. If you cannot connect to the SQL Server
using these tests, the problem is with ODBC configuration or a network
level problem is at play.
If you suspect a network problem is at play, Network Monitor traces will be
very helpful for your troubleshooting. That will at least allow you to
know if your connection request is reaching the SQL Server.
Please let me know if this information helps.
Thank you.
Gary
This posting is provided "AS IS" with no warranties, and confers no rights.
[Microsoft][ODBC SQL Server Driver]Timeout expired
Hi:
I am getting this error when the .asp page tries to connect to the DB server
.
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC SQL Server Driver]Timeout expired
The web server is Windows 2000 Advanced Server, Dual CPU with
Hyperthreading, P4 with 2 GB RAM. The database is SQL 2000 Standard Edition
with SP3 and Cumulative Patch for Microsoft SQL Server (815495)MS03-031
installed on a remote server with the same config. I have also tried all the
possible variations like increasing the VBscript timeout in IIS from 90 to
300 and Global transaction timeout in COM+ applications from 60 to 300. This
however is not helping either. When I check the anonymous concurrent session
s
I find atleast 950 connections at any given time. Also installed MDAC 2.7
Refresh on both the servers.
Can any one help me on this please.
Mitul Z.Hi Mitul,
This error message is somewhat a generic error message for ODBC. Here are
some ideas for troubleshooting the issue.
1. From the server hosting your web server, can you connect to the SQL
Server using Query Analyzer? If you do not have Query Analyzer available,
you can test connectivity by creating a test ODBC DSN and using the test
facility. Can you connect to the SQL Server with these techniques?
2. If you can connect using Query Analyzer or an ODBC test DSN, then the
issue is with the asp page itself. If you cannot connect to the SQL Server
using these tests, the problem is with ODBC configuration or a network
level problem is at play.
If you suspect a network problem is at play, Network Monitor traces will be
very helpful for your troubleshooting. That will at least allow you to
know if your connection request is reaching the SQL Server.
Please let me know if this information helps.
Thank you.
Gary
This posting is provided "AS IS" with no warranties, and confers no rights.
I am getting this error when the .asp page tries to connect to the DB server
.
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC SQL Server Driver]Timeout expired
The web server is Windows 2000 Advanced Server, Dual CPU with
Hyperthreading, P4 with 2 GB RAM. The database is SQL 2000 Standard Edition
with SP3 and Cumulative Patch for Microsoft SQL Server (815495)MS03-031
installed on a remote server with the same config. I have also tried all the
possible variations like increasing the VBscript timeout in IIS from 90 to
300 and Global transaction timeout in COM+ applications from 60 to 300. This
however is not helping either. When I check the anonymous concurrent session
s
I find atleast 950 connections at any given time. Also installed MDAC 2.7
Refresh on both the servers.
Can any one help me on this please.
Mitul Z.Hi Mitul,
This error message is somewhat a generic error message for ODBC. Here are
some ideas for troubleshooting the issue.
1. From the server hosting your web server, can you connect to the SQL
Server using Query Analyzer? If you do not have Query Analyzer available,
you can test connectivity by creating a test ODBC DSN and using the test
facility. Can you connect to the SQL Server with these techniques?
2. If you can connect using Query Analyzer or an ODBC test DSN, then the
issue is with the asp page itself. If you cannot connect to the SQL Server
using these tests, the problem is with ODBC configuration or a network
level problem is at play.
If you suspect a network problem is at play, Network Monitor traces will be
very helpful for your troubleshooting. That will at least allow you to
know if your connection request is reaching the SQL Server.
Please let me know if this information helps.
Thank you.
Gary
This posting is provided "AS IS" with no warranties, and confers no rights.
Saturday, February 25, 2012
[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name
hi
i m connect to the sQL SERVER using system DSN in JREPORT
but it is not working
get the following error
[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name
Try using
i m connect to the sQL SERVER using system DSN in JREPORT
but it is not working
get the following error
[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name
Quote:
Originally Posted by daxter
hi
i m connect to the sQL SERVER using system DSN in JREPORT
but it is not working
get the following error
[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name
Try using
\Control Panel\Administrative Tools\Data Sources (ODBC)
And System DNS tab up the top of that window
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
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denie
Hi all.
I'm running a large data transaction and get the next error :
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.
In this case, I process over many, many records, and then it finally indicated the server doesn't exist. This only occurs sometime.
I have SQLServer 2000 on Windows 2003 Server
Some idea how to solve this.
Thanks advanced
Wil.How are you running this large transaction? VIA ODBC or something? Can you please give us a little more detail.
Thanks,
-Kilka|||Just saw date.|||I also have the same problem as Wil, i'm running my application on :
.... Windows Server 2003
.... SQL Server 2000
.... Delphi 6
when i try to connecting the sql server with delphi application, then the error
'[DBNETLIB][ConnectionOpen(Connect()).]SQLServer does not exist or access denied.' raised.
I wonder if it's got anything wrong with the sql server instalation or the network system.
I'm desperately need help.
thank you
mayra|||My first guess would be that you have not applied Service Pack 3a or later to SQL Server 2000. Windows Server 2003 won't allow SQL Server access to the network until after a current service pack is applied, in order to prevent malware such as Slammer (http://www.microsoft.com/technet/security/alerts/slammer.mspx) from disrupting networks and the Internet.
-PatP|||Thank you Pat for your reply, i really appreciate that ;)
I just read from the book "SQL Server 2000 Bible",that windows server 2003 is using the SQL Server 2000 enterprise edition, while i'm using the personal edition.
So i think that's the main problem, then i started to re-install my sql server , and it works.
Thanks again Pat
mayra|||KBA http://support.microsoft.com/kb/328306/en-us will explain the root cause to resolve the issue.
I'm running a large data transaction and get the next error :
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.
In this case, I process over many, many records, and then it finally indicated the server doesn't exist. This only occurs sometime.
I have SQLServer 2000 on Windows 2003 Server
Some idea how to solve this.
Thanks advanced
Wil.How are you running this large transaction? VIA ODBC or something? Can you please give us a little more detail.
Thanks,
-Kilka|||Just saw date.|||I also have the same problem as Wil, i'm running my application on :
.... Windows Server 2003
.... SQL Server 2000
.... Delphi 6
when i try to connecting the sql server with delphi application, then the error
'[DBNETLIB][ConnectionOpen(Connect()).]SQLServer does not exist or access denied.' raised.
I wonder if it's got anything wrong with the sql server instalation or the network system.
I'm desperately need help.
thank you
mayra|||My first guess would be that you have not applied Service Pack 3a or later to SQL Server 2000. Windows Server 2003 won't allow SQL Server access to the network until after a current service pack is applied, in order to prevent malware such as Slammer (http://www.microsoft.com/technet/security/alerts/slammer.mspx) from disrupting networks and the Internet.
-PatP|||Thank you Pat for your reply, i really appreciate that ;)
I just read from the book "SQL Server 2000 Bible",that windows server 2003 is using the SQL Server 2000 enterprise edition, while i'm using the personal edition.
So i think that's the main problem, then i started to re-install my sql server , and it works.
Thanks again Pat
mayra|||KBA http://support.microsoft.com/kb/328306/en-us will explain the root cause to resolve the issue.
Subscribe to:
Posts (Atom)