Server Application Unavailable

[baclay]

Went on vacation and came back, now cannot access toe Valult Professional - Repository. I am assuming my computer must have downloaded a Microsoft "bug" emm I mean patch. The Event log reports the following error message:

Event Type: Error
Event Source: ASP.NET 2.0.50727.0
Event Category: None
Event ID: 1084
Date: 10/19/2012
Time: 2:48:26 PM
User: N/A
Computer: INKWORKS2
Description:
aspnet_wp.exe could not be started. The error code for the failure is 80004005.
This error can be caused when the worker process account has insufficient rights to
read the .NET Framework files. Please ensure that the .NET Framework is correctly
installed and that the ACLs on the installation directory allow access to the
configured account.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

[Beth]

Look at your VaultAppPool in the IIS Manager to see the account Vault is running under. Then give that account access to the 2.0 .NET framework in C:\Windows\Microsoft.net\v2.0.50727.

If your server is a Windows 2003 server, then also check in your IIS Manager under Web service extensions that the 2.0 .Net framework is still set to allowed.

[baclay]

It is running under INKWORKS2 (local computer) and it already can access the .net 2.0 framework.
BTW, this is a Windows XP SP3 system.

[lbauer]

We could try tweaking permissions, but there are quite a number of accounts/directories that Vault must configure for proper access. It's hard to know what the Microsoft Update changed.

I would recommend uninstalling Vault, keeping the databases, then re-installing. The Vault installer will take care of setting all the proper rights for the accounts and directories and creating the proper database account/permissions.

Back up your databases (sgvault, sgmaster, sgdragnet) first, just in case.

[baclay]

Ok, we are getting somewhere here. I uninstalled and the nreinstalled the Vault Professional Server and now get this error message:

Server Error in '/VaultService' Application.
--------------------------------------------------------------------------------

Configuration Error
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: Unrecognized attribute 'targetFramework'. Note that attribute names are case-sensitive.

Source Error:


Line 11: debugging ASP .NET files.
Line 12: -->
Line 13: <compilation defaultLanguage="c#" debug="false" targetFramework="4.0">
Line 14: <assemblies>
Line 15: <add assembly="System.Design, Version=4.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>


Source File: C:\inetpub\wwwroot\VaultService\web.config Line: 13


--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:2.0.50727.3634; ASP.NET Version:2.0.50727.3634

[lbauer]

Looks like it's still having a framework error.

What version of Vault are you installing?

[baclay]

Vault Professional - Version 6.0.1 (32 bit)

[lbauer]

Do you have the full .NET Framework 4.0? Make sure you have the full Framework for Server and Development, not just the Client (Desktop) version.

It's possible the .NET Framework is not properly registered.


To fix IIS mappings for ASP.NET, run the Aspnet_regiis.exe utility:

1. Click Start, and then click Run.
2. In the Open text box, type cmd, and then press ENTER.
3. At the command prompt, type the following, and then press ENTER:
"C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe" -i

If you have a 64-bit operating system, then use this command:

"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe" -i

[baclay]

Linda,
Thank you Thank you Thank you. That fixed my problem. I did have to install the new client, but it works now.

I don't have a 64-bit machine , but it looked like the ASP register command was the same for both.

Thanks again!

[lbauer]

Glad that helped!

Looks like I didn't put Framework64 for the second command -- I've updated it. But since you have a 32-bit system, the original command was right for you.