Internet Explorer cannot display the webpage?

[ajj3085]

HI,

I just upgrade from Fortress 2.0 to version 2.0.1.18729. Everything works fine, EXCEPT when I try to view http://myserver/Fortress, I get this from IE 8:

Internet Explorer cannot display the webpage

What you can try:
Diagnose Connection Problems

More information

This problem can be caused by a variety of issues, including:

•Internet connectivity has been lost.
•The website is temporarily unavailable.
•The Domain Name Server (DNS) is not reachable.
•The Domain Name Server (DNS) does not have a listing for the website's domain.
•There might be a typing error in the address.
•If this is an HTTPS (secure) address, click Tools, click Internet Options, click Advanced, and check to be sure the SSL and TLS protocols are enabled under the security section.

For offline users

You can still view subscribed feeds and some recently viewed webpages.
To view subscribed feeds

1.Click the Favorites Center button , click Feeds, and then click the feed you want to view.

To view recently visited webpages (might not work on all pages)

1.Click Tools , and then click Work Offline.
2.Click the Favorites Center button , click History, and then click the page you want to view.



The only time this seems to be a problem is if you're using IE8 on Vista 64-bit. IE8 on a server 2003 32-bit IE8 setup displays the page, and Firefox on Vista 64-bit displays the page as well.

Andy Ideas?

[lbauer]

Did this work properly in Fortress 2.0?

Are you able to connect to any of the other links, such as http://yourserver/VaultService/VaultWeb/Login.aspx
What about http://yourserver/VaultService

There may be some setting(s) in IE 8 on Vista x64 that are blocking the page. We'll look into this.

[ajj3085]

Very weird, I rebooted the server and now it works.. but I'm not able to login (using any client). I get this message in the server event log:

Event Type: Information
Event Source: ASP.NET 2.0.50727.0
Event Category: Web Event
Event ID: 1315
Date: 8/25/2009
Time: 9:27:54 AM
User: N/A
Computer: server
Description:
Event code: 4005
Event message: Forms authentication failed for the request. Reason: The ticket supplied was invalid.
Event time: 8/25/2009 9:27:54 AM
Event time (UTC): 8/25/2009 1:27:54 PM
Event ID: b01eef6fe503498fad845210e28853f3
Event sequence: 2
Event occurrence: 1
Event detail code: 50201

Application information:
Application domain: /LM/W3SVC/1/Root/Fortress-2-128956804717548678
Trust level: Full
Application Virtual Path: /Fortress
Application Path: C:\Inetpub\wwwroot\Fortress\
Machine name: server

Process information:
Process ID: 3464
Process name: w3wp.exe
Account name: domain\user

Request information:
Request URL: http://server/fortress/default.aspx
Request path: /fortress/default.aspx
User host address: xxx.xxxx.xxx.xx
User:
Is authenticated: False
Authentication Type:
Thread account name: domain\user

Name to authenticate:

[ajj3085]

And yes everything was working fine w/Fortress 2, except some errors which were occuring with CC.Net integration.

[ajj3085]

Ok, I got it all worked out. Rebooting fixed the Cannot display page message, and turning off identity impersonate fixed the issues not being able to login.

I have to do that everytime; when I specify a custom identity to use, it stores the information in the web.config file by setting identity impersonate to true. This isn't needed though, because I set the VaultAppPool in IIS6 to run under this custom identity already, and it removes the need for the information to be in the .config file. Is there still a need to set that information in the web.config file if IIS6 is being used?

[lbauer]

Is there still a need to set that information in the web.config file if IIS6 is being used

We did some testing and didn't encounter any problems when a custom account was configured in the web.config files as well as in the App Pool. Fortress still worked when we removed the custom account from the web.config files but left it in the App Pool. However, you still probably need to choose a custom account when you're installing Fortress, because this ensures that the Fortress installer will create the proper permissions for the custom account to work.