Error with Logins into SQL 2K

Hello,
I need some advice...
I am running SQL Server 2000... I've installed a new instance of this on a
new
server (to migrate from server1 to server2).
On server1, i have a group set up (domain/SQLGroup)...
On server2, i have the exact same group set up... unfortunately all the
users in this group doesn't get recognized by my new sql installation. I
get the error above (SQL Error 18456, State '28000') when they try and
login. (Access, VB progs, etc)...
I can change permissions for all the users in this group to have "Domain
Admins", but obviously i don't want to do that... by doing this though, all
access works as before...
SP4 is installed on server2, but not on server1...
Server1 is the Domain Controller...running sbs2000 (windows 2000 server).
Server2 is just windows 2003, and is dedicated to sql server 2000...
Does anyone have any suggestions on how to proceed with this?
Thanks.Hi
In my opinion the real problem seems to be with an ODBC connection
Does itt succeeds with NT authentication if and only if the user is an
administrator ?
"RL Tech" <tech_support@.nospamuls.com> wrote in message
news:%23b1DfodUGHA.1688@.TK2MSFTNGP11.phx.gbl...
> Hello,
> I need some advice...
> I am running SQL Server 2000... I've installed a new instance of this on a
> new
> server (to migrate from server1 to server2).
> On server1, i have a group set up (domain/SQLGroup)...
> On server2, i have the exact same group set up... unfortunately all the
> users in this group doesn't get recognized by my new sql installation. I
> get the error above (SQL Error 18456, State '28000') when they try and
> login. (Access, VB progs, etc)...
> I can change permissions for all the users in this group to have "Domain
> Admins", but obviously i don't want to do that... by doing this though,
> all
> access works as before...
> SP4 is installed on server2, but not on server1...
> Server1 is the Domain Controller...running sbs2000 (windows 2000 server).
> Server2 is just windows 2003, and is dedicated to sql server 2000...
> Does anyone have any suggestions on how to proceed with this?
> Thanks.
>
>|||This would help.
http://support.microsoft.com/kb/298897
-oj
"RL Tech" <tech_support@.nospamuls.com> wrote in message
news:%23b1DfodUGHA.1688@.TK2MSFTNGP11.phx.gbl...
> Hello,
> I need some advice...
> I am running SQL Server 2000... I've installed a new instance of this on a
> new
> server (to migrate from server1 to server2).
> On server1, i have a group set up (domain/SQLGroup)...
> On server2, i have the exact same group set up... unfortunately all the
> users in this group doesn't get recognized by my new sql installation. I
> get the error above (SQL Error 18456, State '28000') when they try and
> login. (Access, VB progs, etc)...
> I can change permissions for all the users in this group to have "Domain
> Admins", but obviously i don't want to do that... by doing this though,
> all
> access works as before...
> SP4 is installed on server2, but not on server1...
> Server1 is the Domain Controller...running sbs2000 (windows 2000 server).
> Server2 is just windows 2003, and is dedicated to sql server 2000...
> Does anyone have any suggestions on how to proceed with this?
> Thanks.
>
>|||On server1, NT (windows) authentication works with the group SQLGroup
(whether they are admin or not)... as long as they are part of SQLGroup,
they will be fine.
On server2, NT (windows) authentication only works with Admin users (thus by
adding all the users in SQLGroup to Domain Admins, they would work)... Which
i obviously don't want to do.
Both are mixed mode authentication...
ODBC has worked from the moment i set up that connection with that group...
In fact, it still works fine when i authenticate non-windows usernames...
Do i need to make server2 a Domain controller?
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:eeAlh4jUGHA.5884@.TK2MSFTNGP14.phx.gbl...
> Hi
> In my opinion the real problem seems to be with an ODBC connection
>
> Does itt succeeds with NT authentication if and only if the user is an
> administrator ?
>
> "RL Tech" <tech_support@.nospamuls.com> wrote in message
> news:%23b1DfodUGHA.1688@.TK2MSFTNGP11.phx.gbl...
> > Hello,
> >
> > I need some advice...
> >
> > I am running SQL Server 2000... I've installed a new instance of this on
a
> > new
> > server (to migrate from server1 to server2).
> > On server1, i have a group set up (domain/SQLGroup)...
> > On server2, i have the exact same group set up... unfortunately all the
> > users in this group doesn't get recognized by my new sql installation.
I
> > get the error above (SQL Error 18456, State '28000') when they try and
> > login. (Access, VB progs, etc)...
> >
> > I can change permissions for all the users in this group to have "Domain
> > Admins", but obviously i don't want to do that... by doing this though,
> > all
> > access works as before...
> >
> > SP4 is installed on server2, but not on server1...
> >
> > Server1 is the Domain Controller...running sbs2000 (windows 2000
server).
> > Server2 is just windows 2003, and is dedicated to sql server 2000...
> >
> > Does anyone have any suggestions on how to proceed with this?
> >
> > Thanks.
> >
> >
> >
>|||Hi,
I did look at it yesterday, but i wasn't sure if that was the problem...
I'll give it a try and see if it works out..
Thanks!
...Robin
"oj" <nospam_ojngo@.home.com> wrote in message
news:u1vHDDlUGHA.5004@.TK2MSFTNGP11.phx.gbl...
> This would help.
> http://support.microsoft.com/kb/298897
>
> --
> -oj
>
> "RL Tech" <tech_support@.nospamuls.com> wrote in message
> news:%23b1DfodUGHA.1688@.TK2MSFTNGP11.phx.gbl...
> > Hello,
> >
> > I need some advice...
> >
> > I am running SQL Server 2000... I've installed a new instance of this on
a
> > new
> > server (to migrate from server1 to server2).
> > On server1, i have a group set up (domain/SQLGroup)...
> > On server2, i have the exact same group set up... unfortunately all the
> > users in this group doesn't get recognized by my new sql installation.
I
> > get the error above (SQL Error 18456, State '28000') when they try and
> > login. (Access, VB progs, etc)...
> >
> > I can change permissions for all the users in this group to have "Domain
> > Admins", but obviously i don't want to do that... by doing this though,
> > all
> > access works as before...
> >
> > SP4 is installed on server2, but not on server1...
> >
> > Server1 is the Domain Controller...running sbs2000 (windows 2000
server).
> > Server2 is just windows 2003, and is dedicated to sql server 2000...
> >
> > Does anyone have any suggestions on how to proceed with this?
> >
> > Thanks.
> >
> >
> >
>

Error with Logins into SQL 2K

Hello,
I need some advice...
I am running SQL Server 2000... I've installed a new instance of this on a
new
server (to migrate from server1 to server2).
On server1, i have a group set up (domain/SQLGroup)...
On server2, i have the exact same group set up... unfortunately all the
users in this group doesn't get recognized by my new sql installation. I
get the error above (SQL Error 18456, State '28000') when they try and
login. (Access, VB progs, etc)...
I can change permissions for all the users in this group to have "Domain
Admins", but obviously i don't want to do that... by doing this though, all
access works as before...
SP4 is installed on server2, but not on server1...
Server1 is the Domain Controller...running sbs2000 (windows 2000 server).
Server2 is just windows 2003, and is dedicated to sql server 2000...
Does anyone have any suggestions on how to proceed with this?
Thanks.Hi
In my opinion the real problem seems to be with an ODBC connection
Does itt succeeds with NT authentication if and only if the user is an
administrator ?
"RL Tech" <tech_support@.nospamuls.com> wrote in message
news:%23b1DfodUGHA.1688@.TK2MSFTNGP11.phx.gbl...
> Hello,
> I need some advice...
> I am running SQL Server 2000... I've installed a new instance of this on a
> new
> server (to migrate from server1 to server2).
> On server1, i have a group set up (domain/SQLGroup)...
> On server2, i have the exact same group set up... unfortunately all the
> users in this group doesn't get recognized by my new sql installation. I
> get the error above (SQL Error 18456, State '28000') when they try and
> login. (Access, VB progs, etc)...
> I can change permissions for all the users in this group to have "Domain
> Admins", but obviously i don't want to do that... by doing this though,
> all
> access works as before...
> SP4 is installed on server2, but not on server1...
> Server1 is the Domain Controller...running sbs2000 (windows 2000 server).
> Server2 is just windows 2003, and is dedicated to sql server 2000...
> Does anyone have any suggestions on how to proceed with this?
> Thanks.
>
>|||This would help.
http://support.microsoft.com/kb/298897
-oj
"RL Tech" <tech_support@.nospamuls.com> wrote in message
news:%23b1DfodUGHA.1688@.TK2MSFTNGP11.phx.gbl...
> Hello,
> I need some advice...
> I am running SQL Server 2000... I've installed a new instance of this on a
> new
> server (to migrate from server1 to server2).
> On server1, i have a group set up (domain/SQLGroup)...
> On server2, i have the exact same group set up... unfortunately all the
> users in this group doesn't get recognized by my new sql installation. I
> get the error above (SQL Error 18456, State '28000') when they try and
> login. (Access, VB progs, etc)...
> I can change permissions for all the users in this group to have "Domain
> Admins", but obviously i don't want to do that... by doing this though,
> all
> access works as before...
> SP4 is installed on server2, but not on server1...
> Server1 is the Domain Controller...running sbs2000 (windows 2000 server).
> Server2 is just windows 2003, and is dedicated to sql server 2000...
> Does anyone have any suggestions on how to proceed with this?
> Thanks.
>
>|||On server1, NT (windows) authentication works with the group SQLGroup
(whether they are admin or not)... as long as they are part of SQLGroup,
they will be fine.
On server2, NT (windows) authentication only works with Admin users (thus by
adding all the users in SQLGroup to Domain Admins, they would work)... Which
i obviously don't want to do.
Both are mixed mode authentication...
ODBC has worked from the moment i set up that connection with that group...
In fact, it still works fine when i authenticate non-windows usernames...
Do i need to make server2 a Domain controller?
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:eeAlh4jUGHA.5884@.TK2MSFTNGP14.phx.gbl...
> Hi
> In my opinion the real problem seems to be with an ODBC connection
>
> Does itt succeeds with NT authentication if and only if the user is an
> administrator ?
>
> "RL Tech" <tech_support@.nospamuls.com> wrote in message
> news:%23b1DfodUGHA.1688@.TK2MSFTNGP11.phx.gbl...
a[vbcol=seagreen]
I[vbcol=seagreen]
server).[vbcol=seagreen]
>|||Hi,
I did look at it yesterday, but i wasn't sure if that was the problem...
I'll give it a try and see if it works out..
Thanks!
...Robin
"oj" <nospam_ojngo@.home.com> wrote in message
news:u1vHDDlUGHA.5004@.TK2MSFTNGP11.phx.gbl...
> This would help.
> http://support.microsoft.com/kb/298897
>
> --
> -oj
>
> "RL Tech" <tech_support@.nospamuls.com> wrote in message
> news:%23b1DfodUGHA.1688@.TK2MSFTNGP11.phx.gbl...
a[vbcol=seagreen]
I[vbcol=seagreen]
server).[vbcol=seagreen]
>

Error with linked Servers

I am having an extremely difficult time getting a linked server to
work. I am attempting to link to using an ODBC driver to a proprietary
database. I can create the ODBC connection and see the tables from
with Access using this connection. I can set up the linked server but
as soon as I attempt to view the tables it either gives me an error
7399 or just sits there. Any help would be appreciative and if there
are any other questions I need to answer just let me know.
Thanks,
Matt
Can you elaborate on how are you connecting via Access and how are you using
to create the linked server?
"Matt" wrote:

> I am having an extremely difficult time getting a linked server to
> work. I am attempting to link to using an ODBC driver to a proprietary
> database. I can create the ODBC connection and see the tables from
> with Access using this connection. I can set up the linked server but
> as soon as I attempt to view the tables it either gives me an error
> 7399 or just sits there. Any help would be appreciative and if there
> are any other questions I need to answer just let me know.
> Thanks,
> Matt
>

Error with Linked Servers

From time to time the linked servers we have set up cannot be accessed. When
I click on the tables node under the linked server within enterprise manager
the session hangs and no error message is displayed. When querying the data
via an openquery no error is thrown, the query simply runs until manually
aborted.
I've created a linked server OK but immediately cannot open it. The only way
around this problem we have is a reboot of the server. Does anyone know how
to resolve this problem and also what would cause this.
Thanks
MikeMikeD
Do you have ping to linked server?
"MikeD" <MikeD@.discussions.microsoft.com> wrote in message
news:ACBEC816-1EE1-46E8-9535-8E52BB7C502A@.microsoft.com...
> From time to time the linked servers we have set up cannot be accessed.
> When
> I click on the tables node under the linked server within enterprise
> manager
> the session hangs and no error message is displayed. When querying the
> data
> via an openquery no error is thrown, the query simply runs until manually
> aborted.
> I've created a linked server OK but immediately cannot open it. The only
> way
> around this problem we have is a reboot of the server. Does anyone know
> how
> to resolve this problem and also what would cause this.
> Thanks
> Mike|||I can ping the server that sql is on if that's what you mean. I can see and
create linked servers but cannot query them - see below.
"Uri Dimant" wrote:

> MikeD
> Do you have ping to linked server?
> "MikeD" <MikeD@.discussions.microsoft.com> wrote in message
> news:ACBEC816-1EE1-46E8-9535-8E52BB7C502A@.microsoft.com...
>
>|||MikeD
Do you run the query in this way?
SELECT <> FROM Server.dbname.dbo.table
"MikeD" <MikeD@.discussions.microsoft.com> wrote in message
news:2C11B49F-D1BF-48C2-9ECC-2470666F9691@.microsoft.com...[vbcol=seagreen]
>I can ping the server that sql is on if that's what you mean. I can see and
> create linked servers but cannot query them - see below.
> "Uri Dimant" wrote:
>|||No - it's an openquery so it's :
SELECT * FROM OPENQUERY[linked_server_name], 'Select * from table_name'
But the problem isn't so much in the query it's the fact that when you
select the linked server the system hangs with no error message and the only
way we have of resolving the issue is a server reboot
"Uri Dimant" wrote:

> MikeD
> Do you run the query in this way?
> SELECT <> FROM Server.dbname.dbo.table
>
>
> "MikeD" <MikeD@.discussions.microsoft.com> wrote in message
> news:2C11B49F-D1BF-48C2-9ECC-2470666F9691@.microsoft.com...
>
>|||Well, is it large set data you want to return?
exec sp_serveroption 'servername','data access','true'
"MikeD" <MikeD@.discussions.microsoft.com> wrote in message
news:6EA13818-E61B-49E7-B6E0-35F581ADAF0F@.microsoft.com...[vbcol=seagreen]
> No - it's an openquery so it's :
> SELECT * FROM OPENQUERY[linked_server_name], 'Select * from table_name
'
> But the problem isn't so much in the query it's the fact that when you
> select the linked server the system hangs with no error message and the
> only
> way we have of resolving the issue is a server reboot
> "Uri Dimant" wrote:
>|||It's nothing to do with the query or the size of data. the problem is that
the linked server cannot be accessed until a reboot is done.
"Uri Dimant" wrote:

> Well, is it large set data you want to return?
> exec sp_serveroption 'servername','data access','true'
>
> "MikeD" <MikeD@.discussions.microsoft.com> wrote in message
> news:6EA13818-E61B-49E7-B6E0-35F581ADAF0F@.microsoft.com...
>
>

Error with linked Servers

I am having an extremely difficult time getting a linked server to
work. I am attempting to link to using an ODBC driver to a proprietary
database. I can create the ODBC connection and see the tables from
with Access using this connection. I can set up the linked server but
as soon as I attempt to view the tables it either gives me an error
7399 or just sits there. Any help would be appreciative and if there
are any other questions I need to answer just let me know.
Thanks,
MattCan you elaborate on how are you connecting via Access and how are you using
to create the linked server?
"Matt" wrote:

> I am having an extremely difficult time getting a linked server to
> work. I am attempting to link to using an ODBC driver to a proprietary
> database. I can create the ODBC connection and see the tables from
> with Access using this connection. I can set up the linked server but
> as soon as I attempt to view the tables it either gives me an error
> 7399 or just sits there. Any help would be appreciative and if there
> are any other questions I need to answer just let me know.
> Thanks,
> Matt
>

Error with linked Servers

I am having an extremely difficult time getting a linked server to
work. I am attempting to link to using an ODBC driver to a proprietary
database. I can create the ODBC connection and see the tables from
with Access using this connection. I can set up the linked server but
as soon as I attempt to view the tables it either gives me an error
7399 or just sits there. Any help would be appreciative and if there
are any other questions I need to answer just let me know.
Thanks,
MattCan you elaborate on how are you connecting via Access and how are you using
to create the linked server?
"Matt" wrote:
> I am having an extremely difficult time getting a linked server to
> work. I am attempting to link to using an ODBC driver to a proprietary
> database. I can create the ODBC connection and see the tables from
> with Access using this connection. I can set up the linked server but
> as soon as I attempt to view the tables it either gives me an error
> 7399 or just sits there. Any help would be appreciative and if there
> are any other questions I need to answer just let me know.
> Thanks,
> Matt
>

Error with linked server after failover

Hi all,

The following query that uses a linked server is giving me the error message below after I initiate a failover (ALTER DATABASE Northwind SET PARTNER FAILOVER).I have SQL Server 2005 SP2.I think that without the service pack there is another error too.

The query is run from a database other than northwind of course.

select * from DualLink.northwind.dbo.Test1

Please note that:

without a failover itworks perfectly

it always work if I try to run it a second time - only the first time it fails.

it fails the first time for each of the open connections. A new connection that was open after the failover will work fine.

A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)

A transport-level error has occurred when sending the request to the server. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.)

The linked server is defined as

EXEC master.

dbo.sp_addlinkedserver

@.server = N'DualLink',

@.srvproduct=N'',

@.provider=N'SQLOLEDB',

@.catalog=N'northwind',

@.provstr=N'Server=(local);FailoverPartner=MyIPAddr;'

EXEC master.dbo.sp_addlinkedsrvlogin

@.rmtsrvname = 'DualLink',

@.useself = false,

@.locallogin = 'sa',

@.rmtuser = 'sa',

@.rmtpassword = 'MyPwd'

Thanks,

Avi

I am having the same problem except I don't have a linked server.

I am running SQL Server 2005 sp1 and Windows 2003 using clustering.

In addition to your symptoms I have noticed the following:

1. The error occurs when I make a query through Server Manager and when using a java app that queries a database using an ASP page. However, if I bring up our website as the first request after failover it works fine.

2. If I failover from Server1 to Server2 and don't make any requests while it is on Server2 and then failover back to Server1 I do not get the error. If I make any requests while it is on Server2 then the first request I make on Server1 after failing over will cause the error.

If you have solved the problem I would like to know how. If I find a solution I will post it here.

Blake