Ayuda de vídeo de Screencast
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Fixed the Send Email Null Host Name issue in the SD.RequestAccessToNetworkShare 7.5

Created: 04 Febrero 2013 • Updated: 26 Agosto 2013
el cuadro de los QuietLeni
0 0 Votos
Login to vote

Dear All,

I had a problem with the SD.ResetPassword workflow, such that when it tried to send emails, it errored out with the following:

Application Name : SD.ResetPassword
Process ID : 4064
Date :28/01/2013 17:37:13
Log Level :Error
Log Category :LogicBase.Components.Default.Logging.CreateLogEntryComponent
Machine Name : <SDServer>
Message :
***** Error Occured - Reset Password *****
Location: Primary Model (Email)
Exception component: Requestor's Email Allowed Reset
Exception message:
Value cannot be null.
Parameter name: host
Exception stacktrace:
System.ArgumentNullException: Value cannot be null.
Parameter name: host
at System.Net.Sockets.Socket.Connect(String host, Int32 port)
at LogicBase.Components.Default.Communication.SmtpClient2.GetClientDomain(String targetAddress)
at LogicBase.Components.Default.Communication.SmtpClient2..ctor(String host, Int32 port)
at LogicBase.Components.Default.Communication.SendEmailComponent.Run(IData data)
at LogicBase.Core.ExecutionEngine.SinglePathProcessComponentExecutionDelegate.Execute(IData data, IOrchestrationComponent comp, String& outputPath, IExecutionEngine engine, TLExecutionContext context)
at LogicBase.Core.ExecutionEngine.AbstractExecutionEngine.RunComponent(TLExecutionContext context, IData data, IOrchestrationComponent comp)

Well, I then looked at the SD.RequestAccessToNetworkShare workflow and found that it made the same mistake.

The problem is that all of the components were configured incorrectly and had the name of the Profile Property as "[[ProfileProperties].service_desk_settings_smtpmail_server]". This should be "[[ProfileProperties].service_desk_settings_smtp_mail_server]" instead:

I have submitted this to Symantec for evaluation and they will publish this as a patch later on, but here is the version that is fixed.

Attached is an exact version with the fixes applied.