Could not delete repository

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

Moderator: SourceGear

Post Reply
thinknirmal
Posts: 5
Joined: Thu Jul 30, 2009 7:12 pm
Location: Kuala Lumpur, Malaysia
Contact:

Could not delete repository

Post by thinknirmal » Sat Aug 01, 2009 3:57 am

While I attempted to delete a repository, I received the following script error:

Code: Select all

Webpage error details

User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.0; WOW64; Trident/4.0; SLCC1; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729)
Timestamp: Sat, 1 Aug 2009 09:52:34 UTC


Message: Sys.WebForms.PageRequestManagerParserErrorException: The message received from the server could not be parsed. Common causes for this error are when the response is modified by calls to Response.Write(), response filters, HttpModules, or server trace is enabled.
Details: Error parsing near '


<!DOCTYPE html'.
Line: 4723
Char: 21
Code: 0
URI: http://app-server-01/VaultService/ScriptResource.axd?d=8zsy0IAQbNemsdPVHmJhSgGkxp-Ad1GIxCauZ4UKihJIHCHcSuSC8Uqif8i_Sk-meUlkGvdm-gUVmerLrWd2dC5nbxy7hN_021NDlekVW1I1&t=ffffffffa1d7d61e

Now how to delete a repository? Please help.. :|

jeremy_sg
Posts: 1821
Joined: Thu Dec 18, 2003 11:39 am
Location: Sourcegear
Contact:

Re: Could not delete repository

Post by jeremy_sg » Sat Aug 01, 2009 1:29 pm

We haven't seen this error before, but another user was having repository deletion problems that we thought were something else. Maybe he was having this problem as well. Could you please try to follow the steps outlined at:

http://www.rtraction.com/blog/devit/asp ... ption.html

to see if they resolve the issue that you're seeing? Thanks for your patience.
Subscribe to the Fortress/Vault blog

lmfs
Posts: 5
Joined: Mon Aug 06, 2007 10:21 am

Re: Could not delete repository

Post by lmfs » Mon Aug 03, 2009 6:48 am

The other user was me. That is the same message I recieved, (I said the server returned a malformed response and that is the response I got - sorry for not clarifying that.)

IE (7/8) and Safari (3/4) returns the same error message. Firefox (3.5.1) stops dead when pushing the "OK" button in the delete-repository-warning dialog ("Warning: Deleting a repository may take quite some time...").

Tracing with FireBug, Fiddler2 and Safari yields:

Code: Select all

Sys.WebForms.PageRequestManagerParserErrorException: The message received from the server could not be parsed. Common causes for this error are when the response is modified by calls to Response.Write(), response filters, HttpModules, or server trace is enabled.

Details: Error parsing near '

<!DOCTYPE html'.
http://xyz:nnn/VaultService/ScriptResource.axd?d=1RSd36hIob_Ix4BshlDtFCoP5XTasgF1SPqwncQB5mJaaiwdDtk5ZMlQGNtupN6F0-EFFTwAk2TyYNoYtSVkxsXLOBGTdY4zyyu_sWIhZqYxelNVYNiNSYWbl28vAwYy0&t=d90830a (line 513
Line 513 is inside the "MicrosoftAjaxWebForms.debug.js" Ajax script file (v3.5, included via ScriptManager from Admin/Repositories.aspx).

Code: Select all

    function Sys$WebForms$PageRequestManager$_endPostBack(error, executor, data) {
        if (this._request === executor.get_webRequest()) {
            this._processingRequest = false;
            this._additionalInput = null;
            this._request = null;
        }
        var handler = this._get_eventHandlerList().getHandler("endRequest");
        var errorHandled = false;
        if (handler) {
            var eventArgs = new Sys.WebForms.EndRequestEventArgs(error, data ? data.dataItems : {}, executor);
            handler(this, eventArgs);
            errorHandled = eventArgs.get_errorHandled();
        }
        if (error && !errorHandled) {
513:     throw error;
        }
    }
    function Sys$WebForms$PageRequestManager$_findNearestElement(uniqueID) {
        while (uniqueID.length > 0) {
[There are nested Masterpages at work here, the "ScriptMode" of the ScriptManager tag in VaultSite.master could be set to "Release" in order to decrease the size of Ajax-included files. That does not help avoiding the error, though.]

Disabling event validation has no effect (EnableEventValidation=false).

Running on:
  • Windows 2003 Server, Enterprise Edition. Service Pack 2.
    Microsoft SQL Server 2008, Service Pack 1
    IIS 6
    .NET Framework 3.5.1 (3.5 with latest service pack and updates)
    Clean Vault installation of server and client
    Server is to be clean Vault server (i.e. nothing else installed other than OS, SQL and Vault)
    Locale set to Swedish
I've had no time to further investigate this matter and manual removal through SQL or restoration from clean backup works for me while we are testing the latest release.

Regards,
// Mike

jeremy_sg
Posts: 1821
Joined: Thu Dec 18, 2003 11:39 am
Location: Sourcegear
Contact:

Re: Could not delete repository

Post by jeremy_sg » Mon Aug 03, 2009 1:55 pm

Thank you very much for your help. I'm still investigating the cause of this. Are you having any troubles with the other pages that use AJAX? The other pages that use AnimationExtender are: EmailSettings, and Rebind.
Subscribe to the Fortress/Vault blog

lmfs
Posts: 5
Joined: Mon Aug 06, 2007 10:21 am

Re: Could not delete repository

Post by lmfs » Mon Aug 03, 2009 5:27 pm

No, I've actually used both of these pages (sent test e-mail and bound an old project (this failed but due to another issue, duplicating entries inside the solution (*.sln) file - that's for another thread).

But... I had a few minutes and I somehow forgot the debug logging facility earlier and it looks a bit weird, it's trying to access resources not available.

This is exactly what is reported at the moment when I press "OK" in the delete-repository-ajax modal window (from Vault logfile, loglevel=Debug), fully repeatable:

Code: Select all

----2009-08-04 00:54:51      admin--192.168.0.42(192.168.0.42)--SSL Disabled	DB: GetUserRepositories started. 
----2009-08-04 00:54:51      admin--192.168.0.42(192.168.0.42)--SSL Disabled	DB: GetUserRepositories finished. 
----2009-08-04 00:54:52      admin--192.168.0.42(192.168.0.42)--SSL Disabled	WEB: Could not connect to  http://xxx.yyy.zzz:nnnnn/Fortress/DragnetWebService.asmx -- Web Exception The request failed with HTTP status 404: Not Found. 
----2009-08-04 00:54:53      admin--192.168.0.42(192.168.0.42)--SSL Disabled	WEB: Could not connect to  http://localhost/Fortress/DragnetWebService.asmx -- Web Exception Unable to connect to the remote server 
----2009-08-04 00:54:53      admin--192.168.0.42(192.168.0.42)--SSL Disabled	DB: GetEmailSettings started. 
----2009-08-04 00:54:53      admin--192.168.0.42(192.168.0.42)--SSL Disabled	DB: GetEmailSettings finished. 
----2009-08-04 00:54:53      admin--192.168.0.42(192.168.0.42)--SSL Disabled	DB: GetEmailSettings started. 
----2009-08-04 00:54:53      admin--192.168.0.42(192.168.0.42)--SSL Disabled	DB: GetEmailSettings finished. 
----2009-08-04 00:54:53      admin--192.168.0.42(192.168.0.42)--SSL Disabled	WEB: Could not connect to  http://xxx.yyy.zzz:nnnnn/Fortress/DragnetWebService.asmx -- Web Exception The request failed with HTTP status 404: Not Found. 
----2009-08-04 00:54:53      admin--192.168.0.42(192.168.0.42)--SSL Disabled	DB: GetEmailSettings started. 
----2009-08-04 00:54:53      admin--192.168.0.42(192.168.0.42)--SSL Disabled	DB: GetEmailSettings finished. 
----2009-08-04 00:54:53      admin--192.168.0.42(192.168.0.42)--SSL Disabled	WEB: Could not connect to the Fortress item tracking web service.  Tried: http://xxx.yyy.zzz:nnnnn/, http://localhost/, and http://xxx.yyy.zzz:nnnnn/ 
----2009-08-04 00:54:53      admin--192.168.0.42(192.168.0.42)--SSL Disabled	Uncaught Exception: Exception of type 'System.Web.HttpUnhandledException' was thrown.
Inner Exception: Unable to connect to the Fortress item tracking web service. 
----2009-08-04 00:54:53      admin--192.168.0.42(192.168.0.42)--SSL Disabled	   at System.Web.UI.Page.HandleError(Exception e)
   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
   at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
   at System.Web.UI.Page.ProcessRequest()
   at System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context)
   at System.Web.UI.Page.ProcessRequest(HttpContext context)
   at ASP.admin_repositories_aspx.ProcessRequest(HttpContext context) in c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\vaultservice\dbdd2b86\7751b920\App_Web_ejk0wejt.2.cs:line 0
   at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
   at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
Inner Exeption Stack Trace:    at VaultWebLib.RemoteDragnetService..ctor()
   at VaultWebLib.RemoteDragnetService_DeleteProjectViaWorker..ctor(Int32 nPID)
   at VaultService.Repositories.ButtonOK_Click(Object sender, EventArgs e)
   at System.Web.UI.WebControls.Button.OnClick(EventArgs e)
   at System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument)
   at System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument)
   at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument)
   at System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData)
   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) 
----2009-08-04 00:54:53      admin--192.168.0.42(192.168.0.42)--SSL Disabled	DB: GetUserRepositories started. 
----2009-08-04 00:54:53      admin--192.168.0.42(192.168.0.42)--SSL Disabled	DB: GetUserRepositories finished. 
----2009-08-04 00:54:53      admin--192.168.0.42(192.168.0.42)--SSL Disabled	System.Exception: Unable to connect to the Fortress item tracking web service.
   at VaultWebLib.RemoteDragnetService..ctor()
   at VaultWebLib.RemoteDragnetService_DeleteProjectViaWorker..ctor(Int32 nPID)
   at VaultService.Repositories.ButtonOK_Click(Object sender, EventArgs e)
   at System.Web.UI.WebControls.Button.OnClick(EventArgs e)
   at System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument)
   at System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument)
   at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument)
   at System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData)
   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)    at VaultWebLib.RemoteDragnetService..ctor()
   at VaultWebLib.RemoteDragnetService_DeleteProjectViaWorker..ctor(Int32 nPID)
   at VaultService.Repositories.ButtonOK_Click(Object sender, EventArgs e)
   at System.Web.UI.WebControls.Button.OnClick(EventArgs e)
   at System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument)
   at System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument)
   at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument)
   at System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData)
   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
----2009-08-04 00:54:53      admin--192.168.0.42(192.168.0.42)--SSL Disabled	WEB: Finshed loading Error 
Fortress, or Dragnet for that matter, is not installed. It still tries to call the DragnetWebService.asmx service, probably from the RemoteDragnetService constructor or somewhere in the neighborhood. The libraries are there in the /Fortress directory (a plain catalog - no virtual directory or application below /) but I guess Vault shares common libraries with Fortress. However, no .asmx-files or anything except "bin", "External", "Feeds", "Help" and "Style" directories are present in "Fortress".

It's an uncaught exception and it looks, according to the logfile, like it very well could be the cause of the problem?

Regards,
// Mike

jeremy_sg
Posts: 1821
Joined: Thu Dec 18, 2003 11:39 am
Location: Sourcegear
Contact:

Re: Could not delete repository

Post by jeremy_sg » Tue Aug 04, 2009 9:47 am

Mike,

Thanks for the report. It's a Vault-specific bug where it's trying to connect to the item tracking projects unnecessarily. We'll get that fixed for 5.0.1. If you need a workaround in the meantime, email support@sourcegear.com with a link to this thread. I really appreciate the detail you gave, and your patience.
Subscribe to the Fortress/Vault blog

Post Reply