Known issues related to new EU Data Center Migration

Fri, 19 Dec 2025 18:22:28 GMT

Known Issues After Migration to the New EU Data Center

SMTP connections to external mail servers

If your application sends email through an external SMTP server (that is, not using localhost) over port 25, you may encounter connection errors after migration.

This occurs because our new data center provider blocks outbound port 25 traffic to help prevent spam abuse.

Resolution:

Update your application to use the SMTP Submission port instead.

Recommended port: 587

MIME type configuration errors

If your application defines MIME types in web.config without first removing existing entries, you may receive configuration errors.

This happens because the new servers may already have the MIME type defined at the system level.

Resolution:

Modify your web.config to remove the MIME type before adding it.

Example:

<remove fileExtension=".woff2" /> 
<mimeMap fileExtension=".woff2" mimeType="font/x-woff" />

MySQL ODBC driver compatibility

If your ASP or ASP.NET application connects to a MySQL database using the MySQL ODBC driver, you may experience errors after migration.

The new servers use the MySQL ODBC 5.3 driver, while the previous servers may have used version 5.1 or 5.2. MySQL ODBC drivers do not support side-by-side installation, which can cause driver mismatch issues.

Resolution:
Update your database connection string to reference one of the following drivers:

{MySQL ODBC 5.3 Unicode Driver}
{MySQL ODBC 5.3 ANSI Driver}

How to force Web Deploy and IIS Manager to use TLS 1.2

Thu, 21 Nov 2019 03:13:43 GMT

The below instructions are gathered from the Microsoft support portal. Please note the following will make edits to your registry on your computer. You are doing the following at your own risk.

In order to force TLS 1.2 within Web Deploy and IIS Manager. The following will need to be done per your operating system version. If you are unsure on how to check what OS you're using. Press and Hold the Windows Key + R (This will open the Run prompt) type in winver and press Enter.

Next, Depending on what OS your computer is running on. You will need to create one of the following .reg file and save it on your computer.

For Windows 2016, Windows 10:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319]
"SchUseStrongCrypto"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319]
"SchUseStrongCrypto"=dword:00000001

Open Notepad on your computer and copy and paste the above text and save it as a .reg file.

Next, Type into your search field next to the Start Windows icon and type in regedit hit enter.

Click on File > Import

Look for the .reg file you created and click on Open.

Restart your computer.

For Windows 2012 R2 / 2012, Windows 8.1 / Windows 8

The installed NetFX version must be 4.5.2 or later, as this is the minimum supported NetFX version for 4.x on this OS platform.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319]
"SchUseStrongCrypto"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319]
"SchUseStrongCrypto"=dword:00000001

Open Notepad on your computer and copy and paste the above text and save it as a .reg file.

Next, Type into your search field next to the Start Windows icon and type in regedit hit enter.

Click on File > Import

Look for the .reg file you created and click on Open.

Restart your computer.

For Windows 2008 R2 / Windows 7 please refer to the Microsoft support page.

Newest KB Articles in DiscountASP/Everleap

Known issues related to new EU Data Center Migration

How to force Web Deploy and IIS Manager to use TLS 1.2