Quantcast
Channel: Exchange Server 2013 - General Discussion forum
Viewing all articles
Browse latest Browse all 4521

Exchange 2010 install driving me to madness

$
0
0

I am, and have been trying to install exchange server 2010 onto a brand new server 2012 machine. I have literally tried every fix I can find, but nothing is working. So we will start with what I have done. Prior to starting this install, I did a full migration from a 2000 DC to the 2012 DC. It was complete with full replication etc. However, before I could install Exchange 2012, said 2000 server took a dump and everything was lost. (fortunatly the last IT person was super smart and did backups locally on that machine, and I as an interim IT person and not a computer guy by trade, and since I have no idea what I'm doing, didnt do a backup prior to migration). Anyway, thats where it sits. 

I was finally able to install the CAS role just tonight after tons and tons of errors, which I think were mostly due to having the powershell directory have that Kerbauth error. However, ever since installation I have been unable to connect either through EMC or EMS. (it should be noted that I have never been able to connect through emc or ems) At first I was getting the error that 

 : The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from the destination computer. The content type is absent or invalid.

I can't run the EMT shooter as it craps out when it tries to connect to the FQDN of the exchange server. So on the advice of about a million hours of research, i looked into the name of my powershell virtual directory and noticed it had an error. Through the cmd prompt I accessed the snapin for exchange and removed and rebuilt the powershell virtual exchange. I am now getting this error

  • Connecting to the remote server failed with the following error message: The WinRM client sent a request to an HTTP server and got a response saying the requested HTTP URL was not available. This is usually returned by a HTTP server that does not support the WS-Management protocol.

Every tech support forum I have seen points to the port bindings in iis, however, mine are correct and nothing has changed. Oddly enough, I can browse my default web page (goes to the iis place holder) but I can't "browse" anything within it, I either get an unhandled exception or a (in the case of the powershell directory) an excepption with details system.nullreferenceexception:obejct reference not set to an instance of an object.

I am at my wits end. I have recreated the virtual directory, kerbauth is good, wsman is good, CAS and Hub are installed with no errors, and I have full authority to run cmds in the exchange setting. It should probably be noted that I can't install any of the rollups, every single time I have tried it fails, my guess is because it can't connect to the exchange server. Also, both EMC and EMS give me the same error when I try and access them.

So I am out of options other then dropping 250 in support in the vague hope that they will be able to fix it. I have not yet uninstalled and reinstalled iis and CAS because honestly I'm to afraid to lose any progress I have made so far, however if its a viable solution, i'm in. Im not exactly literate in server so if you do have a complicated fix, if you can spell it out for me in detail I would appreciate it (ie: full paths to things like reg keys) . I have looked at pretty much every tech forum post there is, and I havnt found anything in addition to what I have already done. Please if you can help it would be much appreciated and if you're anywhere near colorado, the first round is on me! Thank you


Viewing all articles
Browse latest Browse all 4521

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>