Windows 2000 server - wierd problem

  • Thread starter Thread starter SJWS
  • Start date Start date
S

SJWS

Guest
Hi

Hope someone can point me in the right ditrection. I have 5 W2K server (all
fully patches), DC1 & DC2, then three member servers - 1 running exchange, 2
running 3rd party apps.

I have been having an issue on the Exchange server with the Exchange
services failing to start. I change the services to manaul start, reboot and
then start services manually, seemed to sort things out.

Not really a situation I want to embrace after server running OK for over
three years so I have been trying to track down the cause but the issue has
been getting worse whilst going through this process.

I am now in a situation when I cannot start the services at all. I did have
an error that seemed to indicate that the computer account was corrupt for
Exchange in the domain - I joined a workgroup and the rejoined the domain and
that sorted the problem but but that no longer works.

I have gone trawling through event logs on Exchange, DC1 and DC2 - one
consistent error I get on Exchange and DC2 is

Error 1000 userenv, Windows cannot determine the user or computer name.
Return value (1722).

Technet KB is a bit vague on this error so I am hoping for more inof from
somewhere.

Have also had the following erros but not all the time, I believe are linked

DC1 -
13508 NtFrs The File Replication Service is having trouble enabling
replication from DC2 to DC1 for c:\winnt\sysvol\domain using the DNS name
dc2.domainname.local. FRS will keep retrying.

Exchange -
2104 - MSExchangeDSAccess - Topology - Process MAD.EXE (PID=1736). All the
DS Servers in domain are not responding.

1005 - MSExchangeSA - General - Unexpected error An unknown error has
occurred. ID no: 80040a01 Microsoft Exchange System Attendant occurred.

Looking forward to your input
 
RE: Windows 2000 server - wierd problem

Also have error in event log on Exchange server

907 - MSExchangeTransport - Routing Engine/Service - Failed to initialize
directory access. The error code is in the data portion of this event.

"SJWS" wrote:

> Hi
>
> Hope someone can point me in the right ditrection. I have 5 W2K server (all
> fully patches), DC1 & DC2, then three member servers - 1 running exchange, 2
> running 3rd party apps.
>
> I have been having an issue on the Exchange server with the Exchange
> services failing to start. I change the services to manaul start, reboot and
> then start services manually, seemed to sort things out.
>
> Not really a situation I want to embrace after server running OK for over
> three years so I have been trying to track down the cause but the issue has
> been getting worse whilst going through this process.
>
> I am now in a situation when I cannot start the services at all. I did have
> an error that seemed to indicate that the computer account was corrupt for
> Exchange in the domain - I joined a workgroup and the rejoined the domain and
> that sorted the problem but but that no longer works.
>
> I have gone trawling through event logs on Exchange, DC1 and DC2 - one
> consistent error I get on Exchange and DC2 is
>
> Error 1000 userenv, Windows cannot determine the user or computer name.
> Return value (1722).
>
> Technet KB is a bit vague on this error so I am hoping for more inof from
> somewhere.
>
> Have also had the following erros but not all the time, I believe are linked
>
> DC1 -
> 13508 NtFrs The File Replication Service is having trouble enabling
> replication from DC2 to DC1 for c:\winnt\sysvol\domain using the DNS name
> dc2.domainname.local. FRS will keep retrying.
>
> Exchange -
> 2104 - MSExchangeDSAccess - Topology - Process MAD.EXE (PID=1736). All the
> DS Servers in domain are not responding.
>
> 1005 - MSExchangeSA - General - Unexpected error An unknown error has
> occurred. ID no: 80040a01 Microsoft Exchange System Attendant occurred.
>
> Looking forward to your input
 
RE: Windows 2000 server - wierd problem

And this one....

2102 - MSExchangeDSAccess - Topology - Process MAD.EXE (PID=640). All Domain
Controller Servers in use are not responding:
dc2.domain.local
dc1.domain.local

"SJWS" wrote:

> Hi
>
> Hope someone can point me in the right ditrection. I have 5 W2K server (all
> fully patches), DC1 & DC2, then three member servers - 1 running exchange, 2
> running 3rd party apps.
>
> I have been having an issue on the Exchange server with the Exchange
> services failing to start. I change the services to manaul start, reboot and
> then start services manually, seemed to sort things out.
>
> Not really a situation I want to embrace after server running OK for over
> three years so I have been trying to track down the cause but the issue has
> been getting worse whilst going through this process.
>
> I am now in a situation when I cannot start the services at all. I did have
> an error that seemed to indicate that the computer account was corrupt for
> Exchange in the domain - I joined a workgroup and the rejoined the domain and
> that sorted the problem but but that no longer works.
>
> I have gone trawling through event logs on Exchange, DC1 and DC2 - one
> consistent error I get on Exchange and DC2 is
>
> Error 1000 userenv, Windows cannot determine the user or computer name.
> Return value (1722).
>
> Technet KB is a bit vague on this error so I am hoping for more inof from
> somewhere.
>
> Have also had the following erros but not all the time, I believe are linked
>
> DC1 -
> 13508 NtFrs The File Replication Service is having trouble enabling
> replication from DC2 to DC1 for c:\winnt\sysvol\domain using the DNS name
> dc2.domainname.local. FRS will keep retrying.
>
> Exchange -
> 2104 - MSExchangeDSAccess - Topology - Process MAD.EXE (PID=1736). All the
> DS Servers in domain are not responding.
>
> 1005 - MSExchangeSA - General - Unexpected error An unknown error has
> occurred. ID no: 80040a01 Microsoft Exchange System Attendant occurred.
>
> Looking forward to your input
 
RE: Windows 2000 server - wierd problem

and this one ....

2102 - MSExchangeDSAccess - Topology - Process MAD.EXE (PID=640). All Domain
Controller Servers in use are not responding:
dc2.domain.local
dc1.domain.local

"SJWS" wrote:

> Hi
>
> Hope someone can point me in the right ditrection. I have 5 W2K server (all
> fully patches), DC1 & DC2, then three member servers - 1 running exchange, 2
> running 3rd party apps.
>
> I have been having an issue on the Exchange server with the Exchange
> services failing to start. I change the services to manaul start, reboot and
> then start services manually, seemed to sort things out.
>
> Not really a situation I want to embrace after server running OK for over
> three years so I have been trying to track down the cause but the issue has
> been getting worse whilst going through this process.
>
> I am now in a situation when I cannot start the services at all. I did have
> an error that seemed to indicate that the computer account was corrupt for
> Exchange in the domain - I joined a workgroup and the rejoined the domain and
> that sorted the problem but but that no longer works.
>
> I have gone trawling through event logs on Exchange, DC1 and DC2 - one
> consistent error I get on Exchange and DC2 is
>
> Error 1000 userenv, Windows cannot determine the user or computer name.
> Return value (1722).
>
> Technet KB is a bit vague on this error so I am hoping for more inof from
> somewhere.
>
> Have also had the following erros but not all the time, I believe are linked
>
> DC1 -
> 13508 NtFrs The File Replication Service is having trouble enabling
> replication from DC2 to DC1 for c:\winnt\sysvol\domain using the DNS name
> dc2.domainname.local. FRS will keep retrying.
>
> Exchange -
> 2104 - MSExchangeDSAccess - Topology - Process MAD.EXE (PID=1736). All the
> DS Servers in domain are not responding.
>
> 1005 - MSExchangeSA - General - Unexpected error An unknown error has
> occurred. ID no: 80040a01 Microsoft Exchange System Attendant occurred.
>
> Looking forward to your input
 
RE: Windows 2000 server - wierd problem

and this one ....
2102 - MSExchangeDSAccess - Topology - Process MAD.EXE (PID=640). All Domain
Controller Servers in use are not responding:
dc2.domain.local
dc1.domain.local

"SJWS" wrote:

> Hi
>
> Hope someone can point me in the right ditrection. I have 5 W2K server (all
> fully patches), DC1 & DC2, then three member servers - 1 running exchange, 2
> running 3rd party apps.
>
> I have been having an issue on the Exchange server with the Exchange
> services failing to start. I change the services to manaul start, reboot and
> then start services manually, seemed to sort things out.
>
> Not really a situation I want to embrace after server running OK for over
> three years so I have been trying to track down the cause but the issue has
> been getting worse whilst going through this process.
>
> I am now in a situation when I cannot start the services at all. I did have
> an error that seemed to indicate that the computer account was corrupt for
> Exchange in the domain - I joined a workgroup and the rejoined the domain and
> that sorted the problem but but that no longer works.
>
> I have gone trawling through event logs on Exchange, DC1 and DC2 - one
> consistent error I get on Exchange and DC2 is
>
> Error 1000 userenv, Windows cannot determine the user or computer name.
> Return value (1722).
>
> Technet KB is a bit vague on this error so I am hoping for more inof from
> somewhere.
>
> Have also had the following erros but not all the time, I believe are linked
>
> DC1 -
> 13508 NtFrs The File Replication Service is having trouble enabling
> replication from DC2 to DC1 for c:\winnt\sysvol\domain using the DNS name
> dc2.domainname.local. FRS will keep retrying.
>
> Exchange -
> 2104 - MSExchangeDSAccess - Topology - Process MAD.EXE (PID=1736). All the
> DS Servers in domain are not responding.
>
> 1005 - MSExchangeSA - General - Unexpected error An unknown error has
> occurred. ID no: 80040a01 Microsoft Exchange System Attendant occurred.
>
> Looking forward to your input
 
Re: Windows 2000 server - wierd problem

Hello SJWS,

On both dc's run dcdiag /v and netdiag /v If you get errors post the complete
output here. Also post an ipconfig /all from both dc's and the member servers
here.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups

> Hi
>
> Hope someone can point me in the right ditrection. I have 5 W2K server
> (all fully patches), DC1 & DC2, then three member servers - 1 running
> exchange, 2 running 3rd party apps.
>
> I have been having an issue on the Exchange server with the Exchange
> services failing to start. I change the services to manaul start,
> reboot and then start services manually, seemed to sort things out.
>
> Not really a situation I want to embrace after server running OK for
> over three years so I have been trying to track down the cause but the
> issue has been getting worse whilst going through this process.
>
> I am now in a situation when I cannot start the services at all. I did
> have an error that seemed to indicate that the computer account was
> corrupt for Exchange in the domain - I joined a workgroup and the
> rejoined the domain and that sorted the problem but but that no longer
> works.
>
> I have gone trawling through event logs on Exchange, DC1 and DC2 - one
> consistent error I get on Exchange and DC2 is
>
> Error 1000 userenv, Windows cannot determine the user or computer
> name. Return value (1722).
>
> Technet KB is a bit vague on this error so I am hoping for more inof
> from somewhere.
>
> Have also had the following erros but not all the time, I believe are
> linked
>
> DC1 - 13508 NtFrs The File Replication Service is having trouble
> enabling replication from DC2 to DC1 for c:\winnt\sysvol\domain using
> the DNS name dc2.domainname.local. FRS will keep retrying.
>
> Exchange -
> 2104 - MSExchangeDSAccess - Topology - Process MAD.EXE (PID=1736). All
> the
> DS Servers in domain are not responding.
> 1005 - MSExchangeSA - General - Unexpected error An unknown error has
> occurred. ID no: 80040a01 Microsoft Exchange System Attendant
> occurred.
>
> Looking forward to your input
>
 
Re: Windows 2000 server - wierd problem

After you try starting you might use sc.exe to query the error code.

An example try;
sc query "service name"

to see what win32 exit code is generated.

This article may also help.
http://www.microsoft.com/technet/su...0&EvtID=1005&EvtSrc=MSExchangeAdmin&LCID=1033



--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

"SJWS" wrote:
> Hi
>
> Hope someone can point me in the right ditrection. I have 5 W2K server
> (all
> fully patches), DC1 & DC2, then three member servers - 1 running exchange,
> 2
> running 3rd party apps.
>
> I have been having an issue on the Exchange server with the Exchange
> services failing to start. I change the services to manaul start, reboot
> and
> then start services manually, seemed to sort things out.
>
> Not really a situation I want to embrace after server running OK for over
> three years so I have been trying to track down the cause but the issue
> has
> been getting worse whilst going through this process.
>
> I am now in a situation when I cannot start the services at all. I did
> have
> an error that seemed to indicate that the computer account was corrupt for
> Exchange in the domain - I joined a workgroup and the rejoined the domain
> and
> that sorted the problem but but that no longer works.
>
> I have gone trawling through event logs on Exchange, DC1 and DC2 - one
> consistent error I get on Exchange and DC2 is
>
> Error 1000 userenv, Windows cannot determine the user or computer name.
> Return value (1722).
>
> Technet KB is a bit vague on this error so I am hoping for more inof from
> somewhere.
>
> Have also had the following erros but not all the time, I believe are
> linked
>
> DC1 -
> 13508 NtFrs The File Replication Service is having trouble enabling
> replication from DC2 to DC1 for c:\winnt\sysvol\domain using the DNS name
> dc2.domainname.local. FRS will keep retrying.
>
> Exchange -
> 2104 - MSExchangeDSAccess - Topology - Process MAD.EXE (PID=1736). All the
> DS Servers in domain are not responding.
>
> 1005 - MSExchangeSA - General - Unexpected error An unknown error has
> occurred. ID no: 80040a01 Microsoft Exchange System Attendant occurred.
>
> Looking forward to your input
 
Back
Top