[THIN] Re: Secure Access Manager Repository Service stopping
- From: Timmy.Shunmugam@xxxxxxxxxxxxx
- To: thin@xxxxxxxxxxxxx
- Date: Wed, 16 Jul 2003 08:04:44 +0200
check the logon policy on the server to see that it is synced with the
domain policy. We had the issue in that the domain policy gave the account
"log on as a service right" but the local policy was not synced. Everytime
the account would not start up the service.
-----Original Message-----
From: Tony Lyne [mailto:Tony.Lyne@xxxxxxxxxxxxxxxxxx]
Sent: 15 July 2003 11:08
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Secure Access Manager Repository Service stopping
Has anyone seen the issue with MSAM where the Repository service will just
stop after a while in use. Restarting it willnot work and it generates
exception errors in the Event log.
If you change the service account to a different one (Administrator for
example) it will start. But why would it do this after working fine for
weeks. Theres nothing wrong with the original service account as its still
the service account used for the other MSAM services.
The Repository Database resides on an SQL 2kSP3a server on the same LAN.
ODBC connections are fine.
Also had a different MSAM service just stop yesterday on the Same server.
Rebooting it fixed the problem.
Tony Lyne
Senior Systems Engineer
Computerland Central
P O Box 1470
PALMERSTON NORTH
Telephone (+64) 06 3537300
Facsimile (+64) 06 3566800
Mobile (+64) 0274 720696
E-mail Tony.Lyne@xxxxxxxxxxxxxxxxxx
Internet <http://www.computerland.co.nz/> http://www.computerland.co.nz
CAUTION: This e-mail message and accompanying data may contain information
that is confidential and subject to privilege. If you are not the intended
recipient, you are notified that any use, dissemination, distribution or
copying of this message or data is prohibited. If you have received this
e-mail in error, please notify me immediately and delete all material
pertaining to this e-mail. Thank you.
This email and all contents are subject to the following disclaimer:
"http://www.didata.com/disclaimer.asp";
Other related posts:
