Can only log into a MSDE ODBC Connection as Administrator

When trying to log into a ODBC connection as a power user on a network we
receive the following error:
Connection failed:
SQLState:'01000'
SQL Server Error: 53
[Microsoft][ODBC SQL Server Driver][DBNET]ConnectionOpen (/cibbect ()),
Connection failed:
SQLState:'08001'
SQL server Error:178
[microsoft][odbc sql server driver][dbnetlib]sql server does not exist or
access denied.
Change the user to Administrator and they are able to login.
Did you add logins for other users who aren't members of the
local admin group on the box where MSDE is installed? It
sounds like they may not have logins setup in MSDE.
By default, members of the local admins group will have
access. For other users, you need to add logins.
-Sue
On Thu, 27 Oct 2005 19:25:02 -0700, "bw"
<bw@.discussions.microsoft.com> wrote:

>When trying to log into a ODBC connection as a power user on a network we
>receive the following error:
>Connection failed:
>SQLState:'01000'
>SQL Server Error: 53
>[Microsoft][ODBC SQL Server Driver][DBNET]ConnectionOpen (/cibbect ()),
>Connection failed:
>SQLState:'08001'
>SQL server Error:178
>[microsoft][odbc sql server driver][dbnetlib]sql server does not exist or
>access denied.
>Change the user to Administrator and they are able to login.
|||Sue,
Yes I did add them to the system as a user. Then created an MSDE Group.
The Group has the following rights:
GROUP EVERYONE - Read to Program Files
MSDE GROUP DOES NOT HAVE FULL CONTROL, NO DEL FOLDERS, TAKE OWNERSHIP,
CREATE FOLDER OR CHANGE PERMISSION TO THE MSDE/SYSTEM FOLDER OR MSDE/SERVER
FOLDER
USING A NOTEBOOK WITH ENTERPRISE MANAGER WE HAD GIVE THE MSDE GROUP -
PUBLIC, DB_WRITER, DB_READER AND DB_BACKUP OPERATOR
APPLIED SERVICE PACK 2 TO THE SYSTEM THAT IS RUNNING THE MSDE SERVICE AND
NOW THE SYSTEM RUNNING ENTERPRISE MANAGER GETS THE FOLLOWING ERROR WHEN
ATTEMPTING TO CONNECT TO THE SYSTEM MAP DRIVE THAT HAS THE MSDE INSTALLED WE
GET THE FOLLOWING ERROR:
AN ERROR OCCURRED WHILE RECONNECTING TO A LOCAL CONNECTION . MICROSOFT
WINDOWN NETWORK. THE LOCAL DEVICE NAME IS ALREADY IN USE.
CANNOT CONNECT THE ENTERPRISE MANAGER TO THE MSDE DATABASE NOW.
I APPRECIATE YOUR HELP.
"Sue Hoegemeier" wrote:

> Did you add logins for other users who aren't members of the
> local admin group on the box where MSDE is installed? It
> sounds like they may not have logins setup in MSDE.
> By default, members of the local admins group will have
> access. For other users, you need to add logins.
> -Sue
> On Thu, 27 Oct 2005 19:25:02 -0700, "bw"
> <bw@.discussions.microsoft.com> wrote:
>
>
|||No need to yell. Using caps is considered yelling in
newsgroups.
By adding the users as logins in SQL Server, that doesn't
have anything to do with adding them to groups on the box
where MSDE is running.
How exactly are you trying to connect? I think something is
missing here as mapping drives is not necessary, giving
users full control on MSDE folders, etc is generally not
necessary either.
-Sue
On Fri, 28 Oct 2005 15:13:03 -0700, "bw"
<bw@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Sue,
>Yes I did add them to the system as a user. Then created an MSDE Group.
>The Group has the following rights:
> GROUP EVERYONE - Read to Program Files
> MSDE GROUP DOES NOT HAVE FULL CONTROL, NO DEL FOLDERS, TAKE OWNERSHIP,
>CREATE FOLDER OR CHANGE PERMISSION TO THE MSDE/SYSTEM FOLDER OR MSDE/SERVER
>FOLDER
>USING A NOTEBOOK WITH ENTERPRISE MANAGER WE HAD GIVE THE MSDE GROUP -
>PUBLIC, DB_WRITER, DB_READER AND DB_BACKUP OPERATOR
>APPLIED SERVICE PACK 2 TO THE SYSTEM THAT IS RUNNING THE MSDE SERVICE AND
>NOW THE SYSTEM RUNNING ENTERPRISE MANAGER GETS THE FOLLOWING ERROR WHEN
>ATTEMPTING TO CONNECT TO THE SYSTEM MAP DRIVE THAT HAS THE MSDE INSTALLED WE
>GET THE FOLLOWING ERROR:
>AN ERROR OCCURRED WHILE RECONNECTING TO A LOCAL CONNECTION . MICROSOFT
>WINDOWN NETWORK. THE LOCAL DEVICE NAME IS ALREADY IN USE.
>CANNOT CONNECT THE ENTERPRISE MANAGER TO THE MSDE DATABASE NOW.
>I APPRECIATE YOUR HELP.
>
>"Sue Hoegemeier" wrote:
|||I apologize I did not know that caps were yelling, I am happy for the help.
Since we are testing this on our network, I am logging into our domain where
both systems reside. The MSDE is running on an XP workstation and we have
other workstations attempting to log into it. When we go into the ODBC setup
we can see the MSDE instance but cannot log on to it.
Bonnie
"Sue Hoegemeier" wrote:

> No need to yell. Using caps is considered yelling in
> newsgroups.
> By adding the users as logins in SQL Server, that doesn't
> have anything to do with adding them to groups on the box
> where MSDE is running.
> How exactly are you trying to connect? I think something is
> missing here as mapping drives is not necessary, giving
> users full control on MSDE folders, etc is generally not
> necessary either.
> -Sue
> On Fri, 28 Oct 2005 15:13:03 -0700, "bw"
> <bw@.discussions.microsoft.com> wrote:
>
>
|||No problem...figured you just didn't know about the caps
thing. Anyway, check the event logs on the XP workstation
where MSDE is running to see if there are any security
errors. Make sure the MSDE instance is listening on TCP/IP
and that the clients are configure to connect with TCP/IP.
You would probably want to start by running through the
following article - it's long but connectivity issues aren't
real easy to resolve as it can be so many different things.
Potential causes of the "SQL Server does not exist or access
denied" error message
http://support.microsoft.com/?id=328306
-Sue
On Mon, 31 Oct 2005 07:01:07 -0800, "bw"
<bw@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>I apologize I did not know that caps were yelling, I am happy for the help.
>Since we are testing this on our network, I am logging into our domain where
>both systems reside. The MSDE is running on an XP workstation and we have
>other workstations attempting to log into it. When we go into the ODBC setup
>we can see the MSDE instance but cannot log on to it.
>Bonnie
>
>"Sue Hoegemeier" wrote:
|||Sue,
We found out we were using the wrong port for MSDE. MSDE was listening on
Port 1143. We were using the SQL default of 1443 Thank you for your help. I
have another question now that this one is resolved. I'll start a new
thread. Thank you again for your help.
"Sue Hoegemeier" wrote:

> No problem...figured you just didn't know about the caps
> thing. Anyway, check the event logs on the XP workstation
> where MSDE is running to see if there are any security
> errors. Make sure the MSDE instance is listening on TCP/IP
> and that the clients are configure to connect with TCP/IP.
> You would probably want to start by running through the
> following article - it's long but connectivity issues aren't
> real easy to resolve as it can be so many different things.
> Potential causes of the "SQL Server does not exist or access
> denied" error message
> http://support.microsoft.com/?id=328306
> -Sue
> On Mon, 31 Oct 2005 07:01:07 -0800, "bw"
> <bw@.discussions.microsoft.com> wrote:
>
>