cancel
Showing results for 
Search instead for 
Did you mean: 

Home page of Discovery Accelerator Web site not found

Dave_Tammi
Level 4
Hi,

I have an Enterprise Vault 8.0 SP2 installation and now I need to install Discovery Accelerator.

The Vault is installed on a two node active/passive MSCS Cluster, We have created a virtual server running Windows Server 2003 standard that I am installing the DA server onto.

On the VM, I installed the Vault 8 API Runtime, .NET 3.5 and the rest of the pre-requisite software.

I am loging into the VM using the same service account that the Vault is running under. This service account is a member of the local administrators group on the VM.

When I install the DA, everything appears to be OK, but I continue to get the Page Not Found error.

I checked all the steps in the trouble shooting guide (page 204), and everything appears to be correct, it just doesn't work.

I am sure it is an issue with the installer (me) doing something obviously stupid, but I am admitting defeat and asking for help.

So, heeeelllppp!

Dave
1 ACCEPTED SOLUTION

Accepted Solutions

Dave_Tammi
Level 4
Hi Guys,

After successfully installing the Discovery accelerator on the offline node in our vault cluster (and not really liking this configuration) I decided to go back to my virtual machine, install Enterprise Vault 8 (not just the API), and then install the accelerator.

Well, the first thing the vault installation did was check for prerequisites and darned if the ASP.Net check failed.

I looked again at the web settings and confirmed that the virtual directory is configured to use ASP.NET 2.0.

What the Discovery Accelerator installer (and I) failed to catch was the ASP.Net 2.0 web service extensions were Prohibited. I changed this to Allowed then restarted the web services and the darned thing started to work as it should have.

I guess the Discovery Accelerator could use a deployment scanner utility too.

View solution in original post

14 REPLIES 14

Not applicable
Are you having runtime error - Server Error in '/EVBADiscovery' Application?

TonySterling
Moderator
Moderator
Partner    VIP    Accredited Certified
So to be clear, these are the steps you followed?

If you receive the message “Page Cannot Be Displayed” when you browse to the
home page of the Accelerator Manager site, Custodian Manager site, or Discovery
Accelerator API site, start IIS Manager and then check the following:
■ The virtual directories have been created.
■ The Web sites are running.
■ The virtual directory is configured to use ASP.NET 2.0 rather than an earlier
version.
If the installation program failed to create the virtual directory as part of the
installation process, you can create it manually.


To create the virtual directory manually
1 Open IIS Manager on the server that is hosting the Web site.
2 Right-click the container for your default Web site and then click New >
Virtual Directory.
3 When the Virtual Directory Creation Wizard appears, click Next.
4 For the virtual directory alias, type one of the following, and then click Next.
EVBAAdmin For the Accelerator ManagerWeb site.
EVBACustodianManager For the Custodian ManagerWeb site.
EVBADiscovery For the Discovery Accelerator APIWeb site.
5 For the Web site home directory, enter the path to the appropriate subfolder
of the Discovery Accelerator program folder (AcceleratorAdminWeb or
CustodianManagerWeb), and then click Next.
6 Whenyou are prompted to set the access permissions for the virtual directory,
click Next without changing the default permissions.
7 Click Finish to close the wizard and create the virtual directory.
To configure the settings for the virtual directory
1 Open IIS Manager on the server that is hosting the Web site.
2 Right-click the EVBAAdmin or EVBACustodianManager virtual directory, and
then click Properties.
3 On the Virtual Directory tab, do the following:
■ Make sure that Read, Log visits, and Index this resource are all checked.
■ Remove the entry in the Application name box.
■ Make sure that the application pool is set to EVAcceleratorAppPool.
4 On the Documents tab, remove all the entries in the Enable default content
page box, and then add Login.aspx.
5 On the Directory Security tab, click Edit under Authentication and access
control.
6 In the Authentication Methods dialog box, uncheck Enableanonymousaccess
and check Integrated Windows authentication. (You can select Basic
authentication, but it is less secure.)
7 Click OK to save the changes you have made to the Authentication Methods
dialog box.
8 Click OK to close the properties dialog box.
9 Check that the Web site is running.

TonySterling
Moderator
Moderator
Partner    VIP    Accredited Certified
Hey Dan,
I think he is installing DA on a virtual server, not the cluster.
"We have created a virtual server running Windows Server 2003 standard that I am installing the DA server onto."

Cheers,

dihrig
Level 4
Partner Accredited

What web page are you trying to access?

dihrig
Level 4
Partner Accredited
Yeah, I got that after reading his post again...thanks.

Dave_Tammi
Level 4
Hi all,

Jhon Apurillo - There are no errors logged in the event logs. Anywhere else I can look?

Tony - You are correct in the steps I performed.

dihrig - The page I am trying to access is http://localhost/evbaadmin/.

Thanks for the quick replies.

Dave

TonySterling
Moderator
Moderator
Partner    VIP    Accredited Certified
Hey Dave,

Have you tried http://serverFQDN/evbaadmin ?

just curious.

Regards,
Tony

Dave_Tammi
Level 4

Tony, no luck.

When I use the server name ("VaultTools") or the FQDN ("VaultTools.domainname.com") I am prompted for my credentials. I enter the same credentials ("domain\username") that I am logged in as and then get the page not found message.

If I don't enter the "evbaadmin", I get the "Under Construction" default page showing me that IIS is running.

Thanks for helping.

Dave

Dave_Tammi
Level 4
Hi again.

I copied the default "iisstart.htm" page to the evbaadmin virtual directory and added it to the document list. When I moved it to the top, this default page loaded. When Login.aspx was on top, Page not found.

This sounds more and more like a config issue, but I'll be darned if I know where to look next.

Dave

TonySterling
Moderator
Moderator
Partner    VIP    Accredited Certified
That should be empty except for the login.aspx

From above:
To configure the settings for the virtual directory
1 Open IIS Manager on the server that is hosting the Web site.
2 Right-click the EVBAAdmin or EVBACustodianManager virtual directory, and
then click Properties.
3 On the Virtual Directory tab, do the following:
■ Make sure that Read, Log visits, and Index this resource are all checked.
■ Remove the entry in the Application name box.
■ Make sure that the application pool is set to EVAcceleratorAppPool.
4 On the Documents tab, remove all the entries in the Enable default content
page box, and then add Login.aspx.

5 On the Directory Security tab, click Edit under Authentication and access
control.
6 In the Authentication Methods dialog box, uncheck Enableanonymousaccess
and check Integrated Windows authentication. (You can select Basic
authentication, but it is less secure.)
7 Click OK to save the changes you have made to the Authentication Methods
dialog box.
8 Click OK to close the properties dialog box.
9 Check that the Web site is running.

you might want to uninstall and re-install.

Regards,
Tony

Dave_Tammi
Level 4
I only added the iisstart.htm page to verify that the virtual directory pointed to the correct location and was working properly.

I did have the Login.aspx entry as the only one in the documents list.

When iisstart.htm was the first entry, the iisdefault page loaded. When the Login.aspx page was the first entry, and after I deleted the iisstart.htm entry, I get page not found.

I installed the Enterprise Vault 8 API runtime, since the Vault runs on a different server. Was this correct or should I have installed Vault?

I also did a remove, reboot, reinstall with no change.

Regards

Dave

TonySterling
Moderator
Moderator
Partner    VIP    Accredited Certified
The runtime should be fine but if you have doubts you can uninstall it and install EV.

Dave_Tammi
Level 4
Right now, for me, the end justifies the means.

I installed the runtime because I thought that is what is required when the Vault is on a different server. From what you are saying, that should be correct.

I have not yet found where the Discovery license information is loaded. Could this be the reason for my "Page Not Found" error running the Login.aspx page? Because this is an aspx page, is there some config file stuff I need to set up?

Dave_Tammi
Level 4
Hi Guys,

After successfully installing the Discovery accelerator on the offline node in our vault cluster (and not really liking this configuration) I decided to go back to my virtual machine, install Enterprise Vault 8 (not just the API), and then install the accelerator.

Well, the first thing the vault installation did was check for prerequisites and darned if the ASP.Net check failed.

I looked again at the web settings and confirmed that the virtual directory is configured to use ASP.NET 2.0.

What the Discovery Accelerator installer (and I) failed to catch was the ASP.Net 2.0 web service extensions were Prohibited. I changed this to Allowed then restarted the web services and the darned thing started to work as it should have.

I guess the Discovery Accelerator could use a deployment scanner utility too.