Problem installing SP3a

I have kind of a messed up server I think. It had two instances of SQL
Server installed and I removed one.
Now, I'm getting an error trying to schedule run a scheduled DTS job. I
looked it up in the knowledge base and the best answers were to re-install
the service pack. So...
Reinstalling the service pack failes because it looks like the service pack
wants to authenticate itself to the SQL Server but can't. My guess is it
can't find the right instance to use to authenticate.
Does anyone know where I can set this? It sees the instance and brings it
up during the installation process, but both SQL Server authentication and
Windows Authentication both fail. I get the error message "Setup was unable
to validate the logged user. Press Retry to enter another option, or Cancel
to exit setup."
I tried the resolutions in Q814844 but they were either already set or
didn't make a difference. I'm guessing it might have something to do with
the second instance throwing off the installation so it doesn't know where
to authenticate itself.
Any ideas?
Thanks,
GaryDid you use "sa" and the corresponding password for the same ?
--
HTH,
Vinod Kumar
MCSE, DBA, MCAD
http://www.extremeexperts.com
"Gary" <tuffboystl@.hotmail.com> wrote in message
news:eYlt7KjdDHA.1880@.TK2MSFTNGP10.phx.gbl...
> I have kind of a messed up server I think. It had two instances of SQL
> Server installed and I removed one.
> Now, I'm getting an error trying to schedule run a scheduled DTS job. I
> looked it up in the knowledge base and the best answers were to re-install
> the service pack. So...
> Reinstalling the service pack failes because it looks like the service
pack
> wants to authenticate itself to the SQL Server but can't. My guess is it
> can't find the right instance to use to authenticate.
> Does anyone know where I can set this? It sees the instance and brings it
> up during the installation process, but both SQL Server authentication and
> Windows Authentication both fail. I get the error message "Setup was
unable
> to validate the logged user. Press Retry to enter another option, or
Cancel
> to exit setup."
> I tried the resolutions in Q814844 but they were either already set or
> didn't make a difference. I'm guessing it might have something to do with
> the second instance throwing off the installation so it doesn't know where
> to authenticate itself.
> Any ideas?
> Thanks,
> Gary
>|||yes.
"Vinodk" <vinodk_sct@.NO_SPAM_hotmail.com> wrote in message
news:O%23YUONodDHA.1620@.TK2MSFTNGP12.phx.gbl...
> Did you use "sa" and the corresponding password for the same ?
> --
> HTH,
> Vinod Kumar
> MCSE, DBA, MCAD
> http://www.extremeexperts.com
>
> "Gary" <tuffboystl@.hotmail.com> wrote in message
> news:eYlt7KjdDHA.1880@.TK2MSFTNGP10.phx.gbl...
> > I have kind of a messed up server I think. It had two instances of SQL
> > Server installed and I removed one.
> >
> > Now, I'm getting an error trying to schedule run a scheduled DTS job. I
> > looked it up in the knowledge base and the best answers were to
re-install
> > the service pack. So...
> >
> > Reinstalling the service pack failes because it looks like the service
> pack
> > wants to authenticate itself to the SQL Server but can't. My guess is
it
> > can't find the right instance to use to authenticate.
> >
> > Does anyone know where I can set this? It sees the instance and brings
it
> > up during the installation process, but both SQL Server authentication
and
> > Windows Authentication both fail. I get the error message "Setup was
> unable
> > to validate the logged user. Press Retry to enter another option, or
> Cancel
> > to exit setup."
> >
> > I tried the resolutions in Q814844 but they were either already set or
> > didn't make a difference. I'm guessing it might have something to do
with
> > the second instance throwing off the installation so it doesn't know
where
> > to authenticate itself.
> >
> > Any ideas?
> >
> > Thanks,
> > Gary
> >
> >
>