The greater Charlotte area's DotNetNuke user group's web site.
While working with a Cpanel Website running WordPress, you attempt to upload a file and receive an error:
“The uploaded file exceeds the upload_max_filesize directive in php.ini”
Login to the WHM Administration system. Note that this is usually the HOST provider that has access to this.
Softare >> MultiPHP INI Editor
Then for the Different PHP Version in the Dropdown, selecting for example ea-php55 or ea-php56
Edit the post_max_size to something bigger that the default 8M
Edit the upload_max_filesize to something bigger than the default 2M
Loged in as the Account holder,
Software MultiPHP INI Editor
Select the location that you will apply this modification to. This should be the site or sub domain you are experiencing the problem with. (In our example we have the wordpress.projectcentre.com.au)
This applies to Cpanel April 2018 V68
alphassl the requested property value is empty Exception for HRESULT 0x80094004
When completing an Alphassl certificate install on IIS using the “Complete Certificate Request” you receive the error:
There was an error while performing this operation.Details: The requested property value is empty. (Exception from HRESULT: 0x80094004)
Now this is a Typical Microsoft Error in that it really only has meaning to the person who created the error. For us end users stuck in this weird Microsoft world, the error message is trying to tell us that the Certificate you pointed to for the “Complete Certificate Request function in IIS
is pointing to a .CER file that is not valid as a certificate for import.
So at this point it is time to check what certificate you placed in the .CER file that you are trying to import.
In particular with Alphassl certificates, the process of completing a new certificate request is completed by email. The end of the process involves receiving an email with instructions on how to complete the process of import.
Now if you are anything like me, and you think you know what you are doing having completed this process a few times. You tend to work fast and read instructions later (like an IKEA assembly job). And on several of my certificate install jobs I have made the same error. That being that I read to point 2 above. Click the link which if I read it is obviously to the Root Certificate Install. Then proceed to copy and paste the SHA-256 Certificate into the process and save is as a .cer file, then try to complete the process with that hash.
So basically this is all wrong. The certificate Hash is actually included in the bottom of the email received from Alphassl and that hash from the bottom fo the email is the correct hash to copy and paste to your IIS server and save as a .cer file. It is then this file that you use to complete the process with your IIS “Complete Certificate Request” function. Not the above Root certificate.
In August 2017 Microsoft released another version of Outlook for Office 365 for PC that caused a major problem for people connecting to Exchange 2016 servers. This problems is all to do with the AutoDiscovery setup that Outlook uses. Microsoft appear to have set outlook to use their Office 365 servers as an initial point of setup configuration regardless of how you have configured AutoDiscovery.
The bottom line is that outlook keeps trying to authenticate agains office365 and not your own server. While this is a known issue, as of January 2018 it has not been fixed in the next version of Outlook.
There are two fixes, and either one should work. We suggest Fix 1
First one involves setting a registry entry on the computer experiencing the issue. To fix this issue, create a text file and copy/paste this text below.
Windows Registry Editor Version 5.00
Then save it, and rename it as ExcludeExplicitO365Endpoint.reg and run it (this will import the applicable registry key). ONLY DO THIS if you are using an Exchange On-Premise account, and not a Office365 or hosted exchange account.
The solution I’ve found to work and the only one to stop this annoying popup of “enter your password”, is to downgrade to a lower version of office update.here is a script i wrote, in case you need to push this to several computers.
C:\Progr~1\Common Files\Microsoft Shared\officeClickToRun /update user updatetoversion=16.0.8326.2107 1>officec2rclient.exe
this will take your office 2016 to update 8326.2107 where this issue doesn’t happen.nothing will show up on the screen, but give it about 10 minutes and restart the computer. check the control panel/ add-remove programs and make sure office is on the new (or actually old…) version.
Here is a link to some helpful information in running this update: https://support.microsoft.com/en-us/help/2770432/how-to-revert-to-an-earlier-version-of-office-2013-or-office-2016-clic