having problems on new server so I followed instructions to remove Exchange Server 2013 Sp1 using ADSI edit p;er these instructions:

http://blog.dargel.at/2012/11/20/complete-remove-exchange-2013-using-adsiedit/

now when I re-run setup for exchange 2013 SP1 I get the error :    

"Error: The type initializer for 'Microsoft.Exchange.Configuration.Tasks.ThrottlingModule`1' threw an exception."

that is a dumb  answer, no help just you did it wrong! 

how else do you remove exchange when install is corrupt?

brand new install failed, all MS suggestions failed so I had to remove it and reinstall 

I suppose I should never use regedit and MS stuff never fails....

several KB's refer to ADSI edit

Hi,

I have seen some people have the above error you meet. In that case, formatting the Exchange server is the recommended method. What's more, please install fresh AD and then install Exchange 2013.

What's more, please check if there is anything left about old Exchange server in ADSIEdit. If yes, please delete it.

Hope it helps.

Best regards,

If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

ok reinstalled server 2012, exchange2013 and now I got an error about database not connected, fixed that

so now when I try to access EAC I get error:

Hi,

The above error occurs if the "deny" permission is effective on the ms-Exch-EPI-Token-Serialization user right on a computer object that has an Exchange Server 2013 role assigned.

In order to resolve this issue, you need to remove the computer object from the restricted group.

Note: After the above setting, you need to restart the computer that has the Exchange Server 2013 role assigned.

For more information, here is a kb for your reference.

Error message in EMS, EAC, ECP, or OWA in Exchange Server 2013

http://support.microsoft.com/kb/2898571

Hope it helps.

Best regards,

If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

I ran Get-ADPermission -Identity <ExchangeComputerObject> | where {($_.ExtendedRights -like "ms-Exch-EPI-Token-Serialization") -and ($_.Deny -like "True")} | ft -autosize User,ExtendedRights

why are domain admins denied?

the exchange server is not a member of those groups

this time I get :

this is a clean install I have not deleted anything

Server Error in '/ecp' Application.

Hi,

For the error code 404, it means not found. To know if the problem is with the DNS resolution, we can login ecp using the following url and see if it can access successfully:

https://localhost/ecp.

Please also confirm if the error comes before you entering the user credential or after you entering the credential.

Sent By

Silver

• Edited by Silver ShenModerator Friday, July 04, 2014 5:36 AM wrong

Hi,

Any update?

Sent By

Silver

I get that same error locally or not.

seems like maybe an IIS permissions thing. Wish I could just check or re-run setup for  the IIS part like permissions and setup

• Edited by Sheetzhappens Wednesday, July 09, 2014 4:24 PM

What's dumb is that you ask the question after you do the dumb thing and then call the person who answers your question dumb because he doesn't agree with your dumb

Hi,

We can try to recreate ECP VD or OWA VD to reset the paermission:

Remove-EcpVirtualDirectory

http://technet.microsoft.com/en-us/library/dd351147(v=exchg.150).aspx

New-EcpVirtualDirectory

http://technet.microsoft.com/en-us/library/dd351218(v=exchg.150).aspx

Sent By

Silver

What is dumb is that you complain that I didn't tell you something you didn't ask for.

To answer that question, what you would do is complete the failed installation or run a recovery installation (/RecoverServer) and then remove the server.  That is what is supported.

Hi,

We can try to recreate ECP VD or OWA VD to reset the paermission:

Remove-EcpVirtualDirectory

http://technet.microsoft.com/en-us/library/dd351147(v=exchg.150).aspx

New-EcpVirtualDirectory

http://technet.microsoft.com/en-us/library/dd351218(v=exchg.150).aspx

Sent By

Silver

no joy same error

403 Sorry! Access denied :( You don't have permission to open this page. If you're a new user or were recently assigned credentials, please wait 15 minutes and try again. You're still signed in. If you want to sign out, use the link below.

I click refresh page and then get this:

Server Error in '/ecp' Application.

actually I did ask for help, telling me that it is not supported offered no help

even this MS KB suggests ADSI edit - 

http://technet.microsoft.com/en-us/library/dd876880(v=exchg.150).aspx

now I have a new error and you are still not really helping

BTW - I had completed the failed installation and tried /recoverserver with no luck

Yeah, it tells you to use ADSI Edit, but to look something up, not to remove the server, which, despite all the well-meaning posts, is unsupported, likely for reasons that caused your problems.

BTW, had you completed the failed installation, there would have been no need to run /recoverserver.  Instead, what you should have done at that point would have been to run /mode:uninstall.  So what did you really do?

Post complete and consistent information and don't take such an argumentative and arrogant attitude, then maybe you'll get more and better help.

Yeah, it tells you to use ADSI Edit, but to look something up, not to remove the server, which, despite all the well-meaning posts, is unsupported, likely for reasons that caused your problems.

BTW, had you completed the failed installation, there would have been no need to run /recoverserver.  Instead, what you should have done at that point would have been to run /mode:uninstall.  So what did you really do?

Post complete and consistent information and don't take such an argumentative and arrogant attitude, then maybe you'll get more and better help.

1.  How many times it has been used is not relevant to whether or not it's supported.  You've followed unsupported practices so many times in the past yet you have troubles today.  I made my post that in the future someone who finds this thread knows the support stance before following the same procedure you did.  I'm wasn't telling you to do anything different since your damage is done.

2.  The ADSI Edit method may leave links behind, which is why it's not supported.  I can't say whether that is the cause of your problems or not based on what you posted.

3.  Have you Binged "exchange 2013 ecp 404"?

1.  How many times it has been used is not relevant to whether or not it's supported.  You've followed unsupported practices so many times in the past yet you have troubles today.  I made my post that in the future someone who finds this thread knows the support stance before following the same procedure you did.  I'm wasn't telling you to do anything different since your damage is done.

2.  The ADSI Edit method may leave links behind, which is why it's not supported.  I can't say whether that is the cause of your problems or not based on what you posted.

3.  Have you Binged "exchange 2013 ecp 404&

below is the link for the ECP 404 error fix 

http://support.microsoft.com/kb/2778897

Did you end up having to format your server?  I am also getting this error:

Error:
The type initializer for 'Microsoft.Exchange.Configuration.Tasks.ThrottlingModule`1' threw an exception.

unfortunately yes

exchange 2013 is very touchy

I am glad I found this thread. I installed Exchange 2013 on an existing server but in an organization that has no MS Exchange so this was the first and only server. The installation worked as in it completed without any errors but then when I tried to run the Exchange Administrative Module I got numerous errors, including 404, 403 and a complaint that some module was compiled with a newer .Net than I was running. I have .Net 4.5.1 installed. So at this point I decided to uninstall and start over. Well, uninstall wouldn't work because there were existing mailboxes which it told me I could enumerate and disable or delete with Get-Mailbox. Get-Mailbox failed with "no such cmdlet" so then someone suggested I used ADSIEdt to remove Exchange from AD, which I did. Eventually I got to the point where the installation would run again, and then I got the problem that is the subject of this thread.

So now, thanks to this thread, my way forward is clear - I shall return MS Exchange on the grounds that MS admits it doesn't work and that it's all my fault it doesn't work. I am sure my customer will be very disappointed, especially since I had been telling them what an excellent job Exchange does at meeting their requirements for Public Folders etc. The notion that I have to do a clean re-install of the OS after reformatting a production server is absurd. I'd like to thank Ed Crowley for displaying superb arrogance while totally failing to help David Sheetz. If that is how an MCP is treated I can see there is no chance at all for me to get this working.

contrary to what Ed says you can fix this, it is way harder than it should be and I have NEVER had this many issues on a  fresh build! 

things to note on Exchange 2013

1. IPv6 MUST work and also DNS set manually, verify port 25 is open on your firewalls!

2. even if services are running make sure there are no errors in the application event log and check that all services on the Exchange server are set to ACTIVE. to find out type the below command in exchange management shell

Get-ServerComponentState Identity servername

3. The group "everyone" did not have the right "Access this computer from the network". This could be seen by an audit failure in the security log stating that the user "<mailbox server name>" did not have the required login type (login type 3).

Adding everyone to the "Access this computer from the network" right solved the issue. 

To enable "Access this computer from the network" :

• Run "gpedit.msc"
• Navigate through Computer Configuration > Windows Settings > Security Settings > Local Policies > User Rights Assignment
• Double click on "Access this computer from the network", and ensure "Everyone" is added.

4. verify all connectors are setup correctly

Also I found an error in the event log Event ID: 1009 once I fixed that emails started to fly!

To resolve the issue, use one of the following methods.

Method 1

1. Create a new Active Directory group that is named ContentSubmitters, and then grant Admistrators and NetworkService full access to the group. This is a dummy group and should be used as a placeholder only. You might want to add a description so that the group is not removed.
2. Force or wait for Active Directory replication.
3. Restart the following services:
   • Microsoft Exchange Search
4. Microsoft Exchange Search Host Controller

Method 2

You can also resolve this problem by removing a configuration entry that refers to the ContentSubmitters group. This entry is present in four files. Each file is calledWcfConfigurator.xml, and you can find each file in the following folder:

Here, %ExchangeInstallPath% is the Exchange installation root path (available in the environment variable of that name), and the placeholder <var style="border:0px;font-family:monospace, monospace;font-size:1em;font-style:inherit;font-weight:inherit;margin:0px;outline:0px;padding:0px;vertical-align:baseline;">NODENAME</var> represents one of the following names. (There is one name for each of the four files that are to be edited.)

Helpful articles

http://blog.dargel.at/2012/11/20/complete-remove-exchange-2013-using-adsiedit/

http://exchangeserverpro.com/exchange-2013-manually-configure-dns-lookups/

True, Ed, but I didn't see one constructive comment. To be honest, you are not alone. It's very seldom that anyone from MS ever plays a positive role in anything. All they ever do is state the bleeding obvious. There are SERIOUS flaws in the way Exchange 2013 installs. Some of us, who don't spend all day every day with Exchange expect that if we follow the install sensibly that it will at least work. But when NOTHING works and it won't even uninstall there is a serious problem. Remember, I hadn't even gotten as far as configuring it. The configuration website just flat out didn't work. If Linux programmers had spent any time at all on trying to produce easier to install software rather than doubling the number of distros every few nanoseconds, MS would be forced to be more responsive. I remember the days when you put in a CD, pressed "Install" and most things just pretty much worked.

Nowhere did I say you cannot

Just want to try to add a full solution to this issue:

"Error: The type initializer for 'Microsoft.Exchange.Configuration.Tasks.ThrottlingModule`1' threw an exception."

Step 1. Open cmd shell and type regedit.exe

Navigate to the following path and create the keys that do not exist. Pay attention to the order that each key is created. Navigate to this area:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v15\

Right Click --> Create new Key

Create the following keys Under v15 key: FIP-FS, Pickup, and Search.  Create this key: SQM under FIP-FS. Create SystemParameters key under Search.

Finally from within powershell, cd to Microsoft Exchange Server 2013 Setup.exe file directory.

Install Exchange roles using powershell command:

Setup.exe /role:ClientAccess,Mailbox /IAcceptExchangeServerLicenseTerms

Hope this helps everyone out.

Draaco Aventura

Chief Solutions Architect/CEO

Certified Ethical Hacker, CHFI, ECSA

www.integrated-cyber-solutions.com

• Proposed as answer by Integrated Cyber Solutions Wednesday, July 23, 2014 9:47 PM

If you don't care about anything in your organization being preserved, you can blow away the entire organization by going into ADSI Edit, selecting the Configuration naming context, and deleting the Microsoft Exchange Server subtree under Services.  For good measure, in ADU&C remove the Microsoft Exchange System Objects and Microsoft Exchange Security Groups OUs and their children too.  Flatten the server, too.  Then you should be able to start fresh with a new organization installation of any version you wish.

I don't know if this is supported or not, but it should wipe things away cleanly enough that a reinstallation shouldn't be bothered with any left

If you don't care about anything in your organization being preserved, you can blow away the entire organization by going into ADSI Edit, selecting the Configuration naming context, and deleting the Microsoft Exchange Server subtree under Services.  For good measure, in ADU&C remove the Microsoft Exchange System Objects and Microsoft Exchange Security Groups OUs and their children too.  Flatten the server, too.  Then you should be able to start fresh with a new organization installation of any version you wish.

I don't know if this is supported or not, but it should wipe things away cleanly enough that a reinstallation shouldn't be bothered with any left

i did a little research that led me to believe that the throttling error was IIS bandwidth management related. I really didnt want to mess with that or a lot of rework. Here is how i got around it:  I rebooted between each step.

demote the DC on the exchange 2013 server (this was the 2nd DC)
uninstall iis
reinstall iis
recheck the exchange prerequisites and reinstall them  
promote DC on the exchange server
reinstall exchange 2013 and be happy.

• Edited by shade.tree Wednesday, September 10, 2014 2:18 AM

Thanks shade.tree!

I can confirm uninstalling IIS with (causes server restart!):

Import-Module ServerManager    
Remove-WindowsFeature Web-Server -restart

And re-running the pre-requisite install command:

Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation

Cleared the error: "Error: The type initializer for 'Microsoft.Exchange.Configuration.Tasks.ThrottlingModule`1' threw an exception." for me.

...who knows how the rest of the install will go...

A: Error: The type initializer for Microsoft.Exchange.Configuration.Tasks.ThrottlingModule`1 threw an exception.

I followed these steps after removing exchange server 2013 using ADSIEdit:

1. First remove [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer]

And then add the following Keys:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v15]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v15\FIP-FS]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v15\FIP-FS\SQM]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v15\Pickup]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v15\Search]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v15\Search\SystemParameters]

2. Step Two is to Uninstall IIS, restart the the exchange server and then re-run the pre-requisite install command in Windows Powershell on the Exchange Server:

"Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation"

I tried these two steps and it cleared the 'throthlingModule' error for me.