mssqlserver service user profile

greetings, I am trying to get MSSQLserver service to get
started under LocalSystem account. Where can I get info.
regarding this? I am currently starting the MSSQLserver
service under a network user that also has SQL2k profile
with admin role. What user is LocalSystem using. Thanks
for any info. you can send my way.
Sincerely,FredPerusing several on-line book topics, the following comprises some of the
information surrounding the Local System account:
The local system account does not require a password, does not have network
access rights in Windows 2000, Windows XP, and Windows Server 2003, and
restricts your SQL Server installation from interacting with other servers.
==Run SQL Server services with the lowest possible privileges. Associate SQL
Server services with Windows accounts.
==In Windows NT/2000, the Local System account is generally understood to mean
the operating system itself. Selecting the Local System account always
works. However, this account has no network access rights. Therefore, if
you want to integrate more than one SQL Server on your network or integrate
SQL Server with other BackOffice services such as Microsoft Exchange Server,
you should run the SQL Server services under a user account.
--
Keith Wilson
This posting is provided "AS IS" without express or implied warranty,
guarantee, or rights.
"fred ghaffari" <fred_ghaffari@.yahoo.com> wrote in message
news:014301c34c8b$1418ca80$a401280a@.phx.gbl...
> greetings, I am trying to get MSSQLserver service to get
> started under LocalSystem account. Where can I get info.
> regarding this? I am currently starting the MSSQLserver
> service under a network user that also has SQL2k profile
> with admin role. What user is LocalSystem using. Thanks
> for any info. you can send my way.
> Sincerely,Fred

MsSql7 merge replication error

Greetings colleagues!

I recently set up replication between a Windows2000/Mssql7 server set up as distributor/publisher, and outside the firewall, an NT4/Mssql7 server.

I tried to set up Merge replication and initially i got the error 14010 whenever i tried to push a publication from the dist./pub. to the subscriber. This i fixed by having an alias created within the domain "inside" the firewall protected area, for the server in the DMZ(which was known until then only by its IP number).
I simply canceled the test publications and recreated them.

At first glance everything seemed to work perfectly until i got the error for the merge agent: 20084 , subscription cannot be accepted by subscriber database, An error i understand only to appear in the case of PULL subscription, yet i had only used PUSH subscriptions from the dist./pub. server.

I have to admit i'm mystified by this error, and having perused books online, Microsoft/technet and other sources i'm no closer to solving the problem.

I would really appreciated any help in fixing the problem and get my replication running.
Thank you very much, Vincent Seghers, Programmer-Analyst
Gent.beThe problem turned out to be a reference to a server on its actual IP "name" and not its nam. I declared an Alias (lettername short, no special characters) in the Client Network utility and it worked fine from then on.

Originally posted by VincentJS
Greetings colleagues!

I recently set up replication between a Windows2000/Mssql7 server set up as distributor/publisher, and outside the firewall, an NT4/Mssql7 server.

I tried to set up Merge replication and initially i got the error 14010 whenever i tried to push a publication from the dist./pub. to the subscriber. This i fixed by having an alias created within the domain "inside" the firewall protected area, for the server in the DMZ(which was known until then only by its IP number).
I simply canceled the test publications and recreated them.

At first glance everything seemed to work perfectly until i got the error for the merge agent: 20084 , subscription cannot be accepted by subscriber database, An error i understand only to appear in the case of PULL subscription, yet i had only used PUSH subscriptions from the dist./pub. server.

I have to admit i'm mystified by this error, and having perused books online, Microsoft/technet and other sources i'm no closer to solving the problem.

I would really appreciated any help in fixing the problem and get my replication running.
Thank you very much, Vincent Seghers, Programmer-Analyst
Gent.be

MSSQL Server 2005 reported account locked out for user 'sa'

Greetings,

I receive an error message in event log when i try to connect to the Database Server using ODBC on a client machine. The database server is running on Windows 2003 Server Standard Edition and the client machine is Windows XP Professional. Following is the error message from the event log:

2147467259 - [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'sa' because the account is currently locked out. The system administrator can unlock it.

What causes the error to occur and how to resolve it?Appreciate for your assistence.

Thanks and regards,

Viknes

That error message means that the number of unsuccessful attempts to connect as the ‘sa’ account on your server and triggered the lockout policy on SQL Server 2005 for this account.

I would recommend verifying the logs and trying to find out the reason why the account was locked out. It is possible that one of your applications is using an outdated password and it needs to be fixed, but it may also be possible it was an automated attack trying to guess the SA password.

The following links will hopefully help you to resolve your problem, but if you have any further question or if the documentation is not clear enough, please let us know:

· Password Policy (http://msdn2.microsoft.com/en-us/library/ms161959.aspx)

· Alter Login (TSQL) (http://msdn2.microsoft.com/en-us/library/ms189828.aspx)

· Changing password programmatically (http://msdn2.microsoft.com/en-us/library/ms131024.aspx)

-Raul Garcia

SDE/T

SQL Server Engine

|||Also remember that SQL Server accounts can now use Windows Security policies on whiche SQL Server is running(Password complexity, password expiration, etc.) This only works for Windows Server 2003