I had to rebuild my SQL development computer, which runs XP Pro, and is
not a domain controller or a member of a domain.

I have SQL 2000 server (SP4) and SQL 2005 server on this development
computer. My problem here is with SQL 2000.

I used to have all of this working on SQL 2000, before the reinstall of
everything, but now I am in a strange catch-22:

Trying to manually start a job listed in SQL 2000 Agent tells me that
the SQL server agent is not running, therefore it can't be notified of
the job, so I can't start the job. (It is running.) I am using local
user accounts that are defined on the same computer to run SQL 2000
server and SQL 2000 agent under, since they need access to a shared
folder (which resides on my "main" computer).

The fix for this error (per KB article 911841) is to replace the ./SQL_
2000_Server username in the registry with <computer_name>/SQL_2000
_Server for the service. SQL 2000 can't correctly interpret the "dot"
for the local computer name.

HOWEVER, then I get the message after reboot that the SQL 2000 server
failed to start because a dependency failed. That dependency is the Net
Logon service. (Although it's not listed as an explicit dependency
under the Dependency tab of the service.)

In a non-domain computer, if you set Net Logon to start automatically,
it starts and stops and says it has nothing to do. Microsoft says that
the Net Logon service should be set to Manual on a non-domain computer.

(Apparently the Net Logon service might have work to do if it wouldn't
just STOP when it sees that it's on a non-domain computer.)

[[Extrainfo: My SQL 2000 development server is a non-domain computer
because it ONLY connects to my "main" computer. My "main" computer has
2 ethernet cards, and the other card connects out to the Internet and to
the rest of our local network.]]

----

SOOOOO, I can't change the period to a computer name per KB911841, since
that would require that Net Logon be running. I can't run Net Logon in
a non-domain computer.

And I can't follow the workaround in KB article 307288, which says to
use Local System for SQL 2000 server and agent, because this SQL 2000
server needs access to a network share, and also because using
LocalSystem for SQL 2000 server or SQL 2000 agent is a bad idea from a
security perpective (see any number of Microsoft articles, such as "10
Stepe to Secure SQL Server 2000").

I *know* that I had this working before the reinstall.

Any getting out of this catch-22, so I can start scheduled jobs
manually, would be greatly appreciated.

David Walker

Hello David,

If I understand the issue correctly, you change the dot mark with the
computer name under the following registry key, and SQL 2000 service cannot
start due to that netlogon service cannot start. If I'm off-base, please
let me know.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\MSSQL$InstanceName\

As I know, netlogon service is supposed to be started for a domain member
machine. Since you have an non-domain machine, it's not necessary.

I'm not sure which account do you use for SQL Server service? Is it a local
user account? Since your computer is not a non-domain machine, do you use a
local user account to access remote machines in your network?

You may want to try a different user account with local admin account to
test the situation. If the issue persists, please refer to the following
article to generate Alliance Edition of MPS report for reviewing.

818742.KB.EN-US Overview of the Microsoft Configuration Capture Utility
(MPS_REPORTS)
http://support.microsoft.com/default...B;EN-US;818742

Please remmove Online from my displayed email address. Thanks.

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications
<http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
<http://msdn.microsoft.com/subscriptions/support/default.aspx>.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

petery@online.microsoft.com ("Peter Yang[MSFT]") wrote in
news:07AuRwGEIHA.360@TK2MSFTNGHUB02.phx.gbl:

> Hello David,
>
> If I understand the issue correctly, you change the dot mark with the
> computer name under the following registry key, and SQL 2000 service
> cannot start due to that netlogon service cannot start. If I'm
> off-base, please let me know.
>
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\MSSQL
$InstanceName
> \
>
> As I know, netlogon service is supposed to be started for a domain
> member machine. Since you have an non-domain machine, it's not
> necessary.
>
> I'm not sure which account do you use for SQL Server service? Is it a
> local user account? Since your computer is not a non-domain machine,
> do you use a local user account to access remote machines in your
> network?
>
> You may want to try a different user account with local admin account
> to test the situation. If the issue persists, please refer to the
> following article to generate Alliance Edition of MPS report for
> reviewing.
>
> 818742.KB.EN-US Overview of the Microsoft Configuration Capture
> Utility (MPS_REPORTS)
> http://support.microsoft.com/default...B;EN-US;818742
>
> Please remmove Online from my displayed email address. Thanks.
>
> Best Regards,
>
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Community Support
> ==================================================

Sorry, but your answer didn't me at all.

It doesn't matter WHAT userid I would use for the SQL server and SQL
agent logon -- I could use any userid I wanted. They are local userids,
as I said already. I made them up myself. What the userid actually IS
has nothing to do with the problem.

The PROBLEM is that if I replace the dot with the local machine name,
then the SQL server and SQL agent services fail to start because they
want the Net Logon service running -- that service appears to be a
dependency. If I leave the dot in place, then those services start just
fine, and SQL runs just fine. But then I get the error that 911841
talks about.

And I can't run net logon in my non-domain environment.

Are you asking me to run that tool and send you the results? Which
version? The network version or the SQL version?

I doubt that either one would you. I am sure that you can
reproduce my set of conflicting problems on any non-domain computer that
has SQL installed on it.


David Walker

Hello David,

Thank you for your reply. I tried to reproduce the issue on my side by
change the objectname value of the registry key
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\MSSQLserver and I did
reproduce the issue.

I tried the following steps to fix the problem:

1. Ran services.msc, and changed the start account to "localsystem"
account. I still cannot start the service.

2. Restarted the computer and the SQL service started properly

3. Changed start account to a local user account agian, and restarted
Service. It started OK.

4. Check the registry key value objectname and it is .\localusername again.

From the test, I believe ".\localusername" shall be the proper name for
local user account. If you use "machinename\localusername", it will try to
use Netlogon service to resolve it via domain. Therefore, for a local user
account, we cannot use the 911841.

I then tried to run jobs under SQL agent entry, and it works fine. For now,
please try to change start account to localsystem and restart the machine
to fix the SQL service start issue. After that, please change the startup
account to local user account again.

As for SQL agent job issue, please capture a screen shot so that I could do
more research on the issue. As for MPSreport, please get the Alliance
Edition (general purpose).

I look forward to your reply. Thank you.

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support

================================================== ====

This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====

petery@online.microsoft.com ("Peter Yang[MSFT]") wrote in
news:jEW2ADVEIHA.1256@TK2MSFTNGHUB02.phx.gbl:

> Hello David,
>
> Thank you for your reply. I tried to reproduce the issue on my side by
> change the objectname value of the registry key
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\MSSQLserver and I
> did reproduce the issue.
>
> I tried the following steps to fix the problem:
>
> 1. Ran services.msc, and changed the start account to "localsystem"
> account. I still cannot start the service.
>
> 2. Restarted the computer and the SQL service started properly
>
> 3. Changed start account to a local user account agian, and restarted
> Service. It started OK.

Are you on a non-domain computer?

>
> 4. Check the registry key value objectname and it is .\localusername
> again.
>
> From the test, I believe ".\localusername" shall be the proper name
> for local user account. If you use "machinename\localusername", it
> will try to use Netlogon service to resolve it via domain. Therefore,
> for a local user account, we cannot use the 911841.

OK, you are contradicting what 911841 says, but I will try what you
suggest below.

>
> I then tried to run jobs under SQL agent entry, and it works fine. For
> now, please try to change start account to localsystem and restart the
> machine to fix the SQL service start issue. After that, please change
> the startup account to local user account again.
>
> As for SQL agent job issue, please capture a screen shot so that I
> could do more research on the issue. As for MPSreport, please get the
> Alliance Edition (general purpose).

OK, I will do that.

David

>
> I look forward to your reply. Thank you.
>
> Best Regards,
>
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Partner Support
>
> ================================================== ====
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights. ================================================== ====
>
>
>
>
>

petery@online.microsoft.com ("Peter Yang[MSFT]") wrote in
news:jEW2ADVEIHA.1256@TK2MSFTNGHUB02.phx.gbl:

> Hello David,
>
> Thank you for your reply. I tried to reproduce the issue on my side by
> change the objectname value of the registry key
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\MSSQLserver and I
> did reproduce the issue.
>
> I tried the following steps to fix the problem:
>
> 1. Ran services.msc, and changed the start account to "localsystem"
> account. I still cannot start the service.
>
> 2. Restarted the computer and the SQL service started properly
>
> 3. Changed start account to a local user account agian, and restarted
> Service. It started OK.
>
> 4. Check the registry key value objectname and it is .\localusername
> again.
>
> From the test, I believe ".\localusername" shall be the proper name
> for local user account. If you use "machinename\localusername", it
> will try to use Netlogon service to resolve it via domain. Therefore,
> for a local user account, we cannot use the 911841.
>
> I then tried to run jobs under SQL agent entry, and it works fine. For
> now, please try to change start account to localsystem and restart the
> machine to fix the SQL service start issue. After that, please change
> the startup account to local user account again.
>
> As for SQL agent job issue, please capture a screen shot so that I
> could do more research on the issue. As for MPSreport, please get the
> Alliance Edition (general purpose).
>
> I look forward to your reply. Thank you.
>
> Best Regards,
>
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Partner Support
>

I did all of the steps in this order, and guess what, it worked!

I don't know why you have to restart after changing the SQL service
userid to a local user account, instead of just starting it then.
Strange things are happening here.

And once I restarted many times, I was able to start the SQL agent jobs
manually like I need to.

Thank you for your . It looked like I was stuck with no way out.
Restarting after every step seems to fix things internally!

David Walker

Hello David,

Great to hear you solved the issue!

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support

================================================== ====

This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====