SharePoint Designer Workflow - Email problem

I've created a workflow in SharePoint Designer, and the workflow works fine except for the "send email" part.

I know the MOSS can send emails as it does for the out-of-the-box workflows and alerts. But even though the workflow says it was completed successfully, no emails are sent.

I even tried sending to DOMAIN\user and user@domain.com

But nothing works, no error no email no nothing.

Does anyone know anything about this ! (I don't want to go into VS just for this simple workflow)

Thanks.

Yes, as the MOSS server can send emails (alerts and out-of-the-box workflows).

There shouldn't be any problem, but it just won't send anything.

Any ideas

When you say "no error" have you checked the ULS logs (C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\LOGS).

Something could be logged there.

-Dave

It's not in the SPAM folder.

and as I already said, I tried sending to Domain\username and to username@domain.com

moreover, the User account (using people and groups) is configured with the email.

This really should work, I suppose there's something wrong with the MOSS, but I don't know what. I don't think it's anything related to the WorkFlow itself.

In addition to checking the ULS logs (see my previous post), check the Event Viewer. Without any information as to what is happening, this is going to be hard to troubleshoot.

I don't know any details as to the workflow you are attempting to send. As a simple test, can you create a painfully simple workflow in SPD that does nothing but send an email. I know you said that MOSS can send the email, but let's just try to see if it is a problem with SPD workflows.

Another thing to try for testing is to create a similarly simple workflow in Visual Studio. Under the covers, the same code is executed (the SPD Action is just a thin configuration wrapper around the VS Activity), so this will just help narrow down where the problem may or not be.

Just thinking out loud here. Any additional info you can post will help.

Thanks,

Dave

I am having the same problem with a custom workflow. Apparently it expects a user object, not simply a user name or email address. If I choose to send it to the creator, or tell it to use a people field it works fine. This is an important feature, as I need to be able to send emails to people that may not have an individual user name, since we are limited by the number of users allowed in the current hosting scheme unless we pay an addition $50/mo for all the email addresses we would need.

In the log files I am getting an error like so:

03/28/2007 18:00:59.36 w3wp.exe (0x2490) 0x1900 Windows SharePoint Services General 0 Unexpected ERROR: request not found in the TrackedRequests. We might be creating and closing webs on different threads. ThreadId = 8, Free call stack = at Microsoft.SharePoint.SPRequestManager.Release(SPRequest request) at Microsoft.SharePoint.SPWeb.Invalidate() at Microsoft.SharePoint.SPWeb.Close() at Microsoft.SharePoint.SPSite.Close() at Microsoft.SharePoint.SPSite.Dispose() at Microsoft.SharePoint.Workflow.SPWorkflowAutostartEventReceiver.AutoStartWorkflow(SPItemEventProperties properties, Boolean bCreate, Boolean bChange, AssocType atyp) at Microsoft.SharePoint.Workflow.SPWorkflowAutostartEventReceiver.AutoStartWorkflow(SPItemEventProperties properties, Boolean bCreate, Boolean bChange) at Microsoft.SharePoint.Workflow.SPWorkflowAutostartEventReceiver.ItemAdded(SPItemEventProperties properties) at Microsoft.SharePoint.SPEventManager.RunItemEventReceiver(SPItemEventReceiver receiver, SPItemEventProperties properties, SPEventContext context, String receiverData) at Microsoft.SharePoint.SPEventManager.RunItemEventReceiverHelper(Object receiver, Object properties, SPEventContext context, String receiverData) at Microsoft.SharePoint.SPEventManager.<>c__DisplayClass8`1.<InvokeEventReceivers>b__0() at Microsoft.SharePoint.SPSecurity.CodeToRunElevatedWrapper(Object state) at Microsoft.SharePoint.SPSecurity.RunAsUser(SPUserToken userToken, Boolean bResetContext, WaitCallback code, Object param) at Microsoft.SharePoint.SPSecurity.RunAsUser(SPUserToken userToken, CodeToRunElevated code) at Microsoft.SharePoint.SPEventManager.InvokeEventReceivers[ReceiverType](SPUserToken userToken, RunEventReceiver runEventReceiver, Object receivers, Object properties, Boolean checkCancel) at Microsoft.SharePoint.SPEventManager.InvokeEventReceivers[ReceiverType](Byte[] userTokenBytes, RunEventReceiver runEventReceiver, Object receivers, Object properties, Boolean checkCancel) at Microsoft.SharePoint.SPEventManager.HandleEventCallback[ReceiverType,PropertiesType](Object callbackData) at Microsoft.SharePoint.Utilities.SPThreadPool.WaitCallbackWrapper(Object state) at System.Threading._ThreadPoolWaitCallback.WaitCallback_Context(Object state) at System.Threading.ExecutionContext.runTryCode(Object userData) at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state) , Allocation call stack (if present) null

I am not setting it in the code directly, but simply using the SPD with the action to send email, and using a lookup to pull in the email address into the To field. I logged the output of the lookup, and it correctly shows the email address in the workflow history. Do I need to create a custom action for this to work If that is the case I am out of luck, as I need to host this on an external server that does not allow any customization like that, although there are other cases on our intranet server that a custom email action could be used.

Hi,

We have developed a workflow using SPD. It is working fine if we run on the same site. But, if we save this site as template and create a another site based on this template, it doesn't work. When I view the document library in the newly created sites, I see the workflow embedded in it. But, it doesn't work and display Failed on start (Retrying).

I'm getting the following entry in the log file and did not get any entry in Event viewer.

Any help is highly appreciated.

05/16/2007 11:36:20.20 w3wp.exe (0x1B00) 0x0A14 Windows SharePoint Services General 0 Unexpected ERROR: request not found in the TrackedRequests. We might be creating and closing webs on different threads. ThreadId = 6, Free call stack = at Microsoft.SharePoint.SPRequestManager.Release(SPRequest request) at Microsoft.SharePoint.SPSite.Close() at Microsoft.SharePoint.SPSite.Dispose() at Microsoft.SharePoint.Workflow.SPWorkflowAutostartEventReceiver.DelayedStartWorkflow(SPItemEventProperties properties) at Microsoft.SharePoint.Workflow.SPWorkflowAutostartEventReceiver.ItemCheckedIn(SPItemEventProperties properties) at Microsoft.SharePoint.SPEventManager.RunItemEventReceiver(SPItemEventReceiver receiver, SPItemEventProperties properties, SPEventContext context, String receiverData) at Microsoft.SharePoint.SPEventManager.RunItemEventReceiverHelper(Object receive...
05/16/2007 11:36:20.20* w3wp.exe (0x1B00) 0x0A14 Windows SharePoint Services General 0 Unexpected ...r, Object properties, SPEventContext context, String receiverData) at Microsoft.SharePoint.SPEventManager.<>c__DisplayClass8`1.<InvokeEventReceivers>b__0() at Microsoft.SharePoint.SPSecurity.CodeToRunElevatedWrapper(Object state) at Microsoft.SharePoint.SPSecurity.RunAsUser(SPUserToken userToken, Boolean bResetContext, WaitCallback code, Object param) at Microsoft.SharePoint.SPSecurity.RunAsUser(SPUserToken userToken, CodeToRunElevated code) at Microsoft.SharePoint.SPEventManager.InvokeEventReceivers[ReceiverType](SPUserToken userToken, RunEventReceiver runEventReceiver, Object receivers, Object properties, Boolean checkCancel) at Microsoft.SharePoint.SPEventManager.InvokeEventReceivers[ReceiverType](Byte[] userTokenBytes, RunEventReceiver runEventReceiver, Object r...
05/16/2007 11:36:20.20* w3wp.exe (0x1B00) 0x0A14 Windows SharePoint Services General 0 Unexpected ...eceivers, Object properties, Boolean checkCancel) at Microsoft.SharePoint.SPEventManager.HandleEventCallback[ReceiverType,PropertiesType](Object callbackData) at Microsoft.SharePoint.Utilities.SPThreadPool.WaitCallbackWrapper(Object state) at System.Threading._ThreadPoolWaitCallback.WaitCallback_Context(Object state) at System.Threading.ExecutionContext.runTryCode(Object userData) at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at Sy...
05/16/2007 11:36:20.20* w3wp.exe (0x1B00) 0x0A14 Windows SharePoint Services General 0 Unexpected ...stem.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state) , Allocation call stack (if present) null

We have developed a workflow using SPD. It is working fine if we run on the same site. But, if we save this site as template and create a another site based on this template, it doesn't work. When I view the document library in the newly created sites, I see the workflow embedded in it. But, it doesn't work and display Failed on start (Retrying).

Workflows built with SPD do not work when ported to another site. Even within the same collection. They are meant to work in one site and one site only.

When SPD references a particular object in Sharepoint, it does so internally by GIUD. Externally, in the Designer window, you see the name of the object. But internally, it only know the GUID reference.

A workflow step attempting to get some info from MyCustomList is actually getting it from GUID 123456789. At the new site, MyCustomList may have been given a GUID of 654987321. The workflow does not know where to find it, so it fails.

Workarounds Open SPD and attach to the new site. If you can see the new workflow at the new site, you have to go to each and every step and re-reference the particular object it needs at that point. The basic structure of the workflow will still be there, but no specifics. You must do this by hand.

Long term fix. Delve into the morass of building workflows with Visual Studio.

Hope this helps