sa password was inadvertently changed. With a kicker...

From: Ryan Gaudet (rgaudet_at_hushmail.com)
Date: 08/08/03

  • Next message: Tai Yee [MSFT]: "Re: What's the real difference between SP3 and SP3a?"
    Date: Thu, 7 Aug 2003 15:01:55 -0700
    
    

    Hi,
    I have a SQL Server 7 Standard edition server running in a
    clients IT environment. Sometime last week, the IT
    department installed a new application that needed a new
    SQL server database that was to be installed on a
    different SQL Server. When they were prompted to select
    the server to install the database to, they inadvertently
    installed to our server. (our sa password was blank and
    that's how they could do this....Very bad, I know)The
    script that created the database reset the sa password and
    noone seems to know what it is.
    Here's the kicker; When we installed the SQL server, it
    was part of domain "A" and we were logged in as a service
    account user as per our application requirements but the
    client installed a new PDC last spring and we moved the
    server to the new domain so the account we used to install
    the SQL server doesn't exist so we don't have an account
    with admin rights. We tried setting up a bogus PDC with
    the old domain name, setting up a trust between the
    domains and logging in with the original account name to
    see if we could trick it that way but to no avail.
    Is there any way that we will be able to reset the sa
    password or change the domain reference to the NT user
    account with admin priveledges? If not, will Microsoft be
    able to reset the sa password? I know it will cost money
    if they can but we need to get this resolved.

    Thanks in advance.


  • Next message: Tai Yee [MSFT]: "Re: What's the real difference between SP3 and SP3a?"

    Relevant Pages

    • Re: sa password was inadvertently changed. With a kicker...
      ... Use some other account that the client has (any domain admin should have ... Did around there install package, and see if the sql script that changed ... Put the database files back where they should ... > I have a SQL Server 7 Standard edition server running in a ...
      (microsoft.public.sqlserver.security)
    • Re: SQL Sever 2008 RC0 fail to install almost all services
      ... Now I removed the account from local Administrators group. ... The SQL Server Log File reports an error 15209, ... Note that I use a specific account named SQLServerServices to install ... This is an informational message only. ...
      (microsoft.public.sqlserver.setup)
    • Re: Compromise?
      ... >made the patches available and advised customers to ... >install it. ... >>Server was installed and if your SQL Server is running ... >>administrator account, you just gave anybody who has a ...
      (microsoft.public.sqlserver.security)
    • Re: Get "credentials not valid" message installing SQL2008 Failver
      ... The user account (domain account) has to be pre-created. ... The network name gets created during the install process. ... Microsoft SQL Server MVP ...
      (microsoft.public.sqlserver.setup)
    • Re: SQL Server 2008 set up
      ... work on this Account so I would like to use that. ... "SQL Server System Administrators" list during SQL Server 2008 Setup. ... The install completed successfully. ... Microsoft Online Community Support ...
      (microsoft.public.sqlserver.setup)