John
Fri Aug 19 10:57:11 CDT 2005
You are correct, it is flawless. So now lets look at the Exchange Server
Setup Progress.log for any further detailed errors? I believe it is on the
root c:
--
John Oliver, Jr.
MCSE, MCT, CCNA, Exchange MVP
Microsoft Certified Partner
"Jerry Farkas" <JerryFarkas@discussions.microsoft.com> wrote in message
news:3F919AF8-1208-439B-8BB6-B5AE47FF56B0@microsoft.com...
> Everything seems to be fine. Heres is the collected data. I mean
> everything
> is flawless with these diags.
>
> This is from DCDIAG
>
> Doing initial required tests
>
> Testing server: Default-First-Site-Name\SASCMHAD1
> Starting test: Connectivity
> ......................... SASCMHAD1 passed test Connectivity
>
> Doing primary tests
>
> Testing server: Default-First-Site-Name\SASCMHAD1
> Starting test: Replications
> ......................... SASCMHAD1 passed test Replications
> Starting test: NCSecDesc
> ......................... SASCMHAD1 passed test NCSecDesc
> Starting test: NetLogons
> ......................... SASCMHAD1 passed test NetLogons
> Starting test: Advertising
> ......................... SASCMHAD1 passed test Advertising
> Starting test: KnowsOfRoleHolders
> ......................... SASCMHAD1 passed test KnowsOfRoleHolders
> Starting test: RidManager
> ......................... SASCMHAD1 passed test RidManager
> Starting test: MachineAccount
> ......................... SASCMHAD1 passed test MachineAccount
> Starting test: Services
> ......................... SASCMHAD1 passed test Services
> Starting test: ObjectsReplicated
> ......................... SASCMHAD1 passed test ObjectsReplicated
> Starting test: frssysvol
> ......................... SASCMHAD1 passed test frssysvol
> Starting test: frsevent
> ......................... SASCMHAD1 passed test frsevent
> Starting test: kccevent
> ......................... SASCMHAD1 passed test kccevent
> Starting test: systemlog
> ......................... SASCMHAD1 passed test systemlog
> Starting test: VerifyReferences
> ......................... SASCMHAD1 passed test VerifyReferences
>
> Running partition tests on : ForestDnsZones
> Starting test: CrossRefValidation
> ......................... ForestDnsZones passed test
> CrossRefValidati
>
> Starting test: CheckSDRefDom
> ......................... ForestDnsZones passed test CheckSDRefDom
>
> Running partition tests on : DomainDnsZones
> Starting test: CrossRefValidation
> ......................... DomainDnsZones passed test
> CrossRefValidati
>
> Starting test: CheckSDRefDom
> ......................... DomainDnsZones passed test CheckSDRefDom
>
> Running partition tests on : Schema
> Starting test: CrossRefValidation
> ......................... Schema passed test CrossRefValidation
> Starting test: CheckSDRefDom
> ......................... Schema passed test CheckSDRefDom
>
> Running partition tests on : Configuration
> Starting test: CrossRefValidation
> ......................... Configuration passed test
> CrossRefValidatio
> Starting test: CheckSDRefDom
> ......................... Configuration passed test CheckSDRefDom
>
> Running partition tests on : sascmh
> Starting test: CrossRefValidation
> ......................... sascmh passed test CrossRefValidation
> Starting test: CheckSDRefDom
> ......................... sascmh passed test CheckSDRefDom
>
> Running enterprise tests on : sascmh.siemens.com
> Starting test: Intersite
> ......................... sascmh.siemens.com passed test Intersite
> Starting test: FsmoCheck
> ......................... sascmh.siemens.com passed test FsmoCheck
>
>
> This is from Netdiag
>
>
> Computer Name: SASCMHMSG1
> DNS Host Name: sascmhmsg1.sascmh.siemens.com
> System info : Windows 2000 Server (Build 3790)
> Processor : x86 Family 15 Model 4 Stepping 1, GenuineIntel
> List of installed hotfixes :
> KB890046
> KB893756
> KB896358
> KB896422
> KB896428
> KB896727
> KB899587
> KB899588
> KB899591
> KB901214
> Q147222
>
>
> Netcard queries test . . . . . . . : Passed
>
>
>
> Per interface results:
>
> Adapter : Local Area Connection 3
>
> Netcard queries test . . . : Passed
>
> Host Name. . . . . . . . . : sascmhmsg1
> IP Address . . . . . . . . : 136.157.175.13
> Subnet Mask. . . . . . . . : 255.255.255.128
> Default Gateway. . . . . . : 136.157.175.2
> Dns Servers. . . . . . . . : 136.157.175.6
> 136.157.175.11
>
>
> AutoConfiguration results. . . . . . : Passed
>
> Default gateway test . . . : Passed
>
> NetBT name test. . . . . . : Passed
> [WARNING] At least one of the <00> 'WorkStation Service', <03>
> 'Messe
> r Service', <20> 'WINS' names is missing.
>
> WINS service test. . . . . : Skipped
> There are no WINS servers configured for this interface.
>
>
> Global results:
>
>
> Domain membership test . . . . . . : Passed
>
>
> NetBT transports test. . . . . . . : Passed
> List of NetBt transports currently configured:
> NetBT_Tcpip_{745F3690-A747-4C9D-8466-0D8E70D95473}
> 1 NetBt transport currently configured.
>
>
> Autonet address test . . . . . . . : Passed
>
>
> IP loopback ping test. . . . . . . : Passed
>
>
> Default gateway test . . . . . . . : Passed
>
>
> NetBT name test. . . . . . . . . . : Passed
> [WARNING] You don't have a single interface with the <00> 'WorkStation
> Se
> ce', <03> 'Messenger Service', <20> 'WINS' names defined.
>
>
> Winsock test . . . . . . . . . . . : Passed
>
>
> DNS test . . . . . . . . . . . . . : Passed
>
>
> Redir and Browser test . . . . . . : Passed
> List of NetBt transports currently bound to the Redir
> NetBT_Tcpip_{745F3690-A747-4C9D-8466-0D8E70D95473}
> The redir is bound to 1 NetBt transport.
>
> List of NetBt transports currently bound to the browser
> NetBT_Tcpip_{745F3690-A747-4C9D-8466-0D8E70D95473}
> The browser is bound to 1 NetBt transport.
>
>
> DC discovery test. . . . . . . . . : Passed
>
>
> DC list test . . . . . . . . . . . : Passed
>
>
> Trust relationship test. . . . . . : Passed
> Secure channel for domain 'SASCMH' is to
> '\\sascmhad2.sascmh.siemens.com'
>
>
> Kerberos test. . . . . . . . . . . : Passed
>
>
> LDAP test. . . . . . . . . . . . . : Passed
>
>
> Bindings test. . . . . . . . . . . : Passed
>
>
> WAN configuration test . . . . . . : Skipped
> No active remote access connections.
>
>
> Modem diagnostics test . . . . . . : Passed
>
> IP Security test . . . . . . . . . : Skipped
>
> Note: run "netsh ipsec dynamic show /?" for more detailed information
>
>
> The command completed successfully
>
>
> "John Oliver, Jr. [MVP]" wrote:
>
>> During the Exchange Deployement Wizard did you run DCDIAG and NETDIAG?
>> Any
>> errors?
>>
>> --
>> John Oliver, Jr.
>> MCSE, MCT, CCNA, Exchange MVP
>> Microsoft Certified Partner
>>
>> "Jerry Farkas" <JerryFarkas@discussions.microsoft.com> wrote in message
>> news:97D1266D-A40B-4A63-8EE5-170AD3394E04@microsoft.com...
>> > John, I uninstalled ASP and IIS etc.. and reinstalled and I also
>> > uninstalled
>> > Exchange 2003 and now when I go to run the Standard setup for Exchange
>> > 2003 I
>> > get that same error. It doesnt make sense and Im at a lose. You got
>> > anymore
>> > ideas?
>> >
>> >
>> > Thanks.
>> >
>> > "John Oliver, Jr. [MVP]" wrote:
>> >
>> >> Do you have all IIS prerequisites installed on the server?
>> >>
>> >>
http://www.microsoft.com/technet/prodtechnol/exchange/guides/Ex2k3DepGuide/ce7d539d-ee38-4a71-9ba8-cebeb7bb1512.mspx
>> >>
>> >> --
>> >> John Oliver, Jr.
>> >> MCSE, MCT, CCNA, Exchange MVP
>> >> Microsoft Certified Partner
>> >>
>> >> "Jerry Farkas" <JerryFarkas@discussions.microsoft.com> wrote in
>> >> message
>> >> news:FB894414-FF25-49BF-8134-0287B4392291@microsoft.com...
>> >> >I got AD going and dns etc... I have 2 existing exchange 5.5
>> >> >servers.
>> >> >One
>> >> > is called MSG and the other is sascmhmsg02. MSG is the main
>> >> > Exchange
>> >> > 5.5
>> >> > server. I did the Exchange 2003 on a different server called
>> >> > sascmhmsg1
>> >> > and choose to Coexist
>> >> > with my Exchange 5.5 server. I have ADC working perfectly and I
>> >> > went
>> >> > to
>> >> > install Exchange 2003 and have it coexist with my Exchange 5.5
>> >> > servers
>> >> > and
>> >> > I
>> >> > get the following error when It goes to nstall the Messaging and
>> >> > Collaboration Services.
>> >> >
>> >> > Setup encountered an error while checking the prerequisites for the
>> >> > component "Microsoft Exhcnage Messaging and Collaboration Services":
>> >> > 0XFFFFFFAF (65455: An Unknown Error has Occurred.
>> >> >
>> >> > Anyone know hwo to resolve this issue?
>> >> >
>> >> > Thanks.
>> >> >
>> >> >
>> >> >
>> >> >
>> >>
>> >>
>> >>
>>
>>
>>