I just ran into a similar issue and was told in no uncertain terms that CS2 was too old for product activation. If Adobe won't even do an activation, they won't offer any other support whatever.
Too bad I'd deactivated from one machine before activating on another.
I'd thought I was buying a software license in perpetuity, not one that would expire in four years. I'm not asking for technical support, I'm looking to continue to use the software I bought.
That is absolute nonsense (not your post, the fact that it's too old for activation).
Call back and speak to someone else. If they can't/won't help, insist on speaking to a supervisor. Get names and case numbers.
Let us know how you make out.
Oh, boy...thank you all so much for this solution. It worked for me too...on Win7.
I bought CS2 shortly before Vista came out, intending to use it on my XP desktop. Poor thing died before I got it installed and it was several weeks before I could afford to replace it. When I did, there was no way to even buy something that wasn't Vista...which pissed me off at Microsoft. Then I found out that CS2 wouldn't play nice with Vista and fraking Adobe KNEW it and refused to support it. REALLY?
I bought this program for A CRAPLOAD of money...for me, anyhow...BOUGHT, not hacked. I expected support. I got jack.
Then Win7 came out and I was finding that some of my older software was able to run just fine on it. I thought I'd give the stupid CS2 that I had paid a bucketful of money for and never gotten to use once a try on it. Only to come up with this idiotic error message. The support guy said the usual, "Old product, not tested, isn't supported, blah, blah, blah." But oh, hey, I still have an activation left on it! Oh, joy! Since I have never used the fraking thing, I would hope so!
I would like to beat Microsoft, then Adobe and then Microsoft again...til both of them exsanguinate. Jerks. Nothing but bullies. They both need their arses whooped. Bah. Better yet...they both need to be sued for selling software and operating systems that don't play together.
BUT! Thank you to you folks who are out there helping for free. Go figure. The "support" guy coulda told me this, but he had to stick to the company line of NONsupport.
Do you feel better now?
Good. Because you sound like a very bitter person who has no understanding about how software works.
You can't take pieces from one jigsaw puzzle and fit them into another. And your story about not being able to find an XP machine doesn't exactly ring true.
And you obviously left out the fact that you went to 64 bit. Had you come here with those very facts back then you'd have been up and running in no time.
Gee, Bob...you're right. I AM bitter. I spent a lot of money for software I am only getting to try to use 3 years later. Back in 2007, when Vista came out, you could NOT find an XP machine. If you want to get in your wayback machine and try it, go ahead. They only brought back a few XP machines when Vista turned into such a marketing nightmare for them. By then, everyone had already replaced all the software they needed.
I replaced my Vista when it died an untimely and inconvenient death [aren't they always] a few weeks back...when yes, I DID get a 64 bit machine. NOW, not back then, Bob. And don't think I didn't look for a solution back then. All anyone would say back then was "upgrade to CS3".
So, yeah. Bitter. Big deal. I should be able to vent a bit with others who have been mistreated by Adobe the same as I have, not snarked at by a "community professional". Same treatment I got from "customer service", by the way, who could have easily given me this fix.
I do appreciate whoever it was that posted this solution though. Thanks again.
I posted the solution. And my point is that this is a user to user forum.
Would you walk into a room full of strangers and start complaining to them? Because in essence that's what you just did.
Thanks for this thread everyone! I was getting the same serial number missing/invalid message, and I reinstalled my CS2 on 64-bit Windows 7 using C:\Progra~2\Adobe as the folder and it's working fine now.
I just bought a Windows 7 machine, and like many others here, couldn't get CS2 to run (same errors messages after installation). I'd like to uninstall and reinstall, using the progra~2\adobe and see if that works, but I can't get CS2 to uninstall.
When I try to remove the program, it says:
"Missing or invalid personalization information."
"Missing resources library."
I ran Revo Uninstaller after reading that advice on another forum, and that didn't work, either. I've kind of had at it like a chimp with a hammer and feel like I need to nuke CS2 off my system and start over, but I can't seem to make that happen.
I very much appreciate this thread...
I recently upgraded my hardware from an HP m7640n running XP to a Dell Studio XPS 9100 running Win7. I have CS5 Design Premium and am comfortable running all of the programs except for Dreamweaver... (it's on my list, and I KNOW I need to learn it...) but my web sites are still written and maintained with GoLive CS2.
For the life of me, I couldn't get GoLive properly installed onto my new Dell and have been holding my breath each time that I have to update my sites, praying that my old machine, (running GoLive) wouldn't make it's final gasp (the blue screen of death...), cutting me off from my site maintenance... Everything else is migrated over except my web site maintenance, because I couldn't get GoLive to properly install on the new computer--with the serial number issue hiccup that this thread is centered upon... And my old HP, which has served me well, is indeed gasping, so I know it's only a matter of time...
THANK YOU, THANK YOU, THANK YOU!!! After reading and re-reading through the solutions offered here, I did manage to get my old CS2 GoLive installed onto the Dell. Installing into
C:\Progra~2\Adobe didn't work for me... My solution was:
--to create a destination folder for the installation files on my desktop.
--Install using Disks 1 & 4 (since I only needed GoLive from the CS2 suite), into the desktop destination folder
--The program accepted the serial number in the initial installation box, (but had hung up when it was time to set preferences, asking for the serial number again, and subsequently rejected...) so, when this installation progressed to that preferences screen, I didn't do anything with it... just left it open while I checked my program list and found Adobe GoLive 2 listed as an available program...
--When I clicked on it, GoLive opened and allowed me to activate!
Now that that crisis is averted, it's time for me to roll up my sleeves, learn Dreamweaver and start re-writing my site... (I once picked up a couple of books on HTML & CSS--waaay over my head...) But at least now I have some time. Thanks to everyone who has posted to this thread with information.
I think the problem I got when encoutering the same issues ("Your Adobe Photoshop username, organization, or Serial Number is missing or invalid. The application cannot continue and must now exit.") was that Photoshop 7.0 installs to c:\program files (x86)\Adobe, but when I try the CS2 upgrade it says that is an invalid directory. Then presumably because they don't match up if I then put it in c:\program files\adobe, it doesn't know they're linked and won't let me use any of the CS2 stuff.
However, I then removed them both and tried again, putting them both in c:\program files\adobe.
However, after I again got the message from the CS2 install about it not being a valid directory name, I browsed and selected where I wanted to put it, and then when I ran Photoshop CS2, it gave me the same error message!!
After looking at c:\program files\Adobe, I found that nothing had changed...then I decided to look in C:\Program Files (x86)\Adobe and lo and behold...there were all the folders for CS2.
so it can install there after all, and even when I tell it to install somewhere else!
So I still can't use anything (other than photoshop 7), and will have to remove CS2 all over again!
Sort it out!
EDIT> Now it just ignores the fact it "can't" put it in the (x86) due to invalid characters and install it there anyway!
The only way I can see now is ignoring the whole program files bit and installing it in c:\Adobe or something.
What's the point of allowing users to choose where to install and just doing what it wants (which is not the same as what it did by default).!!!???!?!
Yep, that's worked...although it did create an 'Adobe Utilities' in the x86 folder.
But photoshop 7 and CS2 upgrade are both in c:\Adobe and it works fine now. Well it opens anyway.
I removed Adobe Reader X just for the hell of it first so there were no Adobe folders in either program files.
Lets hope I dont get the same problem when work sanction the CS5 upgrade too.
I'd have to second Bob's comment! Although I got my cs2 version of GoLive up & running on my new machine, it was far from productive. (I took it off for fear of it actually messing up my new system.) I'm gingerly coaxing my old XP machine along until I nail the basics of Dreamweaver enough to start re-writing my site... Fortunately, my business isn't dependant on my web site...
Every OTHER computer program I have from that era works. I tried the screen name "Chill Bob" but it was already taken. I have found a user's comments above frankly biased and unnecessarily offensive. Condemning people for expecting something they bought to work? Really? Condemning people for complaining in frustration after hours trying to install their legal software? Really? "Of course it won't work on 64-bit!" Really? I have a whole Program Files folder of programs that do.
Complaining someone sounds bitter for spending 100's of dollars and getting nothing? Really? That is neither helpful nor fair nor reasonable. SIMPLE: They bought software for hundreds of dollars, the company refuses to support it because they want monthly lifetime subscriptions. And to top it off, the poster wasn't snitty over one post, but a year or longer.
Customers traded X for Y. They gave X. They didn't get Y. And they are bitter? Of course.
It is not their comments unmerited in a "support" forum, but the clearly unsupportive.
And for my part, I have downloaded the update, now offered, only to be confronted with an allegedly unsupported serial number that I triple checked from my user account.
Bitter? The poster should look in a mirror, for they, unlike the above poster, have a reason to be.