Yes, I can connect to the dc/ex5.5 box
from the new ex2k3 member server using ldp on both ports 389 and 38900. I can
also bind using the enterprise/domain admin account and the ex service account. I am not trying to do a direct upgrade
from 5.5 to 2k3, rather I am trying to do an interim upgrade to ex2k, then
upgrade from ex2k to ex2k3. I am receiving the database inconsistent errors
when trying to do the ex2k upgrade. Note: I am not sure if it matters, but in
ex5.5 administrator, the ldap protocol for the site is set to 38900, but for
the server it is set to 389. I tried changing it in the server to 38900, but
that stopped mail from flowing. Dan From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brian Desmond Could be all sorts
of things here, but lets start simple. Can you do an ldap bind to the exchange
box on port 38900 using the ldp tool (or similar) from the support tools? You can’t do
an inplace upgrade from 5.5 to 2003 which is what it sounds like you’re
doing when you get the consistency error. From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dan DeStefano I have taken over administration of a w2k AD domain running
Exchange 5.5. This domain was a mess and it took a lot of doing just to resolve
all the errors in the event logs, but now they are just about all resolved and
the DC/Ex5.5 server passes all netdiag/dcdiag tests. My current project is to upgrade the Ex5.5 server (which is
also the domain’s only DC) to Ex2k3, but I am running into problems. I
have successfully run Forestprep and Domainprep. However, when I attempt to run
the installation, I receive the error “Exchange… cannot be assigned
the task “upgrade” because… the directory database is in an
inconsistent state… the private and or public stores are in an
inconsistent state”. However, when using Eseutil to check database
consistency of all 3 databases, it reports that they are consistent. Even so, I
tried using Eseutil to: repair all 3 DBs and perform soft recovery on all 3
DBs, but nothing worked. I then ran every test/repair using isinteg, all of
which completed successfully and only some of which reported errors. However,
nothing has worked and I am still getting the same errors when trying to
upgrade. I also upgraded the ADC to the Ex2k SP3 version, which had no effect. Now my plan is to install a new WS2k3/Ex2k3 server into the
Ex5.5 organization, move all mailboxes to it, then decommission the old Ex5.5
box. While waiting for my maintenance window to upgrade the current ADC to the
2k3 version, I installed EX2k3 ADC on the new mail server (which is not a DC).
Now, when I try to run the “Data collection” step in ADC tools on
the new ws2k3 box, I receive the error “Server <myserver>:389 is
not an Exchange 5.5 server or an SRS service”. I realized that since it
was installed on a DC that the LDAP port in ADC was changed to 38900, so I
changed it in ADC tools. However, I am now receiving the error “Could not
connect to server <myserver>:38900 with LDAP error 6. Check server
name, port number and account permissions”. I am logged on with the
Enterprise/Domain Administrator account and the ADC service is set to use the
same service account as the ADC on the Ex5.5 server. If you need any more info please let me know. Any help that anyone can provide will be greatly
appreciated. Dan DeStefano Info-lution Corporation MCSE - 2073750 If you have received this message in error
please notify the sender, disregard any content and remove it from your
possession. If you have received this message in error please notify the sender, disregard any content and remove it from your possession. |
- RE: [ActiveDir] Exchange 5.5 Upgrade Problems Brian Desmond
- RE: [ActiveDir] Exchange 5.5 Upgrade Problems Dan DeStefano
- RE: [ActiveDir] Exchange 5.5 Upgrade Problems Brian Desmond
- RE: [ActiveDir] Exchange 5.5 Upgrade Problems Dan DeStefano
- RE: [ActiveDir] Exchange 5.5 Upgrade Problems Dan DeStefano
- RE: [ActiveDir] Exchange 5.5 Upgrade Problems Dan DeStefano
- RE: [ActiveDir] Exchange 5.5 Upgrade Problems Dan DeStefano