The type initializer for 'System.Data.SqlClient.SqlConnection' threw an exception. InnerException: Requested registry access is not allowed.

I have read some of the other posts for people that got this error, but none seem to apply to me.
My program has been working for weeks.  I made some minor changes, and started getting the error (full details below).
I did a TFS "undo pending changes" and still getting the same error, even after logging off.  The one odd thing is that I did change my Windows password this week. The connection string is using a SQL user id and password that has no issues.
I'm an Admin own my own box (running WIn XP SP3).  I even tried "Run as Admin" on Visual Studio.
I'm doing a Debug-Start, running a Console-Test-Program that calls a WCF service, which on local machine is hosted by "ASP.NET Development Server".
We have two other developers, one has the same problem, one does not.  In theory, we have all done "get latest" and are running the same code.
The SQL Connection is related to a trace database; we are using this library http://ukadcdiagnostics.codeplex.com which has worked fine for months.
When I do "Start Run" in Visual Studio, I get this error:
{"The type initializer for 'System.Data.SqlClient.SqlConnection' threw an exception. "}
with InnerException: {"The type initializer for 'System.Data.SqlClient.SqlConnectionFactory' threw an exception."}
and it has InnerException: {"Requested registry access is not allowed. "}
Outmost StackTrace:
   at System.Data.SqlClient.SqlConnection..ctor()
   at System.Data.SqlClient.SqlConnection..ctor(String connectionString)
   at FRB.Diagnostics.Listeners.SqlDataAccessCommand..ctor(String connectionString, String commandText, CommandType commandType)
   at FRB.Diagnostics.Listeners.SqlDataAccessAdapter.CreateCommand()
   at FRB.Diagnostics.Listeners.SqlTraceListener.TraceEventCore(TraceEventCache eventCache, String source, TraceEventType eventType, Int32 id, String message)
   at FRB.Diagnostics.Listeners.CustomTraceListener.FilterTraceEventCore(TraceEventCache eventCache, String source, TraceEventType eventType, Int32 id, String message)
   at FRB.Diagnostics.Listeners.CustomTraceListener.TraceEvent(TraceEventCache eventCache, String source, TraceEventType eventType, Int32 id, String format, Object[] args)
   at System.Diagnostics.TraceSource.TraceEvent(TraceEventType eventType, Int32 id, String format, Object[] args)
   at System.Diagnostics.TraceSource.TraceInformation(String message)
   at FRB.EC.AdminService.AdminService.TestHelloWorldWithTrace(String name)
   at SyncInvokeTestHelloWorldWithTrace(Object , Object[] , Object[] )
   at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)
   at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)
Second Inner StackTrace:
   at System.Data.SqlClient.SqlConnection..cctor()
Third Inner StackTrace:
      at System.Data.SqlClient.SqlConnectionFactory..cctor()
When I do "Run as Admin", I get this error:
{"Could not load file or assembly 'FRB.EFDataAccess, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. Access is denied. "}
Server stack trace:
   at System.ServiceModel.Channels.ServiceChannel.ThrowIfFaultUnderstood(Message reply, MessageFault fault, String action, MessageVersion version, FaultConverter faultConverter)
   at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc)
   at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at FRB.EC.AdminService.ConsoleTester.svcRef.IAdminService.GetDispositionStatusTypeList()
   at FRB.EC.AdminService.ConsoleTester.svcRef.AdminServiceClient.GetDispositionStatusTypeList() in C:\SourceEagleConnect\EagleConnect\Dev\WCFServices\FRB.EC.AdminService.ConsoleTester\Service References\svcRef\Reference.cs:line 2459
   at FRB.EC.AdminService.ConsoleTester.ConsoleProgram.GetDispositionStatusTypeList() in C:\SourceEagleConnect\EagleConnect\Dev\WCFServices\FRB.EC.AdminService.ConsoleTester\ConsoleProgram.cs:line 565
   at FRB.EC.AdminService.ConsoleTester.ConsoleProgram.ExecuteNewRelease103QueryMethods() in C:\SourceEagleConnect\EagleConnect\Dev\WCFServices\FRB.EC.AdminService.ConsoleTester\ConsoleProgram.cs:line 189
   at FRB.EC.AdminService.ConsoleTester.ConsoleProgram.Main(String[] args) in C:\SourceEagleConnect\EagleConnect\Dev\WCFServices\FRB.EC.AdminService.ConsoleTester\ConsoleProgram.cs:line 76
   at System.AppDomain._nExecuteAssembly(RuntimeAssembly assembly, String[] args)
   at System.AppDomain.ExecuteAssembly(String assemblyFile, Evidence assemblySecurity, String[] args)
   at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly()
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()
I am also posting the web.config/app.config, but I would rather not focus on that since there were absolutely no changes to it between the time it was working and the time it began failing. 
Client app.config
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
  <connectionStrings>
  </connectionStrings>
  <system.serviceModel>
    <behaviors>
      <serviceBehaviors>
        <behavior name="ServiceBehavior">
          <serviceMetadata httpGetEnabled="true"/>
          <serviceDebug includeExceptionDetailInFaults="false"/>
          <serviceAuthorization impersonateCallerForAllOperations="true"/>
        </behavior>
      </serviceBehaviors>
      <endpointBehaviors>
        <behavior name="FRB.AllowImpersonate">
          <clientCredentials>
            <windows allowedImpersonationLevel="Impersonation"/>
          </clientCredentials>
        </behavior>
      </endpointBehaviors>
    </behaviors>
    <bindings>
      <wsHttpBinding>
        <binding name="WSHttpBinding_IAdminService" closeTimeout="00:01:00"
          openTimeout="00:01:00" receiveTimeout="00:10:00" sendTimeout="00:01:00"
          bypassProxyOnLocal="false" transactionFlow="false" hostNameComparisonMode="StrongWildcard"
          maxBufferPoolSize="524288" maxReceivedMessageSize="5565536"
          messageEncoding="Text" textEncoding="utf-8" useDefaultWebProxy="true"
          allowCookies="false">
          <readerQuotas maxDepth="32" maxStringContentLength="8192" maxArrayLength="16384"
            maxBytesPerRead="4096" maxNameTableCharCount="16384" />
          <reliableSession ordered="true" inactivityTimeout="00:10:00"
            enabled="false" />
          <security mode="Message">
            <transport clientCredentialType="Windows" proxyCredentialType="None"
              realm="" />
            <message clientCredentialType="Windows" negotiateServiceCredential="true"
              algorithmSuite="Default" />
          </security>
        </binding>
      </wsHttpBinding>
    </bindings>
        <client>
              <endpoint address="http://localhost:3588/AdminService.svc" binding="wsHttpBinding"
                    bindingConfiguration="WSHttpBinding_IAdminService" contract="svcRef.IAdminService"
                    name="WSHttpBinding_IAdminService">
                    <identity>
                          <dns value="localhost" />
                    </identity>
              </endpoint>
        </client>
    </system.serviceModel>
</configuration>
web.config of WCF service:
  <?xml version="1.0"?>
<configuration>
    <configSections>
    <section name="FRB.Diagnostics" type="FRB.Diagnostics.Configuration.UkadcDiagnosticsSection, FRB.Diagnostics"/>
  </configSections>
    <appSettings>
       <!-- whatever goes here -->
    </appSettings>
    <!-- connection string section -->
  <connectionStrings>
    <add name="log" connectionString="Data Source=myserver;Initial Catalog=ECWCFLOG_SharedDev;User ID=myuser;Password=mypass;MultipleActiveResultSets=True" providerName="System.Data.SqlClient"/>
    <add name="DBConn" connectionString="Data Source=myserver;Initial Catalog=ECData_SharedDev;User ID=myuser;Password=mypass;MultipleActiveResultSets=True" providerName="System.Data.SqlClient"/>
    <add name="EagleConnectEntities" connectionString="metadata=res://*/EagleConnect.csdl|res://*/EagleConnect.ssdl|res://*/EagleConnect.msl;provider=System.Data.SqlClient;provider connection string=&quot;Data Source=myserver;Initial
Catalog=ECData_SharedDev;User ID=myuser;Password=mypass;MultipleActiveResultSets=True&quot;" providerName="System.Data.EntityClient"/>
  </connectionStrings>
    <!-- FRB.Diagnostics logging section -->
    <FRB.Diagnostics>
        <sqlTraceListeners>
            <sqlTraceListener name="sqlTraceListenerSettings"
                        connectionStringName="log"
                        commandText="INSERT INTO LogStore VALUES(@Source, @ActivityId, @ProcessId, @ThreadId, @EventType, @Message, @Timestamp)"
                        commandType="Text">
                <parameters>
                    <parameter name="@Source" propertyToken="{Source}"/>
                    <parameter name="@ActivityId" propertyToken="{ActivityId}"/>
                    <parameter name="@ProcessId" propertyToken="{ProcessId}"/>
                    <parameter name="@ThreadId" propertyToken="{ThreadId}"/>
                    <parameter name="@EventType" propertyToken="{EventType}" callToString="true"/>
                    <parameter name="@Message" propertyToken="{Message}"/>
                    <parameter name="@Timestamp" propertyToken="{DateTime}"/>
          <!-- <parameter name="@UserId" propertyToken="{WindowsIdentity}"/> -->
        </parameters>
            </sqlTraceListener>
        </sqlTraceListeners>
        <smtpTraceListeners>
            <smtpTraceListener name="smtpTraceListenerSettings"
                         host="vssmtp"
                         port="25"
                         from="[email protected]"
                         to="[email protected]"
                         subject="AdminService Logging Event: {EventType}, {MachineName}"
                         body="{Message}&#xA;=======&#xA;Process={ProcessId},&#xA;Thread={ThreadId},&#xA;ActivityId={ActivityId}"/>
        </smtpTraceListeners>
    </FRB.Diagnostics>
    <!-- System.Diagnostics logging section -->
    <system.diagnostics>
        <sources>
            <source name="FRB.EC.AdminService" switchValue="All">
                <listeners>
                    <clear/>
                    <add name="ods"/>
                    <add name="smtp"/>
                    <add name="sql"/>
                </listeners>
            </source>
            <source name="System.ServiceModel" switchValue="Off" propagateActivity="true">
                <listeners>
                    <add name="ignored" type="System.Diagnostics.ConsoleTraceListener"/>
                </listeners>
            </source>
        </sources>
        <sharedListeners>
            <!-- OutputDebugStringTraceListener -->
            <add name="ods"
           type="FRB.Diagnostics.Listeners.OutputDebugStringTraceListener, FRB.Diagnostics"
           initializeData="{ActivityId}|{EventType}: {Message} - {DateTime}, Process={ProcessId}, Thread={ThreadId}"/>
            <!-- SqlTraceListener -->
            <add name="sql"
           type="FRB.Diagnostics.Listeners.SqlTraceListener, FRB.Diagnostics"
           initializeData="sqlTraceListenerSettings"
           traceOutputOptions="Timestamp"/>
            <!-- SmtpTraceListener -->
            <add name="smtp"
           type="FRB.Diagnostics.Listeners.SmtpTraceListener, FRB.Diagnostics"
           initializeData="smtpTraceListenerSettings">
                   <filter type="System.Diagnostics.EventTypeFilter"
                   initializeData="Error"/>
            </add>
        </sharedListeners>
        <trace autoflush="true"/>
    </system.diagnostics>
    <system.web>
    <compilation debug="true" targetFramework="4.0">
    </compilation>
        <roleManager enabled="true" defaultProvider="AspNetWindowsTokenRoleProvider"/>
    </system.web>
    <system.serviceModel>
        <services>
            <service name="FRB.EC.AdminService.AdminService"
               behaviorConfiguration="FRB.EC.AdminService.AdminServiceBehavior">
                <!-- Service Endpoints -->
                <endpoint address="" binding="wsHttpBinding"
                  bindingConfiguration="wsHttpEndpointBinding"
                  contract="FRB.EC.AdminService.IAdminService">
                    <!--
              Upon deployment, the following identity element should be removed or replaced to reflect the
              identity under which the deployed service runs. 
              If removed, WCF will infer an appropriate identity automatically.
          -->
                    <identity>
                        <dns value="localhost"/>
                    </identity>
                </endpoint>
                <endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange"/>
            </service>
        </services>
        <bindings>
            <wsHttpBinding>
                <binding name="wsHttpEndpointBinding"
                 maxBufferPoolSize="2147483647"
                 maxReceivedMessageSize="500000000">
                    <readerQuotas maxDepth="2147483647"
                        maxStringContentLength="2147483647"
                        maxArrayLength="2147483647"
                        maxBytesPerRead="2147483647"
                        maxNameTableCharCount="2147483647"/>
                    <security>
                        <message clientCredentialType="Windows"/>
                    </security>
                </binding>
            </wsHttpBinding>
        </bindings>
        <behaviors>
            <serviceBehaviors>
                <behavior name="FRB.EC.AdminService.AdminServiceBehavior">
                    <!-- To avoid disclosing metadata information, set the value below to false and
               remove the metadata endpoint above before deployment -->
                    <serviceMetadata httpGetEnabled="true"/>
                    <!-- To receive exception details in faults for debugging purposes, set the value below to true. 
               Set to false before deployment to avoid disclosing exception information -->
                    <serviceDebug includeExceptionDetailInFaults="true"/>
                    <serviceCredentials>
                    </serviceCredentials>
                    <!--<serviceAuthorization principalPermissionMode="UseAspNetRoles"
                roleProviderName="AspNetWindowsTokenRoleProvider"/>-->
                    <serviceAuthorization principalPermissionMode="UseWindowsGroups"
                                impersonateCallerForAllOperations="true"/>
                </behavior>
                <behavior name="FRB.EC.AdminService.IAdminServiceTransportBehavior">
                    <!-- To avoid disclosing metadata information, set the value below to false and
               remove the metadata endpoint above before deployment -->
                    <serviceMetadata httpGetEnabled="true"/>
                    <!-- To receive exception details in faults for debugging purposes, set the value below to true. 
               Set to false before deployment to avoid disclosing exception information -->
                    <serviceDebug includeExceptionDetailInFaults="false"/>
                    <serviceCredentials>
                        <clientCertificate>
                            <authentication certificateValidationMode="PeerTrust"/>
                            <!--<authentication certificateValidationMode="Custom" customCertificateValidatorType="DataFactionServices.FRBX509CertificateValidator"/>-->
                        </clientCertificate>
                        <serviceCertificate findValue="WCfServer"
                                storeLocation="LocalMachine"
                                storeName="My" x509FindType="FindBySubjectName"/>
                    </serviceCredentials>
                </behavior>
            </serviceBehaviors>
        </behaviors>
        <serviceHostingEnvironment multipleSiteBindingsEnabled="true"/>
    </system.serviceModel>
    <system.webServer>
        <modules runAllManagedModulesForAllRequests="true"/>
    </system.webServer>
</configuration>
Thanks for any help.
Neal

I think I found it... this is sure a strange error for what is really happening.
Apparently it had happened to me before, and fortuantely, I actually added the following comment:
            // Above is related to the WCFLOG SQL Diagnostics Trace 
            // If you get error here an inner exception "requested registry access is not allowed"
            // inside exception "type initializer for System.Data.SqlClient.SqlConnection"
            // then make sure you have impersonation enabled in your client.
            // See AdminConsole web.config or FRB.EC.AdminService.ConsoleTester.app.config for examples
Now I think I will do a try catch and spit out the same text.
Still testing to assure that this really was the issue.
      <endpointBehaviors>
        <behavior name="FRB.AllowImpersonate ">
          <clientCredentials>
            <windows allowedImpersonationLevel="Impersonation"/>
          </clientCredentials>
        </behavior>
      </endpointBehaviors>
The line below in BOLD below is what somehow seemed to disappear from my app.config - probably due to a TFS human error - still checking that also:
        <client>
              <endpoint address="http://localhost:4998/AdminService.svc"
                              behaviorConfiguration="FRB.AllowImpersonate"
                              binding="wsHttpBinding"
                              bindingConfiguration="WSHttpBinding_IAdminService"
                             contract="svcRef.IAdminService"
                        name="WSHttpBinding_IAdminService">
                    <identity>
                          <dns value="localhost" />
                    </identity>
              </endpoint>
        </client>
Here's how I "idiot-proofed" this error for now, to give an error that actually at least points to a solution:
        public SqlDataAccessCommand(string connectionString, string commandText, CommandType commandType)
            try
                _connection = new SqlConnection(connectionString);
                // Above is related to the WCFLOG SQL Diagnostics Trace  
                // If you get error here an inner exception "requested registry access is not allowed"
                // inside exception "type initializer for System.Data.SqlClient.SqlConnection"
                // then make sure you have impersonation enabled in your client.
                // See AdminConsole web.config or FRB.EC.AdminService.ConsoleTester.app.config for examples
            catch (Exception ex)
                if (ex.ToString().Contains("The type initializer for"))
                throw new System.ApplicationException(@"
                Your client app <endpoint> must be cofigured have a
              'behaviorConfiguration' attribute like this:
                behaviorConfiguration='FRB.AllowImpersonate'
               that points back to a behavior that has this syntax:         
          <behavior name='FRB.AllowImpersonate'>
             <clientCredentials>
                 <windows allowedImpersonationLevel='Impersonation'/>
             </clientCredentials>
          </behavior>
          ", ex);
               else
                    throw ex;
            _command = _connection.CreateCommand();
            _command.CommandText = commandText;
            _command.CommandType = commandType;
            // TODO _command.CommandTimeout = ;
Neal

Similar Messages

  • SSRS Database Configuration Manager Error - Could not connect to server: The type initializer for 'System.Data.SqlClient.SqlConnection' threw an exception

    I'm Getting the "Could not connect to server: The type initializer for 'System.Data.SqlClient.SqlConnection' threw an exception" Error on an existing Instance of SSRS that had been working previously (lots of installs/patches since).
    Any time I try to hit the "Test Connection" button on existing connections or create new ones from the SSRS Config Mgr., it throws that error.
    I know the SQL Server connectivity works (I have SSMS installed on there and can cut and paste server Login to connect). The problem is I can't really get any more details on the error...Event Viewer isn't logging anything, I have upped the trace level
    to 4 in the reportingservicesservice.config file, I have even watched it with procmon and nothing obvious pops up.
    Let me know if anyone else has been down this path and what they have tried.

    Hi BillOlive,
    Based on my research, the issue may be related to user access permission. You can refer to the following method to troubleshooting the issue:
    Open C:\Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG folder | right click on the machine.config file | Properties | Security | make sure your domain account has FULL CONTROL permission on this file.
    If above steps still do not work, please backup your machine.config file to somewhere else and replace with the attached one from my Windows Server 2008 environment.
    Alternatively, app.config file also may cause the same issue. There is a similar issue, you can refer to it.
    http://stackoverflow.com/questions/6922879/exception-type-initializer-for-system-data-sqlclient-sqlconnection
    Hope this helps.
    Regards,
    Alisa Tang
    If you have any feedback on our support, please click
    here.
    Alisa Tang
    TechNet Community Support

  • Exchange 2013 CU3 Fails "The type initializer for 'Microsoft.Exchange.Flighting.RotationHash' threw an exception."

    I can't get Exchange 2013 to install in our Server 2008 R2 infrastructure. Setup fails with the following error when preparing AD. This is running on Server 2008 R2 SP1 VM's.
    Welcome to Microsoft Exchange Server 2013 Cumulative Update 3 Unattended Setup
    Copying Files...
    File copy complete. Setup will now collect additional information needed for installation.
    Performing Microsoft Exchange Server Prerequisite Check
        Prerequisite Analysis                                                                            
    COMPLETED
     Task module "CmdletHealthCountersModule.Task_IterateCompleted" fails with exception "The type initializer for 'Microsof
    t.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be aff
    ected.
     Task module "CmdletIterationEventModule.LogCmdletIterationEvent" fails with exception "The type initializer for 'Micros
    oft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be a
    ffected.
     Task module "CmdletHealthCountersModule.Task_Release" fails with exception "The type initializer for 'Microsoft.Exchang
    e.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be affected.
    Configuring Microsoft Exchange Server
        Organization Preparation                                                                         
    FAILED
         The following error was generated when "$error.Clear();
            install-DefaultAcceptedDomain -Name $RoleFullyQualifiedDomainName -DomainName $RoleFullyQualifiedDomainName -Dom
    ainController $RoleDomainController
    " was run: "The type initializer for 'Microsoft.Exchange.Flighting.RotationHash' threw an exception.".
     Task module "CmdletHealthCountersModule.Task_IterateCompleted" fails with exception "The type initializer for 'Microsof
    t.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be aff
    ected.
     Task module "CmdletIterationEventModule.LogCmdletIterationEvent" fails with exception "The type initializer for 'Micros
    oft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be a
    ffected.
     Task module "CmdletHealthCountersModule.Task_Release" fails with exception "The type initializer for 'Microsoft.Exchang
    e.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be affected.
    The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the

    I have set the PowerShell Execution Policy to unrestricted. After running setup /PS I get the following output
    PS C:\Windows\system32> cd c:\temp\ex2013cu3
    PS C:\temp\ex2013cu3> ./setup /ps /iacceptexchangeserverlicenseterms
    Welcome to Microsoft Exchange Server 2013 Cumulative Update 3 Unattended Setup
    Copying Files...
    File copy complete. Setup will now collect additional information needed for installation.
    Performing Microsoft Exchange Server Prerequisite Check
        Prerequisite Analysis                                                                            
    COMPLETED
     Task module "CmdletHealthCountersModule.Task_IterateCompleted" fails with exception "The type initializer for 'Microsof
    t.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be aff
    ected.
     Task module "CmdletIterationEventModule.LogCmdletIterationEvent" fails with exception "The type initializer for 'Micros
    oft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be a
    ffected.
     Task module "CmdletHealthCountersModule.Task_Release" fails with exception "The type initializer for 'Microsoft.Exchang
    e.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be affected.
    Configuring Microsoft Exchange Server
        Extending Active Directory schema                                                                
    COMPLETED
     Task module "CmdletHealthCountersModule.Task_IterateCompleted" fails with exception "The type initializer for 'Microsof
    t.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be aff
    ected.
     Task module "CmdletIterationEventModule.LogCmdletIterationEvent" fails with exception "The type initializer for 'Micros
    oft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be a
    ffected.
     Task module "CmdletHealthCountersModule.Task_Release" fails with exception "The type initializer for 'Microsoft.Exchang
    e.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be affected.
    The Exchange Server setup operation completed successfully.
    PS C:\temp\ex2013cu3>
    The installation was started at 10:13am and hung for sometime at 94% of the prereq stage. Installation finally completed at 10:47am. The errors seem to indicate that setup will continue. However upon running setup /prepareAD the installation hangs for sometime
    at 21% of Organization Preparation before finally failing with the following output....
    PS C:\temp\ex2013cu3> ./setup /prepareAD /iacceptexchangeserverlicenseterms
    Welcome to Microsoft Exchange Server 2013 Cumulative Update 3 Unattended Setup
    Copying Files...
    File copy complete. Setup will now collect additional information needed for installation.
    Performing Microsoft Exchange Server Prerequisite Check
        Prerequisite Analysis                                                                            
    COMPLETED
     Task module "CmdletHealthCountersModule.Task_IterateCompleted" fails with exception "The type initializer for 'Microsof
    t.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be aff
    ected.
     Task module "CmdletIterationEventModule.LogCmdletIterationEvent" fails with exception "The type initializer for 'Micros
    oft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be a
    ffected.
     Task module "CmdletHealthCountersModule.Task_Release" fails with exception "The type initializer for 'Microsoft.Exchang
    e.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be affected.
    Configuring Microsoft Exchange Server
        Organization Preparation                                                                         
    FAILED
         The following error was generated when "$error.Clear();
            install-DefaultAcceptedDomain -Name $RoleFullyQualifiedDomainName -DomainName $RoleFullyQualifiedDomainName -Dom
    ainController $RoleDomainController
    " was run: "The type initializer for 'Microsoft.Exchange.Flighting.RotationHash' threw an exception.".
     Task module "CmdletHealthCountersModule.Task_IterateCompleted" fails with exception "The type initializer for 'Microsof
    t.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be aff
    ected.
     Task module "CmdletIterationEventModule.LogCmdletIterationEvent" fails with exception "The type initializer for 'Micros
    oft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be a
    ffected.
     Task module "CmdletHealthCountersModule.Task_Release" fails with exception "The type initializer for 'Microsoft.Exchang
    e.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be affected.
    The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the
    <SystemDrive>:\ExchangeSetupLogs folder.
    PS C:\temp\ex2013cu3>

  • The type initializer for 'Oracle.DataAccess.Client.OracleConnection' threw

    Hi All,
    I am .Net developer [.Net Fream work 2.0].
    In my new windows [C#] project , I have to use oracle Database [11g] which is intalled in one of the server.
    I have installed [my local mechine] odp.net and Oracle.DataAccess.dll version is 2.111.7.20.
    I added reference the above dll and its working fine in my mechine.
    I have build the applicatrion with release option. then i moved the release folder to QA mechine [because QA team needs to test. when the are testing , they are getting below msg
    "The type initializer for 'Oracle.DataAccess.Client.OracleConnection' threw "
    Please could some one can help,
    whether i have to intall odp.net in QA mechine also ?
    thanks
    Babu                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

    Hi,
    As per my experience, Type initializer exception by ODP coulod also be due to mismatch between ODP.Net and dependant layers, especially with the service layer, which communicates with the OCI.
    So, please do following:
    - As suggested earlier, if not installed and then do install the ODP ship home on the target test machine.
    - If already installed, ensure that versions do match, essentially you cannot pick a different ODP dll and try to make it work with a different version of ship home dlls.
    thanks,
    Mrinal

  • The timer service encountered an exception checking for the upgrade mode registry key. Requested registry access is not allowed.

    Once in a while i get the error
    Event ID 6463
    The timer service encountered an exception checking for the upgrade mode registry key. Requested registry access is not allowed.
    This also happens when i restart the timer service.
    I already cleared the SharePoint cache (xml's) but no success with that.
    Environment is
    SharePoint 2013 SP1 + CU Dec 2014

    This is a brand new SP13 with SP1 installation after binaries installation i also installed Dec 2014 CU and then created the SP farm.
    The Apppool/Timer account is member of WSS_ADMIN_WPG.
    Issue can be reproduced with restarting SharePoint Timer Service.
    Hereby the Process Monitor output. Hence i filtered it on NOT SUCCESS and Path contains the word UPGRADE
    11:37:57,4244851 OWSTIMER.EXE
    6272 RegQueryValue
    HKLM\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\15.0\WSS\UpgradeLogLevelOverride
    NAME NOT FOUND Length: 144
    11:37:57,6632057 OWSTIMER.EXE
    6272 RegOpenKey
    HKLM\SOFTWARE\Microsoft\Fusion\PublisherPolicy\Default\v4.0_policy.15.0.Microsoft.Office.Access.Services.Moss.Upgrade__71e9bce111e9429c
    NAME NOT FOUND Desired Access: Read
    11:37:57,6632889 OWSTIMER.EXE
    6272 RegOpenKey
    HKLM\SOFTWARE\Microsoft\Fusion\PublisherPolicy\Default\policy.15.0.Microsoft.Office.Access.Services.Moss.Upgrade__71e9bce111e9429c
    NAME NOT FOUND Desired Access: Read
    11:37:57,7140763 OWSTIMER.EXE
    6272 RegOpenKey
    HKLM\SOFTWARE\Microsoft\Fusion\PublisherPolicy\Default\v4.0_policy.15.0.Microsoft.PerformancePoint.Scorecards.Upgrade__71e9bce111e9429c
    NAME NOT FOUND Desired Access: Read
    11:37:57,7141089 OWSTIMER.EXE
    6272 RegOpenKey
    HKLM\SOFTWARE\Microsoft\Fusion\PublisherPolicy\Default\policy.15.0.Microsoft.PerformancePoint.Scorecards.Upgrade__71e9bce111e9429c
    NAME NOT FOUND Desired Access: Read
    11:37:57,7313089 OWSTIMER.EXE
    6272 RegOpenKey
    HKLM\SOFTWARE\Microsoft\Fusion\PublisherPolicy\Default\v4.0_policy.15.0.Microsoft.SharePoint.Portal.Upgrade__71e9bce111e9429c
    NAME NOT FOUND Desired Access: Read
    11:37:57,7313403 OWSTIMER.EXE
    6272 RegOpenKey
    HKLM\SOFTWARE\Microsoft\Fusion\PublisherPolicy\Default\policy.15.0.Microsoft.SharePoint.Portal.Upgrade__71e9bce111e9429c
    NAME NOT FOUND Desired Access: Read
    11:37:59,2026527 OWSTIMER.EXE
    6272 RegQueryValue
    HKLM\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\15.0\WSS\MS_InternalUse_Only_UpgradeableVersion
    NAME NOT FOUND Length: 144
    11:37:59,2109400 OWSTIMER.EXE
    6272 RegQueryValue
    HKLM\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\15.0\WSS\MS_InternalUse_Only_UpgradeableVersion
    NAME NOT FOUND Length: 144
    11:38:05,3534303 OWSTIMER.EXE
    6272 RegQueryValue
    HKLM\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\15.0\WSS\MS_InternalUse_Only_UpgradeableVersion
    NAME NOT FOUND Length: 144
    11:38:05,3537846 OWSTIMER.EXE
    6272 RegQueryValue
    HKLM\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\15.0\WSS\MS_InternalUse_Only_UpgradeableVersion
    NAME NOT FOUND Length: 144
    11:38:05,3594290 OWSTIMER.EXE
    6272 RegQueryValue
    HKLM\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\15.0\WSS\MS_InternalUse_Only_UpgradeableVersion
    NAME NOT FOUND Length: 144
    11:38:05,3597316 OWSTIMER.EXE
    6272 RegQueryValue
    HKLM\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\15.0\WSS\MS_InternalUse_Only_UpgradeableVersion
    NAME NOT FOUND Length: 144
    11:38:05,3653094 OWSTIMER.EXE
    6272 RegQueryValue
    HKLM\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\15.0\WSS\MS_InternalUse_Only_UpgradeableVersion
    NAME NOT FOUND Length: 144
    11:38:05,3656118 OWSTIMER.EXE
    6272 RegQueryValue
    HKLM\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\15.0\WSS\MS_InternalUse_Only_UpgradeableVersion
    NAME NOT FOUND Length: 144

  • The type initializer for 'Event.ReportDocument' threw an exception

    I know that I asked this question last week, but I cannot access that account anymore, and this issue that I'm having hasn't been fixed as of yet.
    Situaiton:
    Crystal Reports web app previously built using VS.NET 2003 (.NET 1.1), was upgraded to .NET 2.0 with Visual Studio 2005.  Built, and works perfect on local machine.
    Deployed application to remote Windows 2003 SP1 server, with .NET 2.0 SP1, Crystal Reports for .NET framework 2.0, and Microsoft Visual C++ 2005 Redistributable installed.
    When the application is run, I receive the following error when trying to build my report:
    The type initializer for 'CrystalDecisions.CrystalReports.Engine.ReportDocument' threw an exception.
    I've tried to install a Merge Module package, but each time I do, I get about 19 .dll's that can't/won't register.  Also, these dll's all point to a drive that's different from C:/.
    Seriously confused, and a little agitated.  I've torqued the SysAdmin's as well due to so many restarts on the server.
    Any help would be greatly appreciated.

    The fact that things are not registering is likely the cause of this issue.  They may not be installing for a few reasons.  Not enough permissions and missing dependancies are the main two you want to look at. 
    Try running a utility called [process monitor |http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx] , this will allow you to monitor all registry and file access during the install to see if you are getting an access denied somewher.
    To detect dependancies, try running [Dependency Walker|http://dependencywalker.com/] on the Dlls that are not registering.

  • The type initializer for 'Oracle.DataAccess.Client.OracleClientFactory'

    Hi
    Microsoft Visual Studio 2008
    Version 9.0.21022.8 RTM
    Microsoft .NET Framework
    Version 3.5 SP1
    Oracle Developer Tools for Visual Studio 11.1.0.7.20
    I have DB 11.2.0.1 installed on my machine ( OraDb11g_home1 ) and ODT in another home OraClient11g_home1 on my Windows 7 32-bits
    After installing ODT I tried to create a new DataSource, it succeeded (test connection is succesful) but while saving I get
    "The type initializer for 'Oracle.DataAccess.Client.OracleClientFactory' threw an exception." messagebox.
    In registry I have both keys
    HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\ODP.NET\2.111.7.20
    HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\ODP.NET\2.112.1.0
    of course I can connect to db from both homes.
    I've been searching for simmilar issues but have not found something that would help me solve this one.

    ODP.NET actually consists of several DLLs, some managed, some not. If you are missing one of the DLLs in the chain or it somehow picks up mismatched DLLs from several different versions then you will get this error. So if you hand copied DLL's rather than using an installer, this might be the cause.
    Another typical cause of this error is that you deployed your application to another machine (web server) and did not properly install ODP.NET over there.
    The best solution is to reinstall ODP.NET using the installer on the machine where you will run your application. If you already have ODP.NET there, make sure it is the right version and perform a clean up to make sure old versions are not lying around.

  • Type initializer for 'Oracle.DataAccess.Client.CThreadPool' threw an excep.

    Hi all,
    I have a .NET application which save data in an oracle database (about 2000 database read / write each day).
    Every thing works fine since few years...
    However, yesterday, one of my client got this error :
    System.Runtime.InteropServices.SEHException: External component has thrown an exception.
    at Oracle.DataAccess.Client.CThreadPool..cctor()
    The type initializer for 'Oracle.DataAccess.Client.CThreadPool' threw an exception.
    at Oracle.DataAccess.Client.CThreadPool.SetMaxThreads(UInt32 MaxWorkerThreads, UInt32 MaxIOCompletionThreads)
    at Oracle.DataAccess.Client.OracleCommand.set_CommandTimeout(Int32 value)
    Any ideas ?
    Regards.

    Hi,
    thanks for the answer. Yes the Inner exception returns "The provider is not compatible with the version of Oracle client".
    Could it be the Oracle Client Version? I just noticed that on that machine there is the Oracle Client version 11.1.

  • System.Data.SqlClient.SqlException: Cannot open database "MSCRM_CONFIG" requested by the login. The login failed. Login failed for user 'NT AUTHORITY\SYSTEM

    Dear ALL 
    After successfully shifting the CRM from 2011 to 2013 i found a problem in Reporting section none of the report is working after some finding i conclude that MSCRM_FetchDataSource is not able to connect successfully 
    Through my report manager i tried to test the connection of MSCRM_FetchDataSource but i got the following error 
    System.Data.SqlClient.SqlException: Cannot open database "MSCRM_CONFIG" requested by the login. The login failed. Login failed for
    user 'NT AUTHORITY\SYSTEM'. 
    I already add the NT Authority \ System as a db_owner under my database user of MSCRM_CONFIG
    But still no success any one have any idea why it's happaning 
    Regards 
    RB

    I found a solution I hope my post will help other
    I gave the  db_owner to 'NT AUTHORITY\SYSTEM' and 'NT AUTHORITY\NETWORK' and assigned with both CRM and Config database
    It resolved my issue
    RB

  • Readiness Checks fail with "The type initializer for 'Microsoft.Exchange.Configuration.Tasks.ThrottlingModule`1' threw an exception."

    There's another thread about this issue but the accepted answer actually has nothing at all to do with the original problem/question so that's a bit deceptive.
    Anyway, when trying to install Exchange 2013 SP1 (on 2012 R2 Datacentre) the installation reaches the Configuring Prerequisites part of the Readiness Checks and then fails out with the message:
    The type initializer for 'Microsoft.Exchange.Configuration.Tasks.ThrottlingModule`1' threw an exception.
    I honestly can't find any way around this issue and the only mentions I've seen resulted in people reinstalling Windows which obviously isn't really a resolution to the problem.
    Is there any known fix for this issue?

    Ok well I've managed to get around that now by recreating a few registry keys and documented that here (apparently I'm not allowed to create links so can't put that here).
    I have a new issue now though. It seemed to get almost all the way through the installation process but is now failing due to a "memory" issue although due to the wording I can't tell whether it means RAM or Disk space. Either way, neither should
    apply. The drive has 80GB of space available and the machine has 8GB of RAM (only 2GB in use at the time the installer was ran and the amount didn't drop).
    The exact error is...
    Error:
    The following error was generated when "$error.Clear();
    Write-ExchangeSetupLog -Info "Setting up FIPS configuration based on Exchange Install Path";
    $FipsDataPath = [System.IO.Path]::Combine($RoleInstallPath, "FIP-FS\Data");
    $FipsEnginesPath = [System.IO.Path]::Combine($FipsDataPath, "Engines");
    Write-ExchangeSetupLog -Info "Loading FipFs snapin";
    Add-PsSnapin Microsoft.Forefront.Filtering.Management.PowerShell -ErrorAction SilentlyContinue;
    Set-ConfigurationValue -XPath "/fs-conf:Configuration/fs-sys:Machine/fs-sys:Paths/fs-sys:TraceFile" -Value $FipsDataPath -Confirm:$false
    Set-ConfigurationValue -XPath "/fs-conf:Configuration/fs-sys:Machine/fs-sys:Paths/fs-sys:Engines" -Value $FipsEnginesPath -Confirm:$false
    # Copy Microsoft Engine to Engines folder during the install
    $FipsBinPath = [System.IO.Path]::Combine($RoleInstallPath, "FIP-FS\Bin");
    $MicrosoftEngineSourcePath = [System.IO.Path]::Combine($FipsBinPath, "Engine\Microsoft");
    $MicrosoftEngineDestinationPath = [System.IO.Path]::Combine($FipsEnginesPath, "amd64\Microsoft");
    $MicrosoftEngineExists = Test-Path $MicrosoftEngineDestinationPath
    if(! $MicrosoftEngineExists)
    Robocopy $MicrosoftEngineSourcePath $MicrosoftEngineDestinationPath /S /COPYALL
    " was run: "Creating an instance of the COM component with CLSID {2DC947D7-A2DC-4276-A554-891346CE2032} from the IClassFactory failed due to the following error: 8007000e Not enough storage is available to complete this operation. (Exception from HRESULT: 0x8007000E (E_OUTOFMEMORY)).".
    Error:
    The following error was generated when "$error.Clear();
    Write-ExchangeSetupLog -Info "Setting up FIPS configuration based on Exchange Install Path";
    $FipsDataPath = [System.IO.Path]::Combine($RoleInstallPath, "FIP-FS\Data");
    $FipsEnginesPath = [System.IO.Path]::Combine($FipsDataPath, "Engines");
    Write-ExchangeSetupLog -Info "Loading FipFs snapin";
    Add-PsSnapin Microsoft.Forefront.Filtering.Management.PowerShell -ErrorAction SilentlyContinue;
    Set-ConfigurationValue -XPath "/fs-conf:Configuration/fs-sys:Machine/fs-sys:Paths/fs-sys:TraceFile" -Value $FipsDataPath -Confirm:$false
    Set-ConfigurationValue -XPath "/fs-conf:Configuration/fs-sys:Machine/fs-sys:Paths/fs-sys:Engines" -Value $FipsEnginesPath -Confirm:$false
    # Copy Microsoft Engine to Engines folder during the install
    $FipsBinPath = [System.IO.Path]::Combine($RoleInstallPath, "FIP-FS\Bin");
    $MicrosoftEngineSourcePath = [System.IO.Path]::Combine($FipsBinPath, "Engine\Microsoft");
    $MicrosoftEngineDestinationPath = [System.IO.Path]::Combine($FipsEnginesPath, "amd64\Microsoft");
    $MicrosoftEngineExists = Test-Path $MicrosoftEngineDestinationPath
    if(! $MicrosoftEngineExists)
    Robocopy $MicrosoftEngineSourcePath $MicrosoftEngineDestinationPath /S /COPYALL
    " was run: "Creating an instance of the COM component with CLSID {2DC947D7-A2DC-4276-A554-891346CE2032} from the IClassFactory failed due to the following error: 8007000e Not enough storage is available to complete this operation. (Exception from HRESULT: 0x8007000E (E_OUTOFMEMORY)).".
    So if it's not the drive (there's only one drive in the machine) or RAM then what exactly has it ran out of?

  • Error occurred in deployment step 'Activate Features': The type initializer for ' 'threw an exception

    Hi,
    I have develeoped custom timer job using vs 2010 to deploy in sharepoint server.
    While I right click on solution explorer and click on deploy then system throws an error "Error occurred in deployment step 'Activate Features': The type initializer for 'TestTimerJob.TestTimerJob' threw an exception."
    Please suggest.
    Thanks.
    Knowledge is power.

    Debugger is not firing at all. SO not able t do debugging.
    Knowledge is power.
    Have you tried to set break point on feature activate? If not then set break point on feature activate and try to debug your code line by line.
    See this mSDN article to debug timer job:
    http://msdn.microsoft.com/en-us/library/ff798310.aspx
    http://www.codeproject.com/Articles/70866/Debugging-Custom-SharePoint-Timer-Jobs
    Also make sure that:
    1. Once you deploy the time job, you need to reset the IIS
    2. restart the window timer service from services.msc
    Let us know your result
    Hemendra: "Yesterday is just a memory,Tomorrow we may never see"
    Whenever you see a reply and if you think is helpful, click "Vote As Helpful"! And whenever
    you see a reply being an answer to the question of the thread, click "Mark As Answer

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

    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

    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
    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.
    Force or wait for Active Directory replication.
    Restart the following services:
    Microsoft Exchange Search
    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%\Bin\Search\Ceres\HostController\Data\Nodes\Fsis\<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>\Configuration\Local
    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

  • The Type initializer for 'Microsoft.Exchange.Configuration.Tasks.ThrottlingModule1' threw an exception

    Hello,
    I am getting the error message listed in the topic subject when i try to install the Exchange Server 2013 SP1 Evaluation Mode downloaded from your website. After completing all requirements & pre-requisites, I started the installation with the Mailbox
    & Client Access role selected, when i get to the screen which says "Readiness Check" main page subject, and the progress says Configuring Prerequisites, before any progress in the %, i get the error message:
    The Type initializer for 'Microsoft.Exchange.Configuration.Tasks.ThrottlingModule1' threw an exception
    and it says retry.
    Knowing that the server is a member of a domain.How would i resolve this issue?
    Thanks,
    Elie

    hi Ed,
    i am running Windows Server 2012 R2 Standard Evaluation Edition with Exchange Server 2013 Evaluation, But that error message was resolved by removing and re-installing .NET Framework 3.5. That is fine now.
    But now i am getting another error message When it tries to install the Management Tools.
    (Step 1 of 9: Management Tools)
    Error: The Following error was generated when "$error.Clear();
    Set-LocalPermissions
    "was run: "The process does not possess the 'SeSecurityPrivilege' privilege which is required for this operation"'
    knowing that the server is part of a domain and the domain controller runs Windows Server 2008 R2 Evaluation Edition.
    Any ideas why this error message popups up?
    Regards,

  • Event viewer : The type initializer for 'advancedsetttings' threw an exception

    I am recieving a " The type initializer for 'advancedsetttings' threw an exception" error when i try to view subscriptions in event viewer.  The machine is a windows 2008r2 server.  It was working before but just stoped working. 
    I tried loging in as the local admin account on machine and that did not work.  It also does not work with an account that is a domain admin.  Has anyone else experienced this or know how to fix this issue?

    Hi,
    Based on my research, Event Subscriptions functionality depends on the Windows Remote Management (WinRM) service and the Windows Event Collector (Wecsvc) service, please make sure that
    both of these services are running on computers participating in the forwarding and collecting process.
    More information for you:
    Event Subscriptions
    http://technet.microsoft.com/en-us/library/cc749183.aspx
    Best Regards,
    Amy

  • The type initializer for B1Wizard.Globalsu2019 threw an except

    Hi All
    I had to reinstall my B1DE few days ago for my 2007. And till today it is still having problem . When I open eventlog or Form Generator ...etc I get:
    ERROR: The type initializer for B1Wizard.Globalsu2019 threw an exception.
    I am using Visual Studio 2005 (VB.net)
    Please help me
    Thanks in Advance
    Bo Peng

    Hi Bo Peng     
    Down load the B1DE 2.1 source code , recompile it and create a new installer .
    Also remove the read only property set for the files and folders inside the directory
    C:\Program Files\SAP\SAP Business One Development Environment.
    If it is not solved then reinstall the DI Api
    Hope this will help
    Regards
    Arun

Maybe you are looking for