Error while updating the project from Nuxeo Studio - nuxeo

I am getting following error whenver I try to update my studio project from Nuxeo Platform. Earlier I was getting a transaction timeout error and I increased the nuxeo.db.transactiontimeout to 900. But now I see this error as below.
Also, when I stop and start the nuxeo server, in the summary tab I see that one the application fails to start. There is also an error An error was detected during startup = Component Loading Status: Pending: 0 / Missing: 0 / Unstarted: 1 / Total : 770

Related

Hybris server startup issue on M1 Mac

Getting intermittent issue for server startup of hybris(1905 version).
--> Wrapper Started as Console
wrapper-macosx-universal-64(12108,0x2001ce600) malloc: Heap corruption detected, free list is damaged at 0x600002104910
*** Incorrect guard value: 105553116300640
wrapper-macosx-universal-64(12108,0x2001ce600) malloc: *** set a breakpoint in malloc_error_break to debug
after getting issue as workaround ,doing ant clean all and some time it work some time it's not working any solution.

The "InvokePowerShell" task failed unexpectedly when publishing from Visual Studio to Azure

Recently I copied my project (ASP.NET Core on Visual Studio 2015) to a new computer. Everything is set up except that I can't seem to publish to the existing App Service without getting an "InvokePowerShell" error.
I have tried creating a new publish profile, resetting the publish profile for the App Service on Azure, running Visual Studio as administrator but no good. Anyone kindly have an idea how to solve this?
Published 1/1 projects successfully
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\DotNet\Microsoft.DotNet.Publishing.targets(408,5): Error MSB4018: The "InvokePowerShell" task failed unexpectedly.
System.Management.Automation.PSSecurityException: AuthorizationManager check failed. ---> System.Management.Automation.Host.HostException: A command that prompts the user failed because the host program or the command type does not support user interaction. The host was attempting to request confirmation with the following message: Run only scripts that you trust. While scripts from the internet can be useful, this script can potentially harm your computer. If you trust this script, use the Unblock-File cmdlet to allow the script to run without this warning message. Do you want to run C:\Users\rober\OneDrive\Documents\Visual Studio 2015\Projects\willfon\src\willfon\Properties\PublishProfiles\willfon20180423121452 - Web Deploy-publish.ps1?
at System.Management.Automation.Internal.Host.InternalHostUserInterface.ThrowPromptNotInteractive(String promptMessage)
at System.Management.Automation.Internal.Host.InternalHostUserInterface.PromptForChoice(String caption, String message, Collection`1 choices, Int32 defaultChoice)
at Microsoft.PowerShell.PSAuthorizationManager.RemoteFilePrompt(String path, PSHost host)
at Microsoft.PowerShell.PSAuthorizationManager.CheckPolicy(ExternalScriptInfo script, PSHost host, Exception& reason)
at Microsoft.PowerShell.PSAuthorizationManager.ShouldRun(CommandInfo commandInfo, CommandOrigin origin, PSHost host, Exception& reason)
at System.Management.Automation.AuthorizationManager.ShouldRunInternal(CommandInfo commandInfo, CommandOrigin origin, PSHost host)
--- End of inner exception stack trace ---
at System.Management.Automation.Runspaces.AsyncResult.EndInvoke()
at System.Management.Automation.PowerShell.EndInvoke(IAsyncResult asyncResult)
at Microsoft.Web.Publishing.Tasks.InvokePowerShell.Execute()
at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
at Microsoft.Build.BackEnd.TaskBuilder.<ExecuteInstantiatedTask>d__26.MoveNext()
1>Publish failed due to build errors. Check the error list for more details.
========== Build: 0 succeeded, 0 failed, 1 up-to-date, 0 skipped ==========
========== Publish: 0 succeeded, 1 failed, 0 skipped ==========
2-27-2020 And now today it's working. Who knows why.

Failed to upload report - HTTP code 413: The page was not displayed because the request entity is too large

I'm setting up a fresh installation of SonarQube Version 7.9.1 (build 27448)
It's running behind a reverse-proxy in IIS using URL Rewrite.
I can login just fine into SonarQube.
It is failing when running analysis for my .Net solution (a big one) using sonar-scanner-msbuild-4.7.1.2311-net46. It failes at the end, after compilation and analysis happened.
INFO: Analysis report generated in 33994ms, dir size=196 MB
INFO: Analysis report compressed in 191901ms, zip size=71 MB
INFO: ------------------------------------------------------------------------
INFO: EXECUTION FAILURE
INFO: ------------------------------------------------------------------------
INFO: Total time: 1:46:46.636s
INFO: Final Memory: 20M/746M
ERROR: Error during SonarQube Scanner execution
INFO: ------------------------------------------------------------------------
ERROR: Failed to upload report - HTTP code 413: The page was not displayed because the request entity is too large.
ERROR:
The SonarQube Scanner did not complete successfully
00:52:36.207 Post-processing failed. Exit code: 1
Googling HTTP 413 found some solutions to enable <serverRuntime> and set uploadReadAheadSize to it's max (see below).
This did not fix my problem.
I Figured it out.
It was the request filtering feature. I had to up the Maximum allowed content length (Bytes)
See Large File Upload in IIS

Error - Unknown packaging eclipse plugin

I am following the ICCAD_L02_Getting_Started_Connections_Cloud.pdf document available on IBM Greenhouse. I have completed all steps succcessfuly till Step 84.
Once I execute step 85 and complete it I get an error.
Request help in resolving the same

issue with running java me source code on emulator

I just finished installing all the necessary tools for Java ME and I am getting the following error:
Installing suite from: http://127.0.0.1:58255/Homework1.jad
*** Error ***
A problem occured during deploying application from http://127.0.0.1:58255/Homework1.jad
Reason:
Either the configuration or profile is not supported.
It can be either the configuration or profile.
Compare the Microedition Configuration (CLDC) and Microedition Profile at Application Descriptor against your Device Configurations in Project->Properties->Java ME->Edit
They should be the same.

Resources