admin tool: email settings -> crash

vrapp · Post by **vrapp** » Wed Dec 01, 2004 1:12 pm

clicking on "email settings" button in admin tool/server options results in crash:

************** Exception Text **************
System.Web.Services.Protocols.SoapException: 1 : Failure
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at VaultClientNetLib.AdminService.VaultAdminService.ListServerEmailOptions(VaultServerEmailOptions& vOptions)
at VaultClientNetLib.VaultConnection.ListServerEmailOptions(VaultServerEmailOptions& vOptions)
at VaultAdmin.FormEmailOptions..ctor(AdminManager am)
at VaultAdmin.FormMain.buttonEmailOptions_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Loaded Assemblies **************
mscorlib
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///f:/winnt/microsoft.net/framework/v1.1.4322/mscorlib.dll
----------------------------------------
VaultAdmin
Assembly Version: 3.0.0.2752
Win32 Version: 3.0.0.2752
CodeBase: file:///F:/Program%20Files/SourceGear/Admin%20Tool/VaultAdmin.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///f:/winnt/assembly/gac/system.windows.forms/1.0.5000.0__b77a5c561934e089/system.windows.forms.dll
----------------------------------------
System
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///f:/winnt/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
----------------------------------------
VaultPresentationLib
Assembly Version: 3.0.0.2752
Win32 Version: 3.0.0.2752
CodeBase: file:///F:/Program%20Files/SourceGear/Admin%20Tool/VaultPresentationLib.DLL
----------------------------------------
System.Drawing
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///f:/winnt/assembly/gac/system.drawing/1.0.5000.0__b03f5f7f11d50a3a/system.drawing.dll
----------------------------------------
VaultLib
Assembly Version: 3.0.0.2752
Win32 Version: 3.0.0.2752
CodeBase: file:///F:/Program%20Files/SourceGear/Admin%20Tool/VaultLib.DLL
----------------------------------------
VaultClientUILib
Assembly Version: 3.0.0.2752
Win32 Version: 3.0.0.2752
CodeBase: file:///F:/Program%20Files/SourceGear/Admin%20Tool/VaultClientUILib.DLL
----------------------------------------
VaultClientNetLib
Assembly Version: 3.0.0.2752
Win32 Version: 3.0.0.2752
CodeBase: file:///F:/Program%20Files/SourceGear/Admin%20Tool/VaultClientNetLib.DLL
----------------------------------------
System.Web.Services
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///f:/winnt/assembly/gac/system.web.services/1.0.5000.0__b03f5f7f11d50a3a/system.web.services.dll
----------------------------------------
VaultClientOperationsLib
Assembly Version: 3.0.0.2752
Win32 Version: 3.0.0.2752
CodeBase: file:///F:/Program%20Files/SourceGear/Admin%20Tool/VaultClientOperationsLib.DLL
----------------------------------------
System.Xml
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///f:/winnt/assembly/gac/system.xml/1.0.5000.0__b77a5c561934e089/system.xml.dll
----------------------------------------
System.Web
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///f:/winnt/assembly/gac/system.web/1.0.5000.0__b03f5f7f11d50a3a/system.web.dll
----------------------------------------
_tfxyjox
Assembly Version: 0.0.0.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///f:/winnt/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
----------------------------------------
uqna4wox
Assembly Version: 0.0.0.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///f:/winnt/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
----------------------------------------
System.Management
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///f:/winnt/assembly/gac/system.management/1.0.5000.0__b03f5f7f11d50a3a/system.management.dll
----------------------------------------
vs
Assembly Version: 1.0.1787.31312
Win32 Version: 1.0.1787.31312
CodeBase: file:///F:/Program%20Files/SourceGear/Admin%20Tool/vs.DLL
----------------------------------------

Post by **jclausius** » Wed Dec 01, 2004 1:33 pm

Can you log into the server using your Vault GUI client, go to Help -> Technical support. What information is provided there?

Also, is there anything in the server's log file?

vrapp · Post by **vrapp** » Wed Dec 01, 2004 1:50 pm

replied via PM.

Post by **jclausius** » Wed Dec 01, 2004 2:16 pm

The server log file looks like the Vault server encountered a weird error around 1:06 PM, and restarted. Is this the time of the Admin Tool crash?

If so, can you examine your Windows Events for both Application / System. Is there anything in there related to .Net or ASP.Net that may indicate some sort of problem?

vrapp · Post by **vrapp** » Thu Dec 02, 2004 8:28 am

replied via PM.

Post by **jclausius** » Thu Dec 02, 2004 8:55 am

OK... Nothing suspicious there either. Are you running the Admin Tool on the Vault server itself?

Post by **jclausius** » Thu Dec 02, 2004 11:44 am

One other thing to check - vault.config.

Does the ASP.Net process account have read-write access to the VaultService folder as well as the vault.config file ( assuming this is on an NTFS formatted drive )?

vrapp · Post by **vrapp** » Thu Dec 02, 2004 1:37 pm

after I reinstalled the server with impersonation (as in this article) , the crash did not happen. Not AD auth works.

In the email dialog, Help button did not work - Help viewer showed "this page cannot be displayed". The reason I was looking for Help was (1) to find out why would I need an email

, and (2) what is "server URL" for, given that SMTP server was already specified.

BTW, when I specified the domain in the admin tool, it showed a warning with a link. The link was pointing to an article related to shadow folders, while I think that the article I referenced above is more relevant.

Post by **jclausius** » Thu Dec 02, 2004 1:52 pm

I'm a bit confused.

Can you explain your setup the first time around ( impersonation vs. ASP.Net process Account vs. Local System )? Did you change web.config to impersonate outside the installer?

Any additionaly information you can provide would be helpful in trying to determine what exactly happened here.

Also, you mention AD Auth. What was the problem there, as this thread was about the Email Settings.

----------

I'l log a bug about the Help button on the email dialog.

The email notification sends messages to registered users of any changes to the repository. The From address is the user the notification email will be from and the Server URL is the address to the Vault server ( ex: http://vaultserver.sourcegear.com/VaultService ).

This Server URL is used to provide links to the actual file within VaultWeb in case someone wants to "click" to view.

Post by **jeremy_sg** » Fri Dec 03, 2004 9:41 am

vrapp,

I've pointed the kb link to the better article. Thanks for pointing that out. We're still trying to get the kb stuff set up.

vrapp · Post by **vrapp** » Sat Dec 04, 2004 9:28 am

Can you explain your setup the first time around ( impersonation vs. ASP.Net process Account vs. Local System )? Did you change web.config to impersonate outside the installer?

At first I installed (or, rather, upgraded from 2.6) with all default settings, i.e. whatever was the 1st choice for the login in the setup dialog. That's when email button was crashing.

I also wanted domain auth, so I tried to make the impersonation "manually", i.e. by editing web.config; but then Vault did not work at all - probably I was doing something wrong.

Then I simply reinstalled Vault and specified "custom" during the setup, and after that I found both domain auth and email button working.

We're still trying to get the kb stuff set up

Here's a suggestion: currently, your KB articles = your posts in the forum. Make KB a separate entity.

Post by **jeremy_sg** » Sat Dec 04, 2004 1:42 pm

That makes sense. One of my hopes for the future is to create an identity switcher that will set all of the right permissions on the folders and objects that are necessary, as well as make the needed change to the web.config.

With the KB stuff, with 3.0, we've put more dynamic links in the client error dialog to do an automatic search in a separate kb. The impersonation link is one of the few static ones, so it didn't get as much attention as the dynamic links. The goal with setting up the dynamic links using the forum for a backend was so that we could make sure that everyone at Sourcegear had access to edit them and keep them up to date. It's my mission to make sure that the dynamic links from the client don't result in stale information.

Post by **jclausius** » Sat Dec 04, 2004 9:59 pm

vrapp wrote:I also wanted domain auth, so I tried to make the impersonation "manually"

That would explain things. If you take notice during installation, there is a dialog, which states certain NTFS permissions will be granted to some folders. By switching identities outside the installer, the permissions of the newly configured identity were not placed on all folders Vault requires to work correctly.

Jeremy's suggestion of a "security permission checker" would be a welcome fix to the problem.

Guest · Post by **Guest** » Sun Dec 05, 2004 7:56 am

jclausius wrote:
vrapp wrote:I also wanted domain auth, so I tried to make the impersonation "manually"
That would explain things. If you take notice during installation, there is a dialog, which states certain NTFS permissions will be granted to some folders. By switching identities outside the installer, the permissions of the newly configured identity were not placed on all folders Vault requires to work correctly.

No, I think the crash happened before I started playing with the identities.