Hard times with SQL server. sa can not be found.

I've been struggling with many problems around importing a small one table
database in sql 2005 to a new database in 2005. A reply in a thread in the
dts group told me I needed to select "copyschema". That helps so the import
ran with out an error as long as nothing else was selected, hence, nothing
was imported. I then started to experiment with selecting more options such
as copy all tables, etc. Then I got an error saying I could not connect to
that database. I then rebooted the machine and tried to log into SSIS and
the SQL MS and when I was prompted to log in, it said it could not find the
user. I was logging in under Windows authentication. So then I tried sql
server authentication and sa, but got the same error (could not find user
sa). all of this used to work a few minutes ago. This is VERY scary. It
seems that sql server is corrupt and needs to be reloaded as I have no way
of getting into it now. Has anyone seen this before? What is a fix?
Thanks.
moondaddy@.nospam.nospamFound it. Don't know why, but TCP/IP became disabled. I went into SQL
Server Configuration manager and enabled tcp/ip. now i can log in again.
moondaddy@.nospam.nospam
"moondaddy" <moondaddy@.nospam.nospam> wrote in message
news:%234PkvF$7FHA.1864@.TK2MSFTNGP12.phx.gbl...
> I've been struggling with many problems around importing a small one table
> database in sql 2005 to a new database in 2005. A reply in a thread in
> the dts group told me I needed to select "copyschema". That helps so the
> import ran with out an error as long as nothing else was selected, hence,
> nothing was imported. I then started to experiment with selecting more
> options such as copy all tables, etc. Then I got an error saying I could
> not connect to that database. I then rebooted the machine and tried to
> log into SSIS and the SQL MS and when I was prompted to log in, it said it
> could not find the user. I was logging in under Windows authentication.
> So then I tried sql server authentication and sa, but got the same error
> (could not find user sa). all of this used to work a few minutes ago.
> This is VERY scary. It seems that sql server is corrupt and needs to be
> reloaded as I have no way of getting into it now. Has anyone seen this
> before? What is a fix?
> Thanks.
> --
> moondaddy@.nospam.nospam
>|||No that wasnt it. when I was prompted to connect, sqlexpress was the server
i logged into, not the main server. Still need help!
moondaddy@.nospam.nospam
"moondaddy" <moondaddy@.nospam.nospam> wrote in message
news:%23os6WI$7FHA.4076@.tk2msftngp13.phx.gbl...
> Found it. Don't know why, but TCP/IP became disabled. I went into SQL
> Server Configuration manager and enabled tcp/ip. now i can log in again.
> --
> moondaddy@.nospam.nospam
> "moondaddy" <moondaddy@.nospam.nospam> wrote in message
> news:%234PkvF$7FHA.1864@.TK2MSFTNGP12.phx.gbl...
>|||Hello,
Many factors can cause the issue.
Have you ever connect to SQL server using sa successfully? What
authentication mode SQL server use? To connect to SQL server using sa, it
need to use mixed mode . I suggest that you perform the following steps to
narrow down the issue:
Step 1: Restart the SQL server service. Make sure SQL server service is
running.
Step 2: Ping the SQL server machine IP address and name to check if you can
receive the reply.
Step 3: Create a new Local administrative user account. Log on the server
Locally as the new Local administrative user account. Check if you can
connect to SQL server.
Step 4: Check the SQL server error logs on your hard disk to see if there
is any errors related to the issue. By default, the SQL server error log is
located in the "C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG"
folder. You can use notepad to open the log file.
Check the port SQL server is listening on.
Step 5: In the Server Configuration manager, make sure TCP/IP, Shared
memory, Named pipe are enabled under the SQL server 2005 Network
configuration. Check the TCP port and make sure it is correct. If it is a
default instance, the default port is 1433.
Check the pipe name and make sure it is correct.
If you change the configuration, you need to restart the SQL server service.
Step 6: Make sure the TCP/IP, Shared memory, Named pipe are enabled under
the SQL native client configuration.
Please let me know the detail results. I look forward to hearing from you.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
========================================
=============
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.