Unable to Login with Web After Fortress 1.1 Upgrade

jfennell · Post by **jfennell** » Thu May 15, 2008 10:28 am

Hello,

I recently upgraded from Fortress 1.0 to Fortress 1.1. During the upgrade, I received the following errors:

Error 1713. SourceGear Fortress Server cannot install one of its required products.
Contact your technical support group.

Following is a copy of the progress log from the installation:

==============

Looking for IIS Version
Upgrading your Fortress configuration.
Requesting the IIS Process User...Connecting to the SQL Server...OK
Verifying the SQL Server requirements...OK
Requesting Fortress Admin user password...OK
Upgrading the existing source control database...
This may take a long time. Do NOT stop this process!
Checking the installed database version...OK
Ensuring that sgvaultuser has access to the database... Grant database access to sgvaultuser...OK
Upgrading SourceGear master database schema...OK
Upgrading SourceGear source control database schema...OK
Upgrading SourceGear work item tracking database schema...OK
Upgrading SourceGear master stored procedures...OK
Upgrading SourceGear source control stored procedures...OK
Upgrading SourceGear work item tracking stored procedures...OK
Database upgrade succeeded!
Checking permissions on local folders...OK
Adding permissions for temporary asp.net files...
Ok
Looking for websites on this machine...
Looking for websites on this machine...
Prepped IIS Path : IIS://LocalHost/W3SVC. Preparing to do directory entry
Directory Entry succeeded : W3SVC
W3SVC child is Info
W3SVC child is Filters
W3SVC child is 1
1Added to _websites
Found website - 'Default Web Site'
Creating the Virtual Directory, VaultService...Already Exists.
Creating the Virtual Directory, VaultShadowFolder...Already Exists.
Creating the Virtual Directory, Fortress...Already Exists.
Updating Shadow Folder Configuration...OK
Updating Configuration...OK
Updating Server Configuration...OK
Looking for saved shadow folder web.config file...OK
Creating the Server Home Page...OK
Your Server configuration has been successfully upgraded.

After pressing [OK] the install will complete and launch a Web browser where you can enter license keys. Please log in with the user name and password that you supplied during this install.
Please press OK to continue installing the Client (if selected).

================================

After the upgrade, I can connect successfully using the Fortress client and the Admin login, but when I enter the same information for the Admin login on the Fortress Web login page, the page simple refreshes instead of displaying an error or logging me in.

Please help,

Beth · Post by **Beth** » Thu May 15, 2008 12:53 pm

Can you check your Fortress log at %windir%\temp\C:\WINDOWS\Temp\SGFortress\fortress.log?

jfennell · Post by **jfennell** » Fri May 16, 2008 1:34 pm

Wow! After doing some more poking around based on the suggestion of checking the log files, I stumbled across the solution to the problem.

I discovered that I was having no problems when logging in from the localhost machine, using the URL http://localhost/fortress, which redirects to http://localhost/VaultService/VaultWeb/ ... fault.aspx to do the login. I also found that logging in directly from http://localhost/VaultService/VaultWeb/login.aspx works as well.

However, it wasn't working when I was trying to browse to it from another machine on the network. The reason it wasn't working is that the machine where Fortress & Vault are installed is named "bl_desktop" and apparently it does not like underscores in the machine name of the URL. When I mapped the name "bldesktop" (without the underscore) to that machine's IP address, I was able to log in both locally and from any machine on my network.

I should be able to change the machine name to eliminate the underscore, but I had never heard of that being a problem before. Can you shed any light on whether that's just a problem with Fortress, or a problem with .NET authentication, or some other problem?

Thanks again,

jfennell · Post by **jfennell** » Fri May 16, 2008 1:40 pm

Also, in answer to your question about the logs, nothing gets logged in the Fortress log (C:\WINDOWS\temp\SGFortress\fortress.log) even after a successful login. The following gets logged in the Vault log (C:\WINDOWS\temp\sgvault\sgvault.log:

----5/16/2008 3:30:53 PM admin--localhost(127.0.0.1)--SSL Disabled Login

Not sure if the fact that there is nothing in the fortress log is an indication of an error. The item tracking in Fortress seems to be working fine, even though nothing is being logged.

Let me know if you think this is an indication of a problem or perhaps an indication of the "required product" failure from the installation.

Thanks again,

jfennell · Post by **jfennell** » Fri May 16, 2008 1:48 pm

Poking around a bit under Server Settings | Logging, I notice that the "Path to log file" is set to: %SYSTEMROOT%\Temp\sgvault. That might explain why things are being logged to sgvault and not sgfortress.

Beth · Post by **Beth** » Fri May 16, 2008 3:48 pm

On the '_', as far as I understand, cookies don't like '_'. If it was working before, then I can't really explain why it was working.

On the fortress log, I was thinking that log would show a failed login for the item tracking side. Both Vault and Fortress logs are used, but the Vault one more than Fortress, so you beat me to the punch there with checking that.

jfennell · Post by **jfennell** » Fri May 16, 2008 6:27 pm

Thanks Beth. I wasn't sure if it was cookies, sessions or something else. I'm all set now without the underscore.

Beth · Post by **Beth** » Mon May 19, 2008 10:12 am

Thanks for the follow up.