Re: Can't connect to databases through Enterprise Manager
From: Brendan (anonymous_at_discussions.microsoft.com)
Date: 03/25/04
- Next message: Bojidar Alexandrov: "Re: Problem with SQLOLEDB and iis 6 - threading?"
- Previous message: Hari: "Re: Link to dbf file"
- In reply to: Hari: "Re: Can't connect to databases through Enterprise Manager"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 24 Mar 2004 21:52:05 -0800
Thanks for the post. It more or less led me to a
solution. I tried using NT authentication with no
success. Realized the machine was running on the admin
account with no password. For giggles I made a new admin
account with a different user name and an actual password
and tried again. Low and behold it worked. I got into
query analyzer and changed the sa password. Problem
solved. Thanks again.
>-----Original Message-----
>Hi,
>
>It seems the Login ID you are using is defaulted to the
database you have
>deleted. That is the reason you are getting the error.
>
>How to change the SA Password,
>
>1. Login to Query analyzer using Windows Authentication
>2. Execute the beloe command
>
> sp_password null,'passwordsa',sa
>
>(now the password for sa is passwordsa)
>
>How to change the default database of your existing
users, which gave error
>
>1. Login to query analyzer as SA
>2. execute below statement
>
> sp_defaultdb <loginame>,<new database name>
>
>3. After this you will be able to login using the old id
itself.
>
>Thanks
>Hari
>MCDBA
>
>
>
>
>
>"Brendan" <anonymous@discussions.microsoft.com> wrote in
message
>news:124bf01c41152$811230e0$a501280a@phx.gbl...
>> Understand I am not a DBA. I am just the guy who has
to
>> work with this stuff.
>>
>> We have client software that uses SQL 7 as a database.
>> Winpak is a door access software made by Northern. It
>> stores proxy card info, access levels, historys, etc.
in
>> a SQL 7 database. I know the databases are still
there
>> because Winpak connects and I can pull up info.
>>
>> This started because I noticed whoever set up the
primary
>> and archive databases pointed them both to the same
file
>> name. I backed up the primary and deleted it.
Restored
>> it with the full backup and made sure it was pointed
to a
>> different file name. Everything worked fine and still
>> showed up in Enterprise Manager. I restarted the
computer
>> later and tried to go back into Enterprise Manager.
Tried
>> to expand 'SQL Server Group' to list all the databases
and
>> I got an error saying, "A connection could not be
>> established to COMPUTER - Cannot open user default
>> database '<ID>'. Using master database instead.
Please
>> verify SQL Server is running and check your SQL Server
>> registration properties (by right-clicking on the
COMPUTER
>> node) and try again."
>>
>> My services were running just fine and when I checked
my
>> registration properties everything looked fine. Redid
the
>> registration properties with no luck. Using NT
>> authentication and even making a new one. The other
>> problem is that somebody set this thing up 3 years ago
and
>> I have no idea what the 'sa' password is and I have
tried
>> every simple password I can think of. I am checked out
>> the knowledge database articles matching my error
message
>> and they didn't realy help cuz I either needed the 'sa'
>> password or I don't know how to impliment the solution
>> based on my limited knowledge of SQL. I need to do a
>> final backup to move all the info to a new machine with
>> SQL 2000. I am really stuck (and screwed) if I can't
get
>> that info off cuz we just entered in a few hundred more
>> employees so using an old backup isn't going to save
me.
>> Help would be greatly appreciated
>
>
>.
>
- Next message: Bojidar Alexandrov: "Re: Problem with SQLOLEDB and iis 6 - threading?"
- Previous message: Hari: "Re: Link to dbf file"
- In reply to: Hari: "Re: Can't connect to databases through Enterprise Manager"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
