From what I can gather CSXS is part of the CS Extansions system. When I installed this update this morning it was listed as being part of pretty much every CS application. As for what this patch in particular does... No idea. This post is the first thing that comes up when I search for information on the update, and Adobe has no security buletins released today, so Curt Y's "misc. bugs" prediction seems accurate.
As to why you need to restart, if any part of Adobe's startup helpers/daemons were using the extension system while the update was running, then the update may request a restart. I did not need to restart on my Windows Vista or OS X 10.7 machines, so it may be a Windows XP "feature".
Well, I can tell you that I think part of it related to a Creative Cloud subscription was to install a "Adobe Content Viewer" that has the same little purple book icon as seen on the page for the Adobe Digital Publishing Suite: http://www.adobe.com/products/digital-publishing-suite-single/features .html
And it views "folios" - I just noticed it there suddenly and I'm pretty sure it didn't come with the CS6 install of InDesign/Photoshop, etc.. as part of my Cloud subscription prior to this. I noticed it immediately after the upgrade ran and went "What's that?"
I could be wrong, but I don't remember seeing it before this.
This should be helpful.. at least a little. ![]()
http://cookbooks.adobe.com/post_What_is_a__Hybrid_Extension__-19547.ht ml
So if this fails to update, and the error log fails to populate any screen, we should just say, Oh well? Because I am just in trial mode with CS6 and this update has failed and the error log is not active. No support for trial software. ... Win 7 64 bit
well, just tried a 4 time to access the error log. ,
Adobe CSXS InfrastructureCS6
Update is not applicable. Error Code: U44M1P28
Looks like they need to build a better mouse trap here. If it doesn't apply, don't tell us we have an u[pdate.
station_two wrote:
How about those of us that only have the Photoshop 13 point application? The update certainly did something here. Maybe it modified Bridge?
Hi,
It updated components that 1-n Adobe products use. So yes, even a single installed point product will be flagged as an update candidate, but the actual update is to components outside of Ps proper. I'm not privvy to the list of changes, but these are components that Extension panels use. So even if the targeted fix isn't specific to say the Mini Bridge panel, the infrastructure that Mini Bridge panel uses is updated.
Hopefully that makes sense. The basic take away is that this update should just install (Adobe needs to get smarter about shutting down services that might cause restart conflicts), and provide better logic for Beta and non applicable targets.
regards,
steve
R Kelly, Kind of my whole point... If the program is using an auto update or an update feature, then it should be able to tell what version of the software you are using. If it is NOT part of the update regime, then DON'T try and update. It is within the Adobe undate manager. It also took three goes at updating before it allows the error message to be read. Could be an interface issue with ???
I'm just a user such as yourself so i don't have any inside knowledge on how the updater is supposed work, but if your still on the beta
you should uninstall that and download the release version, which is a thirty day trial.
When more updates are released you won't be able to update the beta.
Managing how software updates are going to work across multiple versions is more difficult than you might think. Add in a public beta and things get even more complicated.
I assume people are still using the public beta until such time as it expires, so as to delay the start of a 30 day trial of the released version.
For those who are: It's a beta - you're on your own now, since the product has been released. Isn't it kind of silly to report problems with it? Non-applicable update or not, you're getting more value than you paid for.
-Noel
R Kelly, perhaps we are and perhaps not, a like ; ) I down loaded it and ran it to test plug ins. I get the whole beta software issue.
Noel, the suggestion here is that since your dooing a public beta you get what you get , so deal with it. fair enough.... and I am giving some insight here that I am NOT alone in having that problem. I quickly saw some list where people were having to, with Adobe support, completely uninstall the trial/beta, install their purchased CS6 and still having issues with the installer and update.
Hard doesn't mean the end user should have to spend many hours undoing an installer function because Adobe wants to restructure their sales model and have a 30 day rental option.
As to getting more value, that is a way of dismissing the mess that customers need to unravel as solely on them; a point which could be looked at in different ways.
I don't mean to be critical, but I'm also quite aware that things like "beta tests" require a certain additional wherewithall that not everyone possesses. I also know my own limitations.
There are just things - in life, and on computers - that you have to be willing to take responsibility for.
If you walked up to a ski slope as a beginner and there was a big sign that said Beginners -> pointing to one slope, and another slope off the other way with just little sign with just a black diamond on it but no big letters, would you just go merrily down the black diamond slope and assume that someone will have set everything up to protect you from danger?
Some of us have had no problems whatsoever navigating the betas and releases and understanding what's happening. Is it because someone is there holding our hand, or is it maybe because we have worked to gain knowledge that allows us to participate with sufficient situational awareness to get things right?
Let me put it simply, and I'm sorry if this seems blunt: If you don't have the technical prowess to deal with the additional integration responsibilities needed to try beta software, maybe you shouldn't try beta software.
-Noel
Carboni,
EJ Printer has more experience alpha/beta testing software than most people on this forum
or the planet for that matter. He has worked with one of the major plugin developers for the last
several years as a prime source of feedback and often asks questions based on a 'lack of technical
prowess' just to see what sort of answers he gets as that is exactly the scenario that most of his
customers and test scenarios involve. And your smart a** answer is a prime example of
the fanboy/guru/almighty know-it-all that helps no one with junk like that.
You always seem to be in the 'Some of us have had no problems' category on these forums and
fail to realize that in the real world of Adobe product usage, everybody doesn't have your 'expertise' or
systems that only run casual workflows.
MT
Honestly, I'm having trouble understanding just what's being argued, and I'm sorry if I've stepped on toes with my "education beats guardrails" views. It's not my intention to insult anyone.
I appreciate your feedback, and I promise to try to be less of a smarta** fanboy/guru/almighty know-it-all. ![]()
-Noel
EJ Printer ranted:
If you don't know who the hell you're dealing with...
So let me be blunt, WTFRU? There is no place for that kind of BS in a repsonsible support forum.
Look, I don't need (nor care) to know who you are because what I said is based on experience and common sense:
Don't expect beta software to be polished and idiot proof, and make sure you're prepared to deal with issues running beta software could cause.
You know who I am, because unlike you my name is signed on every post I write. I write carefully and stand behind what I say. Now ask yourself the same profane question. It doesn't take a rocket scientist to see that if you crave recognition, you might want to make yourself recognizable.
I have no interest in a "who's the bigger geek" contest, and you've already lost much of my respect. Please take the attitude and profanity elsewhere.
-Noel
Hi all, Firstly let me apologise for the confusion caused by this updates lack of descriptive text. I do not like applying updates without at least having some idea of what they do, so I went to the Engineering team responsible for the update to get a response and also created a blog post, the copy of which can be found below. We are working on getting the descriptive text applied as quickly as possible.
http://blogs.adobe.com/cssdk/2012/05/about-the-csxs-infrastructure-upd ates-for-cs6.html
Recently we posted updates for various CS6 applications called CSXS Infrastructure updates via the Adobe Application Manager. Unfortunately, there was no text describing what the update was for or indeed what CSXS was. Whilst we work to add in the descriptive text to the update, I wanted to provide some brief information for those that were curious as to what the update was about.
CSXS is the platform that delivers extensibility within Creative Suite products. This update to the CSXS Infrastructure, resolves an issue where certain characters contained in a users Adobe ID caused a login failure.
It’s only a very small update but an important one, so please apply the update if you are a CS6 user, now that you know what it’s for.
Jonathan Ferman | Product Manager
Just curious, why are you all so mistrustful of Adobe? It's not as if they are installing spyware on your computer. You should always keep any software you use up to date, especially Acrobat/Reader because by not updating you expose yourself to vulnerabilities for malware, which you really do need to be worried about.
There are so many bugs in CS6 I would like to know when CS6 updates are install which of the reported bug are being fixed. So far it look like CS6 CSXS Update 3.0.2 just removes the CS6 CSXS 3.0.1 update and installs CS6 CSXS 3.0.2 and fixes none of the reported bugs in CS6.
[ 12176] Mon Jul 02 13:43:28 2012 INFO
Successfully installed 1 component:
- Adobe CSXS Infrastructure CS6_3.0.2_AdobeCSXSInfrastructure3-mul
Total components repaired: 0
Successfully removed 1 component:
- Adobe CSXS Infrastructure CS6_3.0.1_AdobeCSXSInfrastructure3-mul
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Restarting your computer is recommended:
In order to complete the installation, please restart the computer
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
JJMack wrote:
CSXS 3.0.2 ... fixes none of the reported bugs in CS6.
With all due respect, you can't know that. It fixes none of those you reported, perhaps.
In the particular case of 3.0.1 (the original subject of THIS thread) Adobe finally did document that the fix was to make it possible for people with certain special characters in their Adobe ID to actually use the CS6 software. I'm a bit miffed they didn't bother to document why 3.0.2 was released, though. Edit: I see SG has clarified that in the other thread.
-Noel
Here is the release description for CSXS 3.0.2. If this did not appear along with the update please let me know.
Thanks
Jonathan
"
CSXS is the platform that delivers extensibility within Creative Suite products. This update, provides the following:
1) Resolves an issue where certain characters contained in a user’s Adobe ID, caused a login failure (Mac & Win).
2) Update to CS6ServiceManager that improves the performance of authenticating against the Adobe Identity Management Service (Mac & Win).”
3) Resolves an issue in CS6ServiceManager with application signature validation, causing any Keychain access to fail the signature validation step. The result of which invalidates the "Always Allow" option so an alert will always be shown on attempting to access the Keychain (Mac).”
North America
Europe, Middle East and Africa
Asia Pacific