Locked out of Enterprise Manager

Hi all

First post - please be gentle :)

I have had a search of the forum and couldn't find a solution to this one.

On a clean install of SQL Server 2000 on a W2003 server we setup our database as normal, selected appropriate priveldges for everyone and all was well.

Until an adminsitraor accidently turned builtin\administors account to DENY access. We are now locked out of EM and I can't think of a way back in.

We can't access the database via the sa account as it is set to Windows Autentication, and we can't re-register the database for the same reason.

No other user has sufficent priveldges to update the master db or change authenticaion, or even log into EM for that matter.

I think we are snookered, but any thoughts are welcomed.

Cheers

K2Interesting.
There's also one more user that has full admin rights in SQL instance, that is local admin account. i.e., machinename\administrator
Since this user also is part of admin group, try changing it's member group to POWER USERS.
Start-->Run--> control userpasswords2
Select the ADMINISTRATOR user , choose properties and under the Group Membership change it to Power Users.
Now, it won't inherit the BUILTIN/ADMINSTRATOR group , but would still be existing in sqlserver logins as admin user.
Try connecting to sql under this local admin account!

Hopefully, it would work.
AND, please don't forget to create one more ADMIN user on the machine, before changing localadmin user to POWERUSERS :)

If you couldn't connect, you might need to rebuild the master db using rebuild utility, that will leave ur instance intact but rebuild the master db and you will need to reattach ur user dbs after wards.
c:\Program Files\Microsoft SQL Server\80\Tools\Binn\rebuildm.exe|||My first thought would be to restore the master database from before the incident. There is a small chance you can reset the logon mode to mixed authentication, though. Did you ever set a password for sa?|||Interesting.
There's also one more user that has full admin rights in SQL instance, that is local admin account. i.e., machinename\administrator
Since this user also is part of admin group, try changing it's member group to POWER USERS.
Start-->Run--> control userpasswords2
Select the ADMINISTRATOR user , choose properties and under the Group Membership change it to Power Users.
Now, it won't inherit the BUILTIN/ADMINSTRATOR group , but would still be existing in sqlserver logins as admin user.

Hi

I think this would have been a better angle to take than what we did in the end! We didn't think of that one.

In the end we did a rebuild of the master database and this worked just fine.

We did try to change the authentication mode (we had set the sa password) but it wouldn't have it.

Thanks for your help guys!

K

Lock pages in memory right on IA64 edition

I'm planing to install SQL2000 IA64 on Itanium server with win2003-IA64.
Not sure if I need to add "Lock pages in memory" right to SQL service
account or not. I know it must be used on x86 and is also recommended on x64
systems because they use AWE but on IA64 systems AWE is not used so I would
guess it's not necessary. Am I right?
Tom"Tom" <mcseman@.hotmail.com> wrote in message
news:uFRSdkGOGHA.2036@.TK2MSFTNGP14.phx.gbl...
> I'm planing to install SQL2000 IA64 on Itanium server with win2003-IA64.
> Not sure if I need to add "Lock pages in memory" right to SQL service
> account or not. I know it must be used on x86 and is also recommended on
> x64 systems because they use AWE but on IA64 systems AWE is not used so I
> would guess it's not necessary. Am I right?
>
No. My understanding is that "Lock pages in memory" is recommended on
64-bit SQL because it prevents the OS from paging out SQL Server memory
under pressure. Instead SQL Server will reduce its own memory usage when it
notices the system is under memory pressure.
David

Lock pages in memory right on IA64 edition

I'm planing to install SQL2000 IA64 on Itanium server with win2003-IA64.
Not sure if I need to add "Lock pages in memory" right to SQL service
account or not. I know it must be used on x86 and is also recommended on x64
systems because they use AWE but on IA64 systems AWE is not used so I would
guess it's not necessary. Am I right?
Tom"Tom" <mcseman@.hotmail.com> wrote in message
news:uFRSdkGOGHA.2036@.TK2MSFTNGP14.phx.gbl...
> I'm planing to install SQL2000 IA64 on Itanium server with win2003-IA64.
> Not sure if I need to add "Lock pages in memory" right to SQL service
> account or not. I know it must be used on x86 and is also recommended on
> x64 systems because they use AWE but on IA64 systems AWE is not used so I
> would guess it's not necessary. Am I right?
>
No. My understanding is that "Lock pages in memory" is recommended on
64-bit SQL because it prevents the OS from paging out SQL Server memory
under pressure. Instead SQL Server will reduce its own memory usage when it
notices the system is under memory pressure.
David

Lock pages in memory right on IA64 edition

I'm planing to install SQL2000 IA64 on Itanium server with win2003-IA64.
Not sure if I need to add "Lock pages in memory" right to SQL service
account or not. I know it must be used on x86 and is also recommended on x64
systems because they use AWE but on IA64 systems AWE is not used so I would
guess it's not necessary. Am I right?
Tom
"Tom" <mcseman@.hotmail.com> wrote in message
news:uFRSdkGOGHA.2036@.TK2MSFTNGP14.phx.gbl...
> I'm planing to install SQL2000 IA64 on Itanium server with win2003-IA64.
> Not sure if I need to add "Lock pages in memory" right to SQL service
> account or not. I know it must be used on x86 and is also recommended on
> x64 systems because they use AWE but on IA64 systems AWE is not used so I
> would guess it's not necessary. Am I right?
>
No. My understanding is that "Lock pages in memory" is recommended on
64-bit SQL because it prevents the OS from paging out SQL Server memory
under pressure. Instead SQL Server will reduce its own memory usage when it
notices the system is under memory pressure.
David
sql

localhost/reports not found

Everything works ok at work and so I decided to install it at home on Windows 2003.

For some odd reason I can run my report this way:

http://localhost/ReportServer?%2fReport+Project1%2fReportFirstTest&rs:Command=Render

But if I try this..

http://localhost/reports

all I get is "The page cannot be found"

I can also get to the report by clicking on links found on the page I get usinghttp://localhost/ReportServer

I'd guess an IIS setting got messed up somehow, anyone know?

1. Make sure that Home.aspx is a default webpage for the related web site in the IIS, or try thishttp://localhost/reports/home.aspx ; 2. Make sure that the asp.net 2.0 version is selected for this web site; 3. It's better to have an own pool for asp.net 2.0 applications in the win 2003.

Local Database Issue with SQL 2000 Install

I've got a user with a new HP desktop requesting SQL 2000 Developer Server
and Client Tools to be installed. When I install the software along with SQL
SP4, the local database shows up in Enterprise Manager. When the user logs
on to the same machine, the local database is missing in Enterprise Manager.
I had another user with the same type of permissions log on to the machine
and they get the local database to show up as well.
Why can't this particular person get the local database to show up in
Enterprise Manger when they log on? Is there a registry edit that's needed?
Any help is greatly appreciated.
Colette
Hi Colette,
Perhaps it's been removed. Have they tried just registering the server in
Enterprise Manager? (ie: right-click the SQL Servers group in the main tree
and choose the option to register a server)
HTH,
Greg
"Colette" <Colette@.discussions.microsoft.com> wrote in message
news:084583C7-EA4C-4BC5-8EA1-1D0F448FDA32@.microsoft.com...
> I've got a user with a new HP desktop requesting SQL 2000 Developer Server
> and Client Tools to be installed. When I install the software along with
> SQL
> SP4, the local database shows up in Enterprise Manager. When the user
> logs
> on to the same machine, the local database is missing in Enterprise
> Manager.
> I had another user with the same type of permissions log on to the machine
> and they get the local database to show up as well.
> Why can't this particular person get the local database to show up in
> Enterprise Manger when they log on? Is there a registry edit that's
> needed?
> Any help is greatly appreciated.
> Colette

Local Database Issue with SQL 2000 Install

I've got a user with a new HP desktop requesting SQL 2000 Developer Server
and Client Tools to be installed. When I install the software along with SQL
SP4, the local database shows up in Enterprise Manager. When the user logs
on to the same machine, the local database is missing in Enterprise Manager.
I had another user with the same type of permissions log on to the machine
and they get the local database to show up as well.
Why can't this particular person get the local database to show up in
Enterprise Manger when they log on? Is there a registry edit that's needed?
Any help is greatly appreciated.
ColetteHi Colette,
Perhaps it's been removed. Have they tried just registering the server in
Enterprise Manager? (ie: right-click the SQL Servers group in the main tree
and choose the option to register a server)
HTH,
Greg
"Colette" <Colette@.discussions.microsoft.com> wrote in message
news:084583C7-EA4C-4BC5-8EA1-1D0F448FDA32@.microsoft.com...
> I've got a user with a new HP desktop requesting SQL 2000 Developer Server
> and Client Tools to be installed. When I install the software along with
> SQL
> SP4, the local database shows up in Enterprise Manager. When the user
> logs
> on to the same machine, the local database is missing in Enterprise
> Manager.
> I had another user with the same type of permissions log on to the machine
> and they get the local database to show up as well.
> Why can't this particular person get the local database to show up in
> Enterprise Manger when they log on? Is there a registry edit that's
> needed?
> Any help is greatly appreciated.
> Colette

Local Database Issue with SQL 2000 Install

I've got a user with a new HP desktop requesting SQL 2000 Developer Server
and Client Tools to be installed. When I install the software along with SQ
L
SP4, the local database shows up in Enterprise Manager. When the user logs
on to the same machine, the local database is missing in Enterprise Manager.
I had another user with the same type of permissions log on to the machine
and they get the local database to show up as well.
Why can't this particular person get the local database to show up in
Enterprise Manger when they log on? Is there a registry edit that's needed?
Any help is greatly appreciated.
ColetteHi Colette,
Perhaps it's been removed. Have they tried just registering the server in
Enterprise Manager? (ie: right-click the SQL Servers group in the main tree
and choose the option to register a server)
HTH,
Greg
"Colette" <Colette@.discussions.microsoft.com> wrote in message
news:084583C7-EA4C-4BC5-8EA1-1D0F448FDA32@.microsoft.com...
> I've got a user with a new HP desktop requesting SQL 2000 Developer Server
> and Client Tools to be installed. When I install the software along with
> SQL
> SP4, the local database shows up in Enterprise Manager. When the user
> logs
> on to the same machine, the local database is missing in Enterprise
> Manager.
> I had another user with the same type of permissions log on to the machine
> and they get the local database to show up as well.
> Why can't this particular person get the local database to show up in
> Enterprise Manger when they log on? Is there a registry edit that's
> needed?
> Any help is greatly appreciated.
> Colette