Cropping in Neos back-end throws this exception (for Neos beta5):
Uncaught exception #1297759968 in line 271 of /usr/local/www/apache24/data/_sprint2/Data/Temporary/Development/Cache/Code/Flow_Object_Classes/TYPO3_Flow_Mvc_Controller_Argument.php: Exception while property mapping for target type "TYPO3\TYPO3CR\Domain\Model\Node", at property path "": Exception while property mapping for target type "TYPO3\Media\Domain\Model\ImageInterface", at property path "": Could not open stream for resource af0c55f536c860b1d44ce0769f4a1ab52d15b6bd ("company_foldout_short.png") from collection "persistent" while trying to create a temporary local copy. - See also: 20150708145304930495.txt
previousException => Uncaught exception #1297759968 in line 260 of /usr/local/www/apache24/data/_sprint2/Data/Temporary/Development/Cache/Code/Flow_Object_Classes/TYPO3_TYPO3CR_TypeConverter_NodeConverter.php: Exception while property mapping for target type "TYPO3\Media\Domain\Model\ImageInterface", at property path "": Could not open stream for resource af0c55f536c860b1d44ce0769f4a1ab52d15b6bd ("company_foldout_short.png") from collection "persistent" while trying to create a temporary local copy.
Any ideas?
For me it look like a missing original resource, can you try to search if the resource exist first:
ls Data/Persistent/Resources/a/f/0/c/af0c55f536c860b1d44ce0769f4a1ab52d15b6bd
Please try ./flow doctrine:migrate and after that flush the cache.
This should help you.
Related
Core: Exception handler (WEB): Uncaught TYPO3 Exception: Cannot use object of type __PHP_Incomplete_Class as array | Error thrown in file typo3/sysext/backend/Classes/Controller/Page/TreeController.php in line 189
This happened after a core update to TYPO3 - 9.5.17
https://forge.typo3.org/issues/91407
The following thanks to Michael Hitzler.
As far as I can see there is already a solution within the install tool in class BackendUserConfigurationUpdate.
This seems to address exactly the issue.
Not quite sure in which version the additional migration task has been added, but it helps you solving the issue system wide.
Just got to module Admin Tools -> Update and select Update Wizard.
There you should see a new, not yet executed migragtion task:
Update backend user configuration array
The backend user "uc" array, which is persisted in the db, now only allows for arrays inside its structure instead of stdClass objects. Update the uc structure for all backend users.
Execute this migration task and your BE users will be updated and have a sane uc configuration in the end.
Problem solved and page tree can be loaeded again.
./typo3cms upgrade:wizard backendUsersConfiguration
Should solve the issue.
The upgrade procedure is pretty simple and well documented. I have been upgrading jasperreports server since version 4 always using the same procedure (buildomatic).
Now, in 7.5 version I get
java.lang.RuntimeException: KeystoreManager was never initialized or
there are errors while instantiating the instance.
Failed to instantiate
[com.jaspersoft.jasperserver.crypto.KeystoreManager]: Please make sure
that create-keystore was executed;
Error creating bean with name 'keystoreManager': Invocation of init
method failed;
Error creating bean with name 'passwordEncoder': Unsatisfied
dependency expressed through field 'keystoreManager';
The keystore is in /root folder, as it should.
Have you tried the process mentioned in this link https://community.jaspersoft.com/wiki/encryption-jasperreports-server-75
"If the JasperReports Server cannot find the keystore files - maybe because of permissions as noted above, you will get an exception on server start like:
Failed to instantiate [com.jaspersoft.jasperserver.crypto.KeystoreManager]: Please make sure that create-keystore was executed; nested exception is java.lang.RuntimeException: KeystoreManager was never initialized or there are errors while instantiating the instance.
To fix this, you need to move the keystore files into a directory that is accessible by the user running the web app process. See Updating keystore files below."
I am working with the Rule Designer for the Business Rules service on Bluemix to create a BOM entry from an XML schema. When I select the XOM entry in the wizard, I see the error:
"Invalid XOM entry, please check your log file"
The Eclipse log file contains the following stacktrace:
!MESSAGE An error occurred while loading the XML schema
C:\mySchema.xsd.
!STACK 0
ERROR ERR011: in source file:C:/mySchema.xsd, after line 18, before
lines ?, The type reference on MyType cannot be resolved.
ERROR ERR011: in source file:C:/mySchema.xsd, after line 21, before
lines ?,
The type reference on MyType cannot be resolved.
at ilog.rules.xml.model.IlrXsdXomConvertorBase.convertSchema(IlrXsdXomConvertorBase.java:111)
at com.ibm.rules.dynamic.xom.SchemaDriver.loadModel(SchemaDriver.java:159)
at com.ibm.rules.dynamic.xom.XsdBuilder.buildXom(XsdBuilder.java:63)
at ilog.rules.studio.model.xom.impl.IlrDynamicXOMPathEntryImpl.getXsdReflect(IlrDynamicXOMPathEntryImpl.java:676)
...
How do I resolve this?
I had multiple xsd:import statements for the same namespace.
I put all the declarations for the namespace in a single file, and then used a single xsd:import for that namespace.
Another way is to add a new schema file that uses several xsd:include statements to include all the schema declarations for the namespace into this new file.
I had the same error message when I used www. at my xsd namespace.
Try changing your namespace "schema targetNamespace= and xmlns:tns= schema" until you can create the BOM succesfully. Verify you have the same value for both.
I am trying to sync SQL express to a central SQL 2008 r2 database. When I delete a row in the central database and try to sync it to the express database with a download-only scope, it throws the below error:
Deleted row information cannot be accessed through the row.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Data.DeletedRowInaccessibleException: Deleted row information cannot be accessed through the row.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[DeletedRowInaccessibleException: Deleted row information cannot be accessed through the row.]
Microsoft.Synchronization.ISyncSession.Start(CONFLICT_RESOLUTION_POLICY resolutionPolicy, _SYNC_SESSION_STATISTICS& pSyncSessionStatistics) +0
As mentioned in the comment I found the problem in the ChangesApplied event handler.
Changed the code to access row values from
table.Rows[i][j]
to
table.Rows[i][j, DataRowVersion.Original]
to fix it.
In order to get flexibility in load balancing and clustering, I thought of deploying my OFBiz application in JBoss-5.1.0 as per document (https://cwiki.apache.org/OFBTECH/deploying-ofbiz-904-on-jboss-510.html).
Build was successful and I could see all WAR files in server/default/deploy/OFBiz.ear and other JAR files in lib folder. But I am getting a few issues when starting JBoss server. Please take a look and help me if you have any clues.
Issues:
Could not find definition for entity name EntityKeyStore
......................
Could not find definition for entity name JobSandbox
...................
Entity definitions for EntityKeyStore is located in entitymodel.xml of framework/entity/entitydef folder. I could not find this xml anywhere inside OFBiz.ear. (Not only this XML, none of the entitymodel.xml s are found in ear. But no issue with other entities. I do not know why it is so). I checked my database (server/default/data/derby) and found out ENTITY_KEY_STORE there.
The same is the case for JobSandBox.
After this exception, the server seems to proceed with creating dispatcher for each component and it started with accounting. I am getting another issue here.
Could not get root location for component with name [common], error was: org.ofbiz.base.component.ComponentException: No component found named : common
.....
....
....
---- exception report ----------------------------------------------------------
Error processing include at [component://common/webcommon/WEB-INF/common-controller.xml]:java.net.MalformedURLException: Could not get root location for component with name [common], error was: org.ofbiz.base.component.ComponentException: No component found named : common
Exception: java.net.MalformedURLException
This exception is repeatedly printed in log file. And down the line, the same kind of exception is thrown for other components like commonext, accounting and ecommerce.
After these exceptions "Could not find definition for entity name Tenant" is also thrown.
My OFBiz application uses a multitenant environment. Any help is greatly appreciated.