Overview

The customer is experiencing issues while attempting to upgrade from DNN Evoq version 09.01.01 to 09.02.02. The upgrade process is being blocked by errors related to the `installBlocker.lock` file and temporary file errors. Despite several troubleshooting steps, the issue persists.

Solution

To resolve the issue with the upgrade from DNN Evoq version 09.01.01 to 09.02.02, follow these steps:

1. Identify the process locking the `installBlocker.lock` file using tools like Process Explorer. Terminate or suspend the process that is locking the file if it's safe to do so.
2. Ensure the necessary file permissions for the user running the upgrade, particularly if accessing a network share. The user needs both NTFS permissions and share permissions to access this file.
3. Restart IIS and recycle the application pool to release any lingering locks. You can do this by opening Command Prompt or PowerShell with administrative privileges and running `iisreset`. Then, log into DNN as a host user, go to Host Settings, and click Clear Cache under the Performance section. Finally, go to IIS Manager Application Pools, right-click the application pool your DNN site uses, and select Recycle.
4. Ensure that DNN is idle and no other operations are taking place during the upgrade process. You can do this by stopping the application pool in IIS and ensuring that no other sessions are active.
5. Review DNN logs, IIS logs, and Event Viewer for additional errors.
6. If you have any third-party custom modules and skins, ensure all custom modules are compatible with the new DNN version. Before upgrading, try disabling or uninstalling custom modules and skins, then attempt the upgrade again. If the upgrade succeeds without them, this indicates that the custom components are likely causing the issue.
7. If a custom module or skin is causing the issue, you may need to update the code to be compatible with the new DNN version. For modules, check the SQL queries and ensure they match the new schema in DNN Evoq. For skins, ensure that they are using the correct DNN API methods and not directly accessing the database in a way that could conflict with core functionality.
8. If custom modules or skins are using SQL commands to interact with the database (like `UpdatePortalSetting`), make sure those commands are updated to align with any changes in the database schema or stored procedures in the new version of DNN.

Note that issue related to custom modules and skins are outside our scope of support. You will have to reach out to 3rd party vendors to address issues related to these. For in-house custom modules and skins, you will have to address relevant errors from your end.

Summary

By following these steps, you should be able to resolve the issues related to the `installBlocker.lock` file and successfully upgrade from DNN Evoq version 09.01.01 to 09.02.02.

FAQ

1. What is the `installBlocker.lock` file?
   The `installBlocker.lock` file is a lock file that prevents multiple instances of the installer from running at the same time. If this file is locked by another process, it can prevent the upgrade from proceeding.
2. How can I identify the process locking the `installBlocker.lock` file?
   You can use tools like Process Explorer to identify the process that is locking the file. Once identified, you can terminate or suspend the process if it's safe to do so.
3. What should I do if a custom module or skin is causing the issue?
   If a custom module or skin is causing the issue, you may need to update the code to be compatible with the new DNN version. For modules, check the SQL queries and ensure they match the new schema in DNN Evoq. For skins, ensure that they are using the correct DNN API methods and not directly accessing the database in a way that could conflict with core functionality.