I upgraded recently to hybris 2005. And for some reason, the tasks are not being executed, they get stuck at running state. If I access /processing it says:
Welcome to "processing" extension
Task engine status: stopped
I already checked all the properties related to tasks engine, I have the following values:
task.processing.enabled=true
task.engine.loadonstartup=true
On logs I can't see any info related to business process, task engine, etc...
Any tips here?
Related
I have installed Azure Recovery Services (MARS) onto a 2019 server. I can fully configure it using the GUI, but the scheduled backups just don't run.
I can run the back manually and it runs perfectly and completes quickly; however, when I try to use the scheduler, it doesn't run.
I have checked the Task Scheduler and the job keeps switching to disabled with the notification:
User "System" disabled Task Scheduler task "\Microsoft\OnlineBackup\Microsoft-OnlineBackup"
When I installed the application, I changed the default path to C:\Domain Services to keep them separate, is this where it went wrong?
I have other servers on the backup platform which are not having any issues at all, I have also tried the steps in:
https://learn.microsoft.com/en-us/azure/backup/backup-azure-mars-troubleshoot#backups-dont-run-according-to-schedule
And also
https://dirteam.com/bas/2019/01/09/the-mysterious-case-of-azure-backup-agent-not-running-its-schedule/
But it is not fixing the issue.
I am completely out of ideas, hoping that somebody can help me!
Change the settings in the task scheduler for Online Backups. See the snippet below.
I have no idea how, but the system is now working correctly and not being disabled. I tried to remove all the MARS software on the machine and re-installed it and it now works correctly and has been backing up for a few weeks now.
Thank you for all your assistance.
I have been using Openshift 3 seamlessly to build and deploy a Node.js application for several months.
Since yesterday, new builds of the same app systematically fail because they are stuck forever in the Pending state, with the "Started status: not started" until after an hour when the build fails with "No logs available".
Has anyone else had this issue?
I am using starter-us-east-1 (no mention of it in status.starter.openshift.com).
My app runs fine locally and I don't understand what's the issue with Openshift.
Deployment of existing builds seems to work, but there's no way to make new builds, either manually or via webhooks.
I didn't change anything in the configuration, just my code.
Thank you by advance for any hint.
Additional info: The issue doesn't occur in starter-ca-central-1 where I can see a whole new interface with notifications, and the build of the app I have there works fine.
More info: The new interface has been rolled out to starter-us-east-1, but the problem is still more present than ever. Here is a screenshot of my Pods/Events tab:
I receive the following error while publishing and Azure Website from Visual Studio 2013:
12>Publish Succeeded. 12>Creating the scheduler job
12>C:\projectPath\packages\Microsoft.Web.WebJobs.Publish.1.0.7\tools\webjobs.console.targets(110,5):
Error : An error occurred while creating the WebJob schedule: Response
status code does not indicate success: 400 (Bad Request).
I have read another posts with similar issues: 404 error, BadRequest: The condition specified by the ETag is not satisfied... but none of these seem to be the problem here. I have reinstalled the Microsoft Azure Tools for VS 2013, the webjobs.publish package in my solution and it didn't work either. I also checked this post https://social.msdn.microsoft.com/forums/azure/en-US/d5b44e53-c4d7-48ff-a024-4bdd6eb48b79/sheduled-web-jobs-in-azure-web-site-not-configurable-in-same-region-as-web-siteand-workaround?forum=azurescheduler#d5b44e53-c4d7-48ff-a024-4bdd6eb48b79 and did what he tried but it haven't solved the issue.
It looks like all my files are uploaded correctly to the Azure website, and the issue begins when the scheduler jobs are being created.
The strange thing is that the webjobs are uploaded (updated) and that they are also working correctly, but the scheduled webjobs are not in my jobcollection list in the Azure management portal. I also tried to remove my current job collection and all the jobs from my website, but when I publish the site, all the webjobs are created but the job collection is empty.
I had a similar issue with VS and the problemas was that the credentials of the website were expired, but the problem was solved by reentering the credentials in VS. Any idea of how to solve this issue?
Please see my answer to Visual Studio 2015 Publish WebJobs Issue, which shows an alternate way to do scheduling that makes things far simpler and avoids this type of conditions.
To summarize, you can create a settings.job file at the root of your WebJob file, containing a CRON expression. e.g.
{
"schedule": "0 0 * * * *"
}
For more information, about this technique, see the following documentation links:
https://azure.microsoft.com/en-us/documentation/articles/web-sites-create-web-jobs/#CreateScheduledCRON
http://blog.amitapple.com/post/2015/06/scheduling-azure-webjobs/
I faced the same issue today and the solution for me was simpler. What happened is that the startTime I had configured on my webjob-publish-settings.json was for some days ago (while I was developing). I changed the startTime for tomorrow and it worked. Looks like the scheduler is not able to get started when the startTime is not in the future. Hope it helps.
As I have noted in my question, I deleted my webcolletion to solve the issue, but I did not notice that the new collection was created in free mode (I do not know why because my site is in standard mode). So setting the jobcollection to standard mode partially solved the problem. Then I got the following error:
An error occurred while creating the WebJob schedule: Response status
code does not indicate success: 409 (Conflict).
I went to the azure portal, and I saw that all jobs but one were created correctly (as scheduled jobs). I reset the webjob-publish-settings.json file of the webjob, I published it and the problem was solved.
I have developed a custom timer job for SharePoint 2013 in visual studio 2012 which sends email notifications. The issue is that it works fine on development server.
I have followed the following steps to debug it on the development server 1.) Deploy the timer job on respective site. 2.) Restart the timer service in services.msc 3.) Then is do attach to process OWSTIMER in visual studio. 4.) And finally Go to SharePoint 2013 Central administration->Monitoring->Review Job Definition and click on the respective timer job and say run now.
After doing this the breakpoint is hit in visual studio at the Execute() method. So in the development server it is running.
Now on the production server I cannot debug using visual studio so I have deployed the packaged solution(.wsp).
I can see the feature is activated in Site Collection Administration-> Site Collection Features.
Now on the production server I follow the following steps 1.)Restart the timer service in services.msc 2.)And finally Go to SharePoint 2013 Central administration->Monitoring->Review Job
Further to test whether the timer job is working on production server or not I had used PortalLog.LogString("Flow test1"); at the start of the Execute() method. Now this runs on the development server and I see the message in the SharePoint logs but on the production server I can't see "Flow Test1" in the logs after I click Run Now in central admin.
Can anyone suggest what is the issue and a possible solution?
It seems to me that there are two issues:
You should use other way for logging LoggingService should be preferred way. Use WriteEvent to write to EventLog or WriteTrace to write to ULS log.
Running job. Be sure that Owstimer.exe service on all web servers are restarted (can be done by this powershell script). I expect that you have correctly scheduled your job either in your powershell script or in your feature receiver.
Here are a few things to try:
Go to Central Administration and run the timer job from there. Then go to the job history page and check whether it finished successfully or not. If there was an error, you should see the error message from there. That will give you a clue on whats happening.
As Mazin said, restart the timer service in all servers. After deployment, the DLLs are cached by the process and you don't see your changes reflected.
Browse the SharePoint logs and search for an exception or error. You can narrow your search by selecting the timeframe on which your job ran. You can use the following PS script:
Get-SPLogEvent -StartTime "02/02/2014 11:00" -EndTime "02/02/2014 13:00" | Out-GridView
As stated here it seems your job assembly is not deployed in the GAC. Verify that the assembly is present there.
I have been trying to create a worker role using powershell, Azure Emulator and the azure node.js sdk however I have been running into problems when I try to start adding modules to by worker process.
These are the steps I have taken:
1) Run Powershell
2) Create a new azure node.js project
new-azureserviceproject
3) Add a webrole
add-azurenodewebrole
4) Add a worker role
add-azurenodeworkerrole
If I run the project at this stage
start-azureemulator -launch
The site runs fine and without any IIS errors. But when I start installing new modules into the worker role and try running it again I get windows IIS errors such as "Windows Azure Web Role Entry Point Has Stopped Working" without any more information as to why it stopped. Is anybody else encountered these errors and more importantly does anybody have any examples on how to create a worker role to run a cron job and talk to my windows azure table storage? All I want to do is run a cron job every 5 seconds to check table storage for any new updates and do something.
Any ideas?
Details of the error:
Problem Event Name: APPCRASH
Application Name: iisexpress.exe
Application Version: 8.0.8298.0
Application Timestamp: 4f620349
Fault Module Name: iiscore.dll
Fault Module Version: 8.0.8298.0
Fault Module Timestamp: 4f63b65c
Exception Code: c0000005
Exception Offset: 00021767
OS Version: 6.1.7601.2.1.0.256.28
Locale ID: 1033
Additional Information 1: f66d
Additional Information 2: f66d807b515d6b2dc6f28f66db769a01
Additional Information 3: 7b2f
Additional Information 4: 7b2f6797d07ebc2c23f2b227e779722e
Update, if I lower the instance count to 1 for both webrole and worker role then it doesn't crash, perhaps it's a problem with the azure emulator ?
There are several questions here, so let's start with the first. A decent sample for using a worker role that adds modules (socket.io) can be found here:
https://www.windowsazure.com/en-us/develop/nodejs/tutorials/app-using-socketio/
Next up is of course the conversation about modules on Windows. Some modules with binary dependencies don't run on Windows. That has gotten to be a pretty small number, but it is still a possibility. You should see if you can run your worker role code outside of the emulator to validate this.
Next up we should consider this process. You would typically push changes that require action into a Storage Queue from your web role and pull from the at queue in your worker role. If you have a "cron module" then pull the top item from the queue when the timer event is fired. You can always do sleeps here, but that kind of blocking is frowned on in the node world.
This may not be related but I thought I should mention it. I ran into issues because the default version of NodeJS seemed to be too old to work with the modules I was using. You may need to change the version of NodeJS. To see the list of available versions:
Get-AzureServiceProjectRoleRuntime
Then, apply a specific version (example):
Set-AzureServiceProjectRole [Role_Name] Node 0.10.21