RE: SQL 2000 Agent jobs in a non-domain environment

Tech-Archive recommends: Fix windows errors by optimizing your registry

petery@xxxxxxxxxxxxxxxxxxxx ("Peter Yang[MSFT]") wrote in
news:07AuRwGEIHA.360@xxxxxxxxxxxxxxxxxxxxxx:

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\Services\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.aspx?scid=KB;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 help 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 help 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

.

Relevant Pages

  • Re: Implementing row-level security (SQL/AD)
    ... (This has been implemented in both Access and for SQL ... >>> User account details are entered into a form and then I use a stored ... >>> the current database role and gets the current user's employeeid ... >>> The link between the login and an employee record is the hurdle I ...
    (comp.databases.ms-access)
  • Re: Problems connecting to SQL Server
    ... I sat down on the SQL 7 Server and used the SQL ... this with the SA user account / password combination. ... set up the DSN because the application that uses the DSN must supply a ... So, now to MDAC. ...
    (microsoft.public.sqlserver.clients)
  • Re: Sicherheitsupdate installieren
    ... This error occurs when the installation program can't ... start the SQL Server ... invalid user account, user account does not have permission to start ... Hoffe, das Hilft. ...
    (microsoft.public.de.sqlserver)
  • I see whats wrong with forced protocol encryption now! Heres the easiest solution.
    ... Assuming you have a box ready for an SQL install. ... Create yourself an unprivileged user account. ... Install SQL server. ...
    (microsoft.public.sqlserver.security)
  • Re: Need to create SQL-logon-user, any VB code avalable?
    ... This document tells you what you need to do to set up a user account for ... the MSSQLSERVER service. ... > good but now I need to create a user that I will use to start the SQL ... > the SQL server account on all machines to be exactly the same. ...
    (microsoft.public.sqlserver.msde)