Check-in error

[behold]

Some people are getting the follow error when checking in files. File and folder references are different, of course, but the other text is the same.

[9/11/2008 12:59:02 PM] Check in $/FRIS/FRIS2007/FRIS2007/BatchAdjLoad.vb
[9/11/2008 12:59:02 PM] Upload for item $/FRIS/FRIS2007/FRIS2007/BatchAdjLoad.vb failed, retrying...
[9/11/2008 12:59:02 PM] Upload for item $/FRIS/FRIS2007/FRIS2007/BatchAdjLoad.vb failed, retrying...
[9/11/2008 12:59:02 PM] Upload for item $/FRIS/FRIS2007/FRIS2007/BatchAdjLoad.vb failed, retrying...
[9/11/2008 12:59:02 PM] Ending the transaction
[9/11/2008 12:59:02 PM] Transaction failed
[9/11/2008 12:59:02 PM] Upload for item $/FRIS/FRIS2007/FRIS2007/BatchAdjLoad.vb failed too many times, aborting transaction.
Please verify your network settings using the Options dialog under the Tools menu in the Vault GUI Client.
The specific error was "The server had an error processing the file upload but did not return an error header. The remote server returned an error: (500) Internal Server Error."
An exception was encountered during the transaction. Exception: The server had an error processing the file upload but did not return an error header. The remote server returned an error: (500) Internal Server Error. at VaultClientOperationsLib.ClientInstance.UploadItem(ChangeSetItem item, String txID, Byte[]& streamBuffer, Int32& bytesWrittenThisFile, Boolean bIsImport)
at VaultClientOperationsLib.UploadThread.ProcessCommand(UploadThreadCommand command, UploadThreadCommandResult& outputResult)
[9/11/2008 12:59:03 PM] Transaction failed

*******FYI*******
Vault: 3.1.2
Client OS: Vista
SQL Server: 2000(8.0.2039)
Server OS: Windows Server 2000

[Beth]

That's a webserver error.

Can you reach your server with the following two URLs?
http://<your vault server>/vaultservice
and
http://<your vault server>/vaultservice/vaultservice.asmx

Let me know the results of each.

If they don't connect, then go directly to your Vault server, open a browser and try:
http://localhost/vaultservice
and
http://localhost/vaultservice/vaultservice.asmx
Then let me know those results.

[behold]

http://<your vault server>/vaultservice - This worked
http://<your vault server>/vaultservice/vaultservice.asmx - I got the following error

Runtime Error
Description: 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.

Details: 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".


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

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


Notes: 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.


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

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

[Beth]

Open your IIS manager and go to Web Service Extensions. Is aspnet 2.0 set to allow?

[behold]

We found the problem. The server was running out free space on the hard drive.

[Beth]

Thanks for the update.