DRM 11.2.14 Issue with ASP Temporary Directory

While performing a new installation of DRM on a Windows 2022 server, I encountered an error while testing the application. The application copied over and ran fine according to the DRM Configuration Console, and the IIS web site and application pools started normally.

When I would try to access the URL for the DRM Web Client, I would get a “500 Error”, with a comment about there being “too many redirects”. This occurred when going to the local host, the local server name, and the OHS server’s port 19000 proxy URL. I eventually found an error in the DRM Windows server Event Viewer “Application” logs indicating it was an ASP issue. I later found the same error, more readable to me, when trying to access the drm-migration-client URL:

Relevant portions of the image are highlighted for readability.

This error is telling us that the web application deployment (in this case, for the migration-client) set the temporary directory for the app to C:\ade\alm-git\AspTempFiles , and could not find that location.

This issue appears to have been present in a previous version:

Unfortunately, we do not learn what the “correct location” is from this document.

This issue could have been caused by an inability to create the C:\ade\alm-git\AspTempFiles directory by the installing user account, or the installation did not attempt to create the location. The resolution was to instead modify the web.config files for both migration-client and web-client to point to a new location for the AspTempFiles, and restart the application server.

Previous:

Now:

Permissions for this new location had to be modified to allow IIS to access that directory in our case. Please check with your IT provider for an appropriate fix for your circumstances.