The Enterprise Vault service is not available.

[AyazHoda]

Hi

We have currently install EV 9.0.2 but cannot able to open pages via IIS 7.0

For testing purpose I've created test.asp and browse it via IIS 7.0 it worked but no idea why it is not working with IIS 7

HTTP Error 500.0 -

The page cannot be displayed because an internal server error has occurred.

Module	IsapiModule
Notification	ExecuteRequestHandler
Handler	ASPClassic
Error Code	0x00000000

Requested URL	http://localhost:80/EnterpriseVault/GetArchiveSettings.asp
Physical Path	D:\Program Files (x86)\Enterprise Vault\webapp\GetArchiveSettings.asp
Logon Method	Negotiate
Logon User	TI\EVManager

Error Summary

HTTP Error 404.0 - Not Found

The resource you are looking for has been removed, had its name changed, or is temporarily unavailable.

Detailed Error Information

Module	IIS Web Core
Notification	MapRequestHandler
Handler	ASPClassic
Error Code	0x80070002

Requested URL	http://localhost:80/enterprisevault/search02k.asp
Physical Path	D:\Program Files (x86)\Enterprise Vault\webapp\search02k.asp
Logon Method	Negotiate
Logon User	TI\EVManager

Any suggestion

Thanks

[JesusWept3]

What i would suggest is just delete the /EnterpriseVault/ virtual directory and the EnterpriseVaultAppPool in IIS then open a command prompt and CD to your EV install directory (i.e. C:\Program Files (x86)\Enterprise Vault)

Then run the following "cscript webapp.vbs" and press Enter

Also it may be worth running the deployment scanner to make sure that you have all the correct IIS components installed (i.e ASP, IIS6 compatibility stuff, static pages and what not)

And last but not least, its searcho2k.asp as opposed to search02k.asp

 

[AyazHoda]

Already tried doing that via script and Deployment scanner

Two warning with deployment scanner which I think is not critical to run EV

MSMQ Configuration

Back To Top

	Warning
		Either MSMQ is installed with Active Directory Integration or some storage directories are on a system drive. It is recommended that the MSMQ storage directories are located on a non system drive.   MSMQ is installed without Active Directory integration. The following Storage directory is on a system drive. StoreJournalPath: C:\Windows\System32\msmq\storage The following Storage directory is on a system drive. StoreLogPath: C:\Windows\System32\msmq\storage The following Storage directory is on a system drive. StorePersistentPath: C:\Windows\System32\msmq\storage The following Storage directory is on a system drive. StoreReliablePath: C:\Windows\System32\msmq\storage The following Storage directory is on a system drive. StoreXactLogPath: C:\Windows\System32\msmq\storage

Outlook Version

Back To Top

	Warning
		The installed version of Microsoft Outlook ('12.0.6550.5003 SP2') is not supported by Enterprise Vault. For Outlook 2007, Enterprise Vault requires SP2 with hotfix http://support.microsoft.com/kb/2475891. For the latest information on the supported versions of Outlook, see the Enterprise Vault Compatibility Charts at http://entsupport.symantec.com/docs/276547.

[MarkBarefoot]

The Outlook HF IS critical, and for performance the MSMQ info should be implemented.

[JesusWept3]

OK so have you made sure the ISAPI modules aren't disabled?

[AyazHoda]

Not sure!

How to check in IIS 7

[JesusWept3]

OK so go to Start -> Administrative Tools -> Internet Information Services (not 6)
Then under "Start Page" you will have the servername, click this then under "IIS" you will have an option called "ISAPI and CGI Restrictions", double click this and you should see the following

Active Server Pages - Allowd - %windir%\system32\inetsrv\asp.dll
ASP.NET v2.0.50727 - Allowed - %windir%\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll
ASP.NET v2.0.50727 - Allowed - %windir%\Microsoft.NET\Framework64\v2.0.50727\aspnet_isapi.dll

If any of them are set to Deny, then make sure they're allowed

[AyazHoda]

They are all allowed

[JesusWept3]

OK Do the following for me then

1. On the EV Server open up Internet Information Services
2. Expand out "Server Name" -> "Sites" -> "Default Web Site"
3. On the very right hand side under "Manage Web Site" click "Failed Request Tracing"
4. Click "Enable" and give it a decent amount of log files and note where the logs will be written to
5. After pressing OK go to "Default Web Site" -> "EnterpriseVault"
6. Under IIS, double click "Failed Request Tracing Rules"
7. On the very right hand side at the top under "Actions" choose "Add"
8. Under "What would you like to trace" choose "ASP (*.asp)" and press Next
9. Check the "Status Code(s)" and enter "500"
10. Ensure that under providers, everything is checked and set to "Verbose" and then press Finish
11. Go to http://localhost/EnterpriseVault/Search.asp and ensure you get the 500 Internal Error occured etc
12. Go to the FailedReqLogFiles directory you specified from step 4 , see if those log files shed any info

[AyazHoda]

In one of the recent log folder W3SVC1017087010, this is the last information but nothing about EV in all of the log

And in the Failed Request Tracking folder, there's nothing inside that folder, Although I am trying to browser page

#Software: Microsoft Internet Information Services 7.5
#Version: 1.0
#Date: 2011-05-24 15:30:00
#Fields: date time s-ip cs-method cs-uri-stem cs-uri-query s-port cs-username c-ip cs(User-Agent) sc-status sc-substatus sc-win32-status time-taken
2011-05-24 15:30:00 10.0.1.122 GET / - 80 - 10.0.1.122 - 401 2 5 1
2011-05-24 15:30:00 10.0.1.122 GET / - 80 - 10.0.1.122 - 401 1 2148074254 1
2011-05-24 15:30:01 10.0.1.122 GET / - 80 TI\TS5$ 10.0.1.122 - 200 0 0 862
2011-05-24 15:30:01 10.0.1.122 GET /SitePages/Home.aspx - 80 - 10.0.1.122 - 401 2 5 1
2011-05-24 15:30:01 10.0.1.122 GET /SitePages/Home.aspx - 80 - 10.0.1.122 - 401 1 2148074254 3
2011-05-24 15:30:01 10.0.1.122 GET /SitePages/Home.aspx - 80 TI\TS5$ 10.0.1.122 - 200 0 995 741

[JesusWept3 · Accepted solution]

Yup, so i revised the steps for enabling tracing above , you have to set it on the Site level then on the Virtual Directory level and tell it what to trace, try implementing that, you may need to do an IISReset as well, but doubt it