Cannot login using 'sa' user name and password

Used configuration and enabled IP and is fiexed. Thanks.
--
Mike
"Mike9900" wrote:

> Hello,
> When I try to connect it give the following message I copied from the log:
> Source Logon
> Message
> Login failed for user 'sa'. The user is not associated with a trusted SQL
> Server connection. [CLIENT: <local machine>]
>
> I am using Win 2003 Ent. and is domain controller. I use administrator
> login in win 2003. I recently installed a new win2003, but I had Win2003
> before and was fine.
> In SQL Server, it is a mixed mode and everything seems to be fine.
> What could be the other problems?
> Thanks
> --
> MikeHello,
When I try to connect it give the following message I copied from the log:
Source Logon
Message
Login failed for user 'sa'. The user is not associated with a trusted SQL
Server connection. [CLIENT: <local machine>]
I am using Win 2003 Ent. and is domain controller. I use administrator
login in win 2003. I recently installed a new win2003, but I had Win2003
before and was fine.
In SQL Server, it is a mixed mode and everything seems to be fine.
What could be the other problems?
Thanks
Mike|||Used configuration and enabled IP and is fiexed. Thanks.
--
Mike
"Mike9900" wrote:

> Hello,
> When I try to connect it give the following message I copied from the log:
> Source Logon
> Message
> Login failed for user 'sa'. The user is not associated with a trusted SQL
> Server connection. [CLIENT: <local machine>]
>
> I am using Win 2003 Ent. and is domain controller. I use administrator
> login in win 2003. I recently installed a new win2003, but I had Win2003
> before and was fine.
> In SQL Server, it is a mixed mode and everything seems to be fine.
> What could be the other problems?
> Thanks
> --
> Mike

Cannot install report server DB

Hi All,
I have installed VS.Net 2003, SQL Server 2000 with SQL Server 2000 sp3,
enabled Internet Information services, Frontpage server extensions.
However the Report Server database does not appear on my local server.
Is there something I am missing?
Thanks
SanjeevSQL Reporting Services has it's own seperate install. You need to aquire it
and run it on your server and on the client you wish to use the report
designer from in order to begin.
Peace,
Dan
"Sanjeev" <sanjeev@.microsoft.com> wrote in message
news:ON6nskJfFHA.3436@.tk2msftngp13.phx.gbl...
> Hi All,
> I have installed VS.Net 2003, SQL Server 2000 with SQL Server 2000 sp3,
> enabled Internet Information services, Frontpage server extensions.
> However the Report Server database does not appear on my local server.
> Is there something I am missing?
> Thanks
> Sanjeev
>|||Thanks Dan. I will try this.
"Dan Christjohn" <dchristjohn(removethis)@.directapps.com> wrote in message
news:OvNw$yMfFHA.2444@.tk2msftngp13.phx.gbl...
> SQL Reporting Services has it's own seperate install. You need to aquire
> it and run it on your server and on the client you wish to use the report
> designer from in order to begin.
> Peace,
> Dan
> "Sanjeev" <sanjeev@.microsoft.com> wrote in message
> news:ON6nskJfFHA.3436@.tk2msftngp13.phx.gbl...
>> Hi All,
>> I have installed VS.Net 2003, SQL Server 2000 with SQL Server 2000 sp3,
>> enabled Internet Information services, Frontpage server extensions.
>> However the Report Server database does not appear on my local server.
>> Is there something I am missing?
>> Thanks
>> Sanjeev
>

Cannot Generate SSPI context

Hi,
I disabled the Namedpipes and enabled the TCP/IP
protocol in the the sql server box. The box/server
is rebooted after this change. My client workstation
is not to connect to the SQL Server. The SQL Server is
running. With in the SQL Server box, I can use query
analyzer to connect to sql server and works.
From my client workstation, I receive the below error
message.
"Cannot Generate SSPI context"
I restart my workstation too. Still the same problem.
I tried the possible solutions given in the web site.
Article#: 269541.
Could you please help me.
Thanks
Saravanan KunjuSome things to check -
can you ping the server from your workstation?
Have you tried setting up an alias to the server from your
workstation using the Client Network Utility?
You should also refer to the following article for
additional troubleshooting steps:
HOW TO: Troubleshoot the "Cannot Generate SSPI Context"
Error Message
http://support.microsoft.com/?id=811889
-Sue
On Tue, 20 Apr 2004 09:34:54 -0700, "Saravanan Kunju"
<kavisarav@.yah00.com> wrote:

>Hi,
>I disabled the Namedpipes and enabled the TCP/IP
>protocol in the the sql server box. The box/server
>is rebooted after this change. My client workstation
>is not to connect to the SQL Server. The SQL Server is
>running. With in the SQL Server box, I can use query
>analyzer to connect to sql server and works.
>From my client workstation, I receive the below error
>message.
> "Cannot Generate SSPI context"
>I restart my workstation too. Still the same problem.
>I tried the possible solutions given in the web site.
>Article#: 269541.
>Could you please help me.
>Thanks
>Saravanan Kunju
>

Cannot find my SQL Server

I have installed SQL Express in my server with SQL Browser enabled. I also added an exception to the window firewall to port 1433.

My client application is installed in another machine on the same workgroup. But I cannot see the SQL Express unless I disabled the server's firewall.

Without disabling the firewall, what else should I do?

Thanks

sqlexpress is a named instance of sqlserver. thus, it does not listen on tcp 1433 by default. you can follow the below article to configure sqlexpress for accepting remote connect through the firewall.
http://support.microsoft.com/kb/914277|||If it would be on port 1433 you wouldn′t need the SQL Browser as the client always assumes this dfault port. SQL Browser is for routing the request to the appopiate port which *could* be port 1433. But the port can differ from 1433 as there can be many instances hosted on the same server, every instance taking one TCP port.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de
|||By default, when any version of SQL Server 2005 is installed it will not talk to the network. You must use the SQL Server Configuration Manager and enable TCP/IP to talk to the network.|||See my screencast section on my site for more information.

HTH; Jens Suessmeyer.

http://www.sqlserver2005.de|||

I have done the following, but still cannot find my SQL Server 2005 Express installed on WinXP Prof.(SP2) server, My server only has one instance named "AppDefault"

Enable local and remote connections(in Surface Area Configuration for Services and Connections) on the instance of SQL Server that I want to connect to.