Unable to connect to the fortress item tracking web service
Moderator: SourceGear
Unable to connect to the fortress item tracking web service
Hello there,
I recently installed Fortress (FortressServer_1_1_4_18402.msi) at a test machine running Windows XP pro SP3.
I managed to get everything up and running, but ....
- I was able to add a project to the "Item Tracking Projects" once.
- Now when I try to add a new project, after entering a name and pressing the Create button I get the error message:
Error
Unable to connect to the Fortress item tracking web service.
I get the same error when I try to select the project that I was able to add the first time, from the menu at the left hand side of the screen.
(Clicking at the project name just below the header "Item Tracking Projects".
We're should I look to resolve this issue??
Alberto
I recently installed Fortress (FortressServer_1_1_4_18402.msi) at a test machine running Windows XP pro SP3.
I managed to get everything up and running, but ....
- I was able to add a project to the "Item Tracking Projects" once.
- Now when I try to add a new project, after entering a name and pressing the Create button I get the error message:
Error
Unable to connect to the Fortress item tracking web service.
I get the same error when I try to select the project that I was able to add the first time, from the menu at the left hand side of the screen.
(Clicking at the project name just below the header "Item Tracking Projects".
We're should I look to resolve this issue??
Alberto
Re: Unable to connect to the fortress item tracking web service
Is Fortress installed on a Domain Controller?
If not, try this:
Make sure that the "machine key" values are identical in the web.config files in both the Fortress and VaultService folders. The installer should create identical machine keys in both web.config files, but maybe something got messed up.
In Windows 2003 if you chose all of the defaults during installation the NT Authority/Network Service account needs read/write access to the following folders in order for the Server to work:
* the local directories containing the server installation files (by default, c:\InetPub\wwwroot\VaultService and c:\Inetpub\wwwroot\Fortress).
* the directory where the log files are written (by default, WINNT\Temp).
* the IIS process account's %userprofile%\Application Data \Microsoft\Crypto\RSA\MachineKeys or to %ALLUSERSPROFILE%\Application Data\Microsoft\Crypto\RSA\MachineKeys if the IIS process account does not have a user profile.
* the Vault Shadow Folder directory - c:\InetPub\wwwroot\VaultService\VaultShadowFolder
* Windows\Microsoft.NET\Framework\<version>\Temporary ASP.NET Files.
Also, make sure the Fotress and VaultService web service's virtual directories have Anonymous Access enabled in IIS.
If this doesn't help, send a copy of the Fortress_install.log file from your user's directory on the Fortress Server machine to support at sourcegear.com, Attn: Linda. Be sure to include a link to this forum post.
If not, try this:
Make sure that the "machine key" values are identical in the web.config files in both the Fortress and VaultService folders. The installer should create identical machine keys in both web.config files, but maybe something got messed up.
Code: Select all
<machineKey validationKey="HUGE_STRING_OF_NUMBERS" decryptionKey="SLIGHTLY_LESS_HUGE_STRING_OF_NUMBERS" validation="SHA1"/>
* the local directories containing the server installation files (by default, c:\InetPub\wwwroot\VaultService and c:\Inetpub\wwwroot\Fortress).
* the directory where the log files are written (by default, WINNT\Temp).
* the IIS process account's %userprofile%\Application Data \Microsoft\Crypto\RSA\MachineKeys or to %ALLUSERSPROFILE%\Application Data\Microsoft\Crypto\RSA\MachineKeys if the IIS process account does not have a user profile.
* the Vault Shadow Folder directory - c:\InetPub\wwwroot\VaultService\VaultShadowFolder
* Windows\Microsoft.NET\Framework\<version>\Temporary ASP.NET Files.
Also, make sure the Fotress and VaultService web service's virtual directories have Anonymous Access enabled in IIS.
If this doesn't help, send a copy of the Fortress_install.log file from your user's directory on the Fortress Server machine to support at sourcegear.com, Attn: Linda. Be sure to include a link to this forum post.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
Re: Unable to connect to the fortress item tracking web service
Hello Linda,
Enabling Anonymous Access in IIS for the Fortress and VaultService web service's virtual directories solved the problem.
Thanks for your support.
Alberto
Enabling Anonymous Access in IIS for the Fortress and VaultService web service's virtual directories solved the problem.
Thanks for your support.
Alberto
Re: Unable to connect to the fortress item tracking web service
Thanks for the update. That's good news.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
Re: Unable to connect to the fortress item tracking web service
I'm having the same issues, however I tried to do the same thing and everything seems correct... am I missing something here?
Re: Unable to connect to the fortress item tracking web service
What version of Fortress are you using? What are you doing in Fortress when you get the error message?
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
Re: Unable to connect to the fortress item tracking web service
The issue has seemed to been resolved when I switched back to IE
Re: Unable to connect to the fortress item tracking web service
Ok. Let us know if you have additional issues with this.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager