The type initializer for threw an exception ошибка

Free source code and tutorials for Software developers and Architects.; Updated: 16 Nov 2021

I have a c++/cli project and it’s a windows application. In debug mode we didn’t have any problems but after taking it to release mode this error start up. I searched and found some forum-answers but couldn’t help me solve this problem.
Please help me ….

Error :

An unhandled exception of type ‘System.TypeInitializationException’ occurred in Unknown Module.

Additional information: The type initializer for ‘Module’ threw an exception.

Updated 16-Nov-21 14:06pm

I had the same error and found that the class I was referencing was not the problem, but it had a static variable of another type declared that required another assembly to load. That assembly was built for a target platform of x86 (see Properties—>Build tab) however the main project was compiled for Any CPU. I rebuilt the older assembly for Any CPU… problem solved.

Here are some helpful steps for finding the root cause of this problem…

Click Debug—> Exceptions and check ON all the Thrown checkboxes. This will cause the debugger to stop on all first chance exceptions and will help you find the error under the Type Initializer error that you’re seeing. If it is related to another assembly, as mine was, you can use Microsoft’s Assembly Binding Log Viewer tool to help determine the problem.

Does the machine where the application is running has all the required dlls??

Maybe you are missing some interops in the local directory

I recently had the same problem, and it was because I was using Date.Parse on a missing element in the config file:

Date.Parse(System.Configuration.ConfigurationManager.AppSettings.Get(«frex»))

change your .net framework to lower ;)

In my case (so many different cases where this shows up) I was initializing some static fields in their declaration, like this:

public class MyHelperClass
{
    readonly static SolidColorBrush BlueBrush = new SolidColorBrush(Colors.Blue);
    
    public static void ApplyBrush()
    { 
      
    }
}

When I moved the initialization into a static constructor, the exception was no longer thrown:

public class MyHelperClass
{
  readonly static SolidColorBrush BlueBrush;
  
  static MyHelperClass
  {
    BlueBrush = new SolidColorBrush(Colors.Blue);
  }
}
look the repository container in unity.config
<pre><pre lang="xml">
<unity xmlns="http://schemas.microsoft.com/practices/2010/unity">
  <alias type="App.Core.Interfaces.IRepositoryConfiguration, App.Core" alias="IRepositoryConfiguration" />
  <alias type="App.Repository.Mappings.SqlServer.SqlRepositoryConfigurer, App.Repository.Mappings.SqlServer" alias="SqlRepositoryConfigurer" />

  <container name="RepositoryContainer">
    <register type="IRepositoryConfiguration" mapTo="SqlRepositoryConfigurer" >
      <lifetime type="singleton"/>
    </register>
  </container>
</unity>
</pre></pre>

I was making an assignment in a constructor that didn’t have an error handling. 

fileInfo = My.Computer.FileSystem.GetFileInfo(logDirLoc & logFileName)
writer = fileInfo.AppendText()

When I removed it the issue was solved.

tip: I looked through the error details and saw that a file couldn’t be found. That was it.

I faced the Same error that is «System.TypeInitializationException». This error is raised due to Static constructor .

Actually in my case i am accessing some value from the App.config and assigning that value in a static variable . The error is because of the App.config file . That means the app.config file is not well formed (I just missed some tag on app.config ). After putting the missing tag it works fine.

The type initializer for ‘Module’ threw an exception.
Just Run IISRESET

I had this problem also, but my solution wasn’t any of these. It was because I had an unmanaged class with a virtual function that returned a managed pointer.

class A
{
    virtual ManagedType^ Foo();
};

Apparently the C++/CLI runtime can’t handle this. Removing the virtual fixed the problem (luckily for me the virtual wasn’t needed in my case).

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Источник

Tried using System.Drawing.Common package for my .net core web api project. It runs fine under windows but on ubunto (which is my host server), it throws following errors:
This is the method i used to generate thumbnail:

public static bool CreateThumbnail(int Width, int Height, Stream filePath, string saveFilePath)
        {

            try
            {
                var byteArray = filePath;  
                var streamImg = Image.FromStream(byteArray);

                Bitmap sourceImage = new Bitmap(streamImg);
                using (Bitmap objBitmap = new Bitmap(Width, Height))
                {
                    objBitmap.SetResolution(sourceImage.HorizontalResolution, sourceImage.VerticalResolution);
                    using (Graphics objGraphics = Graphics.FromImage(objBitmap))
                    {
                        // Set the graphic format for better result cropping   
                        objGraphics.SmoothingMode = SmoothingMode.HighQuality;
                        objGraphics.PixelOffsetMode = PixelOffsetMode.HighSpeed;
                        objGraphics.InterpolationMode = InterpolationMode.HighQualityBicubic;
                        objGraphics.CompositingQuality = CompositingQuality.HighQuality;
                        objGraphics.DrawImage(sourceImage, 0, 0, Width, Height);

                        // Save the file path, note we use png format to support png file   
                        objBitmap.Save(saveFilePath);
                    }
                }
            }
            catch (Exception ex)
            {
                LogHelper.Log("Create Thumbnail: ERROR:" + ex.Message + "n" + ex.StackTrace);
                return false;
            }
            return true;
        }

ERROR:The type initializer for 'Gdip' threw an exception.
at System.Drawing.SafeNativeMethods.Gdip.GdipLoadImageFromDelegate_linux(StreamGetHeaderDelegate getHeader, StreamGetBytesDelegate getBytes, StreamPutBytesDelegate putBytes, StreamSeekDelegate doSeek, StreamCloseDelegate close, StreamSizeDelegate size, IntPtr& image)
at System.Drawing.Image.InitFromStream(Stream stream)
at System.Drawing.Image.LoadFromStream(Stream stream, Boolean keepAlive)

Already installed
sudo apt-get install libgdiplus
and did this too:

cd /usr/lib
sudo ln -s libgdiplus.so gdiplus.dll

So Any workaround or thoughts on this?

Источник

  • Question

  • 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.»

    David Sheetz MCP

Answers

    • Marked as answer by
      Sheetzhappens
      Saturday, July 12, 2014 6:48 PM

All replies

  • It is not supported to remove Exchange 2013 using ADSIEdit.  Perhaps that’s why you are having that problem.

    Ed Crowley MVP «There are seldom good technological solutions to behavioral problems.»

  • 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

    David Sheetz MCP

  • 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

    Amy Wang
    TechNet Community Support

  • 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:

    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.

    David Sheetz MCP

  • 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

    Amy Wang
    TechNet Community Support

  • 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?

    [PS] C:Windowssystem32>Get-ADPermission -Identity Sheetzexchsrvr | where {($_.ExtendedRights -like «ms-Exch-EPI-Token-
    Serialization») -and ($_.Deny -like «True»)} | ft -autosize User,ExtendedRights

    User                                  ExtendedRights
    —-                                  —————
    SHEETZHAPPENSDomain Admins           {ms-Exch-EPI-Token-Serialization}
    SHEETZHAPPENSSchema Admins           {ms-Exch-EPI-Token-Serialization}
    SHEETZHAPPENSEnterprise Admins       {ms-Exch-EPI-Token-Serialization}
    SHEETZHAPPENSOrganization Management {ms-Exch-EPI-Token-Serialization}
    SHEETZHAPPENSDomain Admins           {ms-Exch-EPI-Token-Serialization}
    SHEETZHAPPENSSchema Admins           {ms-Exch-EPI-Token-Serialization}
    SHEETZHAPPENSEnterprise Admins       {ms-Exch-EPI-Token-Serialization}
    SHEETZHAPPENSOrganization Management {ms-Exch-EPI-Token-Serialization}
    SHEETZHAPPENSDomain Admins           {ms-Exch-EPI-Token-Serialization}
    SHEETZHAPPENSSchema Admins           {ms-Exch-EPI-Token-Serialization}
    SHEETZHAPPENSEnterprise Admins       {ms-Exch-EPI-Token-Serialization}
    SHEETZHAPPENSOrganization Management {ms-Exch-EPI-Token-Serialization}

    David Sheetz MCP

  • 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.

    The resource cannot be found.

    Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable.  Please review the following URL and make sure that it is
    spelled correctly.

    Requested URL: /ecp/login.aspx

    Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.34009 

    David Sheetz MCP

    • Edited by
      Sheetzhappens
      Wednesday, July 2, 2014 8:38 PM

  • 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 Shen
      Friday, July 4, 2014 5:36 AM
      wrong

  • 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 decision.

    Ed Crowley MVP «There are seldom good technological solutions to behavioral problems.»

  • 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

    David Sheetz MCP

  • Can anyone one tell me how I can do a repair reinstall of  Exchange 2013 or check IIS permissions for OWA and ECP?

    • Edited by
      Sheetzhappens
      Wednesday, July 9, 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 decision.

    Ed Crowley MVP «There are seldom good technological solutions to behavioral problems.»

    actually what is dumb is you gave no suggestions for help, plenty of people recommend using ADSI edit and apparently you are unaware that MS recommends it when an install is corrupted. I have been doing this 20 years and ADSI edit has saved many a failed
    exchange installations so keep your insults and lack of suggestions for someone who cares. I was looking for someone who knows something more and could tell me what to try next not what I had done wrong

    David Sheetz MCP

    David Sheetz MCP

  • 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.

    Ed Crowley MVP «There are seldom good technological solutions to behavioral problems.»

  • 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.

    The resource cannot be found.

    Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable.  Please review the following URL and make sure that it is
    spelled correctly.

    Requested URL: /ecp/login.aspx

    Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.34009 

    David Sheetz MCP

  • 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

    David Sheetz MCP

  • 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.

    Ed Crowley MVP «There are seldom good technological solutions to behavioral problems.»

  • 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.

    Ed Crowley MVP «There are seldom good technological solutions to behavioral problems.»

    1. I apologize if you think I was arrogant but it was your first post that seemed arrogant — it is not supported has been used so many times to me by people who can not handle higher level functions -I have used tons of unsupported fixes over the years without
    issue. On top of that you offered no suggestions like, «since you did that unsupported thing I would do this now….»

    2. I installed exchange and had issues which after much troubleshooting I ran /recoverserver that failed to resolve anything so I tried to uninstall from programs control panel, that failed so I tried to run /mode:uninstall that failed so I did the ADSI
    edit thing and rebuilt my Exchange server from scratch, this seemed to install ok but I now have new issues

    3. after all this now I cant access the ECP and I get this error:

    Server Error in ‘/ecp’ Application.

    The resource cannot be found.

    Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable.  Please review the following URL and make sure that it is
    spelled correctly.

    Requested URL: /ecp/login.aspx

    Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.34009             

    David Sheetz MCP

  • 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»?

    Ed Crowley MVP «There are seldom good technological solutions to behavioral problems.»

  • 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»?

    Ed Crowley MVP «There are seldom good technological solutions to behavioral problems.»

    1. fair enough

    2. yes it may leave links but if you know what you are doing you can find them and delete them also , kind of like how I do with regedit. Search for anything exchange related and delete it in ADSI edit.

    3. I didn’t bing, I Googled :) and I fixed that problem, now I can access the ECP but I am back to the original problem, emails stuck in drafts folder

    David Sheetz MCP

    • Marked as answer by
      Sheetzhappens
      Saturday, July 12, 2014 6:48 PM

  • 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

    David Sheetz MCP

  • 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:

    %ExchangeInstallPath%BinSearchCeresHostControllerDataNodesFsis<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>ConfigurationLocal

    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/

    David Sheetz MCP

  • Nowhere did I say you cannot fix that.

    Ed Crowley MVP «There are seldom good technological solutions to behavioral problems.»

  • 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.

  • And, I have given up on 2013 and am going to try installing 2010. I’ll just keep going back in time till I find one that installs.

  • Nowhere did I say you cannot fix that.

    Ed Crowley MVP «There are seldom good technological solutions to behavioral problems.»

    True Ed but you offered no helpful suggestions saying would I should do next since the supported way of uninstalling it failed

    I don’t mean to disrespect you Ed but I came for help not to be told the obvious. It is ok to state the obvious but then follow up with suggestions. I for one, am here to help people AND to get help. We all have unreasonable bosses and deadlines to deal
    with and MS is totally unresponsive to the problems with Exchange 2013… there are known flaws ( see the issue with needing to create an AD group called «content submitters) and failure to have any dashboards for common things like component state and services
    running

    I can not sell Exchange 2013 to anyone because of the trouble I have had — never had this much trouble and I have supported Exchange Server since version 5.0  so thanks MS!

    David Sheetz MCP

  • 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_MACHINESOFTWAREMicrosoftExchangeServerv15

    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 leftovers.

    Ed Crowley MVP «There are seldom good technological solutions to behavioral problems.»

    • Edited by
      Ed CrowleyMVP
      Thursday, July 24, 2014 4:21 AM

  • 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 leftovers.

    Ed Crowley MVP «There are seldom good technological solutions to behavioral problems.»

    Gee Ed wasnt this the very thing you told me wasnt supported? OMGEEEEE   :)

    In ADSI edit you would also want to remove entries for Home Database for each user you had setup with a mailbox in Exchange 2013 under Default Naming Context >>> your domain name >>>users

    for each user there are attribute entries for HomeMDB and msexch*  delete any entry that points to the old exchange before rebuilding the server 

    CAUTION!!! This only works if you have no other servers and dont care about losing all mailboxes and previous Exchange configuration!

    David Sheetz MCP

    • Edited by
      Sheetzhappens
      Thursday, July 24, 2014 5:16 PM

  • No, this is not removing a server from an existing organization, it’s wiping the entire organization, and only when there are no mailbox users.  You are correct that you’d have to do that if there were mailbox users, but he said that there weren’t
    any.

    Ed Crowley MVP «There are seldom good technological solutions to behavioral problems.»

  • i did a little research that led me to believe that the throttling error was IIS bandwidth management related. I really
    didn’t 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_MACHINESOFTWAREMicrosoftExchangeServer]

    And then add the following Keys:

    [HKEY_LOCAL_MACHINESOFTWAREMicrosoftExchangeServer]
    [HKEY_LOCAL_MACHINESOFTWAREMicrosoftExchangeServerv15]
    [HKEY_LOCAL_MACHINESOFTWAREMicrosoftExchangeServerv15FIP-FS]
    [HKEY_LOCAL_MACHINESOFTWAREMicrosoftExchangeServerv15FIP-FSSQM]
    [HKEY_LOCAL_MACHINESOFTWAREMicrosoftExchangeServerv15Pickup]
    [HKEY_LOCAL_MACHINESOFTWAREMicrosoftExchangeServerv15Search]
    [HKEY_LOCAL_MACHINESOFTWAREMicrosoftExchangeServerv15SearchSystemParameters]

    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.

  • I had the same issue recently. I found nothing on the web to resolve the issue. After few tries, the solution was to remove the IIS from the damaged Exchange server. After reboot reinstalled Exchange and it worked great.

    Essam Nasreldin

Источник

Понравилась статья? Поделить с друзьями:
  • The transaction cannot succeed due to error cannot estimate gas
  • The train arrive at 5 pm где ошибка
  • The toast encountered an error please make sure that the app id is set correctly
  • The timing driven placement phase encountered an error
  • The timeout specified has expired ah01075 error dispatching request to