Re: Exchnage services problem

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

From: Richard Follett (rickie_20_at_yahoo.com)
Date: 05/27/04


Date: Thu, 27 May 2004 08:35:51 -0700


Once again thanks for the responce,

Have checked these settings to na avail, they all are
correct.

any other ideas or is this gonna be a rebuild job?

>-----Original Message-----
>It looks like you are having some problems connecting to
the domain.
>PLATTRAIN.LOCAL domain.
>
>This would definitely prevent the SA from starting.
>
>I would check the DNS configuration on the TCP/IP
properties and make sure
>that ONLY your internal DNS server is listed.
>Then reboot and see if the SA will then start.
>
>
>--
>Michael Barta [MSFT]
>Microsoft Exchange Support
>
>Please do not send e-mail directly to this alias. This
alias is for
>newsgroup purposes only.
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>
>"Richard Follett" <rickie_20@yahoo.com> wrote in message
>news:135c401c443d3$eb6790d0$a501280a@phx.gbl...
>> Thanks for the quick responce, listed below are all the
>> errors found in my application log!
>>
>>
>> MSExchangeSA - Unexpected error The network
>> path was not found. Facility: Win32 ID no: 80070035
>> Microsoft Exchange System Attendant occurred.
>>
>> Application Error - Faulting application
>> mad.exe, version 6.5.6944.0, faulting module
wldap32.dll,
>> version 5.2.3790.0, fault address 0x000090f3
>>
>> Userenv - Windows cannot query for the list
>> of Group Policy objects. Check the event log for
possible
>> messages previously logged by the policy engine that
>> describes the reason for this
>>
>> Userenv - Windows cannot
connect
>> to PLATTRAIN.LOCAL domain. (Can't connect to the LDAP
>> server). Group Policy processing aborted
>>
>> Userenv - Windows cannot query
for
>> the list of Group Policy objects. Check the event log
for
>> possible messages previously logged by the policy
engine
>> that describes the reason for this
>>
>> Userenv - Windows cannot connect to
>> plattrain.local domain. (Can't connect to the LDAP
>> server). Group Policy processing aborted
>>
>> MSExchangeMTA - A fatal error occurred
reading a
>> value from the directory. No MTA name was found.
Contact
>> Microsoft Technical Support. [MTA MAIN BASE 1 12] (16)
>>
>> MSExchangeDSAccess - Process EMSMTA.EXE (PID=3684).
All
>> the DS Servers in domain are not responding
>>
>> MSExchangeFBPublish - System Attendant Service
failed to
>> create session for virtual machine SERVER. The error
>> number is 0x8007203b.
>>
>> Microsoft Exchanger Server - The description for Event
ID
>> ( 1000 ) in Source ( Microsoft Exchange Server )
cannot be
>> found. The local computer may not have the necessary
>> registry information or message DLL files to display
>> messages from a remote computer. You may be able to use
>> the /AUXSOURCE= flag to retrieve this description; see
>> Help and Support for details. The following
information is
>> part of the event: mad.exe, 6.5.6944.0, 3edc4e9d,
>> wldap32.dll, 5.2.3790.0, 3e802499, 0, 000090f3
>>
>> MSExchangeSA - Microsoft Exchange System
>> Attendant reported an error '0x8007203b' in its DS
>> Monitoring thread
>>
>> WindowsSgarePoint Server - #50070: Unable to connect
to
>> the database STS_Config on server\SharePoint. Check
the
>> database connection information and make sure that the
>> database server is running
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>>-----Original Message-----
>>>What events are you getting in the application log?
>>>
>>>--
>>>Michael Barta [MSFT]
>>>Microsoft Exchange Support
>>>
>>>Please do not send e-mail directly to this alias. This
>> alias is for
>>>newsgroup purposes only.
>>>This posting is provided "AS IS" with no warranties,
and
>> confers no rights.
>>>
>>>"Richard Follett" <rickie_20@yahoo.com> wrote in
message
>>>news:121f401c44261$4e29a6f0$a501280a@phx.gbl...
>>>> All of a sudden my exchange server 2003 has stopped
>>>> responding.
>>>> The errors I am receiving are as follows:
>>>> Mad.exe caused fault in wldap32.dll 000090F3
>>>>
>>>> When trying to manually restart the service I am
getting
>>>> Exchange System Attendant Started and Stopped.
>>>> Does anyone have any idea how I can resolve this
>> problem?
>>>>
>>>> A quick response would be highly appreciated.
>>>>
>>>> Many Thanks
>>>>
>>>> Rickie
>>>>
>>>
>>>
>>>.
>>>
>
>
>.
>



Relevant Pages

  • Re: Userenv 1030 and 1058 errors! Please help me!
    ... Adrian Grigorof wrote: ... Windows cannot query for the list of Group Policy objects. ... Check the event log for possible messages previously logged by the policy engine that describes the reason for this. ... we have also noticed when the server boots up, it is taking about 5 minutes before we get a logon screen. ...
    (microsoft.public.windows.server.general)
  • Re: Lost DC - getting AD errors
    ... How did you remove that server from AD? ... The File Replication Service is having trouble enabling replication from ... This event log message will appear once per connection, ... Windows cannot query for the list of Group Policy objects. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Userenv 1030 and 1058 errors! Please help me!
    ... Adrian Grigorof wrote: ... Windows cannot query for the list of Group Policy objects. ... Check the event log for possible messages previously logged by the policy engine that describes the reason for this. ... we have also noticed when the server boots up, it is taking about 5 minutes before we get a logon screen. ...
    (microsoft.public.windows.server.general)
  • Userenv 1030 and 1058 errors! Please help me!
    ... We have one server in our domain that's a dc. ... For information about network troubleshooting, ... Windows cannot query for the list of Group Policy objects. ... Check the event log for possible messages previously logged by the policy engine that describes the reason for this. ...
    (microsoft.public.windows.server.general)
  • RE: Several Problems; how to reset security and troubleshoot serve
    ... Security Templates in Windows Server 2003 - ... The Network Service account must be added to the policy settings in the ... This issue may occur if Group Policy settings that were applied at ... When you tried to launch the Remote assistance, ...
    (microsoft.public.windows.server.sbs)