OWA 2003 & IIS 6 and IE Web Browser (premium mode) results in Compression Errors

Hello All,

Running OWA on Exchange Enterprise 2003 on Windows 2003 Enterprise using SSL, and Forms Based Authenication.

When I enable compression as Low or High, I receive the following browser errors when logging in via premium mode (I login, but loads take forever, logouts fail, and loading other pages stalls) on every IE browser I visit with, IE 6 SP1 & w/o SP1 and IE 5.5 on every PC I try, hence I think it's an error with the code for OWA. Same error appears for Low or High. Disable this feature, and error goes away. Any insight?

[edit]
Also, at the main forms based login page, I get an error.

Errors Start from here..., I'll give you guys/gays the rule URL, since it's internal...

https://carrier/exchweb/bin/auth/owalogon.asp?url=https://carrier/exchange&reason=0

Line: 79
Char: 1
Error: Syntax error
Code: 0
URL: https://carrier/exchweb/controls/preload.htm
[/edit]

Thanks,
-Ben

IE 6.0 SP1 Scripting Error
-----------------------------

Line: 15
Char: 30
Error: Object expected
Code: 0
URL: https://"domain"/exchange/"user"/Inbox/?Cmd=contents

Line: 79
Char: 1
Error: Syntax error
Code: 0
URL: https://"domain"/exchange/"user"/Inbox/?Cmd=contents

-----------------------------------------------------------------------------------------
bserebinAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

David WilhoitSenior Consultant, ExchangeCommented:
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
bserebinAuthor Commented:
Hey Kidego,

You're on the money... I actually found the work-around answer on MS Community online.... but, you found a hotfix, I didn't know about. You get the points...

Thanks,
-Ben
0
bserebinAuthor Commented:
Hey Kidego,

Wow... the freaking hotfix was posted today. Very impressive to say the least.... explains why you are rated #1.

-Ben
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

David WilhoitSenior Consultant, ExchangeCommented:
i run 2003 at my house, it's a necessary evil to stay informed on the hotfixes for IIS :)

D
0
bserebinAuthor Commented:
***************
WORD OF CAUTION.
***************

The hotfix broke my Exchange Server from automatically starting, shutdowns fail, and a host of other things I'm trying to clean up the mess. I uninstalled the patch, but it made little good, I don't think it reverted all it's changes back.

-Ben
0
David WilhoitSenior Consultant, ExchangeCommented:
reinstall the IIS services, and reinstall exchange.That will reset the IIS hooks for Exchange. I'm going to test the patch myself, I feel bad that this broke your environment. Keep me posted, and post the errors on startup if you still have them in the event log.

D

0
David WilhoitSenior Consultant, ExchangeCommented:
Call MS support as well, and open a ticket. Tell them what's happened, and this hotfix broke your production server, they should open a free case. At the worst, you'd have to pay upfront, and then get a refund at the end of the call. If there's a problem with this, they should know about it.

d
0
David WilhoitSenior Consultant, ExchangeCommented:
OK, I'm not using forms-based auth, or compression, and the dll works fine. Have you thought of removing the forms based auth and compression for the time being? Or is it already off?
0
bserebinAuthor Commented:
Hello,

      After applied the hotfix last night.... my errors. I only put last night's errors down... I must have rebooted a dozen times already. I ran Exchange DB Integrity checks, just to be sure on the priv and pub dbs, no issues. I also did a backup as well. Oh boy....

        What's the best way to reinstall IIS on Win2k3... I hate to do this, I already setup the OWA Password change site and a many other things....

I'll call MS and open a ticket...
-Ben


-----------------------------------

File Replication Service Log Error

Event Type:      Warning
Event Source:      NtFrs
Event Category:      None
Event ID:      13562
Date:            12/11/2003
Time:            2:06:06 AM
User:            N/A
Computer:      CARRIER
Description:
Following is the summary of warnings and errors encountered by File Replication Service while polling the Domain Controller carrier.net.operationemail.com for FRS replica set configuration information.
 
 Could not find computer object for this computer. Will try again at next polling cycle.

 


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.



System Event Log Errors

Event Type:      Warning
Event Source:      LSASRV
Event Category:      SPNEGO (Negotiator)
Event ID:      40960
Date:            12/11/2003
Time:            1:02:21 AM
User:            N/A
Computer:      CARRIER
Description:
The Security System detected an authentication error for the server carrier$@NET.OPERATIONEMAIL.COM.  The failure code from authentication protocol Kerberos was "There are currently no logon servers available to service the logon request.
 (0xc000005e)".

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 5e 00 00 c0               ^..À    


Event Type:      Warning
Event Source:      LSASRV
Event Category:      SPNEGO (Negotiator)
Event ID:      40961
Date:            12/11/2003
Time:            1:02:21 AM
User:            N/A
Computer:      CARRIER
Description:
The Security System could not establish a secured connection with the server carrier$@NET.OPERATIONEMAIL.COM.  No authentication protocol was available.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 88 03 00 c0               ˆ..À    


Event Type:      Error
Event Source:      Service Control Manager
Event Category:      None
Event ID:      7009
Date:            12/11/2003
Time:            1:04:41 AM
User:            N/A
Computer:      CARRIER
Description:
Timeout (30000 milliseconds) waiting for the Microsoft Exchange System Attendant service to connect.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type:      Error
Event Source:      Service Control Manager
Event Category:      None
Event ID:      7000
Date:            12/11/2003
Time:            1:04:41 AM
User:            N/A
Computer:      CARRIER
Description:
The Microsoft Exchange System Attendant service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


Event Type:      Error
Event Source:      Service Control Manager
Event Category:      None
Event ID:      7001
Date:            12/11/2003
Time:            1:04:41 AM
User:            N/A
Computer:      CARRIER
Description:
The Microsoft Exchange Information Store service depends on the Microsoft Exchange System Attendant service which failed to start because of the following error:
The service did not respond to the start or control request in a timely fashion.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.



Event Type:      Error
Event Source:      Service Control Manager
Event Category:      None
Event ID:      7009
Date:            12/11/2003
Time:            1:04:41 AM
User:            N/A
Computer:      CARRIER
Description:
Timeout (30000 milliseconds) waiting for the Microsoft Exchange Management service to connect.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.



Event Type:      Error
Event Source:      Service Control Manager
Event Category:      None
Event ID:      7000
Date:            12/11/2003
Time:            1:04:41 AM
User:            N/A
Computer:      CARRIER
Description:
The Microsoft Exchange Management service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


Event Type:      Error
Event Source:      Service Control Manager
Event Category:      None
Event ID:      7001
Date:            12/11/2003
Time:            1:04:41 AM
User:            N/A
Computer:      CARRIER
Description:
The Microsoft Exchange MTA Stacks service depends on the Microsoft Exchange System Attendant service which failed to start because of the following error:
The service did not respond to the start or control request in a timely fashion.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


Application Log Erros

Event Type:      Error
Event Source:      MSExchangeAL
Event Category:      LDAP Operations
Event ID:      8026
Date:            12/11/2003
Time:            2:05:58 AM
User:            N/A
Computer:      CARRIER
Description:
LDAP Bind was unsuccessful on directory carrier.net.operationemail.com for distinguished name ''. Directory returned error:[0x51] Server Down.    

For more information, click http://www.microsoft.com/contentredirect.asp.


Event Type:      Error
Event Source:      MSExchangeDSAccess
Event Category:      Topology
Event ID:      2102
Date:            12/11/2003
Time:            2:05:58 AM
User:            N/A
Computer:      CARRIER
Description:
Process MAD.EXE (PID=3728). All Domain Controller Servers in use are not responding:
carrier.net.operationemail.com
 

For more information, click http://www.microsoft.com/contentredirect.asp.

Event Type:      Error
Event Source:      MSExchangeAL
Event Category:      LDAP Operations
Event ID:      8026
Date:            12/11/2003
Time:            2:06:04 AM
User:            N/A
Computer:      CARRIER
Description:
LDAP Bind was unsuccessful on directory carrier.net.operationemail.com for distinguished name ''. Directory returned error:[0x51] Server Down.    

For more information, click http://www.microsoft.com/contentredirect.asp.


Event Type:      Error
Event Source:      MSExchangeAL
Event Category:      LDAP Operations
Event ID:      8026
Date:            12/11/2003
Time:            2:06:05 AM
User:            N/A
Computer:      CARRIER
Description:
LDAP Bind was unsuccessful on directory carrier.net.operationemail.com for distinguished name ''. Directory returned error:[0x51] Server Down.    

For more information, click http://www.microsoft.com/contentredirect.asp.

Event Type:      Error
Event Source:      MSExchangeAL
Event Category:      Service Control
Event ID:      8250
Date:            12/11/2003
Time:            2:06:05 AM
User:            N/A
Computer:      CARRIER
Description:
The Win32 API call 'DsGetDCNameW' returned error code [0x862] The specified component could not be found in the configuration information.  The service could not be initialized.  Make sure that the operating system was installed properly.

For more information, click http://www.microsoft.com/contentredirect.asp.

Event Type:      Error
Event Source:      MSExchangeAL
Event Category:      LDAP Operations
Event ID:      8026
Date:            12/11/2003
Time:            2:06:16 AM
User:            N/A
Computer:      CARRIER
Description:
LDAP Bind was unsuccessful on directory carrier.net.operationemail.com for distinguished name ''. Directory returned error:[0x51] Server Down.    

For more information, click http://www.microsoft.com/contentredirect.asp.



Event Type:      Error
Event Source:      MSExchangeIS
Event Category:      General
Event ID:      1194
Date:            12/11/2003
Time:            9:08:43 AM
User:            N/A
Computer:      CARRIER
Description:
Accept clients on external interface MAPIRPC failed with error 0x4b1.

For more information, click http://www.microsoft.com/contentredirect.asp.


------------------------------------------------------------------------------------------------------
0
bserebinAuthor Commented:
Hello K,

The issue is not OWA related anymore, (I've disabled forms based auth and compress, just as a test), and still on a restart, my server hangs and many of the Exchange services don't start now.

I'm currently on the phone with MS.

-Ben
0
David WilhoitSenior Consultant, ExchangeCommented:
let me know, I'd love to see if the hotfix cause it....I personally think DSAccess is broken, or DNs is messed up.
0
David WilhoitSenior Consultant, ExchangeCommented:
After reading the errors, I'll be surprised if it's the hotfix that broke this, I wondering about some other things. First of all, do the exchange servvices start manually after they fail at boot? Or do they never come up?

also, How many domain controllers/global catalog servers do you have?

Saw this, you may want to take a look:

"Error: MAPIRPC - 0x4b1 - "This issue can occur if the Exchange Server services have not been configured to run in the Inetinfo.exe tool; these services are configured to run in the Dllhost.exe tool, or they are not configured to run in any tool. This issue typically occurs if you removed Internet Information Services (IIS) from a computer that is running Microsoft Exchange Server or Mobile Information Server (or both), and then you reinstalled IIS, but you did not reinstall Exchange Server or Mobile Information Server. " See Q296765 for resolution."
0
bserebinAuthor Commented:
Hello K,

Yes, manually the Exchange servicess do start. I tried to set it to restart in case of failure, but that didn't help. The ones that fail on startup are:
MS Exch. Information Store
MS Exch. Mgmt
MS Exch MTA Stacks
MS Exch Sys Attendant

1 server handles every role, AD root, GC, Exchange, IIS, etc. So, there shouldn't be any communication issues unless it's from corruption.

I also saw that article as well, and the only registry entry missing was the ldapsvc, which I didn't add, until you posted the same article. I'm currently rebooting the server, so I'll let you know what happens.

Still on MS hold for an L2 Support Person...

-Ben
0
bserebinAuthor Commented:
Hello K,

The ldapsvc entry made no difference.... still on hold.

-Ben
0
bserebinAuthor Commented:
Hey K,

I hung up from MS Support after waiting 2 hrs.... I called back, and found out the hold time was 3 hrs. I'll try later this evening...

-Ben
0
David WilhoitSenior Consultant, ExchangeCommented:
Yes, my friends told me the wit time was 3-4 hours when it got busy. See if you can schedule a callback, they'll do it for you.

Still think you should reinstall E2K3 over the top of your current situation, see if it helps. god knows it can't hurt :)
BTW, my stuff is still working. When this is all done, I suggest you d/l MetaEdit 2.2, and use it to back up the metabase before you do this stuff next time, and backup the IIS config to XML file. It might save your bacon, but hey, it's my fault for not telling you sooner.

D
0
bserebinAuthor Commented:
Hello D (since that's how you sign your comments),

I did a reinstall of Exchange 2003 Enterprise, and that seems to have fixed a few errors while creating more. Reboots now take about 11-12 minutes. Before, the reinstall, they were 5-6 minutes. Note some of the errors below are the same, but repeat a few seconds later. Also, the same 4 services fail to start on a reboot. Manual starts still work.

I looked through my DNS, it looks fine. All references are to the lcoal machine, 10.1.1.9. Strange...

Trying to wait on MS hold again... I'll probably head to sleep and try again in the AM. I wish I could schedule a call, but I'm not even able to get through Level 2. I'll see if Level 1 will schedule a call for Level 2.

Good night,
-Ben

-----------------------
Application Log Errrors

Event Type:      Error
Event Source:      MSExchangeAL
Event Category:      LDAP Operations
Event ID:      8026
Date:            12/12/2003
Time:            12:35:02 AM
User:            N/A
Computer:      CARRIER
Description:
LDAP Bind was unsuccessful on directory carrier.net.operationemail.com for distinguished name ''. Directory returned error:[0x34] Unavailable.    

For more information, click http://www.microsoft.com/contentredirect.asp.


Event Type:      Error
Event Source:      MSExchangeDSAccess
Event Category:      Topology
Event ID:      2102
Date:            12/12/2003
Time:            12:35:02 AM
User:            N/A
Computer:      CARRIER
Description:
Process MAD.EXE (PID=800). All Domain Controller Servers in use are not responding:
carrier.net.operationemail.com
 

For more information, click http://www.microsoft.com/contentredirect.asp.

Event Type:      Error
Event Source:      MSExchangeDSAccess
Event Category:      Topology
Event ID:      2104
Date:            12/12/2003
Time:            12:35:02 AM
User:            N/A
Computer:      CARRIER
Description:
Process MAD.EXE (PID=800). All the DS Servers in domain are not responding.

For more information, click http://www.microsoft.com/contentredirect.asp.


Event Type:      Error
Event Source:      MSExchangeAL
Event Category:      LDAP Operations
Event ID:      8026
Date:            12/12/2003
Time:            12:35:08 AM
User:            N/A
Computer:      CARRIER
Description:
LDAP Bind was unsuccessful on directory carrier.net.operationemail.com for distinguished name ''. Directory returned error:[0x51] Server Down.    

For more information, click http://www.microsoft.com/contentredirect.asp.


Event Type:      Error
Event Source:      MSExchangeAL
Event Category:      LDAP Operations
Event ID:      8026
Date:            12/12/2003
Time:            12:35:09 AM
User:            N/A
Computer:      CARRIER
Description:
LDAP Bind was unsuccessful on directory carrier.net.operationemail.com for distinguished name ''. Directory returned error:[0x51] Server Down.    

For more information, click http://www.microsoft.com/contentredirect.asp.



Event Type:      Error
Event Source:      MSExchangeAL
Event Category:      Service Control
Event ID:      8250
Date:            12/12/2003
Time:            12:35:10 AM
User:            N/A
Computer:      CARRIER
Description:
The Win32 API call 'DsGetDCNameW' returned error code [0x862] The specified component could not be found in the configuration information.  The service could not be initialized.  Make sure that the operating system was installed properly.

For more information, click http://www.microsoft.com/contentredirect.asp.


Event Type:      Error
Event Source:      MSExchangeAL
Event Category:      LDAP Operations
Event ID:      8026
Date:            12/12/2003
Time:            12:35:19 AM
User:            N/A
Computer:      CARRIER
Description:
LDAP Bind was unsuccessful on directory carrier.net.operationemail.com for distinguished name ''. Directory returned error:[0x51] Server Down.    

For more information, click http://www.microsoft.com/contentredirect.asp.


Event Type:      Error
Event Source:      MSExchangeAL
Event Category:      LDAP Operations
Event ID:      8026
Date:            12/12/2003
Time:            12:35:20 AM
User:            N/A
Computer:      CARRIER
Description:
LDAP Bind was unsuccessful on directory carrier.net.operationemail.com for distinguished name ''. Directory returned error:[0x51] Server Down.    

For more information, click http://www.microsoft.com/contentredirect.asp.


Event Type:      Error
Event Source:      MSExchangeAL
Event Category:      LDAP Operations
Event ID:      8026
Date:            12/12/2003
Time:            12:35:21 AM
User:            N/A
Computer:      CARRIER
Description:
LDAP Bind was unsuccessful on directory carrier.net.operationemail.com for distinguished name ''. Directory returned error:[0x51] Server Down.    

For more information, click http://www.microsoft.com/contentredirect.asp.


Event Type:      Error
Event Source:      MSExchangeAL
Event Category:      LDAP Operations
Event ID:      8026
Date:            12/12/2003
Time:            12:35:22 AM
User:            N/A
Computer:      CARRIER
Description:
LDAP Bind was unsuccessful on directory carrier.net.operationemail.com for distinguished name ''. Directory returned error:[0x51] Server Down.    

For more information, click http://www.microsoft.com/contentredirect.asp.


Event Type:      Error
Event Source:      MSExchangeAL
Event Category:      Service Control
Event ID:      8250
Date:            12/12/2003
Time:            12:35:22 AM
User:            N/A
Computer:      CARRIER
Description:
The Win32 API call 'DsGetDCNameW' returned error code [0x862] The specified component could not be found in the configuration information.  The service could not be initialized.  Make sure that the operating system was installed properly.

For more information, click http://www.microsoft.com/contentredirect.asp.


Event Type:      Error
Event Source:      MSExchangeAL
Event Category:      Service Control
Event ID:      8250
Date:            12/12/2003
Time:            12:35:22 AM
User:            N/A
Computer:      CARRIER
Description:
The Win32 API call 'DsGetDCNameW' returned error code [0x862] The specified component could not be found in the configuration information.  The service could not be initialized.  Make sure that the operating system was installed properly.

For more information, click http://www.microsoft.com/contentredirect.asp.


System Event Log Errors
-------------------------

Event Type:      Error
Event Source:      W32Time
Event Category:      None
Event ID:      17
Date:            12/12/2003
Time:            12:47:21 AM
User:            N/A
Computer:      CARRIER
Description:
Time Provider NtpClient: An error occurred during DNS lookup of the manually configured peer 'time.apple.com'. NtpClient will try the DNS lookup again in 15 minutes. The error was: No such service is known. The service cannot be found in the specified name space. (0x8007277C)

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


Event Type:      Error
Event Source:      W32Time
Event Category:      None
Event ID:      29
Date:            12/12/2003
Time:            12:47:21 AM
User:            N/A
Computer:      CARRIER
Description:
The time provider NtpClient is configured to acquire time from one or more time sources, however none of the sources are currently accessible.  No attempt to contact a source will be made for 15 minutes. NtpClient has no source of accurate time.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


Event Type:      Error
Event Source:      Service Control Manager
Event Category:      None
Event ID:      7009
Date:            12/12/2003
Time:            12:50:02 AM
User:            N/A
Computer:      CARRIER
Description:
Timeout (30000 milliseconds) waiting for the Microsoft Exchange System Attendant service to connect.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


Event Type:      Error
Event Source:      Service Control Manager
Event Category:      None
Event ID:      7000
Date:            12/12/2003
Time:            12:50:02 AM
User:            N/A
Computer:      CARRIER
Description:
The Microsoft Exchange System Attendant service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


Event Type:      Error
Event Source:      Service Control Manager
Event Category:      None
Event ID:      7001
Date:            12/12/2003
Time:            12:50:02 AM
User:            N/A
Computer:      CARRIER
Description:
The Microsoft Exchange Information Store service depends on the Microsoft Exchange System Attendant service which failed to start because of the following error:
The service did not respond to the start or control request in a timely fashion.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


Event Type:      Error
Event Source:      Service Control Manager
Event Category:      None
Event ID:      7009
Date:            12/12/2003
Time:            12:50:02 AM
User:            N/A
Computer:      CARRIER
Description:
Timeout (30000 milliseconds) waiting for the Microsoft Exchange Management service to connect.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


Event Type:      Error
Event Source:      Service Control Manager
Event Category:      None
Event ID:      7000
Date:            12/12/2003
Time:            12:50:02 AM
User:            N/A
Computer:      CARRIER
Description:
The Microsoft Exchange Management service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.



Event Type:      Error
Event Source:      Service Control Manager
Event Category:      None
Event ID:      7001
Date:            12/12/2003
Time:            12:50:02 AM
User:            N/A
Computer:      CARRIER
Description:
The Microsoft Exchange MTA Stacks service depends on the Microsoft Exchange System Attendant service which failed to start because of the following error:
The service did not respond to the start or control request in a timely fashion.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


---------------------------------------------------------------------------------------------------------------------------------
0
bserebinAuthor Commented:
Hello All,

Well, after being on the phone with Microsoft Support for 534 minutes, yes, that's 8.9 hrs (beauty of Vonage [VoIP] reporting). The final "solution" was for me to do a reinstall of the OS and Exchange and restore the Exchange dbs (since it was testing, and no clients existed yet, restoring the 600MB of mail is not too bad). The tech. I spoke with was awesome, the problem was it was no matter how much we told Exchange Services to log, they wouldn't log. He conferenced in another group, Perfmon (I think, very serious guy) who made me do a series of tests, to prove that the problem was Exchange, and not AD or OS related, he did. So, we spent another 3.5 hrs trying to get more info on the problem. He spoke with countless others, all with no idea. We then discussed the debug options, but it's very time consuming, and I had already spent too much time. So, I decided to call it quits and follow the restore process. The debug was going to add another 4-8 hours, which I wasn't interested in. I did learn a lot though.

[update after 2 days of testing] I did a clean (NTFS format) and installed Win2k3 Enterprise & Exch 2k3 Enterprise and ran into the same exact problem (used solution 2 below, delayed start of services). Thinking it might be a hardware issue, I swapped the NIC and even pulled one of my CPU out. No affect. So, I uninstalled Exch 2k3 Enterprise and installed Exch 2k3 Std and ran into the same services startup problems. I then started testing on VMware and installed Win2k3 Std and Exch 2k3 Std and didn't run into any issues except for the shutdown erros in Exchange. Startup issues didn't occur though (thank goodness) and Installs were identical except for different hardware.
[/update comments end]

Some thing I learned from the Perfmon group, who deal with startup issues.

Minimal Services Required for bootup are:
Event Log
Plug and Play
Remote Procedure Call (RPC)
Windows Management Instrumentation
Logical Disk Manager (not always, depends on HD/partition config)

Required for DC Role
DNS Server
DNS Client
Server
Workstation
TCP/IP NetBIOS Helper Service

Print Spooler
- one of the last services to start


Provided by a Microsoft Enterprise Messaging Support Technician
----------------------------------------------------------------------------

1)      Backup database – verify it is consistent

From the Bin directory run ESEUTIL /MH D:\exchsrvr\mdbdata\priv1.edb (this is example location)

2)      Install Windows 2003 and required drivers

3)      Install Exchange 2003 with the same Org and Admin group name

4)      Dismount databases and delete all database files in the MDBDATA data folder

5)      In Exchange System Manager place a checkbox for “this database can be overwritten by a restore” on the database tab of the stores

6)      Restore the priv1.edb, priv1.stm, pub1.edb, and pub1.stm database files

7)      Mount the databases

8)      Run MBconn following the steps in Q271886

http://support.microsoft.com/default.aspx?scid=kb;en-us;271886

9) Initiate an update on the recipient update service


Solution 2 - to deal with those startup errors (Exch services not starting)
--------------------------------------------------------------------------------------
Even though the server had booted at 12:27:55 AM, and the exchange servers started 2 minutes later. Here are the event log errors, and then my method for slowing down the Exchange Services startup process.
 
Event Type: Error
Event Source: MSExchangeDSAccess
Event Category: Topology
Event ID: 2104
Date:  12/15/2003
Time:  10:44:44 AM
User:  N/A
Computer: CARRIER
Description:
Process INETINFO.EXE (PID=1396). All the DS Servers in domain are not responding.
 
For more information, click http://www.microsoft.com/contentredirect.asp.

 
Event Type: Error
Event Source: MSExchangeFBPublish
Event Category: General
Event ID: 8197
Date:  12/15/2003
Time:  12:06:45 PM
User:  N/A
Computer: CARRIER
Description:
Error initializing session for virtual machine CARRIER. The error number is 0x8004011d. Make sure Microsoft Exchange Store is running.
 
For more information, click http://www.microsoft.com/contentredirect.asp.

 
Method to Slow down Exchaneg Service Startup
 
http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/q137/8/90.asp&NoWebContent=1
 
Then, the one and only application value is a cmd script (c:\myservice\delaystart.cmd) that does a "sleep 120" (that's 2 minutes) and then net starts (method to start services from the command line) in the order that I think the exchange services start.

Delaystart.cmd Contents
----------------------------
sleep 120
net start msexchangeSA
net start resvc
net start msexchangeis
net start msexchangemgmt
net start msexchangemta
net start msexchangees
net start imap4svc
net start pop3svc
net start mssearch

----------------------------------------------------------------------------

These are some of the same errors on reinstall within my VMware Image

Event Type:      Warning
Event Source:      LSASRV
Event Category:      SPNEGO (Negotiator)
Event ID:      40960
Date:            12/19/2003
Time:            9:09:45 AM
User:            N/A
Computer:      CARRIER2
Description:
The Security System detected an authentication error for the server .  The failure code from authentication protocol Kerberos was "There are currently no logon servers available to service the logon request.
 (0xc000005e)".

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 5e 00 00 c0               ^..À    



Event Type:      Warning
Event Source:      LSASRV
Event Category:      SPNEGO (Negotiator)
Event ID:      40961
Date:            12/19/2003
Time:            9:09:45 AM
User:            N/A
Computer:      CARRIER2
Description:
The Security System could not establish a secured connection with the server .  No authentication protocol was available.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 88 03 00 c0               ?..À    



Event Type:      Warning
Event Source:      LSASRV
Event Category:      SPNEGO (Negotiator)
Event ID:      40960
Date:            12/19/2003
Time:            9:09:46 AM
User:            N/A
Computer:      CARRIER2
Description:
The Security System detected an authentication error for the server ldap/carrier2.net.operationemail.com.  The failure code from authentication protocol Kerberos was "There are currently no logon servers available to service the logon request.
 (0xc000005e)".

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 5e 00 00 c0               ^..À    


Event Type:      Warning
Event Source:      LSASRV
Event Category:      SPNEGO (Negotiator)
Event ID:      40961
Date:            12/19/2003
Time:            9:09:46 AM
User:            N/A
Computer:      CARRIER2
Description:
The Security System could not establish a secured connection with the server ldap/carrier2.net.operationemail.com.  No authentication protocol was available.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 88 03 00 c0               ?..À    


---------------------------------------------------------------------------------
0
mlnraoCommented:
Hi,

iam also facing the same issue.
i tried clean install did not help.

if i try to manually start the services everything will be fine.

Iam running in a mixed environment with exchange 5.5 in other domain/same exch org.

Here are my logs

Event Type:      Error
Event Source:      MSExchangeDSAccess
Event Category:      Topology
Event ID:      2104
Date:            2/6/2005
Time:            12:24:57 PM
User:            N/A
Computer:      BLRMAILSERV
Description:
Process INETINFO.EXE (PID=1444). All the DS Servers in domain are not responding.

For more information, click http://www.microsoft.com/contentredirect.asp.


Event Type:      Error
Event Source:      MSExchangeSA
Event Category:      General
Event ID:      1005
Date:            2/6/2005
Time:            12:24:58 PM
User:            N/A
Computer:      BLRMAILSERV
Description:
Unexpected error The server is not operational. Facility: Win32 ID no: 8007203a Microsoft Exchange System Attendant  occurred.

For more information, click http://www.microsoft.com/contentredirect.asp.


Event Type:      Information
Event Source:      MSExchangeSA
Event Category:      General
Event ID:      1004
Date:            2/6/2005
Time:            12:24:58 PM
User:            N/A
Computer:      BLRMAILSERV
Description:
Microsoft Exchange System Attendant failed to start.

For more information, click http://www.microsoft.com/contentredirect.asp.


Event Type:      Information
Event Source:      Microsoft Search
Event Category:      Search Service
Event ID:      7052
Date:            2/6/2005
Time:            12:24:59 PM
User:            N/A
Computer:      BLRMAILSERV
Description:
The Search service has loaded project <ExchangeServer_BLRMAILSERV priv46B5222A>.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


Event Type:      Error
Event Source:      Userenv
Event Category:      None
Event ID:      1030
Date:            2/6/2005
Time:            12:25:05 PM
User:            NT AUTHORITY\SYSTEM
Computer:      BLRMAILSERV
Description:
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.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

i tried changing key HKEY_LOCAL_MACHINE\SYSTEM \CurrentControlSet\Services\MSExchangeDSAccess\TopoCreateTimeoutSecs
as mentioned in http://www.microsoft.com/technet/prodtechnol/exchange/guides/E2k3TechRef/4a05e341-6332-4a33-967b-4ba4a643b247.mspx

but that did not help much, now the problem is random, will start automatically half of the times i reboot it.

After manual start of services as mentioned by  bserebin everything works fine.

Thanks
Lakshmi Narayana
0
David WilhoitSenior Consultant, ExchangeCommented:
Sounds like a DNS configuration, just off the cuff here. No external DNS is configured here, right? Exchange 200x uses internal only, so it can find the GC. On the DSaccess tab in the ESM, check to see that it's trying to connect to the proper server GC/DC/DNS.

If it's more than anything else, you should probably open another question, since this one doesn't answer your issue. good message board etiquette. :)

David
0
kevan<!-4AB71E16B22C7229E25144E693A861D9-->Commented:
To Kidego
You're a genius! I had a similar problem with the network card DNS of the Exchange 2003 pointing to first the internal GC/Domain controller etc and a secondary to the ISP - I just deleted the ISP DNS pointer and all worked.

Keep it simple - network card of Exchange Server 2003 now pointing just to main domain controller (there are only 2 servers here)
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.