Classic Asp project server migration issues

anand m

3y1.1k.NET

Hello Team,

Currently my Classic asp project getting migrated from legacy Windows 2003 to latest Windows 2016 server.

Need your response on the below challenges :

Classic ASP 32 -bit COM components (.dlls) will be compatible or build on this 64-bit Win 2016 /2022 Latest server .
Seagate Crystal Reports 9 is compatible on this new cloned Win 2016 /2022 Latest server .
Is that IIS 10.0.20348.1 is compatibility for Classic asp project.

IS SQL Server 2016 being feasible for Classic asp project execution.

3 Replies

Know the answer? Post it — somebody with the same question will find it here.

Ali Benchaaban3y ago
Accepted answer
Hello anand,

Before proceeding with the migration there are several important considerations and compatibility issues to address:

- Classic ASP applications should generally work on Windows 2016/2022 Server, but it's essential to thoroughly test your application and potentially make adjustments to ensure it functions correctly on the newer platform.

- Verify the compatibility of SAP Crystal Reports 13.0 with Windows 2022 Azure VM. SAP typically provides compatibility information on their website. Ensure that your specific version is supported.

- Migrating from Windows 2003 Server to Windows 2022 Server is indeed possible, but it's not a straightforward cloning process. You'll need to perform a fresh installation of Windows 2022 Server, set up your environment, and then migrate your Classic ASP project and other components.

- Migrating from SQL Server 2000 to SQL Server 2016/2022 is feasible, but it involves several steps. You may need to upgrade to intermediate versions like SQL Server 2005 or 2008 first. The specifics of the migration depend on your database schema and code. DTS packages will need to be converted to SSIS packages.

- Evaluate the compatibility of your COM DLLs with Windows 2016/2022 Server. Some older COM components may require updates or adjustments to function correctly on the new platform.

- ODBC drivers can generally be installed on Windows 2016/2022 Server. However, make sure you have the latest drivers that are compatible with the newer server version.

- Format files used in SQL Server 2000 may require updates or adjustments for compatibility with SQL Server 2016/2022. Test and, if necessary, recreate these files to ensure they work as expected.

===> to migrate a Classic ASP project from Windows 2003 Server to Windows 2016/2022 Azure or on-premises servers is possible, but it's a complex process. It involves multiple steps, including OS and SQL Server upgrades, compatibility checks, and thorough testing. Plan the migration carefully to minimize disruptions to your application.

I hope this helps with your migration efforts. Feel free to ask if you have more specific questions or need further guidance on any of these points.

Regards,
+1
anand m3y ago
Hello Ali,

Can you please confirm on the inputs also before going to execution this classic asp project on win 2016/2022 server
- Is this Classic asp project works on Windows 2022 Azure VM
- SAP Crystal report 13.0 version is compatible on Win 2022 Azure VM
- Current existing system Windows 2003 server now migrating to Win 2022 server is it possible to clone?
- Current classic asp pointing to SQL 2000 is it possible to migrate to SQL 2016/2022
- In SQL 2000 we are having DTS package is it possible to store same as in SQL 2016/22
- any COM dll's compatability issue concern migrating from Win 2003 to Windows 2016/22
- ODBC drivers 11g installed on windows 2003 , if we migrate to win 2016/22 server any issues or challenges?
- Currently SQL server 2000 having fmt files using parameter format files is this format is compatible on SQL server 2016/22 .
finally conclusion can we migrate this windows 2003 server classic asp project to windows 2016/22 azure or on-prem servers?
+1
Ali Benchaaban3y ago
Hello,

Migrating a Classic ASP project from a legacy Windows 2003 server to a modern Windows 2016/2022 server can present various compatibility challenges. Let's address your concerns step by step:

1. **32-bit COM Components in Classic ASP:**
- When operating in a 64-bit environment like Windows Server 2016/2022, using 32-bit COM components is possible. However, you'll need to adjust your IIS application pool settings to run in 32-bit mode. This can be accomplished by setting the "Enable 32-Bit Applications" option to "True" in the Advanced Settings of your application pool.

2. **Seagate Crystal Reports 9:**
- Crystal Reports 9 is an older version and may have limited compatibility with modern operating systems like Windows Server 2016/2022. You may encounter compatibility issues, and upgrading to a more recent version of Crystal Reports could be necessary for improved compatibility.

3. **IIS 10.0.20348.1:**
- IIS 10 should generally be compatible with Classic ASP projects. However, there might be configuration adjustments needed when transitioning from an older IIS version to IIS 10. It's essential to thoroughly test your Classic ASP application after migration and address any issues that arise.

4. **SQL Server 2016:**
- SQL Server 2016 should work well with a Classic ASP project. Classic ASP is adaptable and can function with various database systems, including SQL Server. Nonetheless, you may need to update your connection strings and database access code if they rely on specific features or syntax that have evolved between older and newer SQL Server versions.

In summary, migrating a Classic ASP project to a Windows Server 2016/2022 environment while using SQL Server 2016 is possible. However, anticipate potential compatibility challenges with older components such as Crystal Reports 9. It's advisable to conduct thorough testing and be prepared to update or replace components that don't seamlessly integrate into the new environment. Additionally, ensure correct IIS configuration to enable your Classic ASP application to run in 32-bit mode if required.
+3