I've been trying fix this issue, on a new installation of SharePoint 2013 on a standalone server, for a couple of days now. I'm getting the "Internal status:Suspended" error on all the workflows I run:
RequestorId: 8e9ad795-7a8f-9a68-0000-000000000000. Details: An unhandled
exception occurred during the execution of the workflow instance.
Exception details: System.ArgumentException: AssignedTo at Microsoft.Activities.Hosting.Runtime.Subroutine.SubroutineChild.Execute(CodeActivityContext context) at
System.Activities.CodeActivity.InternalExecute(ActivityInstance instance,
ActivityExecutor executor, BookmarkManager bookmarkManager) at
System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation)
I have found several articles that don't quite seem to solve the problem:
https://technet.microsoft.com/en-us/library/cc263462.aspx#section2
http://sp2013.pro/category/error/wf-cancelssuspends/
The problem exists when I create both SP 2013 workflows and SP 2010 workflows. The OOTB Approval workflow does send emails correctly though, so I know that the mail server is working. I've tried an approval process from within the a custom workflow and that fails... So the problem, I'd assume, lies somewhere within the SharePoint Designer Workflow creation and the server.
The workflows will run up until the point of an email as I've have tested several variable changes and logged the progress to history.
Other things that I have done:
-Full profile synchronization
-SMTP server set up to allow anonymous and relay using only itself
UPDATE: I've just discovered that the workflow seems to have to crash in custom columns within calendar events and also when you manually add a user to the workflow, conversely... a standard custom list will send an email to a manually inputted address and gives the following error before failing when using a custom people/group field:
Retrying last request. Next attempt scheduled in less than one minute.
Details of last request: HTTP BadRequest to
http://domain/_vti_bin/client.svc/sp.utilities.utility.SendEmail
And then suspends itself with a similar message to original issue:
Details: An unhandled exception occurred during the execution of the
workflow instance. Exception details: System.ArgumentNullException: Value
cannot be null. Parameter name: Input at Microsoft.Activities.Hosting.Runtime.Subroutine.SubroutineChild.Execute(CodeActivityContext context) at System.Activities.CodeActivity.InternalExecute(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager) at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation)
Related
Im new to chef and trying to understand why this code does not return any error while if i do the same with 'start' i will get an error for such service does not exist.
service 'non-existing-service' do
action :stop
end
# chef-apply test.rb
Recipe: (chef-apply cookbook)::(chef-apply recipe)
* service[non-existing-service] action stop (up to date)
Don't know which plattform you are running on if you are running on Windows it should at least log
Chef::Log.debug "#{#new_resource} does not exist - nothing to do"
given that you have debug as log level.
You could argue this is the wrong behaviour, but if the service dose not exist it for sure isen't running.
Source code
https://github.com/chef/chef/blob/master/lib/chef/provider/service/windows.rb#L147
If you are getting one of the variants of the init.d provider, they default to getting the current status of a service by grepping the process table. Because Chef does its own idempotence checks internally before calling the provider's stop method, it would see there is no such process in the table and assume it was already stopped.
I have a TFS Build definition using the default template. The build completes on it's own but when I include a post deployment script I get the following error.
Exception Message: The directory name is invalid (type Win32Exception)
Exception Stack Trace:
Server stack trace:
at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
at Microsoft.TeamFoundation.Build.Workflow.Activities.InvokeProcess.ProcessWrapper. Start()
at Microsoft.TeamFoundation.Build.Workflow.Activities.InvokeProcess.InvokeProcessIn ternal.RunCommand(AsyncState state)
at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs)
at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)
Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.EndInvokeHelper(Message reqMsg, Boolean bProxyCase)
at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(Object NotUsed, MessageData& msgData)
at System.Func`2.EndInvoke(IAsyncResult result)
at System.Activities.AsyncCodeActivity`1.System.Activities.IAsyncCodeActivity.FinishExecution(AsyncCodeActivityContext context, IAsyncResult result)
at System.Activities.AsyncCodeActivity.CompleteAsyncCodeActivityData.CompleteAsyncC odeActivityWorkItem.Execute(ActivityExecutor executor, BookmarkManager bookmarkManager)
The script itself is a powershell script that is included in the solution I'm trying to build and it only calls write-host messages. (for testing at this point)
The build definition has all the defaults selected with only the solution, post build arguments and post build script path changed. The script is checked into source control in the solution.
This is a POC environment so I have everything installed on the one server, so the TFS Server and Build Agents are on the same machine.
I've tried several workaround for this but none of them seem to be rooted around this particular error. Any help is much appreciated, thanks.
(Coming from someone who recently encountered this issue themselves)
Check your "Source Settings" in the build definition.
Make sure you haven't cloaked the path to your script. That is, if you have your script in utilities/configuration, make sure you haven't cloaked utilities/
Your Build Agent folder should not use $(BuildDir), it should use $(SourceDir). Bear in mind this might change some paths in your script.
There is apparently a bug in the latest version of TFS that causes this hair-pulling issue. All the stuff about setting %WINDIR% in your Start-in directory for Powershell/Cmd etc. didn't work, but this did.
Two part question:
I need to setup test case where one bean/fact has collection of items - is it possible to do with workbench editor, I picked Guided list and for each item I was trying to do new Item('sku', 'name') .. but when it tries to compiled it it has can not find Item class. Item class is imported.
After deploying artifact to execution server and testing rules with SOAP UI where I did not specify session in the tag - it seems like by default execution server uses statefull session which affect subsequent rule executions.
I went to project properties created "stateless" session
ksession, default=yes, state=stateless, clock=realtime
Now however if I try to execute by test cases in the workbench I get:
Unable to complete your request. The following exception occurred: Cannot find a default KieSession.
Any ideas???
The problem I'm having is with this code:
if (!MessageQueue.Exists(QueueName))
{
MessageQueue.Create(QueueName, true);
}
It will check if a queue exists; if it doesn't I want it to create the queue. This code has been working and hasn't changed for a few months. Today I started receiving this error:
[MessageQueueException (0x80004005): A queue with the same path name
already exists.] System.Messaging.MessageQueue.Create(String path,
Boolean transactional) +239478
The queues are local and if I delete the specific queue it will work once. After the queue is created it starts to fail again with the same error message.
It looks like the issue may be because of the Network Load Balancing (NLB) configuration. I was unaware of a change that recently put the machine in a NLB environment. The configuration we are using is an unsupported one.
More information is in How Message Queuing can function over Network Load Balancing (NLB).
I am trying to set up Report Server 2008 on a separate machine to the Reporting Services databases which are on a SQL Server 2008 R2 machine.
I configure everything in the Reporting Services Configuration Manager (identical to a set up we have working on a different pair of servers). The database connection test works fine, and the final "Progress and Finish" and screen shows "Success". However when I browse to the report server I get the error:
"The report server installation is not initialized. (rsReportServerNotActivated)"
I have seen a number of solutions online for this but they suggest using the Initialization tab on the Reporting Services Configuration Manager to initialize it. Or alternatively to use the rsactivate command. Now in 2008 I can't seem to find either of these so I'm a bit stuck.
When I use the Reporting Services Configuration Manager I get the following errors in the Event Viewer:
The application domain
WindowsService_1 failed to initialize.
Error:
Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerNotActivatedException:
The report server installation is not
initialized. at
Microsoft.ReportingServices.Library.ConnectionManager.b_2()
at
Microsoft.ReportingServices.Diagnostics.RevertImpersonationContext.<>c_DisplayClass1.b__0(Object
state) at
System.Security.SecurityContext.Run(SecurityContext
securityContext, ContextCallback
callback, Object state) at
Microsoft.ReportingServices.Diagnostics.RevertImpersonationContext.Run(ContextBody
callback) at
Microsoft.ReportingServices.Library.ConnectionManager.GetEncryptionKey()
at
Microsoft.ReportingServices.Library.ConnectionManager.ConnectStorage()
at
Microsoft.ReportingServices.Library.ServiceController.ServiceStartThread(Object
firstStart).
followed by:
The application domain
WindowsService_1 failed to initialize.
Error:
Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerNotActivatedException:
The report server installation is not
initialized. at
Microsoft.ReportingServices.Library.ConnectionManager.b_2()
at
Microsoft.ReportingServices.Diagnostics.RevertImpersonationContext.<>c_DisplayClass1.b__0(Object
state) at
System.Security.SecurityContext.Run(SecurityContext
securityContext, ContextCallback
callback, Object state) at
Microsoft.ReportingServices.Diagnostics.RevertImpersonationContext.Run(ContextBody
callback) at
Microsoft.ReportingServices.Library.ConnectionManager.GetEncryptionKey()
at
Microsoft.ReportingServices.Library.ConnectionManager.ConnectStorage()
at
Microsoft.ReportingServices.Library.ServiceController.ServiceStartThread(Object
firstStart).
Is there another way I can initialize the report server installation?
I finally managed to get this working by going to the Reporting Services Configuration Manager > Encryption Keys > Delete Encrypted Content > Delete.
Not sure why this worked, but it did.
Just for completeness I have noticed that I still the get the following error in the Application Log, which luckily doesn't seem to cause any obvious problems for me, but remains nonetheless.
Failed to unload app domain DefaultDomain. The following exception occurred: Error while unloading appdomain. (Exception from HRESULT: 0x80131015).
If I find anything else I'll post back.