accessing data base from remote computer

we have sql 2005 standard edition. i was trying ( unsuccessfully ) to configure RAS on server 2003 to allow the server to authentificate vpn requests. i don't know how but the next day people started complaining about their mapped network drives being disconnected, and now no one can connect to the database via the network, eventhough they still have access to the server, and the network drives were remapped.

Any errors or information in event log for such behaviour?

http://www.microsoft.com/technet/community/chats/trans/windowsnet/win0608.mspx & http://www.tacteam.net/isaserverorg/vpnkitbeta2/vpnclientbrowsing.htm fyi.

I believe this is more based on Windows side question than to SQL Server related.

|||actually now that you mention it, there is a message that keeps showing up since about the time i started playing around with RAS. it is from NfsSvr. it says mapping information could not be obtained from user mapping. another attempt will be made in 30 minutes. this message first appeared about noon on fri. however we started having trouble late thur. the message repeats itself every 30 minutes.

accessing data base from remote computer

we have sql 2005 standard edition. i was trying ( unsuccessfully ) to configure RAS on server 2003 to allow the server to authentificate vpn requests. i don't know how but the next day people started complaining about their mapped network drives being disconnected, and now no one can connect to the database via the network, eventhough they still have access to the server, and the network drives were remapped.

Any errors or information in event log for such behaviour?

http://www.microsoft.com/technet/community/chats/trans/windowsnet/win0608.mspx & http://www.tacteam.net/isaserverorg/vpnkitbeta2/vpnclientbrowsing.htm fyi.

I believe this is more based on Windows side question than to SQL Server related.

|||actually now that you mention it, there is a message that keeps showing up since about the time i started playing around with RAS. it is from NfsSvr. it says mapping information could not be obtained from user mapping. another attempt will be made in 30 minutes. this message first appeared about noon on fri. however we started having trouble late thur. the message repeats itself every 30 minutes.

Access to SQL Server 2000 remotely

I have installed SQL Server at my home computer. I can access from another
computer over internet. But from my company, I can't.
I talk to IT administrator, but he doesn't understand a lot abou this issue.
Any help?
What th IT should do to I have access?
Thanks,
JoseYou will need to allow the appropiate ports on your firewall. SQL
Server uses by default 1433 (which you might have changed during
install or configuration) unless you don=B4t allow this port on the
firewall you won=B4t be able to access the Server.
Most companies do not open these ports and do not even consider doing
it (which is recommended)
HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de
--|||IT probably has the port blocked on the firewall, as they should. Let them
know the port your SQL Server is using (viewable in the SQL Server Errorlog
if you are not sure)
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Jos" <Jos@.discussions.microsoft.com> wrote in message
news:2830F020-B38D-45A1-A490-5BF48A26269A@.microsoft.com...
>I have installed SQL Server at my home computer. I can access from another
> computer over internet. But from my company, I can't.
> I talk to IT administrator, but he doesn't understand a lot abou this
> issue.
> Any help?
> What th IT should do to I have access?
> Thanks,
> Jose
>|||I'm just testing...
My SQL Server is configured to port 1433, is it possible to configure to
another port? For example port 80 only to tensting
Thanks
"Jens" wrote:

> You will need to allow the appropiate ports on your firewall. SQL
> Server uses by default 1433 (which you might have changed during
> install or configuration) unless you don′t allow this port on the
> firewall you won′t be able to access the Server.
> Most companies do not open these ports and do not even consider doing
> it (which is recommended)
> HTH, Jens K. Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
>|||How can i see the ports available?
Thanks
"Kevin3NF" wrote:

> IT probably has the port blocked on the firewall, as they should. Let the
m
> know the port your SQL Server is using (viewable in the SQL Server Errorlo
g
> if you are not sure)
> --
> Kevin Hill
> 3NF Consulting
> http://www.3nf-inc.com/NewsGroups.htm
> Real-world stuff I run across with SQL Server:
> http://kevin3nf.blogspot.com
>
> "José" <Jos@.discussions.microsoft.com> wrote in message
> news:2830F020-B38D-45A1-A490-5BF48A26269A@.microsoft.com...
>
>|||Most likely through the firewall configuration utility...I'm not a network
guy, so I can't really assist you much there
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Jose Perdigao" <JosePerdigao@.discussions.microsoft.com> wrote in message
news:2980F9B4-FA99-4D1F-925A-42C95F039AE4@.microsoft.com...[vbcol=seagreen]
> How can i see the ports available?
> Thanks
> "Kevin3NF" wrote:
>|||You can use a microsoft telnet tool to find out whether you can telnet into
the destination server on a particular port. On the destination server side,
do a netstats to find out the list of portnumbers that are already being
used.
By default, 1433 is the port no that sql server listens on. You can change
it using server network utility. However
when the client tries to connect, make sure that the client network uility
is also configured with the port number changes.
thks,
Mani
"Jose Perdigao" <JosePerdigao@.discussions.microsoft.com> wrote in message
news:2980F9B4-FA99-4D1F-925A-42C95F039AE4@.microsoft.com...[vbcol=seagreen]
> How can i see the ports available?
> Thanks
> "Kevin3NF" wrote:
>|||Where Can I find microsoft telnet tool? I tried to find microsoft downloads
but I didn't find.
Could you help me?
Thanks
"Manikanth" wrote:

> You can use a microsoft telnet tool to find out whether you can telnet int
o
> the destination server on a particular port. On the destination server sid
e,
> do a netstats to find out the list of portnumbers that are already being
> used.
> By default, 1433 is the port no that sql server listens on. You can change
> it using server network utility. However
> when the client tries to connect, make sure that the client network uility
> is also configured with the port number changes.
> thks,
> Mani
>
> "Jose Perdigao" <JosePerdigao@.discussions.microsoft.com> wrote in message
> news:2980F9B4-FA99-4D1F-925A-42C95F039AE4@.microsoft.com...
>
>|||You can use the hyperterminal software to check if you can telnet into that
remote host server on tcp/ip 1433. YOu can find that hyperterminal under
accessories-->communication
thks,
Manikanth
"Jose Perdigao" <JosePerdigao@.discussions.microsoft.com> wrote in message
news:95A1ADE8-C3EE-4878-A81C-3A8AE2075E64@.microsoft.com...[vbcol=seagreen]
> Where Can I find microsoft telnet tool? I tried to find microsoft
> downloads
> but I didn't find.
> Could you help me?
> Thanks
> "Manikanth" wrote:
>|||You can also try by Start -> Run -> cmd
and then write the comand
telnet <server_name> <port_number>
this will run telnet. If screen goes black and cursor will show you have
acces to the serwer.
Mariusz Koprowski
"Jose Perdigao" <JosePerdigao@.discussions.microsoft.com> wrote in message
news:95A1ADE8-C3EE-4878-A81C-3A8AE2075E64@.microsoft.com...[vbcol=seagreen]
> Where Can I find microsoft telnet tool? I tried to find microsoft
> downloads
> but I didn't find.
> Could you help me?
> Thanks
> "Manikanth" wrote:
>

Access to SQL Server 2000 remotely

I have installed SQL Server at my home computer. I can access from another
computer over internet. But from my company, I can't.
I talk to IT administrator, but he doesn't understand a lot abou this issue.
Any help?
What th IT should do to I have access?
Thanks,
Jose
You will need to allow the appropiate ports on your firewall. SQL
Server uses by default 1433 (which you might have changed during
install or configuration) unless you dont allow this port on the
firewall you wont be able to access the Server.
Most companies do not open these ports and do not even consider doing
it (which is recommended)
HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de
|||IT probably has the port blocked on the firewall, as they should. Let them
know the port your SQL Server is using (viewable in the SQL Server Errorlog
if you are not sure)
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Jos" <Jos@.discussions.microsoft.com> wrote in message
news:2830F020-B38D-45A1-A490-5BF48A26269A@.microsoft.com...
>I have installed SQL Server at my home computer. I can access from another
> computer over internet. But from my company, I can't.
> I talk to IT administrator, but he doesn't understand a lot abou this
> issue.
> Any help?
> What th IT should do to I have access?
> Thanks,
> Jose
>
|||I'm just testing...
My SQL Server is configured to port 1433, is it possible to configure to
another port? For example port 80 only to tensting
Thanks
"Jens" wrote:

> You will need to allow the appropiate ports on your firewall. SQL
> Server uses by default 1433 (which you might have changed during
> install or configuration) unless you don′t allow this port on the
> firewall you won′t be able to access the Server.
> Most companies do not open these ports and do not even consider doing
> it (which is recommended)
> HTH, Jens K. Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
>
|||How can i see the ports available?
Thanks
"Kevin3NF" wrote:

> IT probably has the port blocked on the firewall, as they should. Let them
> know the port your SQL Server is using (viewable in the SQL Server Errorlog
> if you are not sure)
> --
> Kevin Hill
> 3NF Consulting
> http://www.3nf-inc.com/NewsGroups.htm
> Real-world stuff I run across with SQL Server:
> http://kevin3nf.blogspot.com
>
> "José" <Jos@.discussions.microsoft.com> wrote in message
> news:2830F020-B38D-45A1-A490-5BF48A26269A@.microsoft.com...
>
>
|||Most likely through the firewall configuration utility...I'm not a network
guy, so I can't really assist you much there
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Jose Perdigao" <JosePerdigao@.discussions.microsoft.com> wrote in message
news:2980F9B4-FA99-4D1F-925A-42C95F039AE4@.microsoft.com...[vbcol=seagreen]
> How can i see the ports available?
> Thanks
> "Kevin3NF" wrote:
|||You can use a microsoft telnet tool to find out whether you can telnet into
the destination server on a particular port. On the destination server side,
do a netstats to find out the list of portnumbers that are already being
used.
By default, 1433 is the port no that sql server listens on. You can change
it using server network utility. However
when the client tries to connect, make sure that the client network uility
is also configured with the port number changes.
thks,
Mani
"Jose Perdigao" <JosePerdigao@.discussions.microsoft.com> wrote in message
news:2980F9B4-FA99-4D1F-925A-42C95F039AE4@.microsoft.com...[vbcol=seagreen]
> How can i see the ports available?
> Thanks
> "Kevin3NF" wrote:
|||Where Can I find microsoft telnet tool? I tried to find microsoft downloads
but I didn't find.
Could you help me?
Thanks
"Manikanth" wrote:

> You can use a microsoft telnet tool to find out whether you can telnet into
> the destination server on a particular port. On the destination server side,
> do a netstats to find out the list of portnumbers that are already being
> used.
> By default, 1433 is the port no that sql server listens on. You can change
> it using server network utility. However
> when the client tries to connect, make sure that the client network uility
> is also configured with the port number changes.
> thks,
> Mani
>
> "Jose Perdigao" <JosePerdigao@.discussions.microsoft.com> wrote in message
> news:2980F9B4-FA99-4D1F-925A-42C95F039AE4@.microsoft.com...
>
>
|||You can use the hyperterminal software to check if you can telnet into that
remote host server on tcp/ip 1433. YOu can find that hyperterminal under
accessories-->communication
thks,
Manikanth
"Jose Perdigao" <JosePerdigao@.discussions.microsoft.com> wrote in message
news:95A1ADE8-C3EE-4878-A81C-3A8AE2075E64@.microsoft.com...[vbcol=seagreen]
> Where Can I find microsoft telnet tool? I tried to find microsoft
> downloads
> but I didn't find.
> Could you help me?
> Thanks
> "Manikanth" wrote:

Access Reporting Web Service from a remote computer

I just installed SQL Server 2005 and reporting services in my home
computer (XP). From a different computer in my basement connected via
peer to peer network I am able to connect to SQL Server installed in
the computer upstairs byusing a SQL Server login.
I have installed only the client components of SQL Server 2005 in my
computer at the basement. I am now trying to add a web reference to
the reporting services web services from my computer in the basement
by typing in
URL:http:/servername/reportserver/reportservice2005.asmx?wsdl
but I get the following error...
"The page cannot be displayed
The page you are looking for is currently unavailable. The Web site
might be experiencing technical difficulties, or you may need to
adjust your browser settings. "
What am I doing wrong? I am new to this so it is very likely that I am
doing something wrong.
I am able to access page when I paste the same URL in my computer
upstairs where I instaled the reporting services.
My main objective is to try and call the RS web services from the
computer in the basement.
My question is what do I need to do so that I can add web references
of reporting services from a remote computer?
Any help in this reagrd will be greatly appreciated. Any links
pertaining to this will also be very helpful.
ThanksHey why dont you write some asp.net code using web services. I dont know why
you are using directly URL, moreover to do what ?
To access remote of web services you need to change it in config about the
state server settings.
Amarnath
"shub" wrote:
> I just installed SQL Server 2005 and reporting services in my home
> computer (XP). From a different computer in my basement connected via
> peer to peer network I am able to connect to SQL Server installed in
> the computer upstairs byusing a SQL Server login.
> I have installed only the client components of SQL Server 2005 in my
> computer at the basement. I am now trying to add a web reference to
> the reporting services web services from my computer in the basement
> by typing in
> URL:http:/servername/reportserver/reportservice2005.asmx?wsdl
> but I get the following error...
> "The page cannot be displayed
> The page you are looking for is currently unavailable. The Web site
> might be experiencing technical difficulties, or you may need to
> adjust your browser settings. "
> What am I doing wrong? I am new to this so it is very likely that I am
> doing something wrong.
> I am able to access page when I paste the same URL in my computer
> upstairs where I instaled the reporting services.
> My main objective is to try and call the RS web services from the
> computer in the basement.
> My question is what do I need to do so that I can add web references
> of reporting services from a remote computer?
> Any help in this reagrd will be greatly appreciated. Any links
> pertaining to this will also be very helpful.
> Thanks
>

Access denied starting SQL Server after joining to new Windows domain

Hi, I made following steps:
1. Remove the SQL Server 2000 computer (W2k3) from old Windows domain
2. The same computer joined to new Windows domain (newdomain)
3. On the Domain Controler (W2k3) I create an domain account
SQLLaunch, which is a member of Domain Users group.
4. On the SQL Server 2003 computer I changed the SQL Server service
startup account to SQLStart@.newdomain account. The same thing made I
with the SQL Server Agent Service. Both the SQL Server Service and SQL
Server Agent start automatically when OS starts.
after these steps I tried to start the SQL Server service, but the
SQL Server did not start. Error message dialog appears as follows:
"Could not start the MSSQLSERVER service on Local Computer
Error 5: Access denied"
After I login to the SQL Server computer using SQLStart@.newdomain
account and try to start the sqlservr.exe in SQL Server home directory
similar error dialog appears:
"Access denied"
first after I made the SQLStart@.newdomain account a member of
the local Administrator group on ther SQL Server computer, everything
is going well.
What can I do to avoid to grant the Administrator's rights to the
SQLStart@.newdomain (in order to
minimize risk of exploits - it is not the right way to grant the
Administrator's rights). The desire is to use a domain account
without any Administration rights. Can anyone help me?
thanks
LiborI don't think that the account needs full admin rights to the server, but it
needs the "log on as a service" rights. When you set the account that runs
the service, the OS will automatically grant this right. I'd expect though
that you need to be logged on with an account that has the rights to grant
this rights to do it. In other words, try to log on the the server as
Administrator (or another account with admin rights) and then set the
account for SQLSERVER and SQLServerAgent service. Then the account should be
granted rights to log on as a service. Then try to restart the server (or
just the service). Remember to remove the SQL acounts from the servers admin
group before you test it.
Regards
Steen
Libor Forejtnik wrote:
> Hi, I made following steps:
> 1. Remove the SQL Server 2000 computer (W2k3) from old Windows domain
> 2. The same computer joined to new Windows domain (newdomain)
> 3. On the Domain Controler (W2k3) I create an domain account
> SQLLaunch, which is a member of Domain Users group.
> 4. On the SQL Server 2003 computer I changed the SQL Server service
> startup account to SQLStart@.newdomain account. The same thing made I
> with the SQL Server Agent Service. Both the SQL Server Service and SQL
> Server Agent start automatically when OS starts.
> after these steps I tried to start the SQL Server service, but the
> SQL Server did not start. Error message dialog appears as follows:
> "Could not start the MSSQLSERVER service on Local Computer
> Error 5: Access denied"
> After I login to the SQL Server computer using SQLStart@.newdomain
> account and try to start the sqlservr.exe in SQL Server home directory
> similar error dialog appears:
> "Access denied"
> first after I made the SQLStart@.newdomain account a member of
> the local Administrator group on ther SQL Server computer, everything
> is going well.
> What can I do to avoid to grant the Administrator's rights to the
> SQLStart@.newdomain (in order to
> minimize risk of exploits - it is not the right way to grant the
> Administrator's rights). The desire is to use a domain account
> without any Administration rights. Can anyone help me?
> thanks
> Libor|||Thank for this usefull advice. There is another way to solve the
problem too. Simply reinstall the server with the option
"registry rebuild". I guess, it makes the same things as You
recomended. In addition, the startup account must be
registered as a SQL Server login.
Unfortunatelly, starting the SQLServerAgent needs to have the startup
account a member of the SQL Server System Administration group.
But this is not a critical for me.
Libor
On Wed, 9 Mar 2005 10:08:37 +0100, "Steen Persson"
<SPE@.REMOVEdatea.dk> wrote:

>I don't think that the account needs full admin rights to the server, but i
t
>needs the "log on as a service" rights. When you set the account that runs
>the service, the OS will automatically grant this right. I'd expect though
>that you need to be logged on with an account that has the rights to grant
>this rights to do it. In other words, try to log on the the server as
>Administrator (or another account with admin rights) and then set the
>account for SQLSERVER and SQLServerAgent service. Then the account should b
e
>granted rights to log on as a service. Then try to restart the server (or
>just the service). Remember to remove the SQL acounts from the servers admi
n
>group before you test it.
>Regards
>Steen
>Libor Forejtnik wrote:
>

Access denied starting SQL Server after joining to new Windows domain

Hi, I made following steps:
1. Remove the SQL Server 2000 computer (W2k3) from old Windows domain
2. The same computer joined to new Windows domain (newdomain)
3. On the Domain Controler (W2k3) I create an domain account
SQLLaunch, which is a member of Domain Users group.
4. On the SQL Server 2003 computer I changed the SQL Server service
startup account to SQLStart@.newdomain account. The same thing made I
with the SQL Server Agent Service. Both the SQL Server Service and SQL
Server Agent start automatically when OS starts.
after these steps I tried to start the SQL Server service, but the
SQL Server did not start. Error message dialog appears as follows:
"Could not start the MSSQLSERVER service on Local Computer
Error 5: Access denied"
After I login to the SQL Server computer using SQLStart@.newdomain
account and try to start the sqlservr.exe in SQL Server home directory
similar error dialog appears:
"Access denied"
first after I made the SQLStart@.newdomain account a member of
the local Administrator group on ther SQL Server computer, everything
is going well.
What can I do to avoid to grant the Administrator's rights to the
SQLStart@.newdomain (in order to
minimize risk of exploits - it is not the right way to grant the
Administrator's rights). The desire is to use a domain account
without any Administration rights. Can anyone help me?
thanks
Libor
I don't think that the account needs full admin rights to the server, but it
needs the "log on as a service" rights. When you set the account that runs
the service, the OS will automatically grant this right. I'd expect though
that you need to be logged on with an account that has the rights to grant
this rights to do it. In other words, try to log on the the server as
Administrator (or another account with admin rights) and then set the
account for SQLSERVER and SQLServerAgent service. Then the account should be
granted rights to log on as a service. Then try to restart the server (or
just the service). Remember to remove the SQL acounts from the servers admin
group before you test it.
Regards
Steen
Libor Forejtnik wrote:
> Hi, I made following steps:
> 1. Remove the SQL Server 2000 computer (W2k3) from old Windows domain
> 2. The same computer joined to new Windows domain (newdomain)
> 3. On the Domain Controler (W2k3) I create an domain account
> SQLLaunch, which is a member of Domain Users group.
> 4. On the SQL Server 2003 computer I changed the SQL Server service
> startup account to SQLStart@.newdomain account. The same thing made I
> with the SQL Server Agent Service. Both the SQL Server Service and SQL
> Server Agent start automatically when OS starts.
> after these steps I tried to start the SQL Server service, but the
> SQL Server did not start. Error message dialog appears as follows:
> "Could not start the MSSQLSERVER service on Local Computer
> Error 5: Access denied"
> After I login to the SQL Server computer using SQLStart@.newdomain
> account and try to start the sqlservr.exe in SQL Server home directory
> similar error dialog appears:
> "Access denied"
> first after I made the SQLStart@.newdomain account a member of
> the local Administrator group on ther SQL Server computer, everything
> is going well.
> What can I do to avoid to grant the Administrator's rights to the
> SQLStart@.newdomain (in order to
> minimize risk of exploits - it is not the right way to grant the
> Administrator's rights). The desire is to use a domain account
> without any Administration rights. Can anyone help me?
> thanks
> Libor
|||Thank for this usefull advice. There is another way to solve the
problem too. Simply reinstall the server with the option
"registry rebuild". I guess, it makes the same things as You
recomended. In addition, the startup account must be
registered as a SQL Server login.
Unfortunatelly, starting the SQLServerAgent needs to have the startup
account a member of the SQL Server System Administration group.
But this is not a critical for me.
Libor
On Wed, 9 Mar 2005 10:08:37 +0100, "Steen Persson"
<SPE@.REMOVEdatea.dk> wrote:

>I don't think that the account needs full admin rights to the server, but it
>needs the "log on as a service" rights. When you set the account that runs
>the service, the OS will automatically grant this right. I'd expect though
>that you need to be logged on with an account that has the rights to grant
>this rights to do it. In other words, try to log on the the server as
>Administrator (or another account with admin rights) and then set the
>account for SQLSERVER and SQLServerAgent service. Then the account should be
>granted rights to log on as a service. Then try to restart the server (or
>just the service). Remember to remove the SQL acounts from the servers admin
>group before you test it.
>Regards
>Steen
>Libor Forejtnik wrote:
>

Access denied starting SQL Server after joining to new Windows domain

Hi, I made following steps:
1. Remove the SQL Server 2000 computer (W2k3) from old Windows domain
2. The same computer joined to new Windows domain (newdomain)
3. On the Domain Controler (W2k3) I create an domain account
SQLLaunch, which is a member of Domain Users group.
4. On the SQL Server 2003 computer I changed the SQL Server service
startup account to SQLStart@.newdomain account. The same thing made I
with the SQL Server Agent Service. Both the SQL Server Service and SQL
Server Agent start automatically when OS starts.
after these steps I tried to start the SQL Server service, but the
SQL Server did not start. Error message dialog appears as follows:
"Could not start the MSSQLSERVER service on Local Computer
Error 5: Access denied"
After I login to the SQL Server computer using SQLStart@.newdomain
account and try to start the sqlservr.exe in SQL Server home directory
similar error dialog appears:
"Access denied"
first after I made the SQLStart@.newdomain account a member of
the local Administrator group on ther SQL Server computer, everything
is going well.
What can I do to avoid to grant the Administrator's rights to the
SQLStart@.newdomain (in order to
minimize risk of exploits - it is not the right way to grant the
Administrator's rights). The desire is to use a domain account
without any Administration rights. Can anyone help me?
thanks
LiborHello Libor,
From your very detailed discription I believe your error is nothing to with
SQL Server, and everything to do with permission on the Server. The reason I
believe this is that firstly the errors your getting 'Access Denied' is not a
SQL Server error, but a Server 2003 error, secondly by putting into your
local administration group you can do it.
This is what I would do to check this out.
NB you will need down time for this...
1. Take the domain id out of the Local Administrators
2. By hand try to access the directories you Server Server lives in,
followed by the Log and data files.
If you get an Access Denied message then you will need to modify the access
rights of the directory to include your new domain account.
Peter
"Cauliflower is nothing but cabbage with a college education."
Mark Twain
"Libor Forejtnik" wrote:
> Hi, I made following steps:
> 1. Remove the SQL Server 2000 computer (W2k3) from old Windows domain
> 2. The same computer joined to new Windows domain (newdomain)
> 3. On the Domain Controler (W2k3) I create an domain account
> SQLLaunch, which is a member of Domain Users group.
> 4. On the SQL Server 2003 computer I changed the SQL Server service
> startup account to SQLStart@.newdomain account. The same thing made I
> with the SQL Server Agent Service. Both the SQL Server Service and SQL
> Server Agent start automatically when OS starts.
> after these steps I tried to start the SQL Server service, but the
> SQL Server did not start. Error message dialog appears as follows:
> "Could not start the MSSQLSERVER service on Local Computer
> Error 5: Access denied"
> After I login to the SQL Server computer using SQLStart@.newdomain
> account and try to start the sqlservr.exe in SQL Server home directory
> similar error dialog appears:
> "Access denied"
> first after I made the SQLStart@.newdomain account a member of
> the local Administrator group on ther SQL Server computer, everything
> is going well.
> What can I do to avoid to grant the Administrator's rights to the
> SQLStart@.newdomain (in order to
> minimize risk of exploits - it is not the right way to grant the
> Administrator's rights). The desire is to use a domain account
> without any Administration rights. Can anyone help me?
> thanks
> Libor
>|||I don't think that the account needs full admin rights to the server, but it
needs the "log on as a service" rights. When you set the account that runs
the service, the OS will automatically grant this right. I'd expect though
that you need to be logged on with an account that has the rights to grant
this rights to do it. In other words, try to log on the the server as
Administrator (or another account with admin rights) and then set the
account for SQLSERVER and SQLServerAgent service. Then the account should be
granted rights to log on as a service. Then try to restart the server (or
just the service). Remember to remove the SQL acounts from the servers admin
group before you test it.
Regards
Steen
Libor Forejtnik wrote:
> Hi, I made following steps:
> 1. Remove the SQL Server 2000 computer (W2k3) from old Windows domain
> 2. The same computer joined to new Windows domain (newdomain)
> 3. On the Domain Controler (W2k3) I create an domain account
> SQLLaunch, which is a member of Domain Users group.
> 4. On the SQL Server 2003 computer I changed the SQL Server service
> startup account to SQLStart@.newdomain account. The same thing made I
> with the SQL Server Agent Service. Both the SQL Server Service and SQL
> Server Agent start automatically when OS starts.
> after these steps I tried to start the SQL Server service, but the
> SQL Server did not start. Error message dialog appears as follows:
> "Could not start the MSSQLSERVER service on Local Computer
> Error 5: Access denied"
> After I login to the SQL Server computer using SQLStart@.newdomain
> account and try to start the sqlservr.exe in SQL Server home directory
> similar error dialog appears:
> "Access denied"
> first after I made the SQLStart@.newdomain account a member of
> the local Administrator group on ther SQL Server computer, everything
> is going well.
> What can I do to avoid to grant the Administrator's rights to the
> SQLStart@.newdomain (in order to
> minimize risk of exploits - it is not the right way to grant the
> Administrator's rights). The desire is to use a domain account
> without any Administration rights. Can anyone help me?
> thanks
> Libor|||Thank for this usefull advice. There is another way to solve the
problem too. Simply reinstall the server with the option
"registry rebuild". I guess, it makes the same things as You
recomended. In addition, the startup account must be
registered as a SQL Server login.
Unfortunatelly, starting the SQLServerAgent needs to have the startup
account a member of the SQL Server System Administration group.
But this is not a critical for me.
Libor
On Wed, 9 Mar 2005 10:08:37 +0100, "Steen Persson"
<SPE@.REMOVEdatea.dk> wrote:
>I don't think that the account needs full admin rights to the server, but it
>needs the "log on as a service" rights. When you set the account that runs
>the service, the OS will automatically grant this right. I'd expect though
>that you need to be logged on with an account that has the rights to grant
>this rights to do it. In other words, try to log on the the server as
>Administrator (or another account with admin rights) and then set the
>account for SQLSERVER and SQLServerAgent service. Then the account should be
>granted rights to log on as a service. Then try to restart the server (or
>just the service). Remember to remove the SQL acounts from the servers admin
>group before you test it.
>Regards
>Steen
>Libor Forejtnik wrote:
>> Hi, I made following steps:
>> 1. Remove the SQL Server 2000 computer (W2k3) from old Windows domain
>> 2. The same computer joined to new Windows domain (newdomain)
>> 3. On the Domain Controler (W2k3) I create an domain account
>> SQLLaunch, which is a member of Domain Users group.
>> 4. On the SQL Server 2003 computer I changed the SQL Server service
>> startup account to SQLStart@.newdomain account. The same thing made I
>> with the SQL Server Agent Service. Both the SQL Server Service and SQL
>> Server Agent start automatically when OS starts.
>> after these steps I tried to start the SQL Server service, but the
>> SQL Server did not start. Error message dialog appears as follows:
>> "Could not start the MSSQLSERVER service on Local Computer
>> Error 5: Access denied"
>> After I login to the SQL Server computer using SQLStart@.newdomain
>> account and try to start the sqlservr.exe in SQL Server home directory
>> similar error dialog appears:
>> "Access denied"
>> first after I made the SQLStart@.newdomain account a member of
>> the local Administrator group on ther SQL Server computer, everything
>> is going well.
>> What can I do to avoid to grant the Administrator's rights to the
>> SQLStart@.newdomain (in order to
>> minimize risk of exploits - it is not the right way to grant the
>> Administrator's rights). The desire is to use a domain account
>> without any Administration rights. Can anyone help me?
>> thanks
>> Libor
>|||Thanks for the advice. I solved the problem by reinstalling the SQL
Server using the "Registry rebuild" option.
Libor
On Tue, 8 Mar 2005 08:41:05 -0800, Peter 'Not Peter The Spate' Nolan
<PeterNotPeterTheSpateNolan@.discussions.microsoft.com> wrote:
>Hello Libor,
>From your very detailed discription I believe your error is nothing to with
>SQL Server, and everything to do with permission on the Server. The reason I
>believe this is that firstly the errors your getting 'Access Denied' is not a
>SQL Server error, but a Server 2003 error, secondly by putting into your
>local administration group you can do it.
>This is what I would do to check this out.
>NB you will need down time for this...
>1. Take the domain id out of the Local Administrators
>2. By hand try to access the directories you Server Server lives in,
>followed by the Log and data files.
>If you get an Access Denied message then you will need to modify the access
>rights of the directory to include your new domain account.
>Peter
>"Cauliflower is nothing but cabbage with a college education."
>Mark Twain
>"Libor Forejtnik" wrote:
>> Hi, I made following steps:
>> 1. Remove the SQL Server 2000 computer (W2k3) from old Windows domain
>> 2. The same computer joined to new Windows domain (newdomain)
>> 3. On the Domain Controler (W2k3) I create an domain account
>> SQLLaunch, which is a member of Domain Users group.
>> 4. On the SQL Server 2003 computer I changed the SQL Server service
>> startup account to SQLStart@.newdomain account. The same thing made I
>> with the SQL Server Agent Service. Both the SQL Server Service and SQL
>> Server Agent start automatically when OS starts.
>> after these steps I tried to start the SQL Server service, but the
>> SQL Server did not start. Error message dialog appears as follows:
>> "Could not start the MSSQLSERVER service on Local Computer
>> Error 5: Access denied"
>> After I login to the SQL Server computer using SQLStart@.newdomain
>> account and try to start the sqlservr.exe in SQL Server home directory
>> similar error dialog appears:
>> "Access denied"
>> first after I made the SQLStart@.newdomain account a member of
>> the local Administrator group on ther SQL Server computer, everything
>> is going well.
>> What can I do to avoid to grant the Administrator's rights to the
>> SQLStart@.newdomain (in order to
>> minimize risk of exploits - it is not the right way to grant the
>> Administrator's rights). The desire is to use a domain account
>> without any Administration rights. Can anyone help me?
>> thanks
>> Libor