Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Exchange 2013 Toolbox snap fails to start after installing yestarday latest 3.0.1 DKIM-Exchange. #141

Closed
mitacs opened this issue Feb 19, 2016 · 5 comments

Comments

@mitacs
Copy link

mitacs commented Feb 19, 2016

Hello,

Exchange 2013 SP1 on Windows 2012 R2. Before installing DKIM-Exchange 3.0.1 (manual installation) I applied Exchange2013-KB2938053-FixIt using PowerShell; #24. DKIM seems to be working well (other than Windows Event 1057, MSExchange Extensibility - Agent 'Exchange DkimSigner' went async).
However, whenever I attempt to start Exchange Toolbox (mmc or Windows Icon/shortcut), it crashes.
I am 99% percent sure that Exchange Toolbox was working well after I patched and rebooted this server ~week ago, as I was monitoring message queue after the reboot. I cannot restart the server and see whether the problem goes away until next month.

Report - Copy.wer.txt

"MMC has detected an error in a snap-in and will unload it"
FX:{714FA079-DC14-470f-851C-B7EAAA4177C1}
Type is not resolved for member 'Microsoft.Exchange.Configuration.MonadDataProvider.MonadDataAdapterInvocationException,Microsoft.Exchange.Configuration.ObjectModel, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.

Exception type:
System.Runtime.Serialization.SerializationException

Exception stack trace:
at Microsoft.ManagementConsole.Internal.IMessageClient.ProcessRequest(Request request)
at Microsoft.ManagementConsole.Executive.RequestStatus.BeginRequest(IMessageClient messageClient, RequestInfo requestInfo)
at Microsoft.ManagementConsole.Executive.SnapInRequestOperation.ProcessRequest()
at Microsoft.ManagementConsole.Executive.Operation.OnThreadTransfer(SimpleOperationCallback callback)

Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: mmc.exe
Problem Signature 02: 6.3.9600.17415
Problem Signature 03: 54504e26
Problem Signature 04: MMCEx
Problem Signature 05: 6.3.9600.16384
Problem Signature 06: 5215552e
Problem Signature 07: 754
Problem Signature 08: e
Problem Signature 09: VZEVNFUPILSVC31Z3H5GTO45URXFKID3
OS Version: 6.3.9600.2.0.0.272.7
Locale ID: 1033
Additional Information 1: df29
Additional Information 2: df291ca819a7dfd9eb786c70f2f0186f
Additional Information 3: b7fc
Additional Information 4: b7fc5e36af54104f3ef4623847c4e676

Please let me know if you need any additional information.

@Pro
Copy link
Owner

Pro commented Feb 27, 2016

@mitacs any news about this issue?
Please close it if it was resolved and post the solution here. Thanks

@mitacs
Copy link
Author

mitacs commented Feb 29, 2016

Thanks Stefan.

I will reboot Exchange server around mid-March and give you update on this issue.

Regards,

Marek

From: Stefan Profanter [mailto:[email protected]]
Sent: February-27-16 6:25 AM
To: Pro/dkim-exchange
Cc: sysadmin
Subject: Re: [dkim-exchange] Exchange 2013 Toolbox snap fails to start after installing yestarday latest 3.0.1 DKIM-Exchange. (#141)

@mitacs https://github.com/mitacs any news about this issue?
Please close it if it was resolved and post the solution here. Thanks


Reply to this email directly or view it on GitHub #141 (comment) .

@mitacs
Copy link
Author

mitacs commented Mar 11, 2016

We think that we found (by coincidence, troubleshooting Exchange Management Shell issue) the problem, Stefan.

I followed this manual DKIM installation instructions:

  1. Execute the following command to allow execution of local scripts (will be reset at last step): Set-ExecutionPolicy Unrestricted
  2. Cd into the folder where the zip has been extracted.
  3. Execute the install script .\install.ps1
  4. Follow the instructions. For the configuration see next section.
  5. Reset the execution policy: Set-ExecutionPolicy Restricted

Step number 5 most likely broke Exchange Toolbox and created this error when opening Exchange Management Shell for us:

“File C:\Program Files\Microsoft\Exchange Server\V15\bin\RemoteExchange.ps1

cannot be loaded because running scripts is disabled on this system. For more

information, see about_Execution_Policies at

http://go.microsoft.com/fwlink/?LinkID=135170”

The fix is to run “Set-ExecutionPolicy RemoteSigned” so “Get-ExecutionPolicy –List” output looks like this:

                              Scope                         ExecutionPolicy

                              -----                         ---------------

                      MachinePolicy                               Undefined

                         UserPolicy                               Undefined

                            Process                               Undefined

                        CurrentUser                               Undefined

                       LocalMachine                            RemoteSigned

Both Exchange Toolbox and Exchange Management Shell are working now. Please test it yourself and let me know whether the problem was somehow only related to our environment. And if not, please update your installation instructions and close this bug report.

Thanks,

Marek

From: Marek Biela
Sent: February-29-16 2:41 PM
To: 'Pro/dkim-exchange'; Pro/dkim-exchange
Cc: sysadmin
Subject: RE: [dkim-exchange] Exchange 2013 Toolbox snap fails to start after installing yesterday latest 3.0.1 DKIM-Exchange. (#141)

Thanks Stefan.

I will reboot Exchange server around mid-March and give you update on this issue.

Regards,

Marek

From: Stefan Profanter [ mailto:[email protected] mailto:[email protected]]
Sent: February-27-16 6:25 AM
To: Pro/dkim-exchange
Cc: sysadmin
Subject: Re: [dkim-exchange] Exchange 2013 Toolbox snap fails to start after installing yestarday latest 3.0.1 DKIM-Exchange. (#141)

@mitacs https://github.com/mitacs any news about this issue?
Please close it if it was resolved and post the solution here. Thanks


Reply to this email directly or view it on GitHub #141 (comment) .

@Pro
Copy link
Owner

Pro commented Mar 28, 2016

@mitacs thans for your valuable feedback! I updated the install instructions according your suggestions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants