Database Service wont start after installing SP2

I am hoping someone can help me. I am having issues changing the service account MSSQLSERVER. I changed it to Local System only due to issues installing Service Packs up SP2 Critical. I used the Configuration tool to do so. I have installed all patches up to and including Critical update ( KB 934458 ). I had a heck of a time getting them to install under custom service accounts. Now when I change the service accounts back to a custom account using the configuration tool the service wont start at all.

To be clear. The service runs fine under Local System Account, but I want to run it under a limited account. I used the config tool and made sure the permissions groups were added, but it still fails to start. I am not sure what SSL log entries below is referring to.

I am running:

SQL Server Standard Edition x86

Windows 2003 Stnd SP2

Below is the log file:

2007-09-01 23:50:16.15 spid9s Starting up database 'model'.
2007-09-01 23:50:16.20 Server Error: 17190, Severity: 16, State: 1.
2007-09-01 23:50:16.20 Server FallBack certificate initialization failed with error code: 1.
2007-09-01 23:50:16.20 Server Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.
2007-09-01 23:50:16.21 Server Error: 17182, Severity: 16, State: 1.
2007-09-01 23:50:16.21 Server TDSSNIClient initialization failed with error 0x80092004, status code 0x80.
2007-09-01 23:50:16.21 Server Error: 17182, Severity: 16, State: 1.
2007-09-01 23:50:16.21 Server TDSSNIClient initialization failed with error 0x80092004, status code 0x1.
2007-09-01 23:50:16.21 Server Error: 17826, Severity: 18, State: 3.
2007-09-01 23:50:16.21 Server Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
2007-09-01 23:50:16.21 Server Error: 17120, Severity: 16, State: 1.
2007-09-01 23:50:16.21 Server SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

I am not DBA or very heavy IT, but rather a developer wearing multiple hats, for the time being. So any help is greatly appreciated.

Thanks, DMC

Can anyone explain to me what SSL log error is referring to?

Database resource won't start after changing cluster subnet

I'm running a SQL Server 2000 SP4 2-node active/acitve cluster on
Windows 2003 Server Enterprise Edition SP1. I changed the subnet mask
of my public network config, as well as the MCS virtual subnet and two
database resource subnets (all are using the same subnet). DNS is
correctly resolving to the IP addresses for all cluster resources. I
have two databases on this cluster. After changing the subnet, the
first one starts correctly on both nodes. The second one fails to
start at the SQL Server resource on node 1, but starts correctly on
node 2. I've included the three major application log errors below.
Before I start troubleshooting any further, I'm looking for any
suggestions. Does anyone know if running the SQL Server installation
advanced options mode would make any difference? Could a machine
reboot be necessary?
Type: Error
User: N/A
Source: MSSQL$LCCSQLINST1
Category: (3)
Event ID: 17052
Description:
[sqsrvres] ODBC sqldriverconnect failed
=======================================
Type: Error
User: N/A
Source: MSSQL$LCCSQLINST1
Category: (3)
Event ID: 17052
Description:
[sqsrvres] checkODBCConnectError: sqlstate = 08001; native error = 11;
message = [Microsoft][ODBC SQL Server
Driver][DBNETLIB]SQL Server does not exist or access denied.
=======================================
Type: Error
User: N/A
Source: MSSQL$LCCSQLINST1
Category: (3)
Event ID: 17052
Description:
[sqsrvres] checkODBCConnectError: sqlstate = 01000; native error = 35;
message = [Microsoft][ODBC SQL Server
Driver][DBNETLIB]ConnectionOpen (Connect()).
=======================================
Thanks,
Curt
http://support.microsoft.com/kb/244980/en-us
There's a section in there on how to change the subnet for the resources on
a SQL Server 2000 failover cluster configuration.
Sincerely,
Anthony Thomas

"Curtis Morrison" <curtmorrison@.hotmail.com> wrote in message
news:1174920700.449721.209260@.l77g2000hsb.googlegr oups.com...
> I'm running a SQL Server 2000 SP4 2-node active/acitve cluster on
> Windows 2003 Server Enterprise Edition SP1. I changed the subnet mask
> of my public network config, as well as the MCS virtual subnet and two
> database resource subnets (all are using the same subnet). DNS is
> correctly resolving to the IP addresses for all cluster resources. I
> have two databases on this cluster. After changing the subnet, the
> first one starts correctly on both nodes. The second one fails to
> start at the SQL Server resource on node 1, but starts correctly on
> node 2. I've included the three major application log errors below.
> Before I start troubleshooting any further, I'm looking for any
> suggestions. Does anyone know if running the SQL Server installation
> advanced options mode would make any difference? Could a machine
> reboot be necessary?
> Type: Error
> User: N/A
> Source: MSSQL$LCCSQLINST1
> Category: (3)
> Event ID: 17052
> Description:
> [sqsrvres] ODBC sqldriverconnect failed
> =======================================
> Type: Error
> User: N/A
> Source: MSSQL$LCCSQLINST1
> Category: (3)
> Event ID: 17052
> Description:
> [sqsrvres] checkODBCConnectError: sqlstate = 08001; native error = 11;
> message = [Microsoft][ODBC SQL Server
> Driver][DBNETLIB]SQL Server does not exist or access denied.
> =======================================
> Type: Error
> User: N/A
> Source: MSSQL$LCCSQLINST1
> Category: (3)
> Event ID: 17052
> Description:
> [sqsrvres] checkODBCConnectError: sqlstate = 01000; native error = 35;
> message = [Microsoft][ODBC SQL Server
> Driver][DBNETLIB]ConnectionOpen (Connect()).
> =======================================
> Thanks,
> Curt
>

database owners

As I am making\changing databases I have, I started thinking about who should be the owners of what database.

Should they all be owned by sa or should I break them out? Like the WebAppDB1 is owned by BJohnson10, who is works mainly with this db as he is lead developer of the Web App that uses the database.

If you need any additional info, reply.

Thank You in advance!!!Hi Unotech

This is a great question, unfortunately there isnt a simple answer.

If you create objects when logged in as sa, then they by default become the porperty of dbo. This seems to be what happens in most databases, and isnt a problem.

If you have other users logging on, and creating objects from their own accounts, then any objects they create will be owned by them. In your example this is BJohnson10. This isnt a problem either.

However now you have the situation where some objects are owned by dbo, and some are owned by BJohnson10, so when a developer comes to write some T-SQL, they have to know who owns the object they want to refer to, and explicitly refer to them using the fully qualified name like this

<Owner>.<Object Name> or BJohnson10.Table1

For objects owned by dbo, this is easier as any object reference automatically defaults to dbo as the owner, so can be referenced just as <Object Name> or Table2. Although the fully qualified name is dbo.Table2, the system manages the dbo part by default.

Another dimension to this whole question is that of security. For more information on creating secure databases solutions, take a look at the latest materials on this at

http://msdn.microsoft.com/practices/compcat/default.aspx?pull=/library/en-us/dnnetsec/html/threatcounter.asp
and
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnnetsec/html/secnetlpMSDN.asp?frame=true

Regards

Steve

database owners

As I am making\changing databases I have, I started thinking about who should be the owners of what database.

Should they all be owned by sa or should I break them out? Like the WebAppDB1 is owned by BJohnson10, who is works mainly with this db as he is lead developer of the Web App that uses the database.

If you need any additional info, reply.

Thank You in advance!!!Hi Unotech

This is a great question, unfortunately there isnt a simple answer.

If you create objects when logged in as sa, then they by default become the porperty of dbo. This seems to be what happens in most databases, and isnt a problem.

If you have other users logging on, and creating objects from their own accounts, then any objects they create will be owned by them. In your example this is BJohnson10. This isnt a problem either.

However now you have the situation where some objects are owned by dbo, and some are owned by BJohnson10, so when a developer comes to write some T-SQL, they have to know who owns the object they want to refer to, and explicitly refer to them using the fully qualified name like this

<Owner>.<Object Name> or BJohnson10.Table1

For objects owned by dbo, this is easier as any object reference automatically defaults to dbo as the owner, so can be referenced just as <Object Name> or Table2. Although the fully qualified name is dbo.Table2, the system manages the dbo part by default.

Another dimension to this whole question is that of security. For more information on creating secure databases solutions, take a look at the latest materials on this at

http://msdn.microsoft.com/practices/compcat/default.aspx?pull=/library/en-us/dnnetsec/html/threatcounter.asp
and
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnnetsec/html/secnetlpMSDN.asp?frame=true

Regards

Steve