I am assuming that by clicking the checkbox you want to make it so that the schema CAN be modified on this DC...
It was already checked so I unchecked it and rechecked it to activate the OK button and then clicked OK.
However, after doing that it again fails with the exact same error. No permission or the server is too busy. The server CAN'T be too busy...and that probably just means the attempt timed out due to failure of the permissions.
Honestly...until I lay my eyes on a machine running Exchange 2003 I won't believe it CAN actually be installed...:-D
Posts: 1917
Joined: 12.Apr.2005
From: London
Status: offline
Wow, back to the drawing board - can you set the administrator account (the account that you are logged on with) TEMP path to a folder such as C:\TEMP?
Posts: 1917
Joined: 12.Apr.2005
From: London
Status: offline
Hiya mate, on the Domain Controller - right click on the "My Computer" and select "Properties" - select the "Advanced" tab and then click on the "Environment Variables" button - in the top box, change both the TEMP and TMP values to c:\temp.
Here is a related but at he same time off topic question..BUT...we have Exchange 2007 standard here also. HOWEVER, when I drop the CD in the drive and do the install with it the error comes up saying it doesn't support our processor.
This is a brand new box with Xeon CPU's. Why would e2k7 NOT support that CPU?
M$ is really starting to upset me...this is exactly why I have run linux on my servers for so many years...
Will exchange 2000 run on server 2003 and possibly update to 2003 ok? I am considering trying to install my personal copy of e2k here and then updating to the e2k3 if it manages to install properly.
I have acces to some local exchange experts that I can possibly pull a favor with...at this point I am just stumped...
Also I can not do much with the DC during business hours and I am the only person that would ever come in after hours to get this job done...pretty lame all the way around...
Posts: 1917
Joined: 12.Apr.2005
From: London
Status: offline
Hiya Chris, Exchange 2000 will not install on Windows 2003 (see http://support.microsoft.com/?kbid=321648) - I am going to look into something for you can will get back to you soon.
I ran a DCDIAG and NETDIAG on the box I am installing the exchange on. Maybe they will give a little insight. I checked the links that you posted here and all of what they point to seems fine. Anyway...here are the dc and net diag logs.
Sorry I was a little vague in the very first post. I think I followed up with enough information though.
Here is the dcdiag.
quote:
dcdiag:
C:\Documents and Settings\Administrator.FFCU>dcdiag /s:06ffcudc
Testing server: Default-First-Site-Name\06FFCUDC Starting test: Replications [Replications Check,06FFCUDC] A recent replication attempt failed: From 06FFCUBC to 06FFCUDC Naming Context: CN=Schema,CN=Configuration,DC=ffcu The replication generated an error (1722): The RPC server is unavailable. The failure occurred at 2007-08-06 12:01:08. The last success occurred at 2006-12-29 13:58:00. 5302 failures have occurred since the last success. [06FFCUBC] DsBindWithSpnEx() failed with error 1722, The RPC server is unavailable.. The source remains down. Please check the machine. [Replications Check,06FFCUDC] A recent replication attempt failed: From 06FFCUBC to 06FFCUDC Naming Context: CN=Configuration,DC=ffcu The replication generated an error (1722): The RPC server is unavailable. The failure occurred at 2007-08-06 12:00:45. The last success occurred at 2006-12-29 14:51:13. 5302 failures have occurred since the last success. The source remains down. Please check the machine. [Replications Check,06FFCUDC] A recent replication attempt failed: From 06FFCUBC to 06FFCUDC Naming Context: DC=ffcu The replication generated an error (1722): The RPC server is unavailable. The failure occurred at 2007-08-06 12:00:22. The last success occurred at 2006-12-29 15:03:17. 5301 failures have occurred since the last success. The source remains down. Please check the machine. ......................... 06FFCUDC passed test Replications Starting test: NCSecDesc ......................... 06FFCUDC passed test NCSecDesc Starting test: NetLogons ......................... 06FFCUDC passed test NetLogons Starting test: Advertising Warning: 06FFCUDC is not advertising as a time server. ......................... 06FFCUDC failed test Advertising Starting test: KnowsOfRoleHolders ......................... 06FFCUDC passed test KnowsOfRoleHolders Starting test: RidManager ......................... 06FFCUDC passed test RidManager Starting test: MachineAccount ......................... 06FFCUDC passed test MachineAccount Starting test: Services w32time Service is stopped on [06FFCUDC] ......................... 06FFCUDC failed test Services Starting test: ObjectsReplicated ......................... 06FFCUDC passed test ObjectsReplicated Starting test: frssysvol ......................... 06FFCUDC passed test frssysvol Starting test: frsevent There are warning or error events within the last 24 hours after the SYSVOL has been shared. Failing SYSVOL replication problems may cause Group Policy problems. ......................... 06FFCUDC failed test frsevent Starting test: kccevent ......................... 06FFCUDC passed test kccevent Starting test: systemlog An Error Event occured. EventID: 0xC00010DF Time Generated: 08/06/2007 12:08:37 (Event String could not be retrieved) An Error Event occured. EventID: 0xC00010DF Time Generated: 08/06/2007 12:10:39 (Event String could not be retrieved) ......................... 06FFCUDC failed test systemlog Starting test: VerifyReferences ......................... 06FFCUDC passed test VerifyReferences
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 CrossRefValidation Starting test: CheckSDRefDom ......................... Configuration passed test CheckSDRefDom
Running partition tests on : ffcu Starting test: CrossRefValidation ......................... ffcu passed test CrossRefValidation Starting test: CheckSDRefDom ......................... ffcu passed test CheckSDRefDom
Running enterprise tests on : ffcu Starting test: Intersite ......................... ffcu passed test Intersite Starting test: FsmoCheck Warning: DcGetDcName(TIME_SERVER) call failed, error 1355 A Time Server could not be located. The server holding the PDC role is down. Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error 135 5 A Good Time Server could not be located. ......................... ffcu failed test FsmoCheck
C:\Documents and Settings\Administrator.FFCU>
I did notice some failures in there. I am not familiar with the DCDIAG too much, but I am going to go through it and figure out as much of it as I can.
The netdiag is below also.
quote:
netdiag:
C:\Documents and Settings\Administrator.FFCU>netdiag
...................................
Computer Name: INTWEB DNS Host Name: INTWEB.ffcu System info : Microsoft Windows Server 2003 R2 (Build 3790) Processor : x86 Family 6 Model 15 Stepping 6, GenuineIntel List of installed hotfixes : KB924667-v2 KB925398_WMP64 KB925902 KB926122 KB927891 KB929123 KB930178 KB931784 KB931836 KB932168 KB933566 KB933566-IE7 KB933854 KB935839 KB935840 KB936357 Q147222
Netcard queries test . . . . . . . : Passed [WARNING] The net card 'Broadcom BCM5708C NetXtreme II GigE (NDIS VBD Client )' may not be working. [WARNING] The net card 'Intel(R) PRO/1000 PT Dual Port Server Adapter' may n ot be working. [WARNING] The net card 'Intel(R) PRO/1000 PT Dual Port Server Adapter #2' ma y not be working.
Per interface results:
Adapter : Local Area Connection 4
Netcard queries test . . . : Failed NetCard Status: DISCONNECTED Some tests will be skipped on this interface.
NetBT name test. . . . . . : Passed [WARNING] At least one of the <00> 'WorkStation Service', <03> 'Messenge 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_{2FCE18F8-7C4F-4EF5-9460-C613CA5C2288} 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 Servi 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_{2FCE18F8-7C4F-4EF5-9460-C613CA5C2288} The redir is bound to 1 NetBt transport.
List of NetBt transports currently bound to the browser NetBT_Tcpip_{2FCE18F8-7C4F-4EF5-9460-C613CA5C2288} The browser is bound to 1 NetBt transport.
DC discovery test. . . . . . . . . : Passed
DC list test . . . . . . . . . . . : Passed
Trust relationship test. . . . . . : Passed Secure channel for domain 'FFCU' is to '\\06ffcudc.ffcu'.
Kerberos test. . . . . . . . . . . : Passed
LDAP test. . . . . . . . . . . . . : Passed [WARNING] Failed to query SPN registration on DC '06ffcubc.ffcu'.
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
This is the first and only DC they have every had. They have a BDC (Back-up DC), but it is no longer on line and all it was used for was a back-up in case this one dies.
I am assuming the 'sites' list is what you are talking about. I have in that list:
Sites> default first sites> servers> 06ffcubc 06ffcudc
There isn't much else in there.
Did the DC and NET diag logs mean anything to you? :)
Posts: 1917
Joined: 12.Apr.2005
From: London
Status: offline
Yes mate, they did - I think that there is an issue in ad with the old "BDC" (which I am assuming is 06ffcubc) - you see there is technically no such thing as a BDC in Windows 200x as it operates what is called a multi master environment.
It would seem at the very least the entry for the BDC is still in site and services (which is giving you the replication errors) can you let me know which server is holding you FSMO roles - in particular the schema master? - you can find whom has the schema master role by using the Schema tool that we install when trying to ensure the schema was set to edit - when in the Schema Management Tool right click on the "Active Directory Schema" and then choose operations master.
Well the '06ffcubc' is merely a desktop computer that is now actually broken and sits in the corner. It is not in any way shape or form connected to the network.
Can I just delete that entry possibly?
I am heading to lunch, but will be back in roughly an hour to investigate further into the schema arrangement with the network.
Posts: 1917
Joined: 12.Apr.2005
From: London
Status: offline
Ok mate, be sure that the machine is gone - then yes you can delete it from the replication topology, then on your working domain controller complete the following;
Start->Run
type CMD and then at the command prompt type:
ntdsutil
then type "roles" (no quotation marks) <press enter>
then type "connections" <press enter>
then type "connect to server <servername> (you must use the server name of your DC)
then type "q"
then type "seize schema master"
You will be prompted if this is ok - say yes.
The screen will change with some information - when the process has finished type "quit" the press enter then type "quit" again and press enter.
I did discuss this with the other person that I work with as to what the BDC box is doing..status wise anyway.
He says it started making noise so they just turned it off and stuck in in a corner...lame...
Anyway..IF in fact I delete it from the whole network will we be able to add it again once the exchange is installed or should I just fire it up and figure out what the 'noise' is...heh.
We are technically required to have a BDC at another site, but they just never got to that point before the thing crapped out.
I would hate to delete it then find we need it...:) If I got it back online and working, though, would that possible sort out the replication error since it is back online and working?