Brad,
not that this is any help with your issue right now, but next time, could
you please reply with history of original message, and perhaps some of the
responses? This would allow those of us who hadn't followed the thread
from inception, to possibly might be of more assistance...
Thanks
Pat
Brad Foss
<BradFoss@Neopo To: "MS-Exchange Admin Issues"
stinc.com> <[EMAIL PROTECTED]>
cc:
10/22/2001 Subject: Exchange Servers Stopped
Talking - Update
04:02 PM
Please respond
to "MS-Exchange
Admin Issues"
Thank you for all of you that posted suggestions!
Our story so far...
We have three Exchange servers (5.5 SP3) in the same site. Two of the
servers are in one NT 4.0 domain, the third is in a W2K AD domain.
This was working, until we had to change the IP addressing scheme in our NT
4.0 domain.
We changed the address for the DNS and WINS server in the Exchange server
in
the AD domain. We can ping the other two servers by name form the AD
domain.
The users on the Exchange server in the AD domain can send mail to each
other, just not to anyone on the NT 4.0 Exchange servers.
I've restarted the servers with no success.
I've tested the network connectivity and found nothing wrong. I can
PCAnywhere to the server. RCPING returns no errors.
I did discover that of the three Exchange servers, the one in the AD domain
shows up in Exchange Administrator as NOT having SP3 installed, even though
I KNOW I installed it.
So, I copied the SP3 files to the server and started the "Update"
During the update, I get the error(s);
----------------------------------------------------------------------
The command
lodctr dsactrs.ini
failed, returning an error code of <1010>
[OK]
Processing file path\server.ins at or near line 153.
An internal component has failed.
Id No. C103798a
[OK]
An internal component has failed
Microsoft Exchange Server Setup
ID no: c103798a
[OK]
According to Technet this is caused by;
1. SNMP locks open the PREf009a.dat file or the PREF009f.dat file
and
stops the installation
2. The following two files in the <WINNT>\SYSTEM32 directory are
either
missing, corrupt or you do not have permission to access them:
Perfc009.dat
Perfh009.dat
3. This behavior occurs if the read-only attribute is set on the
Perfc009.dat and Perfh009.dat files or if the files are locked open by
another process (in the System32 folder).
Or
4. To work around this problem, follow these steps:
Back up and then remove the following registry entries:
HEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EDB\Peformance
HEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ESE\Peformance
HEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeDS\Peformance
HEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\Peformance
HEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeMTA\Peformance
So I;
1.) Stopped the SMTP process,
2.) Verified the permissions on the Perfc009.dat and Perfh009.dat and when
they were correct, extracted new files from the Exchange install CD.
3.) Conformed that the two files weren't 'read-only'
4.) Backed up and deleted the listed registry keys.
I'd like to report success, but I can't.
I can say I'm open to suggestions!
TIA!
List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm
List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm
