SQL Server V6.5 Enterprise Manager Login Failure 
Author Message
 SQL Server V6.5 Enterprise Manager Login Failure

Background: I am in the process of testing/evaluating WindowsNT V4.0 and
SQL Server V6.5 and have installed these products on a
133mhz/32mb/5gb/modem-only Intel PC.  I have no previous experience in
either product though I have an extensive database backgroup.  I read
online help and have purchased two books (Windows Magazine, WindowsNT V4.0
and SQL Server 6.5 Secrets) most of which I have at least surveyed.

Problem: SQL Server Enterprise Manager returns a 'login failed' when I try
to connect to the NT Server after initially attempting to connect with a
Server; however, I can query the master database when I invoke the ISQL_w
query utility directly.

Installation
----------------
WindowsNT 4.0 was installed with the following options:
- Server Type: Stand-Alone Server
- All component options
- Remote access to the network via modem
- Internet
        - TCP/IP
        - NWLink
        - Servers: Internet Information Server; Remote Access Server;
                RPC Configuration; NetBios Interface; Workstation; Server
        - DHCP Server (to resolve IP address)
        - RAS - modem installed on COM2
        - MS Loopback
        - Bindings: NetBios; RSA; Server; Workstation
- CPU name 'IIC1', Workgroup: Workgroup

SQL Server V6.5 installation
- Choose defaults plus Internet software
- Register Server was blank, entered:
        - Server: IIC1
        - Login Security: Standard
                - ID: Administrator
                - Password: (same as WindowsNT Administrator account)
- Also tried:
        - Server: (local)
        - Login Security: Standard
                - ID: sa
                - Password (same as WindowsNT Administrator account)

Initial suggestion was to connect as 'local' but this resulted in same
'login failed' error.

My current thinking is that SQL Enterprise Manager attempts to connect
through the modem to get to the Server but I am still so new to these
products that its just a wild guess.

Any suggestions would be appreciated especially in the general area of
stand-along configurations for testing/evaluation purpose.

Thank you in advance.

mz



Sat, 28 Aug 1999 03:00:00 GMT
 SQL Server V6.5 Enterprise Manager Login Failure

Michael,

Hard to tell without more details... but I might guess that you're using
standard security from isql/w and a trusted connection from SEM. See how
you're server is registered in SEM. A trusted connection means the NT user
currently logged in must have a valid account that can access that
server...

That's my best guess if you can connect from isql/w but not SEM from the
same server. There are many other possibilites if we're talking about this
problem across different clients...

--
Brian Moran
Spectrum Technology Group
MCSE, MCSD, MCT. MVP



Quote:
> Background: I am in the process of testing/evaluating WindowsNT V4.0 and
> SQL Server V6.5 and have installed these products on a
> 133mhz/32mb/5gb/modem-only Intel PC.  I have no previous experience in
> either product though I have an extensive database backgroup.  I read
> online help and have purchased two books (Windows Magazine, WindowsNT
V4.0
> and SQL Server 6.5 Secrets) most of which I have at least surveyed.

> Problem: SQL Server Enterprise Manager returns a 'login failed' when I
try
> to connect to the NT Server after initially attempting to connect with a
> Server; however, I can query the master database when I invoke the ISQL_w
> query utility directly.

> Installation
> ----------------
> WindowsNT 4.0 was installed with the following options:
> - Server Type: Stand-Alone Server
> - All component options
> - Remote access to the network via modem
> - Internet
>    - TCP/IP
>    - NWLink
>    - Servers: Internet Information Server; Remote Access Server;
>            RPC Configuration; NetBios Interface; Workstation; Server
>    - DHCP Server (to resolve IP address)
>    - RAS - modem installed on COM2
>    - MS Loopback
>    - Bindings: NetBios; RSA; Server; Workstation
> - CPU name 'IIC1', Workgroup: Workgroup

> SQL Server V6.5 installation
> - Choose defaults plus Internet software
> - Register Server was blank, entered:
>    - Server: IIC1
>    - Login Security: Standard
>            - ID: Administrator
>            - Password: (same as WindowsNT Administrator account)
> - Also tried:
>    - Server: (local)
>    - Login Security: Standard
>            - ID: sa
>            - Password (same as WindowsNT Administrator account)

> Initial suggestion was to connect as 'local' but this resulted in same
> 'login failed' error.

> My current thinking is that SQL Enterprise Manager attempts to connect
> through the modem to get to the Server but I am still so new to these
> products that its just a wild guess.

> Any suggestions would be appreciated especially in the general area of
> stand-along configurations for testing/evaluation purpose.

> Thank you in advance.

> mz



Sat, 28 Aug 1999 03:00:00 GMT
 SQL Server V6.5 Enterprise Manager Login Failure

MIchael,

It seems we have the exact same problem, I'm also in the process of
evaluating SQL Server 6.5 on a standalone server with remote access via
modem installed.

Isql works fine, but SQL Entreprise Manager returns 'logon failed'. But
wait - I've found an awkward/expensive workaround which might work for you
too until Microsoft releases a patch.

Try opening your remote access to dial the Internet for instance. After
this is up and running, you'll suddenly be able to access SQL Enterprise
Manager. I'm sorry to say that you have to keep this line open. At least
you'll get to see how it works.

Hope this can help you !

P.S. you might check out "db fails to register" from Dave Kowalski too,
seems he's got the same kind of problem.

--
Bjorn Bentzen



Quote:
> Background: I am in the process of testing/evaluating WindowsNT V4.0 and
> SQL Server V6.5 and have installed these products on a
> 133mhz/32mb/5gb/modem-only Intel PC.  ...<Deleted>

> Problem: SQL Server Enterprise Manager returns a 'login failed' when I
try
> to connect to the NT Server after initially attempting to connect with a
> Server; however, I can query the master database when I invoke the ISQL_w
> query utility directly.

> <Deleted>    



Fri, 10 Sep 1999 03:00:00 GMT
 SQL Server V6.5 Enterprise Manager Login Failure


Quote:

> Background: I am in the process of testing/evaluating WindowsNT V4.0 and
> SQL Server V6.5 and have installed these products on a
> 133mhz/32mb/5gb/modem-only Intel PC.  I have no previous experience in
> either product though I have an extensive database backgroup.  I read
> online help and have purchased two books (Windows Magazine, WindowsNT V4.0
> and SQL Server 6.5 Secrets) most of which I have at least surveyed.

> Problem: SQL Server Enterprise Manager returns a 'login failed' when I try
> to connect to the NT Server after initially attempting to connect with a
> Server; however, I can query the master database when I invoke the ISQL_w
> query utility directly.

> Installation
> ----------------
> WindowsNT 4.0 was installed with the following options:
> - Server Type: Stand-Alone Server
> - All component options
> - Remote access to the network via modem
> - Internet
>         - TCP/IP
>         - NWLink
>         - Servers: Internet Information Server; Remote Access Server;
>                 RPC Configuration; NetBios Interface; Workstation; Server
>         - DHCP Server (to resolve IP address)
>         - RAS - modem installed on COM2
>         - MS Loopback
>         - Bindings: NetBios; RSA; Server; Workstation
> - CPU name 'IIC1', Workgroup: Workgroup

> SQL Server V6.5 installation
> - Choose defaults plus Internet software
> - Register Server was blank, entered:
>         - Server: IIC1
>         - Login Security: Standard
>                 - ID: Administrator
>                 - Password: (same as WindowsNT Administrator account)
> - Also tried:
>         - Server: (local)
>         - Login Security: Standard
>                 - ID: sa
>                 - Password (same as WindowsNT Administrator account)

> Initial suggestion was to connect as 'local' but this resulted in same
> 'login failed' error.

> My current thinking is that SQL Enterprise Manager attempts to connect
> through the modem to get to the Server but I am still so new to these
> products that its just a wild guess.

> Any suggestions would be appreciated especially in the general area of
> stand-along configurations for testing/evaluation purpose.

> Thank you in advance.

> mz

Suggestion !
Try to use two different ways of securiry logins:
- NT integrated
- mixed
I had the same problem and solve it with mixed security !
Don't forget to enter your Domain name !
Mikle


Fri, 10 Sep 1999 03:00:00 GMT
 
 [ 4 post ] 

 Relevant Pages 

1. SQL-Server 6.5: Login failed with ISQL_W, login with Enterprise Manager works fine

2. SQL Enterprise Manager Login Failure

3. Login failure in enterprise manager

4. Sql Server 7.0 Login timeout with enterprise manager

5. Server connection failure in Enterprise Manager

6. Need to have a SQL Login that can see the Management tab in Enterprise Manager

7. SQL Server 7 from SQL Server 2000 Enterprise Manager

8. Using SQL Server 7 Enterprise Manager w/SQL Server 2000

9. Administer a SQL Server 6.5 DB from SQL Server 7 Enterprise Manager

10. SQL server task fails-sql executive login failure-

11. SQL Server V6.5 Enterprise Edition

12. Managing Sql Server 7 and Server 2000 from SQL2000 Enterprise Manager


 
Powered by phpBB® Forum Software