Error When Using

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

Moderator: SourceGear

Post Reply
TC

Error When Using

Post by TC » Thu Sep 29, 2005 11:33 pm

I am using Vault 3.1.2 on Windows 2003 with IIS 6.0. I need to shadow folders on the server. In order to do that, I followed instructions from the Vault knowledge base and configured IIS to run in IIS 5.0 isolation mode. As soon as I did that, however, Vault became unusable -- clients could not connect to the server. I received a very long error message which is shown below. I have since turned off IIS 5.0 isolation mode, and except for the non-functioning shadow folders, Vault is working properly again. Any suggestions?

-TC


Unable to connect to http://209.200.83.102/VaultService. No server was found at the specified URL. Please verify your network settings using the Options dialog under the Tools menu in the Vault GUI Client. Web Exception: Client found response content type of 'text/html; charset=utf-8', but expected 'text/xml'.
The request failed with the error message:
--
<html>
<head>
<title>Runtime Error</title>
<style>
body {font-family:"Verdana";font-weight:normal;font-size: .7em;color:black;}
p {font-family:"Verdana";font-weight:normal;color:black;margin-top: -5px}
b {font-family:"Verdana";font-weight:bold;color:black;margin-top: -5px}
H1 { font-family:"Verdana";font-weight:normal;font-size:18pt;color:red }
H2 { font-family:"Verdana";font-weight:normal;font-size:14pt;color:maroon }
pre {font-family:"Lucida Console";font-size: .9em}
.marker {font-weight: bold; color: black;text-decoration: none;}
.version {color: gray;}
.error {margin-bottom: 10px;}
.expandable { text-decoration:underline; font-weight:bold; color:navy; cursor:hand; }
</style>
</head>

<body bgcolor="white">

<span><H1>Server Error in '/VaultService' Application.<hr width=100% size=1 color=silver></H1>

<h2> <i>Runtime Error</i> </h2></span>

<font face="Arial, Helvetica, Geneva, SunSans-Regular, sans-serif ">

<b> Description: </b>An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.
<br><br>

<b>Details:</b> To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".<br><br>

<table width=100% bgcolor="#ffffcc">
<tr>
<td>
<code><pre>

<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration></pre></code>

</td>
</tr>
</table>

<br>

<b>Notes:</b> The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.<br><br>

<table width=100% bgcolor="#ffffcc">
<tr>
<td>
<code><pre>

<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration></pre></code>

</td>
</tr>
</table>

<br>

</body>
</html>

dan
Posts: 2448
Joined: Wed Dec 17, 2003 5:03 pm
Location: SourceGear
Contact:

Post by dan » Mon Oct 03, 2005 7:41 am

It looks like the actual error isn't being displayed because the connection is from a client machine. Can you try to connect from the server machine itself (e.g., go to http://localhost/VaultService on the server), and see whether it gives a better error message?

TC

RE: Error When Using IIS 5.0 Isolation Mode

Post by TC » Mon Oct 03, 2005 3:46 pm

When I use go the server and use a browser to navigate to https://209.200.83.102/VaultService/VaultService.asmx, I get the following error:

Server Error in '/VaultService' Application.

Access denied to 'C:\Inetpub\wwwroot\web.config'. Failed to start monitoring file changes.


-TC

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Post by lbauer » Mon Oct 03, 2005 4:06 pm

Does the account used by Vault have access to 'C:\Inetpub\wwwroot\web.config' ?

See this forum post for a similar problem and solution:

http://support.sourcegear.com/viewtopic.php?t=3097
Linda Bauer
SourceGear
Technical Support Manager

TC

RE: Error When Using IIS 5.0 Isolation Mode

Post by TC » Tue Oct 04, 2005 8:36 pm

There is no file 'C:\Inetpub\wwwroot\web.config'.

If there was such a file, I don't know whether the account used by Vault would have access to it. How can I find out what account is used by Vault?

Thank you for the reference. It seems relevant, but I'm not sure what solution it points to. Did that guy solve the problem just by giving the appropriate account read access on wwwroot? I'd like to try that, but, again, how do I figure out what account Vault is working with?

-TC

mskrobul
Posts: 490
Joined: Wed Jan 14, 2004 10:22 am
Location: SourceGear
Contact:

Post by mskrobul » Wed Oct 05, 2005 8:22 am

Do you have SharePoint installed on that machine or has SharePoint ever been installed on that machine?

SharePoint changes permissions on the IIS root directory when it is installed.

Make sure your Vault service directory has the following permissions:

Everyone: Read & Execute, List Folder Contents, and Read.
SYSTEM: Full Control
Network Service (or whatever process vault is running as is running as): Read & Execute, List Folder Contents, and Read
Mary Jo Skrobul
SourceGear

TC

RE: Error When Using IIS 5.0 Isolation Mode

Post by TC » Wed Oct 05, 2005 1:18 pm

I have worked through many problems, but I am sad to say that shadow folders still do not work.

A summary: I'm using Vault 3.1.2 on Windows 2003 with IIS 6.0. To get shadow folders to work, I turned on IIS 5.0 isolation mode. That caused a connection problem which I have finally solved by giving the ASPNET account modify privileges on the wwwroot folder and all its subfolders.

So, now I'm in IIS 5.0 isolation mode, but shadow folders do not work. As recommended, I deleted all shadow folder assignments and recreated them, but that didn't help. The behavior now is the same as it was before I switched to IIS 5.0 isolation mode: I don't get any errors. I'm allowed to configure shadow folders with no warnings. When I post files to the repository, however, nothing happens. The shadow folders aren't updated at all.

I'm stumped, but I really need to get this working. All advice is appreciated.

-TC

mskrobul
Posts: 490
Joined: Wed Jan 14, 2004 10:22 am
Location: SourceGear
Contact:

Post by mskrobul » Wed Oct 05, 2005 2:47 pm

Are the folders you are shadowing located on the same machine as the server?

Are there any errors logged to the shadow folder log file (VaultSahdowFolderService.txt) located in either %windir%\temp or the ASPNET (if you are in IIS 5.0 isolation mode) user's temp directory?

Does ASPNET have permission to the shadow directories?

Where is the cache information being kept for the shadow folders? This can be checked in the web.config file in your shadow folder directory. If the shadowfolder_cachepath key is commented out the cache file location will be the ASPNET user's application data directory (if you are in IIS 5.0 isolation mode). If this key is uncommented it will use that key's value for the cache location path.

Does ASPNET have permission to the cache directory path?

Are you using impersonation for either Vault Service or Vault Shadow folder service?
Mary Jo Skrobul
SourceGear

TC

RE: Error When Using IIS 5.0 Isolation Mode

Post by TC » Wed Oct 05, 2005 4:23 pm

Here are answers to your questions:
Are the folders you are shadowing located on the same machine as the server?
Yes. For now, I'm shadowing one folder only. It is C:\Inetpub\wwwroot\veecoprobes\work\worka on the server.
Are there any errors logged to the shadow folder log file (VaultSahdowFolderService.txt) located in either %windir%\temp or the ASPNET (if you are in IIS 5.0 isolation mode) user's temp directory?
There are many entries in both log files. I've attached both of them. The last few entries in the ASPNET log are:
10/5/2005 11:23:41 AM <generic>: [<No Name>:220] GetEntryAssembly() returned null; not logging assembly name
10/5/2005 11:24:38 AM <generic>: [<No Name>:220] Error adding shadow folder association: Directory C:\Inetpub\wwwroot\veecoprobes\work\worka doesn't exist
10/5/2005 11:26:50 AM <generic>: [<No Name>:220] Error adding shadow folder association: Directory C:\Inetpub\wwwroot\veecoprobes\work\worka doesn't exist
10/5/2005 11:29:56 AM <generic>: [<No Name>:376] SimpleLogger finalized

I assure you, C:\Inetpub\wwwroot\veecoprobes\work\worka does exist.
Does ASPNET have permission to the shadow directories?
Yes. The ASPNET account has modify, read & execute, list folder contents, read, and write permissions on C:\Inetpub\wwwroot\veecoprobes\work\worka.
Where is the cache information being kept for the shadow folders? This can be checked in the web.config file in your shadow folder directory. If the shadowfolder_cachepath key is commented out the cache file location will be the ASPNET user's application data directory (if you are in IIS 5.0 isolation mode). If this key is uncommented it will use that key's value for the cache location path.
The web.config at C:\Inetpub\wwwroot\VaultService\VaultShadowFolder has shadowfolder_cachepath commented out. The application path for ASPNET is C:\Documents and Settings\DEDE101\ASPNET\Application Data.
Does ASPNET have permission to the cache directory path?
Yes. ASPNET has full control on C:\Documents and Settings\DEDE101\ASPNET\Application Data.

Thank you for taking the time to help me diagnose this problem. I hope these answers give you a clear picture of what is going wrong.

-TC
Attachments
VaultShadowFolderService ASPNET.txt
Log file found in the ASPNET Temp folder
(15.73 KiB) Downloaded 737 times
VaultShadowFolderService Windows.txt
Log file found in the Windows temp folder
(718.69 KiB) Downloaded 733 times

mskrobul
Posts: 490
Joined: Wed Jan 14, 2004 10:22 am
Location: SourceGear
Contact:

Post by mskrobul » Thu Oct 06, 2005 7:43 am

Just as a test can you try to use a different shadow folder location to see if that works?

Try a folder that isn't under wwwroot.
Mary Jo Skrobul
SourceGear

TC

Post by TC » Thu Oct 06, 2005 1:42 pm

Just as a test can you try to use a different shadow folder location to see if that works?
Try a folder that isn't under wwwroot.
No, a different shadow folder location does not work.

I created a folder called C:\worka and made a shadow folder association between it and $/Veeco Probes Website/Work A. Nothing happens. C:\worka is completely empty. Vault has not written any files to it. After creating the shadow folder association, I revised documents and checked them in to the repository. Nevertheless, those files do not appear in C:\worka.

-TC

mskrobul
Posts: 490
Joined: Wed Jan 14, 2004 10:22 am
Location: SourceGear
Contact:

Post by mskrobul » Thu Oct 06, 2005 2:30 pm

Are you still getting the same error in the log file or is there a different error?

Are you sure that the Vault Shadow folder process is running as the ASPNET account on that machine? If you give everyone permission to the shadow folder then recofigure the folder does it work?

Is there anything being created in the shadow folder cache? (C:\Documents and Settings\MACHINE\ASPNET\Application Data\SourceGear\Vault_1\PluginWebService)?

Can you send me your shadow folder web.config file? You can use the email button at the bottom of this message.

Also, at this point it may be easier to trouble shoot this issue over the phone. If you email me your phone number (using the link at the bottom of the message) I will call you.
Mary Jo Skrobul
SourceGear

T.C.

Post by T.C. » Wed Oct 12, 2005 9:33 am

Thanks again for working on this. Here are answers:
Are you still getting the same error in the log file or is there a different error?
I'm getting a variety of errors in the log files. I've attached both files. The error which seems most relevant comes from the ASPNET version of the log file and says:

10/11/2005 2:26:13 PM <generic>: [<No Name>:3968] Vault's Shadow Folders encountered an exception attempting to login to the Vault Server for Repository ID 1. Unable to connect to http://209.200.83.102/VaultService. No server was found at the specified URL. Please verify your network settings using the Options dialog under the Tools menu in the Vault GUI Client. Web Exception: The request failed with HTTP status 403: Forbidden.
Are you sure that the Vault Shadow folder process is running as the ASPNET account on that machine? If you give everyone permission to the shadow folder then recofigure the folder does it work?
I don't know if the Vault Shadow folder process is running as the ASPNET account. How can I tell? (Is there any test I can do to see if the process is running at all? To date, I've seen nothing to suggest that there is a background process.)

If I give everyone permission to the shadow folder, then reconfigure it, it does not work.
Is there anything being created in the shadow folder cache? (C:\Documents and Settings\MACHINE\ASPNET\Application Data\SourceGear\Vault_1\PluginWebService)?
The machine name is DEDE101. There is no folder at C:\Documents and Settings\DEDE101\ASPNET\Application Data\SourceGear.
Can you send me your shadow folder web.config file? You can use the email button at the bottom of this message.
Also, at this point it may be easier to trouble shoot this issue over the phone. If you email me your phone number (using the link at the bottom of the message) I will call you.
I've sent you web.config and my phone number in an email.

-TC
Attachments
VaultShadowFolderService ASPNET.txt
(341.14 KiB) Downloaded 698 times
VaultShadowFolderService Windows.txt
(718.69 KiB) Downloaded 741 times

mskrobul
Posts: 490
Joined: Wed Jan 14, 2004 10:22 am
Location: SourceGear
Contact:

Post by mskrobul » Wed Oct 12, 2005 10:18 am

Update:

After talking to TC on the phone we found that the Vault Server website only allowed secure connections.

Changing the URL value for the shadowfolder_vaultserver key in the Shadow Folder web.config file from "http://..." to "https://..." fixed the problem.
Mary Jo Skrobul
SourceGear

Post Reply