Emails not firing

Jun 14, 2010 at 7:33 PM
I have just successfully gotten ST up and running on a local server here in my office and for security reasons, I am not allowed to tie in AD at this time. I am guessing that the generic error stating 'email not sent' when creating a ticket is due to AD not being integrated with my installation? Ideally I'd like to have some sort of work around. I am a novice coder, however I'm sure with time I could customize some sort of automatic email firing when generating a ticket. My department is 3 persons total, where we will all have full administration rights and simply want the ability to be notified when a ticket has been updated/created and sent to us. Is there an out-of-the-box way I can get this to work or will this require customization since we're not using AD at this time?
Coordinator
Jun 15, 2010 at 4:47 AM

Email has nothing to do with AD - but it does require an exchange server the ways it's coded.  Do you have rights to send on your server with the given account?  Otherwise you could easily alter it to use something like gmail.

Jun 15, 2010 at 12:27 PM
Okay I spoke with IT Administrator, he says I have full access to the server, just need to point to our server name and it should work. Is the file to be updated ticket.aspx?
Coordinator
Jun 15, 2010 at 1:34 PM

No, just change it on the settings page in the admin section through the program

Jun 15, 2010 at 1:40 PM
Edited Jun 16, 2010 at 12:09 PM
Okay I changed it to our smtp server name first and then to the IP address and I'm getting the generic authentication error: 

"The smtp server requires a secure connection or the client was not authenticated. the server response was: 5.7.1 client was not authenticated"

On Tue, Jun 15, 2010 at 9:34 AM, naspinski <notifications@codeplex.com> wrote:

From: naspinski

No, just change it on the settings page in the admin section through the program

Read the full discussion online.

To add a post to this discussion, reply to this email (slickticket@discussions.codeplex.com)

To start a new discussion for this project, email slickticket@discussions.codeplex.com

You are receiving this email because you subscribed to this discussion on CodePlex. You can unsubscribe on CodePlex.com.

Coordinator
Jun 16, 2010 at 10:19 AM

I will add this in the future to be able to specify a secure connect, but until then you will have to edit the SendEmail() method in WebUI/App_Code/utils.cs until then to handle secure connections

Jun 16, 2010 at 1:03 PM
To be honest, I am a novice developer so I am literally learning a lot of this on the fly... 

Would it be simpler to edit this method to use secure connections or go with one of your previous suggestions of using gmail to push the emails? 

On Wed, Jun 16, 2010 at 6:19 AM, naspinski <notifications@codeplex.com> wrote:

From: naspinski

I will add this in the future to be able to specify a secure connect, but until then you will have to edit the SendEmail() method in WebUI/App_Code/utils.cs until then to handle secure connections

Read the full discussion online.

To add a post to this discussion, reply to this email (slickticket@discussions.codeplex.com)

To start a new discussion for this project, email slickticket@discussions.codeplex.com

You are receiving this email because you subscribed to this discussion on CodePlex. You can unsubscribe on CodePlex.com.

Please note: Images and attachments will be removed from emails. Any posts to this discussion will also be available online at CodePlex.com




--
Samuel H. LoSurdo
samuel.h.losurdo@gmail.com
315.415.3877

"When people dream of getting rich, it's about more than nice clothes and fancy vacations. Being rich means freedom: to spend your time as you please, to pursue your real interests and to take chances without courting utter ruin. Paradoxically, the road to riches often means acting as if you already have that freedom."
Coordinator
Jun 17, 2010 at 5:26 AM

Both are trivial to implement.  To make email over ssl, just set the smtp.EndableSsl = true and define the username, password and port.

-or just use the gmail approach: http://naspinski.net/post/Sending-email-programmatically-with-gmail--tutorial.aspx

 

Jun 21, 2010 at 4:31 PM
Hey Stan,

Ran into another issue while trying to get gmail integrated with slickticket... I used that script you sent me and it appears that it requires SQLXML 4.0 and that is only installed with SQL Server 2005 (full) and not in Express... 

Anyways, here's the compiler error I am getting: 

Server Error in '/' Application.

Compilation Error

Description: An error occurred during the compilation of a resource required to service this request. Please review the following specific error details and modify your source code appropriately.

Compiler Error Message: CS0103: The name 'txtMessage' does not exist in the current context

Source Error:

Line 106:		MailMessage message = new MailMessage();
Line 107:		
Line 108:		message.To.Add(txtMessage.Text); 
Line 109:		MailAddress maFrom = new MailAddress("adptickets@gmail.com");
Line 110:		message.From = maFrom;

Source File: c:\SlickTicket\App_Code\utils.cs    Line: 108


Compiler Warning Messages:
Warning: CS1668: Invalid search path 'C:\Program Files\SQLXML 4.0\bin\' specified in 'LIB environment variable' -- 'The system cannot find the path specified. '
Source Error:

[No relevant source lines]

Warning: CS0028: 'Utils.Menus.Main()' has the wrong signature to be an entry point
Source Error:

c:\SlickTicket\App_Code\utils.cs
Line 185:    public class Menus
Line 186:    {
Line 187:        public static IEnumerable<XElement> Main()
Line 188:        {
Line 189:            XDocument x = XDocument.Load(HttpContext.Current.Server.MapPath("~/") + "/App_Data/main_menu.xml");


Show Detailed Compiler Output:

c:\windows\system32\inetsrv> "C:\WINDOWS\Microsoft.NET\Framework\v3.5\csc.exe" /t:library /utf8output /R:"C:\WINDOWS\assembly\GAC_MSIL\System.ServiceModel\3.0.0.0__b77a5c561934e089\System.ServiceModel.dll" /R:"C:\WINDOWS\assembly\GAC_32\System.Data\2.0.0.0__b77a5c561934e089\System.Data.dll" /R:"C:\WINDOWS\assembly\GAC_MSIL\System.Web.Extensions\3.5.0.0__31bf3856ad364e35\System.Web.Extensions.dll" /R:"C:\WINDOWS\assembly\GAC_MSIL\System.Web.Mobile\2.0.0.0__b03f5f7f11d50a3a\System.Web.Mobile.dll" /R:"C:\WINDOWS\assembly\GAC_MSIL\System.DirectoryServices\2.0.0.0__b03f5f7f11d50a3a\System.DirectoryServices.dll" /R:"C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\mscorlib.dll" /R:"C:\WINDOWS\assembly\GAC_MSIL\System.Core\3.5.0.0__b77a5c561934e089\System.Core.dll" /R:"C:\WINDOWS\assembly\GAC_MSIL\System.Runtime.Serialization\3.0.0.0__b77a5c561934e089\System.Runtime.Serialization.dll" /R:"C:\WINDOWS\assembly\GAC_MSIL\System\2.0.0.0__b77a5c561934e089\System.dll" /R:"C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\root\2fc5c153\dc2486a9\App_GlobalResources.hiqvypkm.dll" /R:"C:\WINDOWS\assembly\GAC_MSIL\System.Web.Services\2.0.0.0__b03f5f7f11d50a3a\System.Web.Services.dll" /R:"C:\WINDOWS\assembly\GAC_MSIL\System.Configuration\2.0.0.0__b03f5f7f11d50a3a\System.Configuration.dll" /R:"C:\WINDOWS\assembly\GAC_32\System.Web\2.0.0.0__b03f5f7f11d50a3a\System.Web.dll" /R:"C:\WINDOWS\assembly\GAC_MSIL\System.WorkflowServices\3.5.0.0__31bf3856ad364e35\System.WorkflowServices.dll" /R:"C:\WINDOWS\assembly\GAC_MSIL\System.Drawing\2.0.0.0__b03f5f7f11d50a3a\System.Drawing.dll" /R:"C:\WINDOWS\assembly\GAC_MSIL\System.Xml\2.0.0.0__b77a5c561934e089\System.Xml.dll" /R:"C:\WINDOWS\assembly\GAC_MSIL\System.Data.Linq\3.5.0.0__b77a5c561934e089\System.Data.Linq.dll" /R:"C:\WINDOWS\assembly\GAC_MSIL\System.Xml.Linq\3.5.0.0__b77a5c561934e089\System.Xml.Linq.dll" /R:"C:\WINDOWS\assembly\GAC_MSIL\System.IdentityModel\3.0.0.0__b77a5c561934e089\System.IdentityModel.dll" /R:"C:\WINDOWS\assembly\GAC_32\System.EnterpriseServices\2.0.0.0__b03f5f7f11d50a3a\System.EnterpriseServices.dll" /R:"C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\root\2fc5c153\dc2486a9\assembly\dl3\c5c58e39\0090b6fe_553eca01\AjaxControlToolkit.DLL" /R:"C:\WINDOWS\assembly\GAC_MSIL\System.Data.DataSetExtensions\3.5.0.0__b77a5c561934e089\System.Data.DataSetExtensions.dll" /R:"C:\WINDOWS\assembly\GAC_MSIL\System.ServiceModel.Web\3.5.0.0__31bf3856ad364e35\System.ServiceModel.Web.dll" /out:"C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\root\2fc5c153\dc2486a9\App_Code.gpgqvtxd.dll" /D:DEBUG /debug+ /optimize- /w:4 /nowarn:1659;1699;1701 /warnaserror-  "C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\root\2fc5c153\dc2486a9\App_Code.gpgqvtxd.4.cs" "C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\root\2fc5c153\dc2486a9\App_Code.gpgqvtxd.6.cs" "C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\root\2fc5c153\dc2486a9\App_Code.gpgqvtxd.13.cs" "C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\root\2fc5c153\dc2486a9\App_Code.gpgqvtxd.12.cs" "C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\root\2fc5c153\dc2486a9\App_Code.gpgqvtxd.8.cs" "C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\root\2fc5c153\dc2486a9\App_Code.gpgqvtxd.1.cs" "C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\root\2fc5c153\dc2486a9\App_Code.gpgqvtxd.3.cs" "C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\root\2fc5c153\dc2486a9\App_Code.gpgqvtxd.11.cs" "C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\root\2fc5c153\dc2486a9\App_Code.gpgqvtxd.10.cs" "C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\root\2fc5c153\dc2486a9\App_Code.gpgqvtxd.5.cs" "C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\root\2fc5c153\dc2486a9\App_Code.gpgqvtxd.7.cs" "C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\root\2fc5c153\dc2486a9\App_Code.gpgqvtxd.0.cs" "C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\root\2fc5c153\dc2486a9\App_Code.gpgqvtxd.9.cs" "C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\root\2fc5c153\dc2486a9\App_Code.gpgqvtxd.2.cs"


Microsoft (R) Visual C# 2008 Compiler version 3.5.21022.8
for Microsoft (R) .NET Framework version 3.5
Copyright (C) Microsoft Corporation. All rights reserved.

warning CS1668: Invalid search path 'C:\Program Files\SQLXML 4.0\bin\' specified in 'LIB environment variable' -- 'The system cannot find the path specified. '
c:\SlickTicket\App_Code\utils.cs(187,45): warning CS0028: 'Utils.Menus.Main()' has the wrong signature to be an entry point
c:\SlickTicket\App_Code\utils.cs(108,18): error CS0103: The name 'txtMessage' does not exist in the current context
c:\SlickTicket\App_Code\utils.cs(111,18): error CS0103: The name 'txtMessage' does not exist in the current context
c:\SlickTicket\App_Code\utils.cs(113,21): error CS0103: The name 'txtSubject' does not exist in the current context



So I am trying to work around it by downloading SQLXML but it appears its only packaged and not downloadable as a separate utility. 

Do you have any suggestions for this?

Thanks for all your help!  

Version Information: Microsoft .NET Framework Version:2.0.50727.1433; ASP.NET Version:2.0.50727.1433 

On Thu, Jun 17, 2010 at 1:26 AM, naspinski <notifications@codeplex.com> wrote:

From: naspinski

Both are trivial to implement.  To make email over ssl, just set the smtp.EndableSsl = true and define the username, password and port.

-or just use the gmail approach: http://naspinski.net/post/Sending-email-programmatically-with-gmail--tutorial.aspx

 

Read the full discussion online.

To add a post to this discussion, reply to this email (slickticket@discussions.codeplex.com)

To start a new discussion for this project, email slickticket@discussions.codeplex.com

You are receiving this email because you subscribed to this discussion on CodePlex. You can unsubscribe on CodePlex.com.

Please note: Images and attachments will be removed from emails. Any posts to this discussion will also be available online at CodePlex.com




--
Samuel H. LoSurdo
samuel.h.losurdo@gmail.com
315.415.3877

"When people dream of getting rich, it's about more than nice clothes and fancy vacations. Being rich means freedom: to spend your time as you please, to pursue your real interests and to take chances without courting utter ruin. Paradoxically, the road to riches often means acting as if you already have that freedom."
Coordinator
Jun 22, 2010 at 4:50 AM

The first error is simply because the item 'txtMessage' is not present on the aspx page you are trying to call it from. 

The others I cannot really tell and have never seen these before - but they are not errors that should be caused by trying to implement a new mail procedure.  Sorry I can't help more at the moment, but I am pretty bogged down - hopefully someone else on here can throw out some help.

Jun 22, 2010 at 12:09 PM

Thanks Stan, I am going to try that step first and find which aspx page it is trying to call txtMessage from.