Version 3.0 Configuration: Email Notification
Moderator: SourceGear
Version 3.0 Configuration: Email Notification
Did not do anything within the Admin Tool to setup or enable Email notification. Same for the Server. Within the VaultGui, I added my email address (myname@mycompany.com) and added a folder to "watch." I had someone checkout + modify + checkin a file in the folder I setup the email notification on. Nothing. The VaultGui show the file as Old. I select Refresh: nothing... What else do I have to do?
Thanks, Dan.
Thanks, Dan.
Dan in San Diego
Dan:
You'll need to configure an SMTP server ( for Vault server to send outgoing mail ) within the Admin Tool.
Start the Admin Tool. Log in, and bring up the Server options tab. On this tab, there is a button for email configuration. Click the button and set your outgoing SMTP server along with any other options you wish to use to send the mail along its way.
HTH
You'll need to configure an SMTP server ( for Vault server to send outgoing mail ) within the Admin Tool.
Start the Admin Tool. Log in, and bring up the Server options tab. On this tab, there is a button for email configuration. Click the button and set your outgoing SMTP server along with any other options you wish to use to send the mail along its way.
HTH
Jeff Clausius
SourceGear
SourceGear
Found it, thanks. When trying to configure, we're getting an error:
"Error setting server email options: VaultServiceAPILib.VaultSoapException: Access to the path 'c:\inetpub\wwwroot\vaultservice\vault.config' is denied. at VaultService.VaultAdminService.SetServerEmailOptions(VaultServerEmailOptions vOptions)"
Any tips to correct this?
"Error setting server email options: VaultServiceAPILib.VaultSoapException: Access to the path 'c:\inetpub\wwwroot\vaultservice\vault.config' is denied. at VaultService.VaultAdminService.SetServerEmailOptions(VaultServerEmailOptions vOptions)"
Any tips to correct this?
Hmm... That is strange. A couple of things come to mind:
1) Is the file's read-only status set?
2) Does the ASP.Net Process ( which the Vault server runs under ), have read-write security access to the file?
3) Is the path, C:\inetpub\wwwroot\vaultservice\vault.config, correct?
4) Is some other process locking the file? ( You can test this by a quick edit in notepad or another text editor )
1) Is the file's read-only status set?
2) Does the ASP.Net Process ( which the Vault server runs under ), have read-write security access to the file?
3) Is the path, C:\inetpub\wwwroot\vaultservice\vault.config, correct?
4) Is some other process locking the file? ( You can test this by a quick edit in notepad or another text editor )
Jeff Clausius
SourceGear
SourceGear
Thanks for the quick response!jclausius wrote:Hmm... That is strange. A couple of things come to mind:
1) Is the file's read-only status set?
2) Does the ASP.Net Process ( which the Vault server runs under ), have read-write security access to the file?
3) Is the path, C:\inetpub\wwwroot\vaultservice\vault.config, correct?
4) Is some other process locking the file? ( You can test this by a quick edit in notepad or another text editor )
#1 No, the file is not read-only.
#2 Yes, it does have read/write access.
#3 Yes, the path is correct.
#4 Yes, I can modify the file by hand....but if I enter a password for the SMTP user ( using a text editor ) then I get another error when I try the email settings tab: "VaultServiceAPILib.VaultSoapException: 1 : Failure at VaultService.VaultAdminService.ListServerEmailOptions(VaultServerEmailOptions_vOptions).
I'm having the same problem here.
I installed 3.0.1 over an existing 2.0.6 installation. We are running Windows 2003 Web Edition. Vault is configured to use a custom domain account through its own IIS App Pool. This is the same configuration that we had with 2.0.6. I selected "custom" in the installer, and provided the correct account information.
After this problem started, I checked the web.config. Since the identity impersonation is done through the App Pool, I commented out the identity impersonation in there. No change.
I've checked all the folder permissions as listed in the knowledgebase articles, and everything seems to be fine so far.
There is nothing interesting in the vault server log, but we're not running with debug logging.
Any updates on what is causing this problem and how to fix it?
I installed 3.0.1 over an existing 2.0.6 installation. We are running Windows 2003 Web Edition. Vault is configured to use a custom domain account through its own IIS App Pool. This is the same configuration that we had with 2.0.6. I selected "custom" in the installer, and provided the correct account information.
After this problem started, I checked the web.config. Since the identity impersonation is done through the App Pool, I commented out the identity impersonation in there. No change.
I've checked all the folder permissions as listed in the knowledgebase articles, and everything seems to be fine so far.
There is nothing interesting in the vault server log, but we're not running with debug logging.
Any updates on what is causing this problem and how to fix it?
Admin Tools | Server Options | Email Settings exception
I also upgraded from Vault 2.xx to 3.0.1. When I attempt to configure an SMTP server by clicking on the Email Settings button the Admin Tool reports an unhandled exception.
Vault is running on Windows Server 2003 standard edition, fully patched with .NET Framework 1.1 SP1. The Microsoft smtpsvc is installed and configured locally on the server. Other applications on the server are able to use smtpsvc to send SMTP messages using the System.Web.Mail APIs in the .NET Framework. Vault has it's own AppPool and the AppPool service account has read/write permission to the /VaultService folder. Nothing is locking the vault.config file.
It appears that the exception is generated by /VaultService/VaultAdminService.asmx when ListServerEmailOptions is invoked.
************** 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)
Vault is running on Windows Server 2003 standard edition, fully patched with .NET Framework 1.1 SP1. The Microsoft smtpsvc is installed and configured locally on the server. Other applications on the server are able to use smtpsvc to send SMTP messages using the System.Web.Mail APIs in the .NET Framework. Vault has it's own AppPool and the AppPool service account has read/write permission to the /VaultService folder. Nothing is locking the vault.config file.
It appears that the exception is generated by /VaultService/VaultAdminService.asmx when ListServerEmailOptions is invoked.
************** 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)
There is a bug in the reading of the Vault.config for both 3.0.0 and 3.0.1, where if the <EmailAllowedEndings> element is missing, the email options dialog won't come up correctly. This will be corrected in 3.0.2. A workaround would be to add
right above the </appsettings> line in your vault.config file.
Code: Select all
<EmailAllowedEndings></EmailAllowedEndings>