SQL7 SP4 and 10013 error
From: Carlos Souza (carlos@geekbunker.org)
Date: 02/03/03
- Next message: bhavesh: "Run only one job with different user account"
- Previous message: x y, mvp: "SQL Server benchmarks comparing disk setups?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "Carlos Souza" <carlos@geekbunker.org> Date: Mon, 3 Feb 2003 12:17:54 -0200
Hello
After applying SP4 on SQL7 I got the error
"Operating system error 10013., An attempt was made to access a socket in a
way forbidden by its access permissions."
"Could not set up ListenOn connection '1433'.."
on SQL Server error log.
Because of this error SQL Server could not bind itself to port 1433 and I
was unable to connect to SQL Server using TCP-Ip.
I made a little researh on groups.google.com and found a post from Linda
Deng on 2002-07-30
saying
"You can change the SQL Server startup account to be one of the local
administrator account group. Or, it is recommended that you use a domain
user account that is a member of the Administrators local group".
My SQL Server is running under a domain account with no privileges except
Log On Locally and Log as a Service. I added the SQL account to the local
admins group and the SQL Server was able to bind to port 1433 and everything
start working.
I would like to know if it is really necessary to have SQL account as a
member of the local admin group. SQL account was only a domain account
because of the ideia of just giving the necessary permissions. Putting the
SQL Account in the local admin group will not lead to a security hole?
My Server is Win2k with SP3 and SQL7 with SP4.
Thanks and sorry for the poor english, Im realy trying to improve it :)
-- Carlos Souza MCSE,MCDBA, MCSA
- Next message: bhavesh: "Run only one job with different user account"
- Previous message: x y, mvp: "SQL Server benchmarks comparing disk setups?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
