Content Delivery - Un-publish Error - tridion

We have found a pretty strange issue in SDL Tridion 2011 Sp1 Hr 1 Content Delivery in that when we un-publish content the publishing will fail.
The fail is really weird. We have created two structure groups:
100 Example
400 Other
Each contains the same page types. Pages contain standard metadata (text fields etc)
If I un-publish 100 Example on the SG all files are removed
If I un-publish 400 Other on the SG the publish task fails (CD log snippet below)
If I go into the 400 Other SG and select all files to un-publish, this is fine
The SG items contain no SG, or weird chars in the 'directory' name.
I see there is a hotfix - 'CD_2011.1.0.79212 - Cumulative hotfix' which is referenced in this SDL Tridion forum post (https://forum.sdltridion.com/topic.asp?TOPIC_ID=7554) - but the version number strikes me as SDL Tridion 2011 Sp 1.
I've installed hotfix CD_2011.1.1.83475 (a Cumulative Hotfix), but this doens't resolve the issue.
I didn't raise this with SDL support yet as I wanted to put this info out to the community first.
My error message is:
Unable to store item inside current transaction, Unable to remove data
entity, Unknown entity: com.tridion.storage.ItemMeta_$$_javassist_26,
Unknown entity: com.tridion.storage.ItemMeta_$$_javassist_26, Unable
to remove data entity, Unknown entity:
com.tridion.storage.ItemMeta_$$_javassist_26, Unknown entity:
com.tridion.storage.ItemMeta_$$_javassist_26 for transaction:
tcm:0-24997-66560 2013-02-05 15:10:18,660 ERROR DeployPipelineExecutor
- Final attempt in Phase: Deployment Prepare Commit Phase failed for transaction: tcm:0-24997-66560 2013-02-05 15:10:18,661 ERROR

Related

UWP app update submission failed with error code 1201

I have a UWP Xamarin Forms app that is in the Microsoft Store. I've updated this app in the partner center several times without trouble. My last update was 1/31/2020.
Yesterday I submitted another update but it failed with the following message:
This submission failed with error code(s) 1201
In searching I've come across threads like this This submission failed with error code(s) 2003,1201 which point to problems with Microsoft.NETCore.UniversalWindowsPlatform, but I've not changed that in this submission. Here's a listing of the nuget packages that I changed with this new submission:
Microsoft AppCenter 2.1.1 to 2.6.4
Xamarin.Forms 4.2.0.848062 to 4.4.0.991640
I've also added Xamarin.Essentials 1.3.1
How can I go about troubleshooting this to figure out what the problem is?
Update:
I've determined it is not AppCenter nor Xamarin.Essentials.
Updating from Xamarin.Forms 4.2.0.848062 to 4.3.x OR 4.4.x causes the problem.
In addition, I noticed something I didn't see before: There is a 'silent' error when packaging for the store with Xamarin.Forms 4.3/4.4. This error is NOT present with Xamarin.Forms 4.2.x. The error is:
C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\Microsoft\VisualStudio\v15.0\AppxPackage\Microsoft.AppXPackage.Targets(3385,5): error MSB6006: "mspdbcmf.exe" exited with code 1106.
It seems likely that the above error is related to the submission error.
Update 2:
I found the following post on the mspdbcmf error:
https://developercommunity.visualstudio.com/content/problem/855376/mspdbcmfexe-exited-with-code-1106.html
I used the workaround described and I was able to get rid of the silent build error but my app submission still fails with error 1201.

Corda : Exception during node startup: Certificate is not valid at instant now

I try to run the example CorDapp following this url https://docs.corda.net/tutorial-cordapp.html
But there is error while building Nodes as below error
[ERROR] 15:40:44+0700 [main] internal.NodeStartupLogging.invoke - Exception during node startup: Certificate is not valid at instant now [errorCode=18292z7, moreInformationAt=https://errors.corda.net/OS/4.0/18292z7]
So I understand that if I set devMode=true, the certificate for each nodes won't required but after I configured devMode=true, still does not work.
Update 1:
I installed Windows into VM and do the tutorial. Nodes built successfully on VM. Still looking for the solution.
Finally, I figured it out. After I checked X509Utilities.kt which this error came from.
There is some Date validation. So I changed Format and Date format in Windows Region menu as below image. It works!!
Date format image

How to fake flyway migration?

Two of us made a migration script in different GIT branches. Now, I've pulled origin development branch, and I've corrected GIT merge issues, and renamed my migration script to be the last. So, the new initialization of DB and migration of DB from version of develop branch would be fine.
However, I've got a lot of data in my local testing DB, so I've manually applied new migration scripts that I've pulled in GIT. However, I can't make flyway think, that everything is okay.
So, How can I fake migrations?
When I try to migrate, I get following error:
[ERROR] Failed to execute goal org.flywaydb:flyway-maven-plugin:3.2.1:migrate (default-cli) on project db: org.flywaydb.core.api.FlywayException: Validate failed. Migration Description mismatch for migration 1.118
[ERROR] -> Applied to database : AAA
[ERROR] -> Resolved locally : BBB
[ERROR] -> [Help 1]
You will have to manually update Flyway's metadata table (called schema_version by default)

Drupal 7 uuid.module Database update 7103 fails

I finished upgrading a Drupal 6 site to Drupal 7. All fields have been migrated. When I run update now I get this UUID error
An AJAX HTTP error occurred. HTTP Result Code: 200 Debugging information follows. Path: http://drupal220/update.php?
op=selection&token=bLDFFBM8NZi09U0is5p6eim_do1vePHV5iNjLWLu8u4&id=10&op=do StatusText: OK ResponseText: Fatal error: Cannot access empty property in C:\xampp\htdocs\drupal220\sites\all\modules\uuid\uuid.install on line 266
The update process was aborted prematurely while running update #7103 in uuid.module. All errors have been logged. You may need to check the watchdog database table
manually.
Watchdog report
Location http://drupal220/update.php?op=selection&token=bLDFFBM8NZi09U0is5p6eim_do1vePHV5iNjLWLu8u4&id=9&op=do
Referrer http://drupal220/update.php?op=selection&token=bLDFFBM8NZi09U0is5p6eim_do1vePHV5iNjLWLu8u4&op=start&id=9
Message Notice: Undefined index: label in uuid_update_7103() (line 266 of C:\xampp\htdocs\drupal220\sites\all\modules\uuid\uuid.install).
It seems is an error from the uuid module, try to downgrade the version to 7.x-1.0-alpha5 and I think it fixes the error.
You can download this version here.

No Data Access Object for AudienceManagerProfile

Getting "No Data Access Object for AudienceManagerProfile" when I make any OE API calls.
In the cd_core log I can see:
2012-05-13 11:59:30,520 DEBUG StorageManagerFactory - Default storage provider has caching set to: false
2012-05-13 11:59:30,520 DEBUG StorageManagerFactory - Loaded following dao Properties[publication=0, typeMapping=AudienceManagerProfile, storageId=profiledb, cached=false] for publication/typeMapping/itemExtension: 0 / AudienceManagerProfile / null
2012-05-13 11:59:30,520 DEBUG StorageManagerFactory - Loading a non cached DAO for publicationId/typeMapping/itemExtension: 0 / AudienceManagerProfile / null
2012-05-13 11:59:30,535 ERROR Contact - Unable get contact for requested Identification fields
java.sql.SQLException: No Data Access Object for AudienceManagerProfile
I've checked my cd_storage_conf.xml file and it looks correct (I compared it to Nuno's working version from the forum).
Further up in the log it says:
2012-05-13 11:59:29,724 INFO StorageManagerFactory - Checking if product Tridion CD Storage is enabled....
2012-05-13 11:59:29,724 INFO StorageManagerFactory - Tridion CD Storage is running in limited mode
"Limited mode" sounds bad!
Is this the root cause of the problem or unrelated?
Cheers
If the broker runs in limited mode, it means that it couldn't find a license for the 'full' broker. So either it can't find the license file, or the license file doesn't contain a broker license.
When this happens the broker will fall back to using its built-in ItemType mappings, which means it will only support storing them to file system.
It is typically best to point the cd_storage_conf.xml to the correct location of your license file. You won't depend on built-in search paths that way and the broker will start using the mappings you've configured.
<License Location="/path/to/cd_licenses.xml"/>

Resources