I have created a scheduled job to update a node property in Alfresco 6.2 Enterprise instance.
I get following error while trying to update the node property.
03271369 Access Denied. The system is currently in read-only mode.
However, I am able to update node properties from script. This error message is thrown only from scheduled job.
Anybody has an idea about this?
Thank you.
Related
"Address already in use" This is the error which I get while doing dbmigration, I have written the AddService and Addconfiguration properties file now wanted to do dbmigration and getting this error. How to fix this? Thanks in advance
Tried to check and change the orm property file
Please check and make sure you start dbmigrate only when no other Java application server process is running. If you're using windows check the system Services if any Intershop related service is (automatically) started.
I am using BigQueryCheckOperator in Airflow to know if the data exists in BQ Table, but the Dag is failing with this ERROR - <HttpError 404 when requesting https://bigquery.googleapis.com/bigquery/v2/projects/
Here is the logs of the Dag
Can Someone tell me how to fix this issue?
This is known Airflow issue querying Bigquery datasets residing in non multi-regional locations (US,EU) within some of Bigquery operator submodules, the pull request #8273 has been already raised.
You can also check out this Stack thread for most accurate problem explanation.
By now, it was announced to bring this problem fixed in Airflow 2.0 release, however community group has been pushed Backport package in order to help the users with older Airflow 1.10.* versions and it will be considered in further building Airflow images for GCP Composer.
Looking for a workaround, you can try to adjust BashOperator invoking bq command-line tool in attempt to perform the certain action against Bigquery dataset inside the particular DAG file.
When we are trying to run a normal U-SQL job using azure data factory, which was executing perfectly fine earlier, suddenly failing with the below error for every table being referred in the U-SQL job.
E_SMS_USER_TABLEFILESDELETEDDIRECTLY
But, I dont find any other jobs running at the same time. It is development environment and nobody is currently using it.
Please let us know, how we can fix the same.
The error is misleading. The issue was due to lack of permissions.
When I changed the account being used to connect to Azure Data Lake Analytics(ADLA), in the ADLA linked service in Azure data factory, I was able to successfully execute the job without issues.
i am creating a oracle apex 5.1 application but for the last part after i press the create application button an error occured
Unable to create modules.
ORA-20001: Create pages error. ORA-20001: Unable to create report page. ORA-20001: Error page=13 item="P13__NULL_" id="" ORA-20001: Error page=13 item="P13__NULL_" id="" has same name as existing application-level item. ORA-0000: normal, successful completion
what was the error mean? how can i solve this?
note: i'm creating a classic reports with almost same source queries gathered using query builder is this related to the problem?
I run an ASP.Net MVC3 application and have followed this Windows Azure How-To on how to store my sessions in a co-located cache in Windows Azure.
I have installed the mentioned Nuget-package, and applied the necessary information to my web.config. The web role is setup to run 2 small instances, and use a 30% co-located cache.
When I deploy to Azure, my instances just recycle. Through a remote desktop connection to one of the instances, I have found these two events in the logs, that seem related:
The CacheStatusIndicator service terminated unexpectedly. It has done
this 1 time(s). The following corrective action will be taken in 1000
milliseconds: Restart the service.
The CacheService service terminated unexpectedly. It has done this 1
time(s). The following corrective action will be taken in 60000
milliseconds: Restart the service.
However, I cannot find much information on that.
Does anyone have a clue what I might be missing here?
I am very much sure that your role is missing some of the reference and because of that your see such message from CacheStatusIndicator. Have you verified that your role does have all the modules/references set to "copy local as true" so all of them are part of deployment package. Mainly it is a MVC3 app, you may need to manually set app MVC specific references property to copy local as true to resolved this problem.
Now I spent my shared amount of time dealing with this, and finally it seems to be working. Not sure exactly what part solved the problem, but I'll wrap up the changes I made, in case someone else have the same issue at some point.
While debugging this issue, I also updated my application from MVC3 to MVC4. Not sure if that has anything to do with solving this problem, but at least it is one of the changes I made.
I noticed that another exception was thrown by the the IntelliTrace service, so I disabled that in the deployment and re-deployed the application (my guess is that this problem is what actually caused the instances to cycle.
Response from Microsoft Support on this issue:
I was troubleshooting your deployment with the issue and I got a memory dump from the CacheService.exe
This was the exception being thrown
CLR exception type: System.TypeInitializationException
"The type initializer for 'Microsoft.ApplicationServer.Caching.AzureCommon.AzureUtility' threw
an exception." ModLoad: 000007feea010000 000007feea0fa000
D:\Windows\Microsoft.NET\Framework64\v4.0.30319\diasymreader.dll
* ERROR: Symbol file could not be found. Defaulted to export symbols for D:\windows\system32\KERNEL32.dll -
ntdll!ZwWaitForMultipleObjects+0xa: 00000000`76f5739a c3
ret
The exceptions on this namespace can happen if:
You set the Microsoft.WindowsAzure.Plugins.Caching.ConfigStoreConnectionString setting on ServiceConfiguration to use the local storage emulator
On the web.config you have the identifier value of the <dataCacheClients> section not set to the correct role name
In some rare cases if you have the SDK 1.6 and 1.7 installed together this can cause some mixed up DLLs when project is being built.