Exchange Services do not start after reboot, but starts manually afterwards

Exchange Services do not start after reboot, but starts manually afterwards (Full Version)

All Forums >> [Microsoft Exchange 2003] >> Information Stores

Message

DavidTT -> Exchange Services do not start after reboot, but starts manually afterwards (8.Jul.2007 11:12:46 PM)
Hello all, I recently upgraded my win 2003 servers to service pack 1. There are two domain controllers and both got the update. one domain controller containts the exchange 2003. I noticed after rebooting that the exchange sys attend, info store and Mta stacks do not start. When i manually try to start the services they start up. thign aboout it is that, the logs are showing topology errors. it drills down to ldap errors Details Product: Exchange ID: 2115 Source: MSExchangeDSAccess Version: 6.5.6940.0 Component: Microsoft Exchange Directory Access Cache Message: Process <process name> (PID=<process id>). DSAccess needs to close a connection to the Domain Controller <distinguished name> due to error 0x<error code>. Explanation This event will be seen if Diagnostics Logging on the LDAP category of DSAccess is set to Medium for the server. DSAccess terminated the existing Lightweight Directory Access Protocol (LDAP) connection because of the specified error. The user operation will be retried, and the domain controller will still be used by DSAccess. User Action The error code should be of the format 0x800409ZZ, where ZZ is the hexadecimal value of a standard LDAP error. You can look up the LDAP error description in the "LDAP Error Codes" article on the Microsoft Knowledge Base site. Proceed based on what the ____________________________ Event Type: Warning Event Source: MSExchangeDSAccess Event Category: LDAP Event ID: 2115 Date: 7/7/2007 Time: 5:30:48 PM User: N/A Computer: TTCICSERVER Description: Process WMIPRVSE.EXE -EMBEDDING (PID=2984). DSAccess needs to close a connection to the Domain Controller 127.0.0.1 due to error 0x80040952. For more information, click http://www.microsoft.com/contentredirect.asp. Issues that affect the IIS sevices, but after a while since those services constantlt retries it gets successful startin, judging from the logs. So it seems it some sort of timing, where the domain controller has not been registered the master when sxchange is lookin for. Fruther diggin on thelogs, it was told that the when a DC is demoted , the rcipient update sevices stil looks for that old DC. i have not demoted any DC , but still verified is the same box the exch is looking for. netdiag pass dcdiag pass setspn shows the ldap records I wondering if to run over domainprep.

a.grogan -> RE: Exchange Services do not start after reboot, but starts manually afterwards (9.Jul.2007 7:39:04 AM)
Hiya mate, you have probably been told this but Exchange is not recommended on a DC for a number of reasons. One common issue is that when installed on a DC Exchange will that as is primary topology master, therefore, if the directory has not finished initalising when the Exchange services start they will fail and you will get entries in the Event log like the ones listed. One thing you could try is open the ESM, navigate to Admin groups, right click on your server and then select properties. Click on the Directory Access TAB and then untick the "Automatically Discover Servers" then manually add in the other domain controller for Exchange (you will need to ensure that it is a GC" Cheers A

DavidTT -> RE: Exchange Services do not start after reboot, but starts manually afterwards (9.Jul.2007 11:09:59 AM)
Well i met it on a single box setup, its kinda of an economy situation here. But yes your response makes alot of sense. I will have to promote that 2nd DC to a GC then. But check this out, at a time ago, I did a complete reinstall of that 2nd DC, now the schema is present for exch attribs in the primary DC, but not in the 2nd DC. I have installed the exch system manager tool on the 2nd DC at a point in time and the exch attribs appeared, but i decided to remove it after, and so it stripped it off once again. All active direttory objects are replicated neverthless , so my question is should i be concerned with this behaviour of he attrib if i am looking to promote the 2nd DC to a GC??? I cannot/should not demote the 2nd DC and re-promote it , to see if replication takes the right form , because the 2nd DC is also a Certificate Server. But it seems like the server 2003 sp1 delayed the AD initialising.

echimenga -> RE: Exchange Services do not start after reboot, but starts manually afterwards (9.Jul.2007 11:14:50 AM)
How do you back up the exchange log

DavidTT -> RE: Exchange Services do not start after reboot, but starts manually afterwards (9.Jul.2007 11:28:57 AM)
Currently i do not back up the trans logs. my database path and trans logs path are the same path, hence i have to move the databse to a separate path , so i can just simply select the trans path for backup. there is a daily online backup however, as you would know it will purge the trans logs. but related to my issue, are getting at the backing up of the logs are corrupting the information store start up process? ntbackup

DavidTT -> RE: Exchange Services do not start after reboot, but starts manually afterwards (9.Jul.2007 11:44:56 AM)
Andy, one more question to appened to my last post... if i do promote the 2nd DC to a GC, wont the automatically find GC setting in the ESM find the 2nd one? and i will not have to manually add the entry?

a.grogan -> RE: Exchange Services do not start after reboot, but starts manually afterwords (9.Jul.2007 1:09:46 PM)
Hiya David, Yes, if you make the 2nd DC and GC the topology discoverer (which runs as part of the System Attendant) should detect the GC status, however that does not guarantee that this will solve the problem (I have seen instances where it doesn't) - but give it a try none the less. In terms of the question you posed in your last post about the Attributes I am assuming that you reinstalled the DC and then when accessing AD users and computers the Exchange attributes were not present - then when you installed the Exchange management tools they were. Making the server a GC will not alter this. Thanks A

DavidTT -> RE: Exchange Services do not start after reboot, but starts manually afterwards (9.Jul.2007 1:49:00 PM)
ok but since i have uninstalled the ESM tool on the 2nd DC , which stripped the exchn attribs, since the DC seems to not have the required schema for exch attrib, would it be a suitable DC for being a GC? so if i do reach GC level on that 2nd DC, and i have ot manually select the GCs to choose from, list order implies priority? bare with me i am gonna write the 70-284 exam soon, :) as of the other poster, concerning the exchange logs, is it a good method to : [1] do online backup of IS [2] schedule another backup to backup the trans log files only , which begins right after [1] so the purged trans logs will be smaller and latest. Thing is , i tried recared a test lab with both DCs, restore the exch server , without the trans logs, and it seem to work fine. Any comments on this , feel free.

a.grogan -> RE: Exchange Services do not start after reboot, but starts manually afterwords (9.Jul.2007 2:01:43 PM)
Hello David, Please do not worry, Exchange is a wonderful world of learning! and we are here to help. Just because you have un-installed the Exchange admin tools and the attributes are not present does not mean the DC cannot act as a GC (you can do this via Active Directory Sites and Services->Sites->Default-First-Site-Name->Servers->2nd DC - right click and select properties and then tick the Global Catalog option). The DC still has access to the schema updates that took place during FORESTPREP. I believe that when AUTO discover runs it orders by closest location to the Exchange server - this is why I suggested configuring it manually - however you may wish to leave it alone and see what happens. Cheers A

DavidTT -> RE: Exchange Services do not start after reboot, but starts manually afterwords (9.Jul.2007 3:18:06 PM)
ya i did some research on the GC enabled, pretty simple. And now that i think of it, exch will always check for the DC that is installed on, and when it fails to locate it may go to the 2nd in list, i will try both ways, manual /auto. Something i just remembered, the recipinet update services in ESM, MS posted related info about my issue to that, but based it upon the specified DC in there would be either down on demoted. If your suggestion about the directory services tab-> Manual GC mapping does not work, do you think it is wise to point the recipinet update services info with the 2nd DC which would now be a GC?

a.grogan -> RE: Exchange Services do not start after reboot, but starts manually afterwords (9.Jul.2007 3:26:13 PM)
Sorry chap, I am not sure that I understand - it is true that if you manually configure the Directory Servers to your 2nd DC and that goes down then you will have some problems (if that is what you mean) this was suggested only due to the fact that in your first post the problem was services not starting on a reboot of the Exchange server that is also a DC - but the RUS does not mind if it is on a GC or normal DC by default. Have I missed something? Cheers A

DavidTT -> RE: Exchange Services do not start after reboot, but starts manually afterwords (9.Jul.2007 3:35:10 PM)
ok , if the DC specified in the RUS is down, what are the symptoms ? Would it be anything close to my issue i am seeing here? I am looking at all possible solutions.

a.grogan -> RE: Exchange Services do not start after reboot, but starts manually afterwords (9.Jul.2007 3:36:58 PM)
Ah - right, no what would happen is that when you create mailboxes or change the SMTP addresses for your domain e-mail addresses would not be updated until the DC was back online -or- you changed the management domain controller for RUS. Cheers A

DavidTT -> RE: Exchange Services do not start after reboot, but starts manually afterwords (9.Jul.2007 3:45:23 PM)
I see, to conclude tell me if i am right, when the domain controllers services and directory were loading, exchange sent ldap requets to find GCs. Since i only have 1 GC and it is the same box , it did not find any and hence sys attend failed to load.?? I was even thinking that the possibility of finding some way to delay the exchange services from starting until a minute or 2, which be around the same thing the directory services are fully loaded.

a.grogan -> RE: Exchange Services do not start after reboot, but starts manually afterwords (9.Jul.2007 3:50:48 PM)
Hiya chap, yes, but I think that it is more detailed than that, I think that the Directory service has also not finished loading at the same point the Exchange attempts to start, as Exchange is installed on a domain controller it looks to itself first as a source for the Directory and GC - as this has not finished loading this causes the services to fail. The reason why I have suggested pointing Exchange at your other Domain Controller and making that a GC is that it is unlikely that Domain Contollers will be rebooted at the same time as the DC containing the Exchange - therefore Exchange looking at a Directory and DG which is up. Cheers A

DavidTT -> RE: Exchange Services do not start after reboot, but starts manually afterwords (9.Jul.2007 3:59:13 PM)
yup thanks alot. I will try it out this afternoon and give you an update. here's one for ya, in the past i have noticed emails are stuck in the outlook's outbox, only when you traverse folder , or simply click any other folder then is pushes it to the sent items, and hence it then sends. I have done isinteg alltests , and even offline defrags, it didnt work. one last time i did the isinteg, defrag, then isinteg again to make sure the off defrag has not corrupted anything , no errors, but it seems to work. exch standard, database has grown from 5 to 10gb only, because backups were getting rather huge, 10 is currently huge for my backups, soi usually defrag offline to compact it to about 6 gb. I know it is not recommened to do offline defrag as maintenance, but is was required. but what do you think could be causing it?

a.grogan -> RE: Exchange Services do not start after reboot, but starts manually afterwords (9.Jul.2007 4:06:02 PM)
Hiya mate, it sounds like "lag" between the Outlook client and the Exchange server, I am willing to bet that OWA works fine! I will have a look into it and come back to you, Cheers A

DavidTT -> RE: Exchange Services do not start after reboot, but starts manually afterwards (9.Jul.2007 4:17:56 PM)
yup you won the bet...

a.grogan -> RE: Exchange Services do not start after reboot, but starts manually after wards (9.Jul.2007 4:32:54 PM)
Ok, gonna pop offline and have a think, However a couple of things off the top of my head; 1. Are you using a) Offline Folders / cached mode 2. What addins to Outlook are you using 3. Does the client machine have the correct DNS suffix configured in the DNS settings of the IP config (this would be the same as the Exchange server). 4. Has a delay been configured in the Send Receive settings Cheers A

DavidTT -> RE: Exchange Services do not start after reboot, but starts manually afterwards (9.Jul.2007 5:01:00 PM)
1. Are you using a) Offline Folders / cached mode we just have the usage of pst files. thats it. Its outlook xp btw. 2. What addins to Outlook are you using 3. Does the client machine have the correct DNS suffix configured in the DNS settings of the IP config (this would be the same as the Exchange server). Yes, note its all clients, so is more of a server issue than client. i thought of connectivity as well. 4. Has a delay been configured in the Send Receive settings no delays on this at all. an extra thing i cna point out, is that, there were alot of auditin being done on the server themselves, and hence logs were writting an more than 5 per second. I finally found them and remove the auditing process, and the writes to the log cut down to a normal state. things is that was a month before the problem was resolved with my isinteg trial. Not sure if it took a while for the server to re adjust to the reduced work load. i can safely assume when the auditin was initialise theproblem started, but not definite. I also did reinstall of windows, even on a new machine, and it still occurs for outlook.

Page: [1] 2 3 next > >>