Exchange Service Pack 3 upgrade

[YFronts]

Hi all,

Wonder if anyone has seen this before, technet doesn't seem to have a clue.

We have (finally) decided to upgrade our Exchange 2000 servers to Service Pack 3. Those who've done this before will be aware that the front end server requires upgrading before the back end servers. Our front end server upgraded without any problems, as did the root Exchange server then 2 backend servers.
However, after running the update.exe one of the backend servers I arrive at the components selection screen, I cannot continue until I select 'update' from below messaging and collaboration services, at which point a message tells me:

"The component Microsoft Exchange Messaging and Collaboration Services" cannot be assigned the action "Update" because:
- You must be at least an Exchange Full Administrator at the Administrative Group level to run update. You must use an account that has been granted the Exchange Full Administrator role on the current administrative group , or a higher-level role, using the Exchange Administrative Delefation Wizard/
- Setup is unable to access the Windows 2000 Active Directory
- Failed to contact the Schema Master server for this Active Directory forest."

All 3 backend servers are on different sites, and are connected through a VPN, never had any issues contacting the forest domain controller and replication runs well. Tried several accounts all been delegated control at the top of the forest through the Exchange delegation wizard and are additionally enterprise admins accounts.

Anybody have a clue what on earth this could be about? This server is also a DC and all enterprise admins have full control access rights to it. Any help whatsoever will be greatly appreciated my techie mates!

Thanks

 

[lanamater]

Try using NTDSUTIL from the command line to determine what that box is seeing as the Schema Master and other roles. If is is incorrect-seize the correct schema master and retry.

/m

 

[YFronts]

Thanks for that - tried it and it saw the schema master and domain naming correctly plus the domain roles correctly too.
That is to say, it sees the same schema master as the other back end servers (that upgraded succesfully) do.
Weird..

 

[lanamater]

Yeah that happened to me on a upgrade to SP3. I ended up having to use the actual account used to originally install Exchange (like the administrator account). I had delegated permissions and Enterprise admin and all that-nothing.

It would not work until I used the other account. It is like is holds a ghost account reference or something. However, I thought I would mention it, in case you have access to the original account.

/m

 

[YFronts]

Cheers for that. I have tried every enterprise admin account but not totally sure whether any of them were the original Exchange installation accounts.
Guess what, one of the root servers is still on SP2 for Windows. The guy who was meant to upgrade it overlooked one of the most important servers whilst upgrading to SP2, that is to say it was the Schema master. However, it appears the schema master is no longer on this server. We'll have to see once the upgrade to SP3 takes place tonight.
I'll keep you informed.

 

[YFronts]

Damn..not even upgrading that server made a difference, still exactly the same problem. Totally stumped on this one now, was convinced that was the cause yesterday. Any information, really anything would be great. You never know what you're overlooking.
Cheers all.

 

[lanamater]

http://support.microsoft.com/?kbid=264001

Did you see this?

 

[YFronts]

I hadn't seen that, or even thought about it. However, I forgot to mention that this server is actually a DC and this doc refers to setups on member servers only.
Nevertheless, it pointed me in the right direction. I checked DNS settings on both this DC and and another one, the DHCP server and the settings were all messed up. For resolution of unqualified names I had 'append primary and connection specific DNS suffixes' checked, and consequently there were no DNS suffixes listed in the box below (see in advanced DNS settings). I added in the correct suffixes and a few minutes later was able to run the setup no problem.
Thanks a load for your advice lanamater! B-)

 

[lanamater]

COOL--You da man!