On our Vault Server we got the exception below in event log:
We have installed Vault 3.5.1 on an Windows Server 2003 SP1 .NET 2.0 and a seperate Machine with the SQL Server 2005. We access the Vault Server over a DNS alias.
Here's the exception:
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 22.02.2007 09:09:08
Event time (UTC): 22.02.2007 08:09:08
Event ID: ffcb78f33f9d4b07a53f95f74a668692
Event sequence: 1510
Event occurrence: 1
Event detail code: 0
Application information:
Application domain: /LM/W3SVC/1/Root/VaultService-1-128165160558705152
Trust level: Full
Application Virtual Path: /VaultService
Application Path: D:\Inetpub\wwwroot\VaultService\
Machine name: OUR_MACHINE_NAME
Process information:
Process ID: 880
Process name: w3wp.exe
Account name: NT AUTHORITY\NETWORK SERVICE
Exception information:
Exception type: InvalidOperationException
Exception message: Request format is unrecognized for URL unexpectedly ending in '/Ping'.
Request information:
Request URL: http://vault/VaultService/VaultService.asmx/Ping
Request path: /VaultService/VaultService.asmx/Ping
User host address: 172.16.10.14
User:
Is authenticated: False
Authentication Type:
Thread account name: OUR_DOMAIN\OUR_SQL_USER
Thread information:
Thread ID: 10
Thread account name: OUR_DOMAIN\OUR_SQL_USER
Is impersonating: True
Stack trace: at System.Web.Services.Protocols.WebServiceHandlerFactory.CoreGetHandler(Type type, HttpContext context, HttpRequest request, HttpResponse response)
at System.Web.Services.Protocols.WebServiceHandlerFactory.GetHandler(HttpContext context, String verb, String url, String filePath)
at System.Web.HttpApplication.MapHttpHandler(HttpContext context, String requestType, VirtualPath path, String pathTranslated, Boolean useAppConfig)
at System.Web.HttpApplication.MapHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
Custom event details:
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
============================================
Martin Toth
ASP.NET 2.0 Unhandled Exception (InvalidOperationException)
Moderator: SourceGear
So, outside of that one error, Vault is operating normally, right?
Is your communication going through a firewall by any chance? Sometimes, they can be set to refuse anything that's a ping. Or maybe the server is set to block those out?
Where that ping comes into play is during large operations between client and server. If it's not allowed, you could run into occasional issues with large gets or downloads.
Is your communication going through a firewall by any chance? Sometimes, they can be set to refuse anything that's a ping. Or maybe the server is set to block those out?
Where that ping comes into play is during large operations between client and server. If it's not allowed, you could run into occasional issues with large gets or downloads.
Thx for your answer!
I don't think that there's a firewall between the clients and the server they are all in the LAN - but we have different VLAN's.
I think this is not a real ICMP Ping this is only the call to a WebService with an operation "Ping" from Vault? So there should be no problem with the network.
Should the call to the WebService be "http://vault/VaultService/VaultService.asmx?op=Ping"?
Sometimes CheckIn/CheckOut Operations have poor performance.
but i think this is our sql server. we have some sql server connect timeout exceptions in the log file. we are currently checking the sql server. i have attached the log file.
I don't think that there's a firewall between the clients and the server they are all in the LAN - but we have different VLAN's.
I think this is not a real ICMP Ping this is only the call to a WebService with an operation "Ping" from Vault? So there should be no problem with the network.
Should the call to the WebService be "http://vault/VaultService/VaultService.asmx?op=Ping"?
Sometimes CheckIn/CheckOut Operations have poor performance.
but i think this is our sql server. we have some sql server connect timeout exceptions in the log file. we are currently checking the sql server. i have attached the log file.
- Attachments
-
- 070222sgvault.txt
- Trace with SQL Timeouts
- (35.37 KiB) Downloaded 494 times
You may wish to check out our article on improving performance: http://support.sourcegear.com/viewtopic.php?t=4206.
One thing that could cause the SQL timeout is the setting in the Vault.config file. Look for the entry <SQLCommandTimeout>360</SQLCommandTimeout>. Change this to something longer, like 720 or even 3600.
One thing that could cause the SQL timeout is the setting in the Vault.config file. Look for the entry <SQLCommandTimeout>360</SQLCommandTimeout>. Change this to something longer, like 720 or even 3600.
concerning the performance/sql server timeout i changed in vault.config the following values:
<SQLCommandTimeout>1800</SQLCommandTimeout>
DBBufferSizeKB>768</DBBufferSizeKB>
<TreeManagerSize>100</TreeManagerSize>
and disabled dnsreverselookup.
let's see.
The unhandled exception from the ping request we just ignore. it's no handicap for working with vault.
<SQLCommandTimeout>1800</SQLCommandTimeout>
DBBufferSizeKB>768</DBBufferSizeKB>
<TreeManagerSize>100</TreeManagerSize>
and disabled dnsreverselookup.
let's see.
The unhandled exception from the ping request we just ignore. it's no handicap for working with vault.