OH NO! Please help!

One of my IT guys "disabled" the "BUILTIN\Administrator" account in SQL
server and now we can't connect to the server using Enterprise Manager.
None of the other logins have administration privileges.
How can we either re-enable the account or get administrative access to
SQL server?
--DaveIf you are running in mixed security mode you can use sa.
Christian Smith
"Dave Navarro" <dave@.dave.dave> wrote in message
news:MPG.1a96f8a675e3bc62989785@.news-40.giganews.com...
> One of my IT guys "disabled" the "BUILTIN\Administrator" account in SQL
> server and now we can't connect to the server using Enterprise Manager.
> None of the other logins have administration privileges.
> How can we either re-enable the account or get administrative access to
> SQL server?
> --Dave|||In article <elZTG3m8DHA.2752@.TK2MSFTNGP09.phx.gbl>, csmith@.digex.com
says...
> If you are running in mixed security mode you can use sa.
Tried it and it didn't work.
I had already installed Service Pack 3, but I don't think it was 3a.
The knowledge base seems to indicate that re/installing the service pack
will enable/create the BUILTIN/Administrator account.
Is that correct?
--Dave|||Also, is it the BUILTIN\Administrator user or the BUILTIN\Administrators
group? If it is the user than the group should still be there unless
removed. What about the user that SQL is running under? Was it explicitly
given access or was it using the BUILTIN access?
"Dave Navarro" <dave@.dave.dave> wrote in message
news:MPG.1a96f8a675e3bc62989785@.news-40.giganews.com...
> One of my IT guys "disabled" the "BUILTIN\Administrator" account in SQL
> server and now we can't connect to the server using Enterprise Manager.
> None of the other logins have administration privileges.
> How can we either re-enable the account or get administrative access to
> SQL server?
> --Dave|||SP3 and SP3a are pretty much the same. 3a is only there if you couldn't get
3 to install. Which article said you the SP would fix this? Do you have a
link? Also, how did sa not work? What did you try to do? The
BUILTIN\Adminsitrators is completely different from SQL security model that
sa uses. If you have the password you should be able to access the system
using SA.
Christian Smith
"Dave Navarro" <dave@.dave.dave> wrote in message
news:MPG.1a96fd2a91bf5623989786@.news-40.giganews.com...
> In article <elZTG3m8DHA.2752@.TK2MSFTNGP09.phx.gbl>, csmith@.digex.com
> says...
> > If you are running in mixed security mode you can use sa.
> Tried it and it didn't work.
> I had already installed Service Pack 3, but I don't think it was 3a.
> The knowledge base seems to indicate that re/installing the service pack
> will enable/create the BUILTIN/Administrator account.
> Is that correct?
> --Dave|||http://support.microsoft.com/search/default.aspx?
InCC_hdn=true&Catalog=LCID%3D1033%26CDID%3DEN-US-KB%26PRODLISTSRC%
3DON&withinResults=&QuerySource=gASr_Query&Product=sql2k&Queryc=builtin%
5Cadministrator&Query=builtin%
5Cadministrator&KeywordType=ALL&maxResults=150
&Titles=false&numDays=&InCC=on
I looked over most of the articles in this query and almost every single
one of them says to install/re-install the service pack to fix security
problems.
My train of thought was to try it and see what happens...
--
I was able to get in using info from the following article:
http://www.microsoft.com/sql/techinfo/tips/administration/May3.asp
We're back up and running now.
Thanks for taking the time to help, it's deeply appreciated.
--Dave
In article <eG76HDn8DHA.3404@.TK2MSFTNGP09.phx.gbl>, csmith@.digex.com
says...
> SP3 and SP3a are pretty much the same. 3a is only there if you couldn't get
> 3 to install. Which article said you the SP would fix this? Do you have a
> link? Also, how did sa not work? What did you try to do? The
> BUILTIN\Adminsitrators is completely different from SQL security model that
> sa uses. If you have the password you should be able to access the system
> using SA.
> Christian Smith
> "Dave Navarro" <dave@.dave.dave> wrote in message
> news:MPG.1a96fd2a91bf5623989786@.news-40.giganews.com...
> > In article <elZTG3m8DHA.2752@.TK2MSFTNGP09.phx.gbl>, csmith@.digex.com
> > says...
> > > If you are running in mixed security mode you can use sa.
> >
> > Tried it and it didn't work.
> >
> > I had already installed Service Pack 3, but I don't think it was 3a.
> > The knowledge base seems to indicate that re/installing the service pack
> > will enable/create the BUILTIN/Administrator account.
> >
> > Is that correct?

OH NO! Please help!

One of my IT guys "disabled" the "BUILTIN\Administrator" account in SQL
server and now we can't connect to the server using Enterprise Manager.
None of the other logins have administration privileges.
How can we either re-enable the account or get administrative access to
SQL server?
--DaveIf you are running in mixed security mode you can use sa.
Christian Smith
"Dave Navarro" <dave@.dave.dave> wrote in message
news:MPG.1a96f8a675e3bc62989785@.news-40.giganews.com...
> One of my IT guys "disabled" the "BUILTIN\Administrator" account in SQL
> server and now we can't connect to the server using Enterprise Manager.
> None of the other logins have administration privileges.
> How can we either re-enable the account or get administrative access to
> SQL server?
> --Dave|||In article <elZTG3m8DHA.2752@.TK2MSFTNGP09.phx.gbl>, csmith@.digex.com
says...
> If you are running in mixed security mode you can use sa.
Tried it and it didn't work.
I had already installed Service Pack 3, but I don't think it was 3a.
The knowledge base seems to indicate that re/installing the service pack
will enable/create the BUILTIN/Administrator account.
Is that correct?
--Dave|||Also, is it the BUILTIN\Administrator user or the BUILTIN\Administrators
group? If it is the user than the group should still be there unless
removed. What about the user that SQL is running under? Was it explicitly
given access or was it using the BUILTIN access?
"Dave Navarro" <dave@.dave.dave> wrote in message
news:MPG.1a96f8a675e3bc62989785@.news-40.giganews.com...
> One of my IT guys "disabled" the "BUILTIN\Administrator" account in SQL
> server and now we can't connect to the server using Enterprise Manager.
> None of the other logins have administration privileges.
> How can we either re-enable the account or get administrative access to
> SQL server?
> --Dave|||SP3 and SP3a are pretty much the same. 3a is only there if you couldn't get
3 to install. Which article said you the SP would fix this? Do you have a
link? Also, how did sa not work? What did you try to do? The
BUILTIN\Adminsitrators is completely different from SQL security model that
sa uses. If you have the password you should be able to access the system
using SA.
Christian Smith
"Dave Navarro" <dave@.dave.dave> wrote in message
news:MPG.1a96fd2a91bf5623989786@.news-40.giganews.com...
> In article <elZTG3m8DHA.2752@.TK2MSFTNGP09.phx.gbl>, csmith@.digex.com
> says...
> Tried it and it didn't work.
> I had already installed Service Pack 3, but I don't think it was 3a.
> The knowledge base seems to indicate that re/installing the service pack
> will enable/create the BUILTIN/Administrator account.
> Is that correct?
> --Dave|||http://support.microsoft.com/search/default.aspx?
InCC_hdn=true&Catalog=LCID%3D1033%26CDID%3DEN-US-KB%26PRODLISTSRC%
3DON&withinResults=&QuerySource=gASr_Query&Product=sql2k&Queryc=builtin%
5Cadministrator&Query=builtin%
5Cadministrator&KeywordType=ALL&maxResults=150
&Titles=false&numDays=&InCC=on
I looked over most of the articles in this query and almost every single
one of them says to install/re-install the service pack to fix security
problems.
My train of thought was to try it and see what happens...
I was able to get in using info from the following article:
http://www.microsoft.com/sql/techin...ration/May3.asp
We're back up and running now.
Thanks for taking the time to help, it's deeply appreciated.
--Dave
In article <eG76HDn8DHA.3404@.TK2MSFTNGP09.phx.gbl>, csmith@.digex.com
says...
> SP3 and SP3a are pretty much the same. 3a is only there if you couldn't g
et
> 3 to install. Which article said you the SP would fix this? Do you have
a
> link? Also, how did sa not work? What did you try to do? The
> BUILTIN\Adminsitrators is completely different from SQL security model tha
t
> sa uses. If you have the password you should be able to access the system
> using SA.
> Christian Smith
> "Dave Navarro" <dave@.dave.dave> wrote in message
> news:MPG.1a96fd2a91bf5623989786@.news-40.giganews.com...

ODBC problem

I have been trying to reconfigure specific System DSN's in the ODBC System A
dministrator thru the Control Panel. When I click on Add or Configure button
s, nothing happes. I have tried this at the Domain and Local level with the
same results. I have tried
it as a user and administrator with nothing. This is a W2k PC with SP4 (just
updated) which had MDAC 2.7. I tried to update to MDAC 2.8 which did not so
lve the problem. I reinstalled the MDAC 2.7 and the result was the same. Wha
t could be stopping the Ad
ding or Configuring process from the ODBC Control Panel?
Thanks for any help in this matter.Hello,
double click on your existing dsn and see if configure window is appear
or not.
tell me .
Thanks,
Warm Regards,
Ayaz Ahmed
Software Engineer & Web Developer
Creative Chaos (Pvt.) Ltd.
"Managing Your Digital Risk"
http://www.csquareonline.com
Karachi, Pakistan
Mobile +92 300 2280950
Office +92 21 455 2414
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!

ODBC Invalid DNS Error

I try and remove an entry from ODBC administrator, USER
DSN tab, and i get the error, INVALID DSN.
how can i remove this entry?I had this same problem and after a little searching found a fix at e.ms/archive86-2004-3-446049.html" target="_blank">http://www.mcs
e.ms/archive86-2004-3-446049.html
Here it is:
ODBC entries are controlled in the registry. I would suggest using
regedt32 or regedit (if you are on Win 20003/XP), and go to
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC and try adding full control permissions
for the affected user/groups, replacing the values in the subkeys. Good
luck.
Andy S.
2004-03-04, 12:24 pm
It took a little bit of fighting in my case to get it to take, but when it d
id I logged out then back in and it worked like a charm.
-Nick