Can't get groups to work

Hi,
1. I have an Access ADP on SQL2000, uaing Windows users and groups..
2. Individual users with granted permissions work OK.
3. However, if I drop the individual users and try to uses the Windows
groups which contain them with same permissions granted, the app cannot make
connection.
4. Have revoked logins, re-added logins, database grants, and permissions,
but to no avail.
Any suggestions on what to look for?
Thanks.
AlanCan you make successfull connections from Query Analyser or OSQL.exe based
upon the group ?
Is the group a local group or domain based group?
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Kevin,
Thanks for your reply.
1. I can't connect with query analyzer, logging on to users's machine with
user's login but only his group login and group database access existing in
SQLServer.
2. User's group is a Universal domain group.
Using SQL@.000.
Useer: WinXP
OS: Win2000Server
DB Machine: Win2000 Server.
Regards,
Alan
"Kevin McDonnell [MSFT]" <kevmc@.online.microsoft.com> wrote in message
news:0WvCdgfxEHA.3640@.cpmsftngxa10.phx.gbl...
> Can you make successfull connections from Query Analyser or OSQL.exe based
> upon the group ?
> Is the group a local group or domain based group?
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>|||Ah. The problem may be the Universal Group.. There was a fix for this. Try
this update.
825042 FIX: SQL Server Jobs That Are Owned by Non-sysadmin Users May Not
Start
http://support.microsoft.com/?id=825042
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Kevin,
Thanks for your reply.
This sounds like it applies to jobs only, not regular database accesss. Do
you know if it applies to database access as well.
I'd like to avoid hotfixes on client's computers as well, plus I don't know
if they have installed required Win2000 SP4.
Thanks.
Alan
"Kevin McDonnell [MSFT]" <kevmc@.online.microsoft.com> wrote in message
news:7AkfzfpxEHA.768@.cpmsftngxa10.phx.gbl...
> Ah. The problem may be the Universal Group.. There was a fix for this.
Try
> this update.
> 825042 FIX: SQL Server Jobs That Are Owned by Non-sysadmin Users May Not
> Start
> http://support.microsoft.com/?id=825042
>
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>|||Its' been some time since I did testing, but I don't think we enumerate
Universal Groups only Domain Global Groups.
Try;
xp_logininf groupname
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||"Kevin McDonnell [MSFT]" <kevmc@.online.microsoft.com> wrote in message
news:0mIdcZrxEHA.3984@.cpmsftngxa10.phx.gbl...
> Its' been some time since I did testing, but I don't think we enumerate
> Universal Groups only Domain Global Groups.
> Try;
> xp_logininf groupname
Kevin,
Thanks again for your reply.
I've asked net admin to recreate groups as global, not universal.
In meantime, I've put results of xp_logininfo below.
1. xp_login 'GroupAccountName', 'members': properly displays list of members
2. xp_login 'GroupMemberAccountName', 'all': gives NULL RECORD!!
3. If, as a test, I add the GroupMemberAccountName to SQL logins as new
separate login IndividualUserName and do
xp_login 'IndividualUserName', 'all' :
then displays individual user's record, but no additional record for group
path.
CONCLUSION?
--
Does above mean that somewhere no connection is being made in SQLServer
between the group and the individual member?
BOL on xp_logininfo: If account_name is a valid Windows NT account but that
account does not have permission to access SQL Server, an empty result set
is returned.
Thanks very much.
Alan|||I know that Domain Local Groups won't work correctly for jobs and I
couldn't remember the results with Universal Groups.
Another question is , Is SQL Server in the same Domain that the users
groups are defined in?
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Kevin,
It's in a separate domain.
Alan
"Kevin McDonnell [MSFT]" <kevmc@.online.microsoft.com> wrote in message
news:0Jw0SF1xEHA.3984@.cpmsftngxa10.phx.gbl...
> I know that Domain Local Groups won't work correctly for jobs and I
> couldn't remember the results with Universal Groups.
> Another question is , Is SQL Server in the same Domain that the users
> groups are defined in?
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>

Can't connect to SQl Server 2005 with sa Login

Hello,

I recently installed SQL2005 and SQL2000. I only created SA login permissions with Admin access to the database (There are no Windows Users that have access).

I then installed SQL2000 and it overwrote the "mixed connection mode" . whenever I try to connect with the sa login I get the following error

Login failed for user 'sa'. The user is not associated with a trusted SQL Server connection. (Microsoft SQL Server, Error: 18452)

The problem is explained in a fix http://support.microsoft.com/kb/269587

The only problem is that the fix requires access rights that I don't have. My only logins are "BuiltIn\Users" that have public access rights and then a "sa" login (that doesn't work) that has Admin rights within the db engine.

So my question is... Can I create an sysadmin account with windows authentication (for a normal Windows Admin Account) without having the proper rights within the database engine?

-Tom

I would recommend taking a look to the followign post:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1353448&SiteID=1

If the information there doesn't help you, please let us know, we will be glad to help.

Thanks,

-Raul Garcia

SDE/T

SQL Server Engine

Can't connect from Server A to B but B to A

I have two machines with SQL2000 on both machines.
Machine A is a member of the domain, Machine B is in a workgroup with
the same name as the domain.
Using Enterprise manager I can connect from Machine B and manage the
SQL server on machine A.
When trying to connect from Machine A to manage SQL server on Machine
B I get an error 'SQL Server does not exist or access denied'.
I have double checked username/password several times.
Client Network Utility are set to TCP/IP and Named Pipes on both
machines.
Ping works fines. I can also access shared folders from A to B and
vice versa.
What else could be the problem?Can you connect via SQL Login.
If you're connecting via Windows Login, be sure the account has the same
name and password on both side. Also, check to see if BUILTIN\<account> is
allowed access on serverB. If not, take a look at 'sp_grantlogin' in book
online and give it access.
-oj
"Tosch" <tosch_nospam@.swissonline.ch> wrote in message
news:9hbl51pm68gln1gmqp2ckpk5h1d7a5q7r4@.
4ax.com...
>I have two machines with SQL2000 on both machines.
> Machine A is a member of the domain, Machine B is in a workgroup with
> the same name as the domain.
> Using Enterprise manager I can connect from Machine B and manage the
> SQL server on machine A.
> When trying to connect from Machine A to manage SQL server on Machine
> B I get an error 'SQL Server does not exist or access denied'.
> I have double checked username/password several times.
> Client Network Utility are set to TCP/IP and Named Pipes on both
> machines.
> Ping works fines. I can also access shared folders from A to B and
> vice versa.
> What else could be the problem?
>|||I have tried connecting with SQL Login, no luck. I even tried sa and I
could not connect.
On Mon, 11 Apr 2005 13:54:05 -0700, "oj" <nospam_ojngo@.home.com>
wrote:

>Can you connect via SQL Login.
>If you're connecting via Windows Login, be sure the account has the same
>name and password on both side. Also, check to see if BUILTIN\<account> is
>allowed access on serverB. If not, take a look at 'sp_grantlogin' in book
>online and give it access.|||Hi
What happens if you try to do a telnet to server B using the port specified
in server B's TCP/IP Clinet configuration? By doing this, you can determine
if server B listen's properly on the correct port.
Regards
Steen
Tosch wrote:[vbcol=seagreen]
> I have tried connecting with SQL Login, no luck. I even tried sa and I
> could not connect.
>
> On Mon, 11 Apr 2005 13:54:05 -0700, "oj" <nospam_ojngo@.home.com>
> wrote:
>

Can't connect from Server A to B but B to A

I have two machines with SQL2000 on both machines.
Machine A is a member of the domain, Machine B is in a workgroup with
the same name as the domain.
Using Enterprise manager I can connect from Machine B and manage the
SQL server on machine A.
When trying to connect from Machine A to manage SQL server on Machine
B I get an error 'SQL Server does not exist or access denied'.
I have double checked username/password several times.
Client Network Utility are set to TCP/IP and Named Pipes on both
machines.
Ping works fines. I can also access shared folders from A to B and
vice versa.
What else could be the problem?
Can you connect via SQL Login.
If you're connecting via Windows Login, be sure the account has the same
name and password on both side. Also, check to see if BUILTIN\<account> is
allowed access on serverB. If not, take a look at 'sp_grantlogin' in book
online and give it access.
-oj
"Tosch" <tosch_nospam@.swissonline.ch> wrote in message
news:9hbl51pm68gln1gmqp2ckpk5h1d7a5q7r4@.4ax.com...
>I have two machines with SQL2000 on both machines.
> Machine A is a member of the domain, Machine B is in a workgroup with
> the same name as the domain.
> Using Enterprise manager I can connect from Machine B and manage the
> SQL server on machine A.
> When trying to connect from Machine A to manage SQL server on Machine
> B I get an error 'SQL Server does not exist or access denied'.
> I have double checked username/password several times.
> Client Network Utility are set to TCP/IP and Named Pipes on both
> machines.
> Ping works fines. I can also access shared folders from A to B and
> vice versa.
> What else could be the problem?
>
|||I have tried connecting with SQL Login, no luck. I even tried sa and I
could not connect.
On Mon, 11 Apr 2005 13:54:05 -0700, "oj" <nospam_ojngo@.home.com>
wrote:

>Can you connect via SQL Login.
>If you're connecting via Windows Login, be sure the account has the same
>name and password on both side. Also, check to see if BUILTIN\<account> is
>allowed access on serverB. If not, take a look at 'sp_grantlogin' in book
>online and give it access.
|||Hi
What happens if you try to do a telnet to server B using the port specified
in server B's TCP/IP Clinet configuration? By doing this, you can determine
if server B listen's properly on the correct port.
Regards
Steen
Tosch wrote:[vbcol=seagreen]
> I have tried connecting with SQL Login, no luck. I even tried sa and I
> could not connect.
>
> On Mon, 11 Apr 2005 13:54:05 -0700, "oj" <nospam_ojngo@.home.com>
> wrote:

Can't connect from Server A to B but B to A

I have two machines with SQL2000 on both machines.
Machine A is a member of the domain, Machine B is in a workgroup with
the same name as the domain.
Using Enterprise manager I can connect from Machine B and manage the
SQL server on machine A.
When trying to connect from Machine A to manage SQL server on Machine
B I get an error 'SQL Server does not exist or access denied'.
I have double checked username/password several times.
Client Network Utility are set to TCP/IP and Named Pipes on both
machines.
Ping works fines. I can also access shared folders from A to B and
vice versa.
What else could be the problem?Can you connect via SQL Login.
If you're connecting via Windows Login, be sure the account has the same
name and password on both side. Also, check to see if BUILTIN\<account> is
allowed access on serverB. If not, take a look at 'sp_grantlogin' in book
online and give it access.
--
-oj
"Tosch" <tosch_nospam@.swissonline.ch> wrote in message
news:9hbl51pm68gln1gmqp2ckpk5h1d7a5q7r4@.4ax.com...
>I have two machines with SQL2000 on both machines.
> Machine A is a member of the domain, Machine B is in a workgroup with
> the same name as the domain.
> Using Enterprise manager I can connect from Machine B and manage the
> SQL server on machine A.
> When trying to connect from Machine A to manage SQL server on Machine
> B I get an error 'SQL Server does not exist or access denied'.
> I have double checked username/password several times.
> Client Network Utility are set to TCP/IP and Named Pipes on both
> machines.
> Ping works fines. I can also access shared folders from A to B and
> vice versa.
> What else could be the problem?
>|||I have tried connecting with SQL Login, no luck. I even tried sa and I
could not connect.
On Mon, 11 Apr 2005 13:54:05 -0700, "oj" <nospam_ojngo@.home.com>
wrote:
>Can you connect via SQL Login.
>If you're connecting via Windows Login, be sure the account has the same
>name and password on both side. Also, check to see if BUILTIN\<account> is
>allowed access on serverB. If not, take a look at 'sp_grantlogin' in book
>online and give it access.|||Hi
What happens if you try to do a telnet to server B using the port specified
in server B's TCP/IP Clinet configuration? By doing this, you can determine
if server B listen's properly on the correct port.
Regards
Steen
Tosch wrote:
> I have tried connecting with SQL Login, no luck. I even tried sa and I
> could not connect.
>
> On Mon, 11 Apr 2005 13:54:05 -0700, "oj" <nospam_ojngo@.home.com>
> wrote:
>> Can you connect via SQL Login.
>> If you're connecting via Windows Login, be sure the account has the
>> same name and password on both side. Also, check to see if
>> BUILTIN\<account> is allowed access on serverB. If not, take a look
>> at 'sp_grantlogin' in book online and give it access.

Can't connect from ASP.Net 2.0 to SQL2000 after installing SQL2005

Hey guys,
I have a web application in ASP.Net 2.0 that needs to connect to a local
SQL2000 DB. After I installed SQL2005 this web app stopped working. I get
the following inner exception:
{"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)"}
So after unsuccessfully googling I'm at least pretty sure about the
following: My web app thinks it's talking to a SQL2005 server. That one by
default uses shared memory when local. I think SQL2000 uses TCP/IP.
Who can tell me what I have to do so that my ASP.Net 2.0 web app properly
connects to SQL2000? Among the ideas on Google there were cliconfg.exe,
using <clear /> in the <connectionStrings> area in web.config and a couple
more. But none of them worked.
Thanks a lot, ChristophI'm having a very similar error, only mine connects locally but not remotely.
I was able to change the error slightly by putting the referencing the
database by domain and db, myMachine/myDB.
If it helps I looked at my log and it gave an error of 17187 which seems to
be a file in use, full disk, or low memory. Still researching. If I find it
I'll let you know. If you find the answer would you please post it so I can
try it too?
--
---
Magic is not in the hands of the magician but in the mind of the audience.
Animadverto est verus
"Christoph Wienands" wrote:
> Hey guys,
> I have a web application in ASP.Net 2.0 that needs to connect to a local
> SQL2000 DB. After I installed SQL2005 this web app stopped working. I get
> the following inner exception:
> {"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)"}
> So after unsuccessfully googling I'm at least pretty sure about the
> following: My web app thinks it's talking to a SQL2005 server. That one by
> default uses shared memory when local. I think SQL2000 uses TCP/IP.
> Who can tell me what I have to do so that my ASP.Net 2.0 web app properly
> connects to SQL2000? Among the ideas on Google there were cliconfg.exe,
> using <clear /> in the <connectionStrings> area in web.config and a couple
> more. But none of them worked.
> Thanks a lot, Christoph
>
>