mirror of
https://github.com/Pro/dkim-exchange.git
synced 2026-04-25 17:05:55 +03:00
[GH-ISSUE #94] Server 2008 R2 + Exchange 2013 CU9 #73
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @pavelkos on GitHub (Aug 3, 2015).
Original GitHub issue: https://github.com/Pro/dkim-exchange/issues/94
Won't install
@Pro commented on GitHub (Aug 3, 2015):
Are you using the beta release 2.1.5 or 2.1.4?
https://github.com/Pro/dkim-exchange/releases
@pavelkos commented on GitHub (Aug 3, 2015):
2.1.5.beta-2
@Pro commented on GitHub (Aug 3, 2015):
I just tested upgrading from version 2.0.0 to 2.1.5.beta-2 on my Windows 2012 R2 Server with Exchange 2013 CU9. It worked flawlessly. This seems to be a problem with Windows 2008.
I have to set up a new VM for testing, may take some time.
@pavelkos commented on GitHub (Aug 3, 2015):
For me 2.1.5 work good on many 2012R2 + Exch 2013 CU9. Problem only with 2008 R2. If you need some files from this install - please feel free ask me about it.
@Pro commented on GitHub (Aug 3, 2015):
It's quite strange that the message box above says Exchange Version
15.0.1104.5which is definitely supported:The check is here:
github.com/Pro/dkim-exchange@a268bf9802/Src/Configuration.DkimSigner/InstallWindow.cs (L165)And the constants are defined here:
https://github.com/Pro/dkim-exchange/blob/master/Src/Configuration.DkimSigner/Constants.cs#L37
So the check at line
github.com/Pro/dkim-exchange@a268bf9802/Src/Configuration.DkimSigner/InstallWindow.cs (L167)should not fail for this entry. Very strange...Needs further debugging.
@gogglespisano commented on GitHub (Aug 3, 2015):
@pavelkos If you open the exchange management (power)shell window, what does this command output?
Get-ExchangeServer | fl AdminDisplayVersion
@gogglespisano commented on GitHub (Aug 3, 2015):
@pavelkos Can you make sure that the Configuration.DkimSigner.exe that's running when you see the install failure message is the latest version, and not an earlier build or previous install? Task Manager can show you where it was loaded from in the Command Line column (you may need to add this column), then check the version and timestamp on the file.
@pavelkos commented on GitHub (Aug 3, 2015):
VERBOSE: Connected to exch2-wbbr2.target.local.
[PS] C:\Windows\system32>Get-ExchangeServer | fl AdminDisplayVersion
AdminDisplayVersion : Version 15.0 (Build 1104.5)
have not any previous versions installed
@gogglespisano commented on GitHub (Aug 3, 2015):
Thanks @pavelkos.
When you click on install and while you have the failed install message showing, could you use Task Manager to get the full command line including parameters for Configuration.DkimSigner.exe while it's running?
@pavelkos commented on GitHub (Aug 3, 2015):
Command line column is empty, no parameters
@gogglespisano commented on GitHub (Aug 3, 2015):
Can you try running Configuration.DkimSigner.exe with only "--install" as the command line parameter. It should open the Install window and you should be able to select the install location. Wait several seconds before selecting the install choice and starting the install. Does this procedure still produce the failure message?
@pavelkos commented on GitHub (Aug 3, 2015):
@gogglespisano commented on GitHub (Aug 3, 2015):
I'm running out of ideas. You shouldn't get that message unless the Configuration.DkimSigner.exe doesn't contain that version in it. Either that or the version number looks the same, but for some reason is actually different in Unicode. You could open the .exe in Notepad and then search for "1 1 0 4". it should appear in a block like "1 5 . 0 . 1 1 0 4 . 5 +E x c h a n g e 2 0 1 3 S P 1 C U 9"
@gogglespisano commented on GitHub (Aug 4, 2015):
FYI, the versions shown that are available to install are downloaded by the app, so an older version of the installer will show even the latest version of the software and the latest revisions, even if it isn't up to date itself with the exchange version check.
Maybe the supported version list should be downloaded with the available versions data.
@Pro commented on GitHub (Aug 4, 2015):
Can you try the .exe from this zip: https://dl.dropboxusercontent.com/u/3233048/Release.zip
Open it with the command line parameter
--debugThis will show an additional
Debug Helpertab.Wait until the main tab has loaded the Exchange version. Then switch to the Debug Tab and press the button. Post the message box output here (Screenshot, or just press Ctrl+C when the message box is open)
@pavelkos commented on GitHub (Aug 4, 2015):
Thank you. I'm try to clean up %temp% (in temp many {guid}.zip file's with dkimsigner inside. now all work fine (2.1.5-beta2)