Re: AD/AM VSS Error



Ouch. "domain\user@domain" is a badly formatted name. It should be either
"domain\user" or "user@domain" but not both... If you can reproduce the
problem during adam install, let me know. We should only be putting
"domain\user" there, for the service account that you have chosen. Did you
do an unattend install by any chance?

--
Dmitri Gavrilov
SDE, DS Admin eXperience

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

"Lee Flight" <lef@xxxxxxxxxxxxxxx> wrote in message
news:udNbgZ%23CGHA.2664@xxxxxxxxxxxxxxxxxxxxxxx
> Hi
>
> that seems like an innocuous error; there are usually entries under
> VssAccessControl for the ADAM service accounts. Did you have
> an abortive ADAM install on the system?
>
> Does the entry reappear if you delete the offending value? To be extra
> safe you should probably backup the registry key before modifying it.
>
> Lee Flight
>
> "Doug" <kolpekdb@xxxxxxxxxxxx> wrote in message
> news:1135722102.402471.35140@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>> On all of our AD/AM servers we are getting the following errors in the
>> Application Log:
>>
>> Event Type: Error
>> Event Source: VSS
>> Event Category: None
>> Event ID: 13
>> Date: 12/26/2005
>> Time: 11:57:48 PM
>> User: N/A
>> Computer: EXWL03
>> Description:
>> The user name [OURDOMAIN]\[DOMAINUSERACCOUNT@OURDOMAIN] specified in
>> registry (SYSTEM\CurrentControlSet\Services\VSS\VssAccessControl) does
>> not map to a real user name. The entry is ignored.
>>
>> I believe the AD/AM installation created these registry entries so I'm
>> not sure why they are erroring out. If we look at this registry there
>> are 2 entries there that are identical except that one contains the
>> @OURDOMAIN portion and the other one does not. The account specified
>> here is the domain user account that the AD/AM instance is running
>> under.
>>
>> Any ideas? Do we have something configured wrong?
>>
>> Doug
>>
>
>


.



Relevant Pages

  • RE: unable to start exchange information store
    ... value located in the following registry key is missing or inaccessible: ... Get the service account of the information store. ... Locate the Microsoft Exchange Information Store service. ...
    (microsoft.public.windows.server.sbs)
  • RE: unable to start exchange information store
    ... > value located in the following registry key is missing or inaccessible: ... > If the value is present in the correct key, check the permission setting on ... Get the service account of the information store. ... Locate the Microsoft Exchange Information Store service. ...
    (microsoft.public.windows.server.sbs)
  • RE: At.exe Service Account - scripted or registry?
    ... At.exe Service Account - scripted or registry? ... wrong dummy password - front end validation validate only account name. ... Any idea how to do this in script or ...
    (Focus-Microsoft)