Vault Client on Windows Server 2008

[karlrony]

Althouh I can successfully connect to a 4.1.2.1815 server using Vista Ultimate, Vista Home Premium, and Server 2003 R2, I cannot connect using Windows 2008 32-bit or 64-bit versions. I'm currently trying to use the Windows 2008 32-bit version.

I connect to a server using a website address. The client will successfully find the the repository and determine that the client and server are versions 4.1.2.18185. After I select the repository, the client starts "Retrieving repository structure information from the server..." Instead of the structure, I get the following error in a dialog box after a long delay: There is an error in XML document (1, 16150).

I get the same error with client version 4.1.3.18336.

[Beth]

Are you using Vault through Visual Studio or as a stand-alone? Are others using it the same way?

[karlrony]

Stand-alone. Both ways work on Server 2003 and Vista.

[Beth]

Are you on the same network as the Vault server? If so, could you try the machine name or an IP address for connecting? Don't add http://.

From the Windows 2008 server, could you pull up a browser and try the following URL: http://<your vault server>/vaultservice.
From there, login to the web client. If that works just let me know.

[karlrony]

I am not on the same network, I connect from another state. Someone on the same network tried from Windows 2008 and duplicated my same problem.

We cannot connect using the IP address because the web server is configured to require the host name.

From the Windows 2008 IE browser, we both could successfully log in to the web client using https://vaultserver/vaultservice. In case it makes a difference, we must use https.

[Beth]

Can you connect to https://vaultserver/vaultservice/vaultservice.asmx?

With the client then, you are connecting using vaultserver as the entry for the server to use?

Are you using a Proxy at all?

Could you check your Event Viewer on your Windows 2008 Server? Are there any errors or warnings?

[Beth]

In addition to the last questions I asked, could I have you turn on client-side logging? All you have to do is open a Vault GUI client but press Cancel instead of logging in. Then press Ctrl - Alt - Shift - F12. Then look to the bottom of the window to find the location of the log. More about client logging can be found here: Client Side Logging.

Then try connecting again.

After that could you either post or email your client log and the Vault server log? Posted items can be removed by you after this issue is solved. If you prefer to email, send it to support at sourcegear.com (attn: Beth) with a link to this forum thread.

[karlrony]

I can connect to https://vaultserver/vaultservice/vaultservice.asmx. I'm not using a proxy. I am using SSL. The only errors in my event viewer is when I manually end the Vault Client.

I've attached the log as requested.

[Beth]

I think error in what you posted could be a connection timeout or something just not right with your 2.0 .Net framework. You could either look at how your Windows 2008 Server is networking or re-register and/or repair the 2.0 .NET framework.

The easy things to try would be:

• 1) At a command prompt, run the following commands.

  • Code: Select all

    C:\Windows\Microsoft.NET\framework\v2.0.50727\aspnet_regiis -u

    then

    Code: Select all

    C:\Windows\Microsoft.NET\framework\v2.0.50727\aspnet_regiis -i

  2) If #1 doesn't help, then perform a repair install of the 2.0 .NET framework.

Looking at the networking instead you could:

• 1) Enable network tracing in asp.net. That is described here: http://msdn2.microsoft.com/en-US/library/a6sbz1dx.aspx.
  
  2) Look at your network card setup. Are the network cards in your WIndows 2008 Servers the same as in the Vista machines and are the settings the same? Check the mtu settings for each.
  
  3) Run a packet sniffer to see what may be happening. Is network traffic continuing to run both to and from the machine?
  
  4) Is it possible that the Windows 2008 Server has a more restrictive firewall setting that won't allow communication?

[karlrony]

I ran your commands and then sfc /scannow based on a Google search. NET 2.0 appears to be fine.

Networking...
1) Is Vault client an asp.net app? What file would I modify?
2) I've configured two computers since August as Win 2003 R2 and Win 2008. With Win 2003, the computers had no trouble running Vault Client. With Win 2008, they could not retrieve the repository structure. The OS was the only difference. I loaded the same applications for each configuration on each computer. I don't know what you are talking about mtu settings.
3) I've never run a packet sniffer before. I don't want to learn right now.
4) I turned off the firewall and Vault client still can't retrieve the repository structure information.

Do you have a computer running Win 2008 and Vault client successfully retrieving the repository structure information from the server app running on a separate, Win 2003 R2 server? Would you be willing to try and use your Win 2008 computer and Vault client to connect to my server?

[Beth]

I have run this on a Windows 2008 Server machine and do have a machine still available.

Can you look in your Vault Server Log for any errors that occur at the same time as what you covered in the Vault client?

If you see no errors in the Vault server log that you can post for me, then I think we should take this offline so I can take a closer look.