2
Installation Fails
Problem reported by PT - 4/6/2020 at 1:15 PM
Resolved
Hi all,
I'm trying to install SmarterMail build 7242 using the .exe setup file and I keep getting an error referring to an invalid digital signature for a cabinet file (Smartermail17_v21.cab). I then tried setup via the available .msi file. It completes successfully yet no config wizard runs and there's no website created. Has anyone experienced this? I'm installing on Server 2016 with the prerequisites installed.

Thanks,
PT

12 Replies

Reply to Thread
0
Matt Petty Replied
Employee Post
When using the MSI you will have to create the website yourself. The MSI is more for setups needing to use msi, if your just updating, and we use them sometimes because they run faster, however it does not perform any IIS configuration. We haven't had any reported issues with the installer. We've had some false positive detections in some AV's for our older builds. Newer builds don't have these false detections. I wonder if maybe an AV removed or prevented that .cab file's execution?

EDIT: To create the website yourself, open IIS Manager.
-Add AppPool called SmarterMail, default options.
-Create site, SmarterMail, Select AppPool, Select the Physical path normally: C:\Program Files (x86)\SmarterTools\SmarterMail\MRS
-You should be able to connect locally from that machine to localhost:80, make sure to open any ports etc.
Matt Petty Software Developer SmarterTools Inc. (877) 357-6278 www.smartertools.com
0
PT Replied
Thanks Matt,
I've added the site, pointing to the MRS directory yet I get "Page can't be displayed". All ports are open. What is the default document? How can I run the configuration wizard?

PT
PT
0
Matt Petty Replied
Employee Post
Is MailService.exe running?
Matt Petty Software Developer SmarterTools Inc. (877) 357-6278 www.smartertools.com
0
PT Replied
Yes, the service is running. I also extracted the files from the .exe, ran the IIS Configuration Wizard, and performed the actions in the KB for installing Manually. Still there's no change.

PT
PT
0
PT Replied
Matt,
the error is due to the fact that the host has no Internet connectivity thereby causing the code signing certificate validity check to fail. Is there a way to install SmarterMail by extracting the cabinet file contents manually? When doing so, I see no obvious setup file to use.
I've tried to modify group policy to bypass cert validity checks but it doesn't appear to have an affect on the blocking.

Thanks,

PT
PT
0
Matt Petty Replied
Employee Post

I've been looking into automated docker builds lately and I was looking at this tool https://lessmsi.activescott.com/ 
I never had a chance to test it yet but it would allow you to get the installer files then you'd...

-Install prerequisites, 
RUN powershell -NoProfile -Command Add-WindowsFeature Web-Net-Ext45,Web-Asp-Net45,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-WebSockets

-Copy MRS folder somewhere on the machine, point IIS smartermail app to it.
-Copy Service folder somewhere on the machine, set up the SM service with this poweshell script.

RUN powershell -NoProfile -Command New-Service -Name "MailService" -BinaryPathName "C:\smartermail-service\MailService.exe"

Doing those 3 steps once you have the installer files will allow you to manually install SmarterMail but this is only something I've done in testing.

------

I have questions about your machine, is it completely airgapped? I've been able to install SM while not having an active internet connection. I may try to setup a test machine to give this scenario a try.
Matt Petty Software Developer SmarterTools Inc. (877) 357-6278 www.smartertools.com
0
PT Replied
Thanks for the reply, Matt,
I was able to successfully run the installer by removing the host from the domain. Yet while the setup completes successfully, IE opens to "The webpage cannot be found" and an HTTP 400 Bad Request message. This is at address http://<hostname>:9998.

I then successfully ran the configuration wizard manually with no change.

One of the KB articles states to go to http://<hostname>:9998/interfaces/setup#. The latter contains only folders, no documents. The former contains 3 documents:
favicon.ico
global.asax
web.config
I'm not too familiar with IIS but none of these qualify as a default document. Is that correct? What is the default document?

Thanks again,
PT
PT
0
PT Replied
Just tried installing v16 after rolling back to a pre-install snapshot. The install went without a hitch except when the browser opens to the site, I still get  "The webpage cannot be found" and an HTTP 400 Bad Request message. I can't be the only one experiencing this. Is the application somehow not compatible with Server 2016?

PT
PT
0
John Bowling Replied
Fails for me.  Did a default installation and cannot get the web page to admin to open...wasted half a day so far
0
Gabriele Maoret - SERSIS Replied
Hi John, if you have a new license you can ask SmarterTools to help you with the installation. It's included in the license price:



Gabriele Maoret - Head of SysAdmins at SERSIS Currently manages 6 SmarterMail installations (1 in the cloud for SERSIS which provides services to a few hundred third-party email domains + 5 on-premise for customers who prefer to have their mail server in-house)
0
Evan Anderson Replied
I'm doing an evaluation of this product for a Customer, and I had the same experience as the earlier posters with the "400 Bad Request" when trying to access the administrative website.

I was installing onto a cleanly-loaded copy of Windows Server 2012 R2 as a Hyper-VM guest, with the IIS pre-requisites installed, .NET Framework 4.7.2, and all current Windows updates installed.

I found that the IIS site created during the installation doesn't have a host header binding for "localhost", though the documentation and the installer attempt to access the site via an http://localhost... URL. 

Adding an "(All Unassigned)" binding for port 9998 on the site created during the installation allowed me to access the administrative website.
0
PT Replied
Marked As Resolution
Thanks everyone,
I found that using the FQDN to specify the servername during the install was causing my issue. I re-installed using only the NetBIOS name and the login page was then accessible.
Go figure!

PT
PT

Reply to Thread