Hide an ODBC connection?

We've purchased a 3rd party app that uses an Access db linked to SQL Server. Unfortunately, we've come to discover that a user of ours seems to know access and has decided to take report writing into their own hands.
We have the app and the access db on a server and a mapped a drive for each user.

Unfortunately, I can't lock down the ODBC connection because that would lock it down in the app. Someone suggested using a File DSN and removing the System DSN's off all users machines. I'm not too familiar with File DSN's and wanted to know if this would prevent users from creating their own Access mdb's linked to my server or not.

Any idea's are greatly appreciated.Dude,

Bad news :( - unless you can stop the end user from hacking the registry and prevent access to the odbcad32 (which you really can't lock out and have the machine access the server) there isn't much you can do AFAIK.

You didn't mention what OS's are in play. If you are a Win2k/WinXP shop you may be able to build a policy that limits the user from adding a new DSN, but I doubt even a file DSN will really stop him. If you go look in C:\Program Files\Common Files\ODBC\Data Sources All they really do is point to the system DSN. And he'll be able to pick it in Access.|||I figured the answer would go something like that.
Thank you anyways.

Hidden records?

Hi all,
Using vb6 ado connection I can see the record
e.g. SELECT * FROM table where id=1234
I will see the record
but
Using the same query on Enterprise Manager
the same query results to nothing.
Also
SELECT COUNT(*) AS Expr1
FROM table
Result:
vb6 query:1726 records
Ent. Manager view: 18 records
My questions is why Ent. Manager cannot see all the records
I am using SQL Server 2000 standard edition
The database itselt is nearly 21gb.
Any help or advice appreciated
Regards,
AllanAllan
Are you sure you connected to the same database?
"Allan" <Allan@.discussions.microsoft.com> wrote in message
news:A58D0D12-4BD4-4125-9542-8A45D53BA2E3@.microsoft.com...
> Hi all,
> Using vb6 ado connection I can see the record
> e.g. SELECT * FROM table where id=1234
> I will see the record
> but
> Using the same query on Enterprise Manager
> the same query results to nothing.
> Also
> SELECT COUNT(*) AS Expr1
> FROM table
> Result:
> vb6 query:1726 records
> Ent. Manager view: 18 records
> My questions is why Ent. Manager cannot see all the records
> I am using SQL Server 2000 standard edition
> The database itselt is nearly 21gb.
> Any help or advice appreciated
> Regards,
> Allan
>|||> Also
> SELECT COUNT(*) AS Expr1
> FROM table
> Result:
> vb6 query:1726 records
> Ent. Manager view: 18 records
My guess is that these are different server/databases with the same table.
Try verifying connection context with SELECT @.@.SERVERNAME, DB_NAME().
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Allan" <Allan@.discussions.microsoft.com> wrote in message
news:A58D0D12-4BD4-4125-9542-8A45D53BA2E3@.microsoft.com...
> Hi all,
> Using vb6 ado connection I can see the record
> e.g. SELECT * FROM table where id=1234
> I will see the record
> but
> Using the same query on Enterprise Manager
> the same query results to nothing.
> Also
> SELECT COUNT(*) AS Expr1
> FROM table
> Result:
> vb6 query:1726 records
> Ent. Manager view: 18 records
> My questions is why Ent. Manager cannot see all the records
> I am using SQL Server 2000 standard edition
> The database itselt is nearly 21gb.
> Any help or advice appreciated
> Regards,
> Allan
>|||Uri,
Yes. We only have one database. I connect via ip address and database name
"Uri Dimant" wrote:
> Allan
> Are you sure you connected to the same database?
> "Allan" <Allan@.discussions.microsoft.com> wrote in message
> news:A58D0D12-4BD4-4125-9542-8A45D53BA2E3@.microsoft.com...
> > Hi all,
> >
> > Using vb6 ado connection I can see the record
> > e.g. SELECT * FROM table where id=1234
> > I will see the record
> >
> > but
> > Using the same query on Enterprise Manager
> > the same query results to nothing.
> >
> > Also
> > SELECT COUNT(*) AS Expr1
> > FROM table
> >
> > Result:
> > vb6 query:1726 records
> > Ent. Manager view: 18 records
> >
> > My questions is why Ent. Manager cannot see all the records
> >
> > I am using SQL Server 2000 standard edition
> > The database itselt is nearly 21gb.
> >
> > Any help or advice appreciated
> >
> > Regards,
> > Allan
> >
>
>|||Also, after verifying the same servername/databasename, make sure you use the same table by
owner-qualifying the name, like
SELECT COUNT(*) FROM dbo.table
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:2D08ED0C-D379-4DE6-97E1-3A97037EA0AE@.microsoft.com...
>> Also
>> SELECT COUNT(*) AS Expr1
>> FROM table
>> Result:
>> vb6 query:1726 records
>> Ent. Manager view: 18 records
> My guess is that these are different server/databases with the same table. Try verifying
> connection context with SELECT @.@.SERVERNAME, DB_NAME().
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Allan" <Allan@.discussions.microsoft.com> wrote in message
> news:A58D0D12-4BD4-4125-9542-8A45D53BA2E3@.microsoft.com...
>> Hi all,
>> Using vb6 ado connection I can see the record
>> e.g. SELECT * FROM table where id=1234
>> I will see the record
>> but
>> Using the same query on Enterprise Manager
>> the same query results to nothing.
>> Also
>> SELECT COUNT(*) AS Expr1
>> FROM table
>> Result:
>> vb6 query:1726 records
>> Ent. Manager view: 18 records
>> My questions is why Ent. Manager cannot see all the records
>> I am using SQL Server 2000 standard edition
>> The database itselt is nearly 21gb.
>> Any help or advice appreciated
>> Regards,
>> Allan
>|||Hi Dan
Same reply as Uri
We only have one database. I connect via ip address and database name
I wish that was the case and the problem is solved
Will the size of the database (21 gb) makes any difference to the standard
edition of SQL server?
How about data corruption?
Thank you for your interest
"Dan Guzman" wrote:
> > Also
> > SELECT COUNT(*) AS Expr1
> > FROM table
> >
> > Result:
> > vb6 query:1726 records
> > Ent. Manager view: 18 records
> My guess is that these are different server/databases with the same table.
> Try verifying connection context with SELECT @.@.SERVERNAME, DB_NAME().
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Allan" <Allan@.discussions.microsoft.com> wrote in message
> news:A58D0D12-4BD4-4125-9542-8A45D53BA2E3@.microsoft.com...
> > Hi all,
> >
> > Using vb6 ado connection I can see the record
> > e.g. SELECT * FROM table where id=1234
> > I will see the record
> >
> > but
> > Using the same query on Enterprise Manager
> > the same query results to nothing.
> >
> > Also
> > SELECT COUNT(*) AS Expr1
> > FROM table
> >
> > Result:
> > vb6 query:1726 records
> > Ent. Manager view: 18 records
> >
> > My questions is why Ent. Manager cannot see all the records
> >
> > I am using SQL Server 2000 standard edition
> > The database itselt is nearly 21gb.
> >
> > Any help or advice appreciated
> >
> > Regards,
> > Allan
> >
>|||"Allan" <Allan@.discussions.microsoft.com> wrote in message
news:FE6482BA-6070-40EE-AC99-ABDA230A42BD@.microsoft.com...
> Hi Dan
> Same reply as Uri
> We only have one database. I connect via ip address and database name
> I wish that was the case and the problem is solved
> Will the size of the database (21 gb) makes any difference to the standard
> edition of SQL server?
Not at all.
> How about data corruption?
Highly unlikely that a query one place would return one set of data and the
same query from another place would return different data.
So sounds like something is missing in your description (like a table with
the same name was accidentally created in the MASTER DB and some records
inserted and when you connect the 2nd way you're hitting master, not your
database and seeing the wrong table.
As other have said, to be 100% sure, do a select * from
<dbname>.<owner>.tablename.
> Thank you for your interest
> "Dan Guzman" wrote:
>> > Also
>> > SELECT COUNT(*) AS Expr1
>> > FROM table
>> >
>> > Result:
>> > vb6 query:1726 records
>> > Ent. Manager view: 18 records
>> My guess is that these are different server/databases with the same
>> table.
>> Try verifying connection context with SELECT @.@.SERVERNAME, DB_NAME().
>> --
>> Hope this helps.
>> Dan Guzman
>> SQL Server MVP
>> "Allan" <Allan@.discussions.microsoft.com> wrote in message
>> news:A58D0D12-4BD4-4125-9542-8A45D53BA2E3@.microsoft.com...
>> > Hi all,
>> >
>> > Using vb6 ado connection I can see the record
>> > e.g. SELECT * FROM table where id=1234
>> > I will see the record
>> >
>> > but
>> > Using the same query on Enterprise Manager
>> > the same query results to nothing.
>> >
>> > Also
>> > SELECT COUNT(*) AS Expr1
>> > FROM table
>> >
>> > Result:
>> > vb6 query:1726 records
>> > Ent. Manager view: 18 records
>> >
>> > My questions is why Ent. Manager cannot see all the records
>> >
>> > I am using SQL Server 2000 standard edition
>> > The database itselt is nearly 21gb.
>> >
>> > Any help or advice appreciated
>> >
>> > Regards,
>> > Allan
>> >
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html|||I think Tibor's idea that you have different tables in different schema is
likely. The Best Practice is to always schema-qualify table names. Not
only does this avoid ambiguous references, it helps improve performance too.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Allan" <Allan@.discussions.microsoft.com> wrote in message
news:FE6482BA-6070-40EE-AC99-ABDA230A42BD@.microsoft.com...
> Hi Dan
> Same reply as Uri
> We only have one database. I connect via ip address and database name
> I wish that was the case and the problem is solved
> Will the size of the database (21 gb) makes any difference to the standard
> edition of SQL server?
> How about data corruption?
> Thank you for your interest
> "Dan Guzman" wrote:
>> > Also
>> > SELECT COUNT(*) AS Expr1
>> > FROM table
>> >
>> > Result:
>> > vb6 query:1726 records
>> > Ent. Manager view: 18 records
>> My guess is that these are different server/databases with the same
>> table.
>> Try verifying connection context with SELECT @.@.SERVERNAME, DB_NAME().
>> --
>> Hope this helps.
>> Dan Guzman
>> SQL Server MVP
>> "Allan" <Allan@.discussions.microsoft.com> wrote in message
>> news:A58D0D12-4BD4-4125-9542-8A45D53BA2E3@.microsoft.com...
>> > Hi all,
>> >
>> > Using vb6 ado connection I can see the record
>> > e.g. SELECT * FROM table where id=1234
>> > I will see the record
>> >
>> > but
>> > Using the same query on Enterprise Manager
>> > the same query results to nothing.
>> >
>> > Also
>> > SELECT COUNT(*) AS Expr1
>> > FROM table
>> >
>> > Result:
>> > vb6 query:1726 records
>> > Ent. Manager view: 18 records
>> >
>> > My questions is why Ent. Manager cannot see all the records
>> >
>> > I am using SQL Server 2000 standard edition
>> > The database itselt is nearly 21gb.
>> >
>> > Any help or advice appreciated
>> >
>> > Regards,
>> > Allan
>> >|||To Uri,Dan,Greg and Tibor,
Thank for all your help. It was decided to restore from last nights backup
and redo todays activities.
After restore queries from vb6 and Ent. Manager equalled
I am printing your advice for future reference
Regards,
Allan
"Allan" wrote:
> Hi all,
> Using vb6 ado connection I can see the record
> e.g. SELECT * FROM table where id=1234
> I will see the record
> but
> Using the same query on Enterprise Manager
> the same query results to nothing.
> Also
> SELECT COUNT(*) AS Expr1
> FROM table
> Result:
> vb6 query:1726 records
> Ent. Manager view: 18 records
> My questions is why Ent. Manager cannot see all the records
> I am using SQL Server 2000 standard edition
> The database itselt is nearly 21gb.
> Any help or advice appreciated
> Regards,
> Allan
>|||> Not only does this avoid ambiguous references, it helps improve
> performance too.
Is the performance gain documented any where?
/Sjang|||On Sep 3, 10:46 am, "Henrik Davidsen" <n...@.none.dk> wrote:
> > Not only does this avoid ambiguous references, it helps improve
> > performance too.
> Is the performance gain documented any where?
> /Sjang
You can see for yourself easily:
DECLARE @.i INT, @.SQL NVARCHAR(300)
SELECT @.i = 0
WHILE @.i < 10000 BEGIN
SET @.i = @.i + 1
SET @.SQL = 'CREATE PROCEDURE dbo.DummyProc' + CAST(@.i AS
NVARCHAR(10)) + ' AS RETURN 0'
EXEC sp_executesql @.SQL
END
GO
DECLARE @.i INT, @.j INT, @.d DATETIME, @.SQL NVARCHAR(300), @.SQL_to_run
NVARCHAR(300)
SELECT @.i = 0, @.j = 0, @.d = getdate()
WHILE @.j < 3 BEGIN
SET @.j = @.j + 1
IF @.j = 1 BEGIN
SET @.SQL = 'EXEC DummyProc'
END ELSE BEGIN
SET @.SQL = 'EXEC dbo.DummyProc'
END
WHILE @.i < 10000 BEGIN
SET @.i = @.i + 1
SET @.SQL_to_run = @.SQL + CAST(@.i AS NVARCHAR(10))
--PRINT @.SQL_to_run
IF @.j <3 BEGIN
EXEC sp_executesql @.SQL_to_run
END
END
SELECT DATEDIFF(ms, @.d, GEtdate()) as ms
SELECT @.i = 0, @.d = getdate()
END
GO
DECLARE @.i INT, @.SQL NVARCHAR(300)
SELECT @.i = 0
WHILE @.i < 10000 BEGIN
SET @.i = @.i + 1
SET @.SQL = 'DROP PROCEDURE dbo.DummyProc' + CAST(@.i AS
NVARCHAR(10))
EXEC sp_executesql @.SQL
END
GO
-- without dbo.
ms
--
3860
(1 row(s) affected)
-- with dbo
ms
--
640
(1 row(s) affected)
-- the overhead of running the loop
ms
--
46|||On Mon, 3 Sep 2007 17:46:30 +0200, "Henrik Davidsen" <none@.none.dk>
wrote:
>> Not only does this avoid ambiguous references, it helps improve
>> performance too.
>Is the performance gain documented any where?
Don't have a link handy, but it's mentioned in various white papers,
also just saw it mentioned in Kalen's "Storage Engine 2005" book, near
the middle, I'm too lazy to look up the page!
Per Kalen, in SQL2005 apparently it helps even a little more, if you
don't specify then there is more that SQL2005 does before it decides
you meant dbo. all along.
OK it's a small effect, but on a high-transaction system it might get
you a few TPS, and also there may be something of an increase in the
use of namespaces generally with 2005, so it might be a good practice
just on that basis.
Josh|||You *could* have had an open transaction in snapshot mode on 2005, ...
but it does sound more like corruption. Did you have any crashes
recently? Did you try running DBCC CHECKDB? Was this on a production
system? It's really a table and not a view with some kind of weird
user-sensitive parameters on it? Were you using the same login in
both cases? Was it repeatable - you could log off and log back in
again in both situations and see the same conflicting results?
I know it's moot now, but nobody likes that sort of anomaly.
J.
On Mon, 3 Sep 2007 07:00:00 -0700, Allan
<Allan@.discussions.microsoft.com> wrote:
>Hi all,
>Using vb6 ado connection I can see the record
>e.g. SELECT * FROM table where id=1234
>I will see the record
>but
>Using the same query on Enterprise Manager
>the same query results to nothing.
>Also
>SELECT COUNT(*) AS Expr1
>FROM table
>Result:
>vb6 query:1726 records
>Ent. Manager view: 18 records
>My questions is why Ent. Manager cannot see all the records
>I am using SQL Server 2000 standard edition
>The database itselt is nearly 21gb.
>Any help or advice appreciated
>Regards,
>Allan|||Hi J,
"JXStern" wrote:
> You *could* have had an open transaction in snapshot mode on 2005, ...
We are using SQL Server 2000 standard edition
> but it does sound more like corruption. Did you have any crashes
> recently?
No crashes
Did you try running DBCC CHECKDB?
No.
Was this on a production system?
We are very small company. Production and test system is the same.
It's really a table and not a view with some kind of weird user-sensitive
parameters on it?
Yes it is a table. The query was taken (copied and pasted) directly from vb6
source code that hasn't been changed for 3 years
Were you using the same login in both cases?
There is only one login "sa"
Was it repeatable - you could log off and log back in again in both
situations and see the same conflicting results?
We restarted the SQL server 2000. Same result.
Restarted Windows Server 2003 standard edition. Same result
> I know it's moot now, but nobody likes that sort of anomaly.
> J.
>
> On Mon, 3 Sep 2007 07:00:00 -0700, Allan
> <Allan@.discussions.microsoft.com> wrote:
> >Hi all,
> >
> >Using vb6 ado connection I can see the record
> >e.g. SELECT * FROM table where id=1234
> >I will see the record
> >
> >but
> >Using the same query on Enterprise Manager
> >the same query results to nothing.
> >
> >Also
> >SELECT COUNT(*) AS Expr1
> >FROM table
> >
> >Result:
> >vb6 query:1726 records
> >Ent. Manager view: 18 records
> >
> >My questions is why Ent. Manager cannot see all the records
> >
> >I am using SQL Server 2000 standard edition
> >The database itselt is nearly 21gb.
> >
> >Any help or advice appreciated
> >
> >Regards,
> >Allan
>

Hi Everyone

trying to login to ... SQL.Exception occurs

The result is SQL Server does not exist or access denied . . .

The code Im working with connection string is a forum fix from

http://p2p.wrox.com/topic.asp?TOPIC_ID37898

and the user account has been established.

<appSettings>

<add key="connection String" Value="server=(local)\MYSQLSERVERNAME; database=bids; Trusted_Connection=true"/>

</appSetting>

SQL Service Manager shows Server: SNOEMASTER

Services: MSSQLServerOLAPService

SQL Server Enterprise Manager indicates my SQL Server Group consists of

(local) (Windows NT)

and somewhere along the line I ran into something telling me to rename

(local) (windows NT) = MSSQLServer

Although when I do switch it over through the new registration wizard the connection fails. Stating MSSQLServer does not exist and come up with a error 1722 (RPC Server Unavailable) although in componet services it shows it running.

Initially I tried correctinig this because SQL SERVER repilcation does not support nicknames such as "." or (local) as server names and was given a message to

DELETE THE SQL SERVER REGISTRATION FOR THE SERVER AND REGISTER IT USING THE ACTUAL SERVER NAME MSSQLServer which component services confirmed in the properties tab "Dispaly Name" = MSSQLSERVER.

The problem seems to become two -fold because in the above connection string it maintains (local) as part of the string and instructs me to add on MYSQLSERVERNAME. ex. (local)\MYSQLSERVERNAME; database="bids"

Note: The database folder is named Bid.

Thanks for any input on this one anyone.

What you need to do is to replace MYSQLSERVERNAME with whatever your instance name is. If your SQL Server is the default instance, then user (local) or . directly rather than (local)\MSSQLSERVER or .\MSSQLSERVER

|||

Thank You!

i'm getting an access denied error but i can reset the user property from here. its better then the other errors I was recieving!

It clears up alot.! will make additional instance's of it in the future, one step at a time of course. I just installed SQL 2000 recently and want to make sure i have a solid understanding of what was happening.

http://192.168.1.65/Bid/default.aspx

icon_snowman

|||

After having reinstalled the Bid database and set the IUSR_SNOEMASTER permissions for the it from the SQL enterprise manager Bid \Properties\Security directory , i'm still recieving the double error . SQL server does not exist or access is denied..

I tried several combinations off the above resolution you mentioned but , not working yet. Will try Later.

On the second try I recieved a popup box to remember the passwaord and a confirmation that the user was added to the pool although checking the web.config file I realized I did not replace its original extension and had left it at web.txt to edit it.

Ohhhh is me

|||

System.Data.SqlClient.SqlException: Cannot open database requested in login 'bids'. Login fails. Login failed for user 'SNOEMASTER\IUSR_SNOEMASTER'. at System.Data.SqlClient.ConnectionPool.CreateConnection() at System.Data.SqlClient.ConnectionPool.UserCreateRequest() at System.Data.SqlClient.ConnectionPool.GetConnection(Boolean& isInTransaction) at System.Data.SqlClient.SqlConnectionPoolManager.GetPooledConnection(SqlConnectionString options, Boolean& isInTransaction) at System.Data.SqlClient.SqlConnection.Open() at Bid.Bid.Person.AddCustomer(String familyname, String givenname, String emailaddress, String password, String add1, String add2, String city, String state, String zip, String country) in C:\development\Wrox\6195\Bid\Components\Person.vb:line 169

---

Latest SQL.Exception recieved using

<appSettings>
<add key="ConnectionString" value="server=(local);database=bids;Trusted_Connection=true" />
</appSettings>

Anyone have any ideas or previous same problem.?

icon_snowman

|||From your latest error, your client is able to find the SQL server. The new problem is that you login account may not have login privilege to the database "bids". In order to login successfully, the login account must have login priviledge to the initial database (i.e. bids for your case).|||

In the above example the user (IUSER_SNOEMASTER) was left out of the connection string on purpose.

If I include the user in the connection string ( value="server=(local)\(IUSR_SNOEMASTER);databes=bids; . . . )then the error SQL Server does not exsist or access is denied to the user.

System.Data.SqlClient.SqlException: SQL Server does not exist or access denied. at System.Data.SqlClient.ConnectionPool.CreateConnection() at System.Data.SqlClient.ConnectionPool.UserCreateRequest() at System.Data.SqlClient.ConnectionPool.GetConnection(Boolean& isInTransaction

SQL Server Enterprise Manager:

Console Root|Microsoft SQL Servers|SQL Server Group|(local)(Windows NT)|Databases||bid|Users

In the right pane windows "Login Name" SNOEMASTER\ISUR_SNOEMASTER

"Database Access" status is Permit

If I use value="server=(local)\(SNOEMASTER\IUSR_SNOEMASTER); database=bids the following error occurs

Server Error in '/bid' Application.

---

Configuration Error

Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.
Parser Error Message: Access is denied: 'Bid'.
Source Error:

Line 256: <add assembly="System.EnterpriseServices, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/> Line 257: <add assembly="System.Web.Mobile, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/> Line 258: <add assembly="*"/> Line 259: </assemblies> Line 260:

Source File: c:\windows\microsoft.net\framework\v1.1.4322\Config\machine.config Line: 258
Assembly Load Trace: The following information can be helpful to determine why the assembly 'Bid' could not be loaded.

=== Pre-bind state information === LOG: DisplayName = Bid (Partial) LOG: Appbase = file:///C:/Bid LOG: Initial PrivatePath = bin Calling assembly : (Unknown). === LOG: Policy not being applied to reference at this time (private, custom, partial, or location-based assembly bind). LOG: Post-policy reference: Bid LOG: Attempting download of new URL file:///C:/WINDOWS/Microsoft.NET/Framework/v1.1.4322/Temporary ASP.NET Files/bid/4a7e3fd3/b5ae6ea7/Bid.DLL. LOG: Attempting download of new URL file:///C:/WINDOWS/Microsoft.NET/Framework/v1.1.4322/Temporary ASP.NET Files/bid/4a7e3fd3/b5ae6ea7/Bid/Bid.DLL. LOG: Attempting download of new URL file:///C:/Bid/bin/Bid.DLL. LOG: Policy not being applied to reference at this time (private, custom, partial, or location-based assembly bind). LOG: Post-policy reference: Bid, Version=1.0.885.31008, Culture=neutral, PublicKeyToken=null

---

Version Information: Microsoft .NET Framework Version:1.1.4322.2300; ASP.NET Version:1.1.4322.2300

Using the code below:

<appSettings>
<add key="ConnectionString" value="server=(local);database=bids;Trusted_Connection=true" />
</appSettings>

<appSettings>
<add key="ConnectionString" value="server=.\;database=bids;Trusted_Connection=true" />
</appSettings>

The following error is created:

System.Data.SqlClient.SqlException: Cannot open database requested in login 'bids'. Login fails. Login failed for user 'SNOEMASTER\IUSR_SNOEMASTER'. at System.Data.SqlClient.ConnectionPool.CreateConnection() at System.Data.SqlClient.ConnectionPool.UserCreateRequest() at System.Data.SqlClient.ConnectionPool.GetConnection(Boolean& isInTransaction

|||

server=(local)\(IUSR_SNOEMASTER);
Here (IUSR_SNOEMASTER) should be the instance name, NOT USER ACCOUNT. If your SQL Server is a default instance, then just use "(local)" or "." The client user account is determined by under which Windows account your client application is running if Windows authentication is used. From your last exemple, it looks like you have a default instance and your client app is running under 'SNOEMASTER\IUSR_SNOEMASTER'. So, you need to make sure this account has login priviledge to database "bids", as I said before.

|||

OK Have Login Working:

<appSettings>
<add key="ConnectionString" value="server=(local);database=Bid;Trusted_Connection=true" />
</appSettings>

The problem was that the database=bids was not allowing it to access the Bid folder.

Initially building the data base as prescribed in the http://p2p.wrox.com/toTOPIC_ID=37898 pic.asp?the query uses a plural version of the database "bids" so I continued with this in the connection string. Doesnt work. I read about two lines in the SQL Server Books Online stating that the database names are case sensitive and made the adjustment from bids=Bid and a slight adjustment in the permissions by :

Console Root|Microsoft SQL Servers|(local)(Windows NT)|Databases|bid

In the right-hand pane right clicked properties, highlight SNOEMASTER\IUSR_SNOEMASTER

Clicked Permissions and set settings as instructed http://p2p.wrox.com/toTOPIC_ID=37898 pic.asp?

Clicked Ok then clicked Properties on the bottom. Check that Public is selected.(For what ever reason mine was not. Possibly an over sight having reinstalled the database and permissions.)

Once again set the settings as instructed http://p2p.wrox.com/toTOPIC_ID=37898 pic.asp?and clicked apply and OK and everything seems to be running as it is supposed to.

Thank You Xinwei Hong your response helped me sort it out. Knowing better I should have immediately changed bids=Bid If you recall I made a note of this in my first post at the bottom of the name difference.

Help-me with this error

TITLE: Connect to Database Engine
--
Cannot connect to VEGAS-W-DV-02.
ADDITIONAL INFORMATION:
An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that
under the default settings SQL Server does not allow remote connections.
(provider: Named Pipes Provider, error: 40 - Could not open a connection to
SQL Server) (Microsoft SQL Server, Error: 233)
For help, click:
http://go.microsoft.com/fwlink?Prod...33&LinkId=20476
BUTTONS:
OK
--Can you ping the box?
Have you tried a different protocol, like TCP for instance?
Is your server even listening on named pipes?
Are you on the same subnet as the server?
Can you establish a client connection from the server itself?
*mike hodgson*
http://sqlnerd.blogspot.com
Retf wrote:

>TITLE: Connect to Database Engine
>--
>Cannot connect to VEGAS-W-DV-02.
>--
>ADDITIONAL INFORMATION:
>An error has occurred while establishing a connection to the server. When
>connecting to SQL Server 2005, this failure may be caused by the fact that
>under the default settings SQL Server does not allow remote connections.
>(provider: Named Pipes Provider, error: 40 - Could not open a connection to
>SQL Server) (Microsoft SQL Server, Error: 233)
>For help, click:
>http://go.microsoft.com/fwlink?Prod...33&LinkId=20476
>--
>BUTTONS:
>OK
>--
>
>|||yes
no, how I do this?
I dont know
yes
yes
Thanks to all...
"Mike Hodgson" <e1minst3r@.gmail.com> escreveu na mensagem news:%23OJa$NvcGHA
.3908@.TK2MSFTNGP04.phx.gbl...
Can you ping the box?
Have you tried a different protocol, like TCP for instance?
Is your server even listening on named pipes?
Are you on the same subnet as the server?
Can you establish a client connection from the server itself?
mike hodgson
http://sqlnerd.blogspot.com
Retf wrote:
TITLE: Connect to Database Engine
--
Cannot connect to VEGAS-W-DV-02.
ADDITIONAL INFORMATION:
An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that
under the default settings SQL Server does not allow remote connections.
(provider: Named Pipes Provider, error: 40 - Could not open a connection to
SQL Server) (Microsoft SQL Server, Error: 233)
For help, click:
http://go.microsoft.com/fwlink?Prod...33&LinkId=20476
BUTTONS:
OK
--|||I'm guessing that your server is not listening on any named pipes. You
can change the network protocols in the SQL Server 2005 Surface Area
Configuration tool (in Start | Programs | Microsoft SQL Server 2005 |
Configuration Tools) or in the "SQL Server 2005 Network Configuration"
section of the SQL Server Configuration Manager tool (also in Start |
Programs | Microsoft SQL Server 2005 | Configuration Tools).
Personally, I would turn on TCP, set the port to something other than
1433, make sure named pipes is turned off and always use TCP to connect
to the SQL instance (either by moving the TCP protocol above Named Pipes
in the "SQL Native Client Configuration" section of the SQL Server
Configuration Manager on the client machine (ie. protocol priority) or
by specifying the TCP protocol in the client connection when connecting
to the SQL instance (either in an alias or by explicitly specifying
"tcp:servername,portnum" for the server name in the connection strings)).
*mike hodgson*
http://sqlnerd.blogspot.com
retf wrote:
[vbcol=seagreen]
> yes
> no, how I do this?
> I dont know
> yes
> yes
> Thanks to all...
> "Mike Hodgson" <e1minst3r@.gmail.com <mailto:e1minst3r@.gmail.com>>
> escreveu na mensagem news:%23OJa$NvcGHA.3908@.TK2MSFTNGP04.phx.gbl...
> Can you ping the box?
> Have you tried a different protocol, like TCP for instance?
> Is your server even listening on named pipes?
> Are you on the same subnet as the server?
> Can you establish a client connection from the server itself?
> --
> *mike hodgson*
> http://sqlnerd.blogspot.com
>
> Retf wrote:
>|||Hi,
Thanks for help.
How I change the port 1433 to 1436 (ex)?
Thanks
"Mike Hodgson" <e1minst3r@.gmail.com> escreveu na mensagem news:u86$LbwcGHA.4
932@.TK2MSFTNGP03.phx.gbl...
I'm guessing that your server is not listening on any named pipes. You can
change the network protocols in the SQL Server 2005 Surface Area Configurati
on tool (in Start | Programs | Microsoft SQL Server 2005 | Configuration Too
ls) or in the "SQL Server 2005 Network Configuration" section of the SQL Ser
ver Configuration Manager tool (also in Start | Programs | Microsoft SQL Ser
ver 2005 | Configuration Tools).
Personally, I would turn on TCP, set the port to something other than 1433,
make sure named pipes is turned off and always use TCP to connect to the SQL
instance (either by moving the TCP protocol above Named Pipes in the "SQL N
ative Client Configuration" section of the SQL Server Configuration Manager
on the client machine (ie. protocol priority) or by specifying the TCP proto
col in the client connection when connecting to the SQL instance (either in
an alias or by explicitly specifying "tcp:servername,portnum" for the server
name in the connection strings)).
mike hodgson
http://sqlnerd.blogspot.com
retf wrote:
yes
no, how I do this?
I dont know
yes
yes
Thanks to all...
"Mike Hodgson" <e1minst3r@.gmail.com> escreveu na mensagem news:%23OJa$NvcGHA
.3908@.TK2MSFTNGP04.phx.gbl...
Can you ping the box?
Have you tried a different protocol, like TCP for instance?
Is your server even listening on named pipes?
Are you on the same subnet as the server?
Can you establish a client connection from the server itself?
mike hodgson
http://sqlnerd.blogspot.com
Retf wrote:
TITLE: Connect to Database Engine
--
Cannot connect to VEGAS-W-DV-02.
ADDITIONAL INFORMATION:
An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that
under the default settings SQL Server does not allow remote connections.
(provider: Named Pipes Provider, error: 40 - Could not open a connection to
SQL Server) (Microsoft SQL Server, Error: 233)
For help, click:
http://go.microsoft.com/fwlink?Prod...33&LinkId=20476
BUTTONS:
OK
--|||Other thing , If I have firewall (basic firewam of windows 2003) I need open
this port, ane any else more?
"Mike Hodgson" <e1minst3r@.gmail.com> escreveu na mensagem news:u86$LbwcGHA.4
932@.TK2MSFTNGP03.phx.gbl...
I'm guessing that your server is not listening on any named pipes. You can
change the network protocols in the SQL Server 2005 Surface Area Configurati
on tool (in Start | Programs | Microsoft SQL Server 2005 | Configuration Too
ls) or in the "SQL Server 2005 Network Configuration" section of the SQL Ser
ver Configuration Manager tool (also in Start | Programs | Microsoft SQL Ser
ver 2005 | Configuration Tools).
Personally, I would turn on TCP, set the port to something other than 1433,
make sure named pipes is turned off and always use TCP to connect to the SQL
instance (either by moving the TCP protocol above Named Pipes in the "SQL N
ative Client Configuration" section of the SQL Server Configuration Manager
on the client machine (ie. protocol priority) or by specifying the TCP proto
col in the client connection when connecting to the SQL instance (either in
an alias or by explicitly specifying "tcp:servername,portnum" for the server
name in the connection strings)).
mike hodgson
http://sqlnerd.blogspot.com
retf wrote:
yes
no, how I do this?
I dont know
yes
yes
Thanks to all...
"Mike Hodgson" <e1minst3r@.gmail.com> escreveu na mensagem news:%23OJa$NvcGHA
.3908@.TK2MSFTNGP04.phx.gbl...
Can you ping the box?
Have you tried a different protocol, like TCP for instance?
Is your server even listening on named pipes?
Are you on the same subnet as the server?
Can you establish a client connection from the server itself?
mike hodgson
http://sqlnerd.blogspot.com
Retf wrote:
TITLE: Connect to Database Engine
--
Cannot connect to VEGAS-W-DV-02.
ADDITIONAL INFORMATION:
An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that
under the default settings SQL Server does not allow remote connections.
(provider: Named Pipes Provider, error: 40 - Could not open a connection to
SQL Server) (Microsoft SQL Server, Error: 233)
For help, click:
http://go.microsoft.com/fwlink?Prod...33&LinkId=20476
BUTTONS:
OK
--|||Use the SQL Server Configuration Manager mentioned in my previous reply
(SQL Server 2005 Network Configuration section).
*mike hodgson*
http://sqlnerd.blogspot.com
Retf wrote:
[vbcol=seagreen]
> Hi,
> Thanks for help.
> How I change the port 1433 to 1436 (ex)?
> Thanks
> "Mike Hodgson" <e1minst3r@.gmail.com <mailto:e1minst3r@.gmail.com>>
> escreveu na mensagem news:u86$LbwcGHA.4932@.TK2MSFTNGP03.phx.gbl...
> I'm guessing that your server is not listening on any named
> pipes. You can change the network protocols in the SQL Server
> 2005 Surface Area Configuration tool (in Start | Programs |
> Microsoft SQL Server 2005 | Configuration Tools) or in the "SQL
> Server 2005 Network Configuration" section of the SQL Server
> Configuration Manager tool (also in Start | Programs | Microsoft
> SQL Server 2005 | Configuration Tools).
> Personally, I would turn on TCP, set the port to something other
> than 1433, make sure named pipes is turned off and always use TCP
> to connect to the SQL instance (either by moving the TCP protocol
> above Named Pipes in the "SQL Native Client Configuration" section
> of the SQL Server Configuration Manager on the client machine (ie.
> protocol priority) or by specifying the TCP protocol in the client
> connection when connecting to the SQL instance (either in an alias
> or by explicitly specifying "tcp:servername,portnum" for the
> server name in the connection strings)).
> --
> *mike hodgson*
> http://sqlnerd.blogspot.com
>
> retf wrote:
>|||That's the only incoming port you'll need to open (assuming you don't
need the SQL Server Browser service, which you shouldn't - you may as
well disable that browser service as you won't need it). SQL Server
opens an outgoing connection back to the client, I think, using a high
port but most firewalls allow all outgoing connections by default. And,
in fact, I think the Windows firewall only deals with incoming traffic
so I don't think there's even an option to mess around with outbound ports.
*mike hodgson*
http://sqlnerd.blogspot.com
Retf wrote:
[vbcol=seagreen]
> Other thing , If I have firewall (basic firewam of windows 2003) I
> need open this port, ane any else more?
>
> "Mike Hodgson" <e1minst3r@.gmail.com <mailto:e1minst3r@.gmail.com>>
> escreveu na mensagem news:u86$LbwcGHA.4932@.TK2MSFTNGP03.phx.gbl...
> I'm guessing that your server is not listening on any named
> pipes. You can change the network protocols in the SQL Server
> 2005 Surface Area Configuration tool (in Start | Programs |
> Microsoft SQL Server 2005 | Configuration Tools) or in the "SQL
> Server 2005 Network Configuration" section of the SQL Server
> Configuration Manager tool (also in Start | Programs | Microsoft
> SQL Server 2005 | Configuration Tools).
> Personally, I would turn on TCP, set the port to something other
> than 1433, make sure named pipes is turned off and always use TCP
> to connect to the SQL instance (either by moving the TCP protocol
> above Named Pipes in the "SQL Native Client Configuration" section
> of the SQL Server Configuration Manager on the client machine (ie.
> protocol priority) or by specifying the TCP protocol in the client
> connection when connecting to the SQL instance (either in an alias
> or by explicitly specifying "tcp:servername,portnum" for the
> server name in the connection strings)).
> --
> *mike hodgson*
> http://sqlnerd.blogspot.com
>
> retf wrote:
>|||Hi,
You may also want to check on client machine to make sure both TCPIP and
named pipes are enabled via client network utility or configuration
manager. Port configuration is only valid for TCPIP protocol. Named pipies
is usually based on netbios connection via port 135/138/139 etc.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.

Help?

sorry if im off topic.

I was trying to home network with windows XP, in order for me to shear Internet connection with other computers in the house. I have cable modem and its using USB port.. which makes my Ethernet adopter free.

I've tired contacting the Ethernet adapter to each computer (two computer) using a cat5 Ethernet cord.. but the local area connection show's unplugged..? there for i can't bridge
the computers?

am i missing something?You will need a cross-over ethernet cable to connect 2 PCs directly. You can use straight Cat5 cables if you have an ethernet hub/switch.

HELP: SQL SERVER CONNECTION TIMED OUT

can someone please help me solve this problem.

i'm experiencing sql server error: the database controller returned an error status of sql server connection timed out.

i need some help badly.

thanksWhat is the code doing when it times out? Frequently this is a problem with running a long script that exceeds the timeout. What is the complete text of the exception message?

Don|||>>what is the code doing when it times out?
- the code is posting accounting transactions coming from our accounting system.

>>the complete error message?
- the database controller returned an error status of sql server connection timed out

thanks|||Regarding the complete error message, I mean the full page of stuff that you get by default in ASP.NET, including the full error message, stack trace, and everything else that probably looks useless on the page.

That said, how long is the process taking? You may have to extend the SQL connection time out and perhaps the page time out.

Don

Help: SQL 2000 connection error(.NET 2.0, VS 2005)

Moderated by XIII, please use a normal font size for better readability:

for some reason, my web application can not connect to my SQL 2000

my application is based on .net 2.0 (IIS 5.1) using vs 2005workstation does not install any sql serversql 2000 locates at the remote server.the sql server can be connected via vs environment (data connnection), therefore, i think the connection string, server name and instance name is correcti have tried all the solution i can find online, but it is not workingLocalSQLServer connection string has been removed in GobalSettingalso remove all default connection string in web.config (<clear />)aspnet_regsql can register the sql 2000 db successfulvs 2005 can access and display the data in sql 2000 quite wellhas been reboot lots of times.still bug out

any body have any idea? thanks, it already costs me the whole day

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

Can you telnet to the remote server (test TCP/IP)? And how about "net use\\servername\IPC$" the remote server (test Named pipe)? You can take a look at this post:

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

|||

Thank Jay,

I can telnet to the remote server. Actually, I think the connection to the remote server is correct (in VS 2005 environment the data can be display quite well), the only problem is .NET 2.0 always think the remote server is SQL 2005. I have removed the localSQLServer connection string in web.config file (<clear />) but still not working.

|||

Then how about force to use TCP/IP to connect? You can do this by usingtcp:myinstance,portas Data Source, where port is the tcp port used the SQL instance service. Actually there should be no difference when connect to SQL2005 or SQL2000, you can take a look at this article which shows how to place membership on SQL2000:

http://weblogs.asp.net/scottgu/archive/2005/08/25/423703.aspx

Help: I can open my database in Management Studio, but can't connect it in Integration Services

Received error tip:

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)

I'm using the Evaluation Edition of SQL Server 2005, Windows XP SP2 Home Edition.

I have disabled the firewall.

You need to enable remote connections:

http://www.sqlserver2005.de/Sharedfiles/remoteconnection.jpg

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||

Yes, I have enable remote connections, but still wrong.

Can the Home Edition of Windows XP support SQL Server?

|||

Hi, only the developer edition and the express edition are supposed to work on Windows XP Home (as of the offical system requirements, didn′t tested that out yet). Let me hear some feedback if that worked for you.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||I have installed SQL Server Evaluation Edition on Windows XP Home Edition. It can work. In the Management Studio, the database can be opened and executed. The only one problem is that in the reporting services, the database can't be connetcted.