ywainaqua
asked on
Microsoft, Exchange, 2007, System Attendant not starting
I am migrating our users from an Exchange 2003 Sever to a new Exchange 2007 Server.
After tranferring some of the mailboxes, the Microsoft Exchange System Atendant no the Exchange 2007 server sdtopped is now not starting (Automatically or Manually)
I am, getting these 2 errors in the event viewer:
1.
Event Type: Error
Event Source: MSExchangeSA
Event Category: General
Event ID: 1005
Date: 08/02/2008
Time: 01:30:25 PM
User: N/A
Description:
Unexpected error An unknown error has occurred. ID no: ffffffec Microsoft Exchange System Attendant occurred.
and
2.
Event Type: Error
Event Source: MSExchangeSA
Event Category: General
Event ID: 2060
Date: 08/02/2008
Time: 01:30:25 PM
User: N/A
Description:
The DSProxy failed to start, error '%1'.
What can I do to fix this error?
After tranferring some of the mailboxes, the Microsoft Exchange System Atendant no the Exchange 2007 server sdtopped is now not starting (Automatically or Manually)
I am, getting these 2 errors in the event viewer:
1.
Event Type: Error
Event Source: MSExchangeSA
Event Category: General
Event ID: 1005
Date: 08/02/2008
Time: 01:30:25 PM
User: N/A
Description:
Unexpected error An unknown error has occurred. ID no: ffffffec Microsoft Exchange System Attendant occurred.
and
2.
Event Type: Error
Event Source: MSExchangeSA
Event Category: General
Event ID: 2060
Date: 08/02/2008
Time: 01:30:25 PM
User: N/A
Description:
The DSProxy failed to start, error '%1'.
What can I do to fix this error?
ASKER
Hi,
Thanks for the insight and the links. I removed the Symantec AV from both the Exchange 2003 and 2007 Servers, but still no luck on the System Attendant starting on t he Exchange 2007 server.
Thanks for the insight and the links. I removed the Symantec AV from both the Exchange 2003 and 2007 Servers, but still no luck on the System Attendant starting on t he Exchange 2007 server.
Here are a few other links associated with that error.
http://support.microsoft.com/kb/251640
http://support.microsoft.com/kb/251640
The first one is associated with 2000 but ultimately has to due with restarting the global catalog server. I can't imagine this is the scenario but the second one could be possible, the NWLink protocol is enabled on your network interface card.
I've seen a few articles now on this and it almost everytime has to do with connectivity to the DC. Also look at the date listed in the event viewer logs. It looks like you are way off from the correct date which if it isn't syncing with your time server (typically DC) can cause all types of issues. start there and let me know.
http://support.microsoft.com/kb/251640
http://support.microsoft.com/kb/251640
The first one is associated with 2000 but ultimately has to due with restarting the global catalog server. I can't imagine this is the scenario but the second one could be possible, the NWLink protocol is enabled on your network interface card.
I've seen a few articles now on this and it almost everytime has to do with connectivity to the DC. Also look at the date listed in the event viewer logs. It looks like you are way off from the correct date which if it isn't syncing with your time server (typically DC) can cause all types of issues. start there and let me know.
ASKER
Hi Zuech,
Thanks for your reply, I tried to do the registry changes and still no luck. Upon making the changes none of the MSE Services started.
Although I did get new errors (Pasted below):
Event Type: Warning
Event Source: MSExchange Autodiscover
Event Category: Core
Event ID: 1106
Date: 14/02/2008
Time: 01:34:46 PM
User: N/A
Computer: ANGLER
Description:
Error "Microsoft.Exchange.Autodi scover.Pro viders.Out look.Outlo okAutoDisc overProvid er" while loading the assembly "System.Reflection.TargetI nvocationE xception: Exception has been thrown by the target of an invocation. ---> Microsoft.Exchange.Data.Di rectory.AD TransientE xception: Microsoft Exchange Active Directory Topology Service cannot be contacted via RPC interface, error 0x6D9. ---> Microsoft.Exchange.Rpc.Rpc Exception: Error 6d9 from HrGetServersForRole
at Microsoft.Exchange.Rpc.ADT opology.AD TopoRpcCli ent.HrGetS erversForR ole(String [] currentlyUsedServers, ServerRole role, Int32 serversRequested, ServerInfo[]& suitableServers, Int32[]& mapping)
at Microsoft.Exchange.Data.Di rectory.DS AccessTopo logyProvid er.GetServ ersForRole (String[] currentlyUsedServers, ADServerRole role, Int32 serversRequested, Int32[]& mapping)
--- End of inner exception stack trace ---
at Microsoft.Exchange.Data.Di rectory.DS AccessTopo logyProvid er.GetServ ersForRole (String[] currentlyUsedServers, ADServerRole role, Int32 serversRequested, Int32[]& mapping)
at Microsoft.Exchange.Data.Di rectory.DS AccessTopo logyProvid er.GetConf igDCInfo(B oolean throwOnFailure)
at Microsoft.Exchange.Data.Di rectory.To pologyProv ider.Popul ateConfigN amingConte xts()
at Microsoft.Exchange.Data.Di rectory.To pologyProv ider.GetCo nfiguratio nNamingCon text()
at Microsoft.Exchange.Data.Di rectory.AD Session.Ge tConnectio n(String preferredServer, Boolean isWriteOperation, Boolean isNotifyOperation, ADObjectId& rootId, Int32& maxRetries)
at Microsoft.Exchange.Data.Di rectory.AD Session.Ge tReadConne ction(Stri ng preferredServer, ADObjectId& rootId, Int32& maxRetries)
at Microsoft.Exchange.Data.Di rectory.AD Session.Fi nd(ADObjec tId rootId, String optionalBaseDN, ADObjectId readId, QueryScope scope, QueryFilter filter, SortBy sortBy, Int32 maxResults, IEnumerable`1 properties, CreateObjectDelegate objectCreator, CreateObjectsDelegate arrayCreator)
at Microsoft.Exchange.Data.Di rectory.AD Session.Fi nd(ADObjec tId rootId, QueryScope scope, QueryFilter filter, SortBy sortBy, Int32 maxResults, IEnumerable`1 properties, CreateObjectDelegate objectCtor, CreateObjectsDelegate arrayCtor)
at Microsoft.Exchange.Data.Di rectory.AD Session.Fi nd[TResult ](ADObject Id rootId, QueryScope scope, QueryFilter filter, SortBy sortBy, Int32 maxResults, IEnumerable`1 properties)
at Microsoft.Exchange.Data.Di rectory.Re cipient.AD RecipientS ession.Fin dBySid(Sec urityIdent ifier sId)
at Microsoft.Exchange.Autodis cover.Prov iders.Prov ider.GetQu eryBaseDN( )
at Microsoft.Exchange.Autodis cover.Prov iders.Outl ook.Outloo kAutoDisco verProvide r..ctor(Re questData requestData)
--- End of inner exception stack trace ---
at System.RuntimeMethodHandle ._InvokeCo nstructor( Object[] args, SignatureStruct& signature, IntPtr declaringType)
at System.Reflection.RuntimeC onstructor Info.Invok e(BindingF lags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at System.RuntimeType.CreateI nstanceImp l(BindingF lags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
at Microsoft.Exchange.Autodis cover.Prov idersTable .LoadProvi der(Reques tData requestData, Object[] constructorArgs)".
Stack Trace:%3. This error may occur because the provider file is corrupt, is in an incorrect format, or has insufficient permissions.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Thanks for your reply, I tried to do the registry changes and still no luck. Upon making the changes none of the MSE Services started.
Although I did get new errors (Pasted below):
Event Type: Warning
Event Source: MSExchange Autodiscover
Event Category: Core
Event ID: 1106
Date: 14/02/2008
Time: 01:34:46 PM
User: N/A
Computer: ANGLER
Description:
Error "Microsoft.Exchange.Autodi
at Microsoft.Exchange.Rpc.ADT
at Microsoft.Exchange.Data.Di
--- End of inner exception stack trace ---
at Microsoft.Exchange.Data.Di
at Microsoft.Exchange.Data.Di
at Microsoft.Exchange.Data.Di
at Microsoft.Exchange.Data.Di
at Microsoft.Exchange.Data.Di
at Microsoft.Exchange.Data.Di
at Microsoft.Exchange.Data.Di
at Microsoft.Exchange.Data.Di
at Microsoft.Exchange.Data.Di
at Microsoft.Exchange.Data.Di
at Microsoft.Exchange.Autodis
at Microsoft.Exchange.Autodis
--- End of inner exception stack trace ---
at System.RuntimeMethodHandle
at System.Reflection.RuntimeC
at System.RuntimeType.CreateI
at Microsoft.Exchange.Autodis
Stack Trace:%3. This error may occur because the provider file is corrupt, is in an incorrect format, or has insufficient permissions.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
ASKER
Some more insight to our setup:
Server1 - Exchange 2003
- Windows 2003 Server Enterprise Edition
Server2 - Exchange 2007 (Mailbox, Hub Transport, Client Access)
- Windows 2003 R2 Server x64 Enterprise Edition
Server3 - Exchange 2007 (Client Access, Hub Transport) - Used for Frontend Web Access:OWA
- Windows 2003 R2 Server x64 Enterprise Edition
Server4 - MS AD Server (Windows 2003 R2 Server x64 Enterprise Edition)
Server1 - Exchange 2003
- Windows 2003 Server Enterprise Edition
Server2 - Exchange 2007 (Mailbox, Hub Transport, Client Access)
- Windows 2003 R2 Server x64 Enterprise Edition
Server3 - Exchange 2007 (Client Access, Hub Transport) - Used for Frontend Web Access:OWA
- Windows 2003 R2 Server x64 Enterprise Edition
Server4 - MS AD Server (Windows 2003 R2 Server x64 Enterprise Edition)
I had this error. It can be caused by different protocols being installed on the server. I setup a 2003 x64 R2 standard server and installed exchange standard 2007 sp0 and it said the error you mentioned immediately during the install.
The first time i set it up as a domain controller with a variety of components i wanted. The second time was a very bare install with very little installed. The same error happened.
I scoured the net for solutions and found a post from an admin saying when he installed tcp/ip ipv6 it started working. Also there is a microsoft knowledge base article saying having IPX NWLINK can cause this.
I then realised that one of the things in common with both installs was i ticked Appletalk Protocol on both installs.
So my solution was i removed Appletalk and just for the heck of it installed IPv6, rebooted and it worked perfectly.
Then i immediately applied Ex 2007 sp1. So far so good.
The first time i set it up as a domain controller with a variety of components i wanted. The second time was a very bare install with very little installed. The same error happened.
I scoured the net for solutions and found a post from an admin saying when he installed tcp/ip ipv6 it started working. Also there is a microsoft knowledge base article saying having IPX NWLINK can cause this.
I then realised that one of the things in common with both installs was i ticked Appletalk Protocol on both installs.
So my solution was i removed Appletalk and just for the heck of it installed IPv6, rebooted and it worked perfectly.
Then i immediately applied Ex 2007 sp1. So far so good.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
http://support.microsoft.com/kb/823166
http://support.microsoft.com/kb/822158
http://support.microsoft.com/kb/245822