Upgrade to Fortress 1.1 - Admin web access broken

If you are having a problem using Fortress, post a message here.

Moderator: SourceGear

DaleL
Posts: 11
Joined: Thu Jul 13, 2006 2:56 pm

Upgrade to Fortress 1.1 - Admin web access broken

Post by DaleL » Wed Mar 26, 2008 11:50 am

I upgraded to Fortress 1.1 yesterday and it seemed to go fine. Today however, I cannot access Item Tracking Admin from the web. I get the error:

"Unable to connect to the remote server"

Any ideas?

Thanks!

jeremy_sg
Posts: 1821
Joined: Thu Dec 18, 2003 11:39 am
Location: Sourcegear
Contact:

Post by jeremy_sg » Wed Mar 26, 2008 12:26 pm

In 1.1, the item tracking admin tools connect back to the Fortress web service. It seems that the URL it's attempting to reach isn't finding a web service. Do you see anything in your Vault server log file?

Can you use the Item tracking operations in the GUI client, which also connect to the Web Service?

DaleL
Posts: 11
Joined: Thu Jul 13, 2006 2:56 pm

Post by DaleL » Wed Mar 26, 2008 12:46 pm

Here's the sgvault.log entry when I last tried to connect:

----3/26/2008 11:35:23 AM dlundgren--c-98-203-244-150.hsd1.wa.comcast.net(98.203.244.150)--SSL Disabled System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.InternalConnect(EndPoint remoteEP)
at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception)
--- End of inner exception stack trace ---


The url is: http://www.imaginitdev.com/VaultService ... px?pid=115
The VaultService web service is there and appears to be functioning fine (except for admin access to Item Tracking).

jeremy_sg
Posts: 1821
Joined: Thu Dec 18, 2003 11:39 am
Location: Sourcegear
Contact:

Post by jeremy_sg » Wed Mar 26, 2008 1:01 pm

I noticed that when I clicked on the link, it rewrote
http://www.imaginitdev.com/VaultService/

to

http://www.imaginitdev.com/VAULTSERVICE/

Is it possible that that's confusing things? Try to go directly to

http://www.imaginitdev.com/VaultService ... Login.aspx

and start from there.

DaleL
Posts: 11
Joined: Thu Jul 13, 2006 2:56 pm

Post by DaleL » Wed Mar 26, 2008 1:29 pm

The casing doesn't make a difference. I've noticed that other Admin tasks such as user management use "VAULTSERVICE" and they work fine. It seems related to the Admin/Project.aspx page.

jeremy_sg
Posts: 1821
Joined: Thu Dec 18, 2003 11:39 am
Location: Sourcegear
Contact:

Post by jeremy_sg » Wed Mar 26, 2008 1:56 pm

Other Admin pages don't try to connect back to the same host via a web service. Actually, one does. Can you try the Shadow Folder configuration page to see if it can connect back?

DaleL
Posts: 11
Joined: Thu Jul 13, 2006 2:56 pm

Post by DaleL » Wed Mar 26, 2008 2:10 pm

OK, the Shadow folder gives a bit more descript error:

The Fortress server could not reach the Shadow Folder Service.

Shadow Folder Service URL:

http://localhost/VaultShadowFolder/Vaul ... rvice.asmx

This was all working perfectly prior to the 1.1 upgrade. Any ideas?

jeremy_sg
Posts: 1821
Joined: Thu Dec 18, 2003 11:39 am
Location: Sourcegear
Contact:

Post by jeremy_sg » Wed Mar 26, 2008 2:22 pm

First, please correct the Shadow Folder URL. Try setting it to: http://www.imaginitdev.com/VaultShadowF ... rvice.asmx

DaleL
Posts: 11
Joined: Thu Jul 13, 2006 2:56 pm

Post by DaleL » Wed Mar 26, 2008 2:35 pm

Same issue with and without "www":

The Fortress server could not reach the Shadow Folder Service.

Shadow Folder Service URL:

http://imaginitdev.com/VaultShadowFolde ... rvice.asmx

The Fortress server could not reach the Shadow Folder Service.

Shadow Folder Service URL:

http://www.imaginitdev.com/VaultShadowF ... rvice.asmx

jeremy_sg
Posts: 1821
Joined: Thu Dec 18, 2003 11:39 am
Location: Sourcegear
Contact:

Post by jeremy_sg » Wed Mar 26, 2008 2:39 pm

Can you put in your server's IP address? Also, can you try to connect to any of these URLs from your server machine itself?

DaleL
Posts: 11
Joined: Thu Jul 13, 2006 2:56 pm

Post by DaleL » Thu Mar 27, 2008 10:16 am

Here's the latest:

Logging on by IP Address results in the same error.

If I logon remotely as the user "admin" I can get to the Shadow folders page, but cannot access any Item tracking admin pages.

If I logon locally (from server) as "admin" or as my personal login I can access all the admin functions.

jeremy_sg
Posts: 1821
Joined: Thu Dec 18, 2003 11:39 am
Location: Sourcegear
Contact:

Post by jeremy_sg » Thu Mar 27, 2008 1:27 pm

Which URLs work from the machine, and which don't?

Do you have host headers turned on for this machine?

Which web site (and out of how many) is Fortress installed on?

DaleL
Posts: 11
Joined: Thu Jul 13, 2006 2:56 pm

Post by DaleL » Thu Mar 27, 2008 2:28 pm

Which URLs work from the machine, and which don't?
On the server, "localhost" works completely. imaginitdev.com does not work.

Do you have host headers turned on for this machine?
Yes

Which web site (and out of how many) is Fortress installed on?
imaginitdev.com
7 sites

DaleL
Posts: 11
Joined: Thu Jul 13, 2006 2:56 pm

Post by DaleL » Wed Apr 02, 2008 3:44 pm

Any ideas yet? I'm getting by for now by doing all admin on the server, would like the remote access back.

Thanks,

Dale

egli
Posts: 16
Joined: Tue Jul 25, 2006 10:34 am

Post by egli » Thu Apr 03, 2008 11:29 am

DaleL wrote:Any ideas yet? I'm getting by for now by doing all admin on the server, would like the remote access back.
The bug has been found and fixed, so things should be working in Fortress 1.1.2 when it is released.

In the meantime, a workaround could probably be put in place in order to give you access to the Item Tracking administration when connected remotely. The workaround would involve modifying the "hosts" file (usually found in the folder something like "C:\WINDOWS\system32\drivers\etc") on the server machine.

From what i gather from your reports, this would mean adding the line

Code: Select all

127.0.0.1       imaginitdev.com
to the end of the file.

... Finally, i will note that while the fix in Fortress 1.1.2 should work for most server configurations, there may still be some instances where people with multiple web sites filtered by host headers need to implement such a workaround.

Post Reply