Participating Frequently

Coldfusion 2023 update 25 removed some of the packages

Forum|Forum|11 days ago
September 23, 2026
12 replies
205 views

I installed the update 25 for CF2023 manually. We always install updates on our dev server first which is running CF2023 developer. The update UI didn’t show any issues. After the update some of the packages were removed including cfadmin. Thankfully visiting cfadmin link showed me how to install it from cfpm.bat. I was able to install cfadmin and then from it install the rest of the missing packages.

The update log does show timeouts on downloading some packages but the status on this entry is still shown as Successful after the errors.

Did someone encounter this issue ?

Environment: CF2023 developer on Windows Server 2019

Log entry related to packages:
Downloading the package axis-2023.0.25.330977.jarRead timed outDownloading the dependent package sharepoint-2023.0.25.330977.jarRead timed outDownloading the package adminapi-2023.0.25.330977.jarDownloading the package adminapi-2023.0.25.330977.zipRead timed outDownloading the package administrator-2023.0.25.330977.jarDownloading the package administrator-2023.0.25.330977.zipDownloading the package perfmon-2023.0.25.330977.jarRead timed outDownloading the package orm-2023.0.25.330977.jarDownloading the package ormsearch-2023.0.25.330977.jarDownloading the dependent package report-2023.0.25.330977.jarRead timed outDownloading the package pdf-2023.0.25.330977.jarRead timed outDownloading the package print-2023.0.25.330977.jarRead timed outDownloading the package htmltopdf-2023.0.25.330977.jarRead timed outDownloading the package ccs-2023.0.25.330977.jarDownloading the package ccs-2023.0.25.330977.zipRead timed outDownloading the package gcpstorage-2023.0.25.330977.jarDownloading the dependent package guava-33.5.0-jre.jarRead timed outDownloading the package gcpfirestore-2023.0.25.330977.jarDownloading the dependent package guava-33.5.0-jre.jarRead timed outDownloading the package gcppubsub-2023.0.25.330977.jarRead timed outDownloading the package graphqlclient-2023.0.25.330977.jarDownloading the package apache-maven-3.9.16-bin.zipRead timed outDownloading the package ajax-2023.0.25.330977.jarRead timed outDownloading the package graph-2023.0.25.330977.jarDownloading the package zip-2023.0.25.330977.jarRead timed outDownloading the package debugger-2023.0.25.330977.jarRead timed outDownloading the package saml-2023.0.25.330977.jarDownloading the package scheduler-2023.0.25.330977.jarRead timed outDownloading the package azureblob-2023.0.25.330977.jarDownloading the dependent package guava-33.5.0-jre.jarDownloading the dependent package accessors-smart-2.6.0.jarRead timed outDownloading the package awss3-2023.0.25.330977.jarRead timed outDownloading the package cfmongodb-2023.0.25.330977.jarRead timed outDownloading the package search-2023.0.25.330977.jarRead timed outDownloading the package feed-2023.0.25.330977.jarDownloading the package exchange-2023.0.25.330977.jarRead timed outDownloading the package websocket-2023.0.25.330977.jarDownloading the dependent package netty-common-4.2.7.Final.jarDownloading the dependent package netty-resolver-4.2.7.Final.jarRead timed outDownloading the package ftp-2023.0.25.330977.jarDownloading the dependent package bcprov-jdk18on-1.78.1.jarDownloading the package azureservicebus-2023.0.25.330977.jarDownloading the dependent package accessors-smart-2.6.0.jarDownloading the dependent package json-smart-2.6.0.jarDownloading the dependent package nimbus-jose-jwt-9.37.4.jarRead timed outDownloading the package awslambda-2023.0.25.330977.jarDownloading the dependent package netty-reactive-streams-2.0.13.jarRead timed outDownloading the package axis-2023.0.25.330977.jaraxis (2023.0.25.330977) package and its dependencies have been downloaded successfully.Downloading the dependent package sharepoint-2023.0.25.330977.jarsharepoint (2023.0.25.330977) package and its dependencies have been downloaded successfully.Downloading the package adminapi-2023.0.25.330977.zipadminapi (2023.0.25.330977) package and its dependencies have been downloaded successfully.administrator (2023.0.25.330977) package and its dependencies have been downloaded successfully.Downloading the dependent package elasticsearch-cli-7.17.29.jarDownloading the dependent package aggs-matrix-stats-client-7.17.29.jarDownloading the dependent package elasticsearch-geo-7.17.29.jarDownloading the dependent package elasticsearch-lz4-7.17.29.jarDownloading the dependent package elasticsearch-plugin-classloader-7.17.29.jarDownloading the dependent package elasticsearch-secure-sm-7.17.29.jarDownloading the dependent package lucene-analyzers-common-8.11.3.jarDownloading the dependent package lucene-backward-codecs-8.11.3.jarDownloading the dependent package lucene-grouping-8.11.3.jarDownloading the dependent package lucene-highlighter-8.11.3.jarDownloading the dependent package lucene-join-8.11.3.jarDownloading the dependent package lucene-memory-8.11.3.jarDownloading the dependent package lucene-misc-8.11.3.jarDownloading the dependent package lucene-queries-8.11.3.jarDownloading the dependent package lucene-queryparser-8.11.3.jarDownloading the dependent package lucene-sandbox-8.11.3.jarDownloading the dependent package lucene-spatial3d-8.11.3.jarDownloading the dependent package lucene-suggest-8.11.3.jarDownloading the dependent package mapper-extras-client-7.17.29.jarDownloading the dependent package parent-join-client-7.17.29.jarAn error has occurred while installing the package pmtagent. Exception : Read timed outDownloading the package perfmon-2023.0.25.330977.jarDownloading the dependent package elasticsearch-cli-7.17.29.jarDownloading the dependent package elasticsearch-lz4-7.17.29.jarRead timed outDownloading the dependent package report-2023.0.25.330977.jarRead timed outDownloading the package pdf-2023.0.25.330977.jarDownloading the dependent package bcpkix-jdk15on-153.jarRead timed outDownloading the package print-2023.0.25.330977.jarRead timed outDownloading the package htmltopdf-2023.0.25.330977.jarDownloading the dependent package jetty-util-9.4.58.jarRead timed outDownloading the package ccs-2023.0.25.330977.zipRead timed outDownloading the dependent package google-http-client-1.42.2.jarDownloading the dependent package google-oauth-client-1.34.1.jarDownloading the dependent package google-api-client-2.0.0.jarRead timed outDownloading the package gcppubsub-2023.0.25.330977.jarDownloading the package apache-maven-3.9.16-bin.zipDownloading the package ajax-2023.0.25.330977.jarDownloading the package ajax-2023.0.25.330977.zipRead timed outDownloading the package zip-2023.0.25.330977.jarDownloading the package debugger-2023.0.25.330977.jarRead timed outDownloading the package scheduler-2023.0.25.330977.jarRead timed outDownloading the dependent package nimbus-jose-jwt-9.37.4.jarDownloading the package awss3-2023.0.25.330977.jarRead timed outDownloading the package cfmongodb-2023.0.25.330977.jarDownloading the package search-2023.0.25.330977.jarDownloading the dependent package poi-5.4.1.jarDownloading the package exchange-2023.0.25.330977.jarDownloading the dependent package netty-resolver-4.2.7.Final.jarRead timed outDownloading the dependent package netty-reactive-streams-2.0.13.jarRead timed outThe package pmtagent is marked for uninstallation. Uninstallation will be done, on the next server start.orm (2023.0.25.330977) package and its dependencies have been downloaded successfully.ormsearch (2023.0.25.330977) package and its dependencies have been downloaded successfully.Downloading the dependent package ib6coreutil-1.3.jarDownloading the dependent package report-2023.0.25.330977.jarreport (2023.0.25.330977) package and its dependencies have been downloaded successfully.Downloading the dependent package bcpkix-jdk15on-153.jarDownloading the dependent package cf-acrobat-1.1.jarpdf (2023.0.25.330977) package and its dependencies have been downloaded successfully.Downloading the package print-2023.0.25.330977.jarAn error has occurred while installing the package print. Exception : Read timed outDownloading the dependent package elasticsearch-lz4-7.17.29.jarDownloading the dependent package elasticsearch-plugin-classloader-7.17.29.jarDownloading the dependent package lucene-analyzers-common-8.11.3.jarDownloading the dependent package lucene-highlighter-8.11.3.jarDownloading the dependent package lucene-join-8.11.3.jarDownloading the dependent package lucene-misc-8.11.3.jarDownloading the dependent package lucene-queries-8.11.3.jarDownloading the dependent package lucene-spatial3d-8.11.3.jarDownloading the dependent package lucene-suggest-8.11.3.jarDownloading the dependent package mapper-extras-client-7.17.29.jarDownloading the package print-2023.0.25.330977.jarRead timed outDownloading the dependent package jetty-util-9.4.58.jarRead timed outDownloading the package ccs-2023.0.25.330977.zipDownloading the dependent package google-api-client-2.0.0.jarRead timed outDownloading the package ajax-2023.0.25.330977.zipDownloading the package debugger-2023.0.25.330977.jarDownloading the dependent package jetty-util-9.4.58.jarRead timed outDownloading the package scheduler-2023.0.25.330977.jarDownloading the package awss3-2023.0.25.330977.jarDownloading the dependent package netty-resolver-4.2.7.Final.jarDownloading the dependent package netty-buffer-4.2.7.Final.jarDownloading the dependent package netty-transport-4.2.7.Final.jarRead timed outDownloading the dependent package netty-reactive-streams-2.0.13.jarDownloading the dependent package netty-transport-4.2.7.Final.jarRead timed outThe package print is marked for uninstallation. Uninstallation will be done, on the next server start.Downloading the dependent package jetty-util-9.4.58.jarDownloading the dependent package jetty-util-ajax-9.4.58.jarDownloading the dependent package jetty-xml-9.4.58.jarDownloading the dependent package jetty-server-9.4.58.jarDownloading the dependent package jetty-http-9.4.58.jarDownloading the dependent package jetty-security-9.4.58.jarDownloading the dependent package jetty-io-9.4.58.jarDownloading the dependent package jetty-servlet-9.4.58.jarDownloading the dependent package bcprov-jdk15on-153.jarAn error has occurred while installing the package htmltopdf. Exception : Read timed outDownloading the package print-2023.0.25.330977.jarDownloading the dependent package jetty-util-9.4.58.jarRead timed outDownloading the dependent package google-api-client-2.0.0.jarDownloading the dependent package jetty-util-9.4.58.jarRead timed outDownloading the dependent package netty-transport-4.2.7.Final.jarDownloading the dependent package netty-transport-native-unix-common-4.2.7.Final.jarDownloading the dependent package netty-codec-base-4.2.7.Final.jarDownloading the dependent package netty-codec-compression-4.2.7.Final.jarRead timed outDownloading the dependent package netty-codec-compression-4.2.7.Final.jarRead timed outThe package htmltopdf is marked for uninstallation. Uninstallation will be done, on the next server start.ccs (2023.0.25.330977) package and its dependencies have been downloaded successfully.gcpstorage (2023.0.25.330977) package and its dependencies have been downloaded successfully.gcpfirestore (2023.0.25.330977) package and its dependencies have been downloaded successfully.gcppubsub (2023.0.25.330977) package and its dependencies have been downloaded successfully.graphqlclient (2023.0.25.330977) package and its dependencies have been downloaded successfully.ajax (2023.0.25.330977) package and its dependencies have been downloaded successfully.chart (2023.0.25.330977) package and its dependencies have been downloaded successfully.zip (2023.0.25.330977) package and its dependencies have been downloaded successfully.Downloading the dependent package jetty-util-9.4.58.jarDownloading the dependent package jetty-http-9.4.58.jarDownloading the dependent package jetty-server-9.4.58.jarDownloading the dependent package jetty-security-9.4.58.jarDownloading the dependent package jetty-servlet-9.4.58.jarAn error has occurred while installing the package debugger. Exception : Read timed outDownloading the dependent package jetty-security-9.4.58.jarDownloading the dependent package netty-codec-compression-4.2.7.Final.jarRead timed outDownloading the dependent package netty-codec-compression-4.2.7.Final.jarRead timed outThe package debugger is marked for uninstallation. Uninstallation will be done, on the next server start.saml (2023.0.25.330977) package and its dependencies have been downloaded successfully.scheduler (2023.0.25.330977) package and its dependencies have been downloaded successfully.azureblob (2023.0.25.330977) package and its dependencies have been downloaded successfully.awss3 (2023.0.25.330977) package and its dependencies have been downloaded successfully.cfmongodb (2023.0.25.330977) package and its dependencies have been downloaded successfully.search (2023.0.25.330977) package and its dependencies have been downloaded successfully.feed (2023.0.25.330977) package and its dependencies have been downloaded successfully.exchange (2023.0.25.330977) package and its dependencies have been downloaded successfully.Downloading the dependent package netty-codec-compression-4.2.7.Final.jarDownloading the dependent package netty-handler-4.2.7.Final.jarDownloading the dependent package netty-codec-marshalling-4.2.7.Final.jarDownloading the dependent package netty-codec-protobuf-4.2.7.Final.jarDownloading the dependent package netty-codec-http-4.2.7.Final.jarDownloading the dependent package netty-codec-http2-4.2.7.Final.jarAn error has occurred while installing the package websocket. Exception : Read timed outDownloading the dependent package netty-codec-compression-4.2.7.Final.jarRead timed outDownloading the dependent package netty-codec-compression-4.2.7.Final.jarRead timed outThe package websocket is marked for uninstallation. Uninstallation will be done, on the next server start.ftp (2023.0.25.330977) package and its dependencies have been downloaded successfully.azureservicebus (2023.0.25.330977) package and its dependencies have been downloaded successfully.Downloading the dependent package netty-codec-compression-4.2.7.Final.jarDownloading the dependent package netty-codec-protobuf-4.2.7.Final.jarDownloading the dependent package netty-handler-4.2.7.Final.jarDownloading the dependent package netty-codec-http-4.2.7.Final.jarDownloading the dependent package netty-reactive-streams-http-2.0.13.jarAn error has occurred while installing the package awslambda. Exception : Read timed outDownloading the dependent package netty-codec-compression-4.2.7.Final.jarRead timed outDownloading the dependent package netty-codec-compression-4.2.7.Final.jarRead timed outThe package awslambda is marked for uninstallation. Uninstallation will be done, on the next server start.The package and its dependencies have been downloaded successfully. ColdFusion server is currently not running. The package will be installed automatically once server is up.
Status: SUCCESSFUL

Joseph388194533qbd

Participant

I’ve opened a ticket with cfsup@adobe.com as well for similar behavior experienced when installing CF2023update 24 just yesterday evening.

Packages removed, including admin and axis.
Also, during CF2023 update 24, it updated some packages to 2023.0.25, which is *not* what happened when installing CF2023 update 24 a few weeks ago in our lower environments.

Charlie Arehart

Community Expert

Joseph, as for your first problem, I hope you will read my extended reply below to Simranjit and Tyrone.

As for your second observation, I can explain that. It’s not a bug, but its a rather rare situation. Sometimes, the package updates made available in a given update are defined (by Adobe, in that bundlesdependency.json file) as being able to be used with an EARLIER version than just that latest update.

As such, yes, if you do update 24 (since yesterday), it WILL indeed update many (but not all) of the packages to their 2023.0.25 version. There were over 30 packages updated in the update yesterday, but again not ALL of them would be updated if you’re on u24.

As proof of what I say, folks in that situation can look closely (at the admin “installed packages” list, or cfpm list) to see that specifically their administrator and adminapi packages are still at their 2023.0.24 version. (I know you said that you noticed only “some packages” were updated, so perhaps you already knew that. I am offering this last suggestion as much for others.)

Let me know if this is helpful. That’s all I’m ever trying to do here folks: I don’t work for Adobe. I’m just a fellow CF traveler, helping pull folks out of ditches along the road, and putting up signs of warning/explanation where I can.

/Charlie (troubleshooter, carehart. org)

Joseph388194533qbd

Participant

Charlie, your reply here as well as the wall of text to Simranjit and Tyrone were very helpful.

I’m not finding any download timeouts in the hotfix logs, so not sure if that’s why some packages disappeared

I’ve asked cfsup this too:
Is it ok to use the 2023.0.25 version of the packages on core server 2023update24?

Charlie Arehart

Community Expert

@Simranjit Singh , while you await the helpful offer of Adobe support from @AbhishekJha , I have a couple of thoughts to help you and Tyrone (commenting also here), and future readers.

1 - First, I want to address on point you raised, that “The update log does show timeouts on downloading some packages but the status on this entry is still shown as Successful after the errors.”

This is because it seems the update “success” report is based on the tracking of whether there were fatalerrors or nonfatalerrors as reported at the TOP of that update log (at about line 77). That is only indicating if the “core” update worked without error.

As for those timeout errors you saw, those are about the downloading of package updates which takes place (and is tracked) at the END of that log. By them the “update” had worked, but these downloads had failed.

And if ever they do, for any reason, that will lead to the scenario you presented: the admin or other packages will be uninstalled...but that doesn’t happen until the following startup of CF. That’s why I always tell people to look at all 3 places (the tracking of errors at the top of that update log, the downloading of packages at the bottom of that update log, and then the coldfusion-out.log for the startup of CF AFTER the update).

The way the update process works (for now, and since CF2021 introduced “packages”) is that during that next startup, the startup log will show that CF will first be “uninstalling” all the packages that were to be updated...and it will do this whether the packages WERE successfully downloaded or not. Currently, this step does not know or check for that.

Then it would attempt to install the updated packages (though it never logs that), and then normally it would report only if the package then “started”. Sadly, when the uninstall happens but the update/re-install does not (for any reason), then you are left in this state where those packages to be updated are left uninstalled.

And worse, nearly every update that updates packages includes an update to the admin (and adminapi) packages...and so when any such problem (of downloading the packages) happens, it’s easy to end up with the admin not able to run.

It’s very disappointing, yes. But I am just a troubleshooter who helps folks. I don't work for Adobe and it’s up to them to improve the process. I have some ideas to suggest (related to the above, and more) that I’ve thought about blogging.

Anyway, I wanted to let you know all that, if it may help. I realize your first focus (and that of Tyrone, commenting also below) is “how to get back to working”. Adobe may help you (and perhaps him).

2 - As for how to solve things, that depends on why the download of the package failed.

You show it “timing out”. If somehow the java process (doing the update, as kicked off from the admin) couldn’t reach Adobe’s servers to get the updates, that’s the most common cause. That can happen because of a change in firewall rules. You can test that by doing a test cf page that does a cfhttp call to the url listed in the Admin “package manager” page’s “settings” tab. That has a “packages site” field whose “site url” defaults to https://www.adobe.com/go/cf2025_packages for CF2025 and https://www.adobe.com/go/cf2023_packages for cf2023. (And each of those does a redirect to yet another url, which cfhttp will by default follow. It’s https://cfmodules.adobe.com/cf2025/bundlesdependency.json and https://cfmodules.adobe.com/cf2023/bundlesdependency.json, respectively.)

Does a cfhttp call to the url in that field work or fail for you? (Don’t just test it in your browser. Test it FRO CF via cfhttp.) If it fails, you need to find out why CF can’t reach that url. And if it can’t then it likely explains why the java process doing the actual CF update also can’t.

2b - And some people already KNOW that their CF machine (or CF itself) can’t reach out to the internet to access such a URL. In that case, the CF update technotes always offer a “manual offline update” set of steps (involving downloading the zip, extracting it to a new location, then changing that cf admin “package manager” settings value for the “packages site” “site url” to be the bundlesdependency.json within that extracted folder.

(And that can be changed in the cfusion/lib/neo_updates.xml file also, in its “packagesurl” field. But one needs to be VERY careful about doing that--and they should NOT change the “defaultpackagesurl” value, even though some resoures suggest that. That’s the value which would be filled into the CF admin if you clicked its “restore default url” button on that “settings” page. And to be clear, if you change that value in the admin, that changes this field in the file. As such, if you can’t see the admin, you can change it in the file.)

Unfortunately, many people try to shortcut those steps. Note that you should NOT just extract the downloaded zip into CF’s “bundles” folder, though it may seem like “it’s the same thing”. It is NOT. The uninstall of the packages expects to find what’s in that current CF bundles folder (and its underlying repo folder), and then it wants to pull changes out of that extracted zip (like it would download from Adobe, if it was online) to place those (and only what it things it should place) into that CF “bundles” folder.

When people instead just either extract the zip into that “bundles” folder or even “save it off” and “replace the bundles folder with the extracted zip”, either can lead to other reasons that the package “download” step (bottom of the update log) and then perhaps even the “uninstall” step (and certainly the install step) during the startup will fail...and they will be in this situation you are.

Sadly, those people will see the offered command to “just run the cfpm to fix the problem”, but that will ALSO use the value found in that “sites url” (as shown in the admin, or that packagesurl value in the neo_updates.xml file). If that’s still NOT correct, then even the cfpm steps will fail.

Finally, another negative ramification of people “solving this offline update” problem by changing that packagesurl value in the file (the “packages site” “site url” in the admin) is that when they apply the NEXT CF update, they then have to REPEAT the process of changing that value to point to the NEWLY extracted zip. They often forget, and end up in this same conundrum.

As I noted above, there are things I think Adobe could do to improve this process, such as to improve its reliability, including detecting and preventing problems before they happen. Some might even argue they need to more dramatically change how it works. We’ve been dealing with these sort of package update issues for now over 5 years. Some are well understood, but many remain a mystery.

That’s why I’ve written this wall of text. Even if it may be too much for some, I hope it may help others...or may help AI if it finds and offers it to people. And again in time I hope to repeat it (and perhaps even elaborate a bit) in a blog post of my own. But I started writing this, and wanted to finish it here, rather than leave it for that “later” effort.

/Charlie (troubleshooter, carehart. org)

Simranjit SinghAuthor

Participating Frequently

Very interesting and helpful read. I didn’t know the workflow for package updates and Adobe can surely improve and make it more reliable.

As for the why it failed for us, I haven’t made changes to the the defaults for package downloads. @AbhishekJha has inspected the neo_updates.xml and confirmed we still had the default url in place. He did suggest packages zip download method for offline downloads. Although, I’ll heed your warnings and not change the defaults for package downloads.

It seems that a temporary network issue while downloading the packages could a possible explanation. I’ve tested the adobe packages urls with cfhttp from the server and was able to get successful responses from both of them. I’ve also raised a request to our infra team to investigate the logs if there were any network/firewall issues on our end the may have caused an issue accessing the urls during the installation. I’ll post an update here once I hear back from them.

After restarting Coldfusion, I did get the “install cfadmin using cfpm.bat” message when trying to access cfadmin. So I ran the command and it successfully installed the cfadmin package. As you mentioned cfpm.bat also uses the url/path in neo_updates.xml to download the packages, this means the server was able to reach Adobe urls at that time. This is why I believe there is no permanent network/firewall block on our end.

I was also able to download the rest of the packages from cfadmin afterwards without any issues.

For now the most likely explanation is that there was some temporary network issue which led to timeouts on package downloads. As you mentioned Adobe should make the process for updating packages more reliable.

I really appreciate your help and detailed explanations, very helpful in understanding what happened. Hopefully this thread will also be useful for others in the similar situation.

Charlie Arehart

Community Expert

Thanks for the update and glad to have helped.

And yep, that timeout logged during the package download was telling. It can happen for many reasons, including transient ones--whether from Adobe's side or yours.

1 - As for your side, note again that technically it's a Java process doing that (as kicked off by the cf admin update buttons) rather than cf itself. Same with when you run cfpm.

And in the latter case the Java process runs for the cfpm request as whoever is logged into the machine, whereas the java process kicked off by the admin runs as whatever user is running cf. That can be another reason cfpm works while the admin update fails.

2 - On an related point, the admin has long offered the download button for the core update. Some may notice they don't offer one for the package updates, and they may wonder why that (or cfpm) couldn't just get the zip.

But technically when you update a package (or run that core update) cf pulls down ONLY the jars related to the specific package update(s). It doesn't pull down the entire zip. That was a tradeoff (it gets larger and larger with each update, often more than a gig after several updates exist for a given cf version).

I'm referring here to the default state of when the "packages site" "site url" points to Adobe rather than a zip downloaded manually. (And again, that technically points to where the bundlesdependency.json file lives, which then is also where Adobe "downloads" updates from--whether remotely or locally.)

3 - One more potential gotcha (of many) is that sometimes the pulling of that bundlesdependency.json file "works" but it does not have in it the expected reference to the NEW update's jar files.

This is what leads to the errors that refer to "opaque part", when the underlying Felix mechanism can't find a jar its been told to implement. (Or so it's seemed to me.)

That failure (to have the latest json file) could be due to a caching issue at Adobe (on the day/day after a new update), or a caching issue BETWEEN one's cf instance and Adobe, or it could absolutely happen for someone doing the "manual offline update" but they've forgotten to point that "packages site" "site url" to the newly downloaded bundlesdependency.json file--a very easy mistake to make.

Adobe could improve that step (for both local or remote scenarios) by verifying that the json IS updated to correspond to the core version currently installed.

4 - Those 3 above are just some facets to why the update process can be unexpectedly (and even only transiently) brittle. But yes, it seems past time for some improvement.

Sadly, it's not clear they'll see this. I guess I should raise a bug report. As you can see, it's not just a matter of a few words.

In any case, I hope the additional background in this thread will help those who find it...and the AIs that others may rely upon.

/Charlie (troubleshooter, carehart. org)

Tyrone27602746bdcm

Participant

I’ve had this exact same thing happen to me. Half my packages including CFadmin were gone. Mine happened when I uninstalled “Chart” and then attempted to reinstall “Chart” via admin, but it kept stalling. So I installed “Chart” via CFPM. That’s when it removed half of my packages.

AbhishekJha

Inspiring

@Simranjit Singh Please share the output screenshot and the update install log as .txt with us to cfsup@adobe.com.

Thank You,

Abhishek

Simranjit SinghAuthor

Participating Frequently

Thanks for quick response. I’ve sent the email.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.