Open naveennathanial opened 4 years ago
DJBenson
commented
4 years ago In terms of the configuration GUI, I think it’s reasonable to assume it will not work on an operating system designed without a GUI. I just copied the executable to a VM I have which has Server Core 2019 and I can replicate the same issue.
Are you also saying that once configured (you can configure the signer manually using the instructions in the Wiki) that you still receive errors?
stryqx
commented
4 years ago Howdy,
Might be worth installing the App Compatibility FOD and see if that works for you. More info here - https://docs.microsoft.com/en-us/windows-server/get-started-19/install-fod-19 If it doesn't work I can confirm that installing dkim-exchange on Server Core 2019 and copying over config + keys to it works, as this is how I migrated my Exchange 2016 setup to Exchange 2019 on Server Core 2019. The pre-Vista Open File Dialog should work on all Core installs. Someone with better coding skills than I could put in Core install detection logic and use this classic interface instead.
-- Regards, Chris Knight
On Wed, Jan 22, 2020, 05:50 naveennathanial notifications@github.com wrote:
Versions
- Windows Server Version: Windows Server 2019 Core Standard - 10.0.17763 Build 17763
- Exchange Version: Exchange Server 2019 Standard Build 15.2.464.5
- Installed DKIM Exchange Version: 3.2.3
Description
Is dkim-exchange expected to work with Exchange 2019 standard on Server Core OS?
On the Domain Settings page when I click "Generate New key or Select key file it errors with "Unhandled exception" ** Exception Text ** System.Runtime.InteropServices.COMException (0x80040111): Creating an instance of the COM component with CLSID {DC1C5A9C-E88A-4DDE-A5A1-60F82A20AEF7} from the IClassFactory failed due to the following error: 80040111 ClassFactory cannot supply requested class (Exception from HRESULT: 0x80040111 (CLASS_E_CLASSNOTAVAILABLE)). at System.Windows.Forms.OpenFileDialog.CreateVistaDialog() at System.Windows.Forms.FileDialog.RunDialogVista(IntPtr hWndOwner) at System.Windows.Forms.CommonDialog.ShowDialog(IWin32Window owner) at Configuration.DkimSigner.MainWindow.btDomainKeySelect_Click(Object sender, EventArgs e) in C:\Users\jonathan.thomson\Documents\GitHub\dkim-exchange\Src\Configuration.DkimSigner\MainWindow.cs:line 971 at System.Windows.Forms.Control.OnClick(EventArgs e) at System.Windows.Forms.Button.OnClick(EventArgs e) at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent) at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ButtonBase.WndProc(Message& m) at System.Windows.Forms.Button.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
I have private key created using openssl and have the file in the folder: C:\Program Files\Exchange DKIM Signer\keys - However event log shows that "it couldn't load private key for the domain. The key file does not exist."
Any help is appreciated.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/Pro/dkim-exchange/issues/291?email_source=notifications&email_token=AEEHYXO4AQYANUPXUQMAAI3Q647WLA5CNFSM4KJYJYH2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IHXB45A, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEEHYXJJSSLYXCRKHAF4P53Q647WLANCNFSM4KJYJYHQ .
vatec
commented
4 years ago I can confirm that App Compatibility FOD does not fix this issue.
However, you can even run the software on any windows machine, create the keys, then copy the config and keys folder across to the Exchange Server if you need it.
naveennathanial
commented
4 years ago Howdy, Might be worth installing the App Compatibility FOD and see if that works for you. More info here - https://docs.microsoft.com/en-us/windows-server/get-started-19/install-fod-19 If it doesn't work I can confirm that installing dkim-exchange on Server Core 2019 and copying over config + keys to it works, as this is how I migrated my Exchange 2016 setup to Exchange 2019 on Server Core 2019. The pre-Vista Open File Dialog should work on all Core installs. Someone with better coding skills than I could put in Core install detection logic and use this classic interface instead. … -- Regards, Chris Knight On Wed, Jan 22, 2020, 05:50 naveennathanial @.*> wrote: Versions - Windows Server Version: Windows Server 2019 Core Standard - 10.0.17763 Build 17763 - Exchange Version: Exchange Server 2019 Standard Build 15.2.464.5 - Installed DKIM Exchange Version: 3.2.3 Description Is dkim-exchange expected to work with Exchange 2019 standard on Server Core OS? On the Domain Settings page when I click "Generate New key or Select key file it errors with "Unhandled exception" **** Exception Text ** System.Runtime.InteropServices.COMException (0x80040111): Creating an instance of the COM component with CLSID {DC1C5A9C-E88A-4DDE-A5A1-60F82A20AEF7} from the IClassFactory failed due to the following error: 80040111 ClassFactory cannot supply requested class (Exception from HRESULT: 0x80040111 (CLASS_E_CLASSNOTAVAILABLE)). at System.Windows.Forms.OpenFileDialog.CreateVistaDialog() at System.Windows.Forms.FileDialog.RunDialogVista(IntPtr hWndOwner) at System.Windows.Forms.CommonDialog.ShowDialog(IWin32Window owner) at Configuration.DkimSigner.MainWindow.btDomainKeySelect_Click(Object sender, EventArgs e) in C:\Users\jonathan.thomson\Documents\GitHub\dkim-exchange\Src\Configuration.DkimSigner\MainWindow.cs:line 971 at System.Windows.Forms.Control.OnClick(EventArgs e) at System.Windows.Forms.Button.OnClick(EventArgs e) at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent) at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ButtonBase.WndProc(Message& m) at System.Windows.Forms.Button.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) I have private key created using openssl and have the file in the folder: C:\Program Files\Exchange DKIM Signer\keys - However event log shows that "it couldn't load private key for the domain. The key file does not exist." Any help is appreciated. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#291?email_source=notifications&email_token=AEEHYXO4AQYANUPXUQMAAI3Q647WLA5CNFSM4KJYJYH2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IHXB45A>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEEHYXJJSSLYXCRKHAF4P53Q647WLANCNFSM4KJYJYHQ .
Installing App Compatibility FOD was all I had to do to fix the unhandled exception it was throwing earlier. DKIM signing works like a charm on my Exchange 2019 running on windows Server 2019 core. Thanks a ton Chris!
GLComputing
commented
4 years ago @naveennathanial - Does the verification work on Core, as well?
naveennathanial
commented
4 years ago Yes it does!
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10
From: Mike Lazarus notifications@github.com Sent: Saturday, February 22, 2020 3:12:56 PM To: Pro/dkim-exchange dkim-exchange@noreply.github.com Cc: naveennathanial naveennathanial@outlook.com; Mention mention@noreply.github.com Subject: Re: [Pro/dkim-exchange] Is dkim-exchange expected to work with Exchange 2019 standard on Server Core OS? (#291)
@naveennathanialhttps://github.com/naveennathanial - Does the verification work on Core, as well?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/Pro/dkim-exchange/issues/291?email_source=notifications&email_token=AOK5XKMYHOM6QYX4DHSJOD3REGINRA5CNFSM4KJYJYH2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMVKVHY#issuecomment-589998751, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AOK5XKIYPOSTCCZCLVROQ3TREGINRANCNFSM4KJYJYHQ.
GLComputing
commented
4 years ago How do I create the config and keys if I only have the one Ex2019 or 2019Core?
I haven't tried the install yet, just want to have an idea of what I need to have ready
Versions
Description
Is dkim-exchange expected to work with Exchange 2019 standard on Server Core OS?
On the Domain Settings page when I click "Generate New key or Select key file it errors with "Unhandled exception" ** Exception Text ** System.Runtime.InteropServices.COMException (0x80040111): Creating an instance of the COM component with CLSID {DC1C5A9C-E88A-4DDE-A5A1-60F82A20AEF7} from the IClassFactory failed due to the following error: 80040111 ClassFactory cannot supply requested class (Exception from HRESULT: 0x80040111 (CLASS_E_CLASSNOTAVAILABLE)). at System.Windows.Forms.OpenFileDialog.CreateVistaDialog() at System.Windows.Forms.FileDialog.RunDialogVista(IntPtr hWndOwner) at System.Windows.Forms.CommonDialog.ShowDialog(IWin32Window owner) at Configuration.DkimSigner.MainWindow.btDomainKeySelect_Click(Object sender, EventArgs e) in C:\Users\jonathan.thomson\Documents\GitHub\dkim-exchange\Src\Configuration.DkimSigner\MainWindow.cs:line 971 at System.Windows.Forms.Control.OnClick(EventArgs e) at System.Windows.Forms.Button.OnClick(EventArgs e) at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent) at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ButtonBase.WndProc(Message& m) at System.Windows.Forms.Button.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
I have private key created using openssl and have the file in the folder: C:\Program Files\Exchange DKIM Signer\keys - However event log shows that "it couldn't load private key for the domain. The key file does not exist."
Any help is appreciated.