topic Re: Vault Basic 2023 Test for System Readiness Failed in Vault Forum

Vault Basic 2023 Test for System Readiness Failed

ryohn — Thu, 22 Dec 2022 20:10:01 GMT

We had an issue with Autodesk Vault failing after an update last night. We went to reinstall the program after removing it and when it runs the Test for System Readiness I am getting a failure that says: Checking ASP Status: ASPX file failed to run at URL http://localhost:80/TestASP/TestASPNet.aspx. When I look at the Tool Log file it tells me that the failure is "Accessing a static file through the HTTP protocol has passed. ASPX file failed to run at URL:http://localhost:80/TestASP/TestASPNet.aspx.The remote server returned an error: (500) Internal Server Error."

I have tried everything I could find online to correct the issue but I can't seem to get past this issue. I did notice that once I close the installer the TestASP disappears from IIS and will reappear once I start the installation again. Not sure if that is normal or not.

Thanks for your assistance.

Rick

Re: Vault Basic 2023 Test for System Readiness Failed

JonathanKruger — Mon, 16 Jan 2023 02:32:12 GMT

I realize that this post may be too late as you have probably found a workaround already.

I assume you have a valid backup that you are going to restore from? I would Remove IIS from windows components and restart the PC, then when you re-start the installation, it will automatically reinstall and configure IIS how it wants it to be and should resolve your issue.

Re: Vault Basic 2023 Test for System Readiness Failed

ryohn — Thu, 23 Feb 2023 15:53:26 GMT

Just getting back to this. The removal and reinstall of IIS didn't help. I ready numerous articles and still not having any luck. Any other suggestions would be appreciated.

Thanks

Rick

Re: Vault Basic 2023 Test for System Readiness Failed

JonathanKruger — Fri, 24 Feb 2023 08:08:33 GMT

Did you remove IIS and reboot and then let the installer put IIS back on? May need to see more steps.

Re: Vault Basic 2023 Test for System Readiness Failed

ryohn — Fri, 24 Feb 2023 13:59:56 GMT

Yes, i did that. But i still get the same message after the reboot and the installer put IIS back on.

Re: Vault Basic 2023 Test for System Readiness Failed

GunnarNilsson — Fri, 24 Feb 2023 15:20:21 GMT

Which OS do you have on your vault server?

Re: Vault Basic 2023 Test for System Readiness Failed

ryohn — Fri, 24 Feb 2023 16:50:13 GMT

Windows 10 Pro 64 bit

Re: Vault Basic 2023 Test for System Readiness Failed

GunnarNilsson — Fri, 24 Feb 2023 17:05:39 GMT

Check that you get IIS start screen when you browse to http://localhost/iisstart.htm.

If not, go into Control Panel/Administrative Tools/IIS Manager and verify that Default web site and all Application Pools are started.

Re: Vault Basic 2023 Test for System Readiness Failed

ryohn — Fri, 24 Feb 2023 17:10:32 GMT

Yes, the IIS Start page loads correctly.
Rick

Re: Vault Basic 2023 Test for System Readiness Failed

GunnarNilsson — Fri, 24 Feb 2023 17:58:33 GMT

Ok. Install "C:\VBS2023_ENU_64bit_dlm\en-us\edmPrechecks\TestASPNet.msi" and see if you can browse to http://localhost/TestASP/TestASPNetStatic.txt, http://localhost/TestASP/TestASPNet.asmx and http://localhost/TestASP/TestASPNet.aspx (just a blank page if ok)

Re: Vault Basic 2023 Test for System Readiness Failed

ryohn — Fri, 24 Feb 2023 18:46:31 GMT

I get an error when trying to run that file.

"there is a problem with this windows installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor."

Re: Vault Basic 2023 Test for System Readiness Failed

GunnarNilsson — Fri, 24 Feb 2023 19:17:26 GMT

Ok, you need to run the installer, choose to run self test to let the installer set up the test files. Then you can try to browse.

Re: Vault Basic 2023 Test for System Readiness Failed

ryohn — Fri, 24 Feb 2023 19:39:18 GMT

Where do I find the self-test? When I run the installer I have the Run Pre-Test option, but that's where I get the original error message. I still get the same error but now I also get a warning that says " Check permissions of the account used by ASP.NET."

Re: Vault Basic 2023 Test for System Readiness Failed

ryohn — Fri, 24 Feb 2023 19:49:15 GMT

I was able to clear the warning but I am back to the ASPX File that failed to run at URL http://localhost:80/TestASP/TestASPNet.aspx

Re: Vault Basic 2023 Test for System Readiness Failed

ryohn — Fri, 24 Feb 2023 19:56:40 GMT

i did test the

http://localhost/TestASP/TestASPNetStatic.txt - Worked "Static File"

http://localhost/TestASP/TestASPNet.asmx - HTTP Error 404.3 - Not Found

http://localhost/TestASP/TestASPNet.aspx - HTTP Error 404.3 - Not Found

Re: Vault Basic 2023 Test for System Readiness Failed

GunnarNilsson — Fri, 24 Feb 2023 20:45:49 GMT

In IIS Manager, Application Pools. have you checked AutodeskTestDMPool that it runs .Net 4 in integrated mode?

Check AutodeskTestDMPool (.NET Framework version and Managed pipeline mode settings).
1. Launch IIS Manager.
2. In the IIS Manager window, expand local computer and select Application Pools.
3. Right click on AutodeskTestDMPool and select Basic Settings.
4. Select .NET Framework v4.0.30319 and Integrated pipeline mode.
5. Click OK.

Re: Vault Basic 2023 Test for System Readiness Failed

ryohn — Fri, 24 Feb 2023 21:20:51 GMT

Those are the settings I have currently on the IIS AutodeskTestDMPool.

Re: Vault Basic 2023 Test for System Readiness Failed

GunnarNilsson — Fri, 24 Feb 2023 21:41:41 GMT

Try this then:

Check that IIS ASP .NET Application Development feature is enabled.
On Windows 8, 8.1, 10, Server 2012, and Server 2012 R2
1. Launch the administrative command prompt.
2. Run command %windir%\system32\DISM.exe /Online /Enable-Feature /FeatureName:IIS-ASPNET45 /All /quiet /NoRestart

About the error message, is HTTP Error 404.3 - Not Found all you get?

Re: Vault Basic 2023 Test for System Readiness Failed

ryohn — Fri, 24 Feb 2023 21:46:16 GMT

Ran the command and still same issue.

Here is the 403 error i get:

Server Error in '/' Application.
Could not load file or assembly 'Microsoft.Build.Utilities.v4.0, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.Build.Utilities.v4.0, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Assembly Load Trace: The following information can be helpful to determine why the assembly 'Microsoft.Build.Utilities.v4.0, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' could not be loaded.

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

Stack Trace:

[FileNotFoundException: Could not load file or assembly 'Microsoft.Build.Utilities.v4.0, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.]
System.Web.Compilation.MultiTargetingUtil.InitializeKnownAndLatestFrameworkNames() +0
System.Web.Compilation.MultiTargetingUtil.EnsureFrameworkNamesInitialized() +161
System.Web.Compilation.BuildManager.Initialize() +364
System.Web.Compilation.BuildManager.InitializeBuildManager() +392
System.Web.HttpRuntime.HostingInit(HostingEnvironmentFlags hostingFlags, PolicyLevel policyLevel, Exception appDomainCreationException) +504

[HttpException (0x80004005): Could not load file or assembly 'Microsoft.Build.Utilities.v4.0, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.]
System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +552
System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +122
System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context) +737

Re: Vault Basic 2023 Test for System Readiness Failed

GunnarNilsson — Sat, 25 Feb 2023 08:42:09 GMT

You can try this to see what file or assembly it's looking for:

To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].