hey guys,

i'm attempting to repackage adobe photoshop cs and am running into an error 1911 error when trying to do a test install.

the error msg i get from the installer is "Error 1911. Could not register type library for file C:\Program Files\Adobe\Photoshop CS\TypeLibrary.tlb. Contact your support personnel."

and the platform sdk is (also) unhelpful. it just says "Could not register type library for file [2]. Contact your support personnel."

using wise's windows installer editor, i went to the components table and browsed my way to the TypeLibrary.tlb entry. i selected the 'Files' tab and brought up the File Details window. Under the 'Self Registration' tab i changed the 'Registration Method' from 'Do Not Register' to 'Use Order Specified Below'. i'm still getting the same error when trying to install. i'll try the Unordered Registration Method, but i fear the results will be the same.

any ideas?
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

2
This isn't a native MSI is it? These registration errors are often a result of including system files or portions of MDAC that do not belong. As a troubleshooting measure, I would start by removing any items that are destined for the system directory. A new tool to help avoid problems like this called PackageCleaner was just released - check it out here: http://www.packagecleaner.com

When you repackage the registration information is normally captured in your package so the DLLs do not normally need to be set to register themselves at all.

Let us know what you discover!
Answered 12/05/2003 by: bkelly
Red Belt

Please log in to comment
2
womp:
The issue with the file TypeLibrary.tlb is specific to the advertised information for the component. Removing the advertisment for this component should fix this problem. You should not remove this file from the installation.
Answered 12/05/2003 by: jdelgadillo
Senior Yellow Belt

Please log in to comment
2
hi guys,

removing the advertisement worked. the app installs without any problems! unfortunately, it doesnt run. :) i'm getting a "could not complete your request because of missing or invalid personalization information" dialoge box as the app loads.

maybe i left something out while creating the package, but i kinda doubt it. i'll post back when figure this out.

thanks for help!
Answered 12/05/2003 by: womp
Senior Yellow Belt

Please log in to comment
2
The personalization error you are receiving is most likely due to the serial number information missing from your installation. With a lot of Adobe applications, the serial is not captured into a 'property' during install but added as a reg entry and validated at first execution.
Answered 12/07/2003 by: jdelgadillo
Senior Yellow Belt

Please log in to comment
1
thanks for the help guys. here's a quick run down of getting a working repackage for photoshop cs (at least for me).

1. browse for typelibrary.tlb under the component tab and delete the advertisement. [jdelgadillo]

2. run photoshop on your repackaging box and add to the package registry the settingss from HKLM/Software/Microsoft/Uninstall/EFB21DE7...[jdelgadillo]

3. i went ahead and included the installshield files that were captured during the install process. i'm sure i could do without these files.

i hope this helps the next guy trying to repackage an adobe app.
Answered 12/09/2003 by: womp
Senior Yellow Belt

Please log in to comment
1
If I could change the subject slightly...

I repackaged Photoshop CS v8.0 using Wise 9.0. I can install my packaged application on a test machine OK. However, when I launch the application, the splash screen appears and then a message stating "Could not complete your request because of missing or invalid personalization information". I noticed that when the splash screen appears after the vendor install, there is User, Company and Serial number information shown at the bottom of the screen. My packaged version does not display this information.

Does anyone have an idea of what Wise is not capturing from the vendor install?
Answered 01/06/2004 by: Ron Duca
Senior Yellow Belt

Please log in to comment
1
i doubt i'm going to be much help anymore, but did you confirm #2 in my message above yours?
Answered 01/06/2004 by: womp
Senior Yellow Belt

Please log in to comment
1
The simplest way to package adobe apps is to use the abcpy.ini file and supply it with your companies information. Then you only need run the setup to complete the installation. Hoever CS's new online registration process puts a HUGE cramp into our packaged installs.
Looks like a little creative packaging will be in order to bypass the register hitch.
Answered 01/08/2004 by: JMAN
Yellow Belt

Please log in to comment
1
I'm having the same error message with another program, but I cannot remove the advertisement..
Using Wise for Windows Installer 3.2 here..
I can Rescan Advertising, but I'm not sure of what that does [:-]
Answered 01/28/2004 by: possamai
Orange Senior Belt

Please log in to comment
1
I'm facing the same error message "Could not complete your request because of missing or invalid personalization information" after installing using file abcpy.ini. Any idel pls help.

Thanks,
Answered 02/04/2004 by: binhpham75
Yellow Belt

Please log in to comment
1
thanks for the help guys. here's a quick run down of getting a working repackage for photoshop cs (at least for me).

1. browse for typelibrary.tlb under the component tab and delete the advertisement. [jdelgadillo]

2. run photoshop on your repackaging box and add to the package registry the settingss from HKLM/Software/Microsoft/Uninstall/EFB21DE7...[jdelgadillo]

3. i went ahead and included the installshield files that were captured during the install process. i'm sure i could do without these files.

i hope this helps the next guy trying to repackage an adobe app.


This is correct for all you Wise Package Studio or other Wise product users. The only thing missing to get rid of the error you are receiving is that you must change the Product Code in the Properties Table to match the product code of the Original Adobe Product Code. They must have some trigger set to check this.

This worked for me, I hope it helps out others who have to continually struggle with any Adobe product.
Answered 02/16/2004 by: duke22
Yellow Belt

Please log in to comment
1
why dont you use a command line like that to make a clean package:

msiexec /i "AcroPro.msi" ALLUSERS=2 COMPANYNAME="Ure-company" EULA_ACCEPT=YES ISX_SERIALNUMBER=XXXX-XXXX-XXXX-XXXX-XXXX

XXX <- ure serial number.
Answered 02/19/2004 by: thales
Senior Yellow Belt

Please log in to comment
1
Although I have not tried the product code trick, I know that Adobe puts serial and reg info into the Uninstall Key in the registry which is not captured by repackagers because there is no need to capture it. If you do and regular install and look in the Uninstall Key you will find the info and you can add it to the package.
Answered 02/25/2004 by: neldog2
Yellow Belt

Please log in to comment
1
Thanx guys the info relating to the rego info in the uninstall key saved me alot of effort :-) Works like a dream
Answered 04/14/2004 by: PuterFix.biz
Senior Yellow Belt

Please log in to comment
1
I'm trying to repackage PS CS - thanks to the registry info from this thread I was able to get past the "missing or invalid personalization information" error. Now I'm getting "The Adobe UI font could not be loaded. For best results, please exit the program and either install it or uninstall other fonts." I'm missing something somewhere - the font (ADMU13.fon) appears to be installed (it shows up in the font control panel) and, other than the fonts that come standard with XP and whatever Photoshop may have installed, there are no other fonts on the system. I've tried reinstalling it to no avail. Any suggestions?
Answered 04/23/2004 by: capo
Yellow Belt

Please log in to comment
1
However CS's new online registration process puts a HUGE cramp into our packaged installs.
Looks like a little creative packaging will be in order to bypass the register hitch.



Anyone find where the activation info is hiding? Trying to work around this in a repackaging attempt..

Thanks!

Tom
Answered 05/19/2004 by: Nuke
Senior Yellow Belt

Please log in to comment
1
Hello,
I'm repackaging Adobe Photoshop CS with Installshield Repackager. I'm having troubles with files what contains is "%"-character at filename, when I trying to compile MSI. Is this a bug or feature at Installshield.
(Normally I use Wise-products but this is unique case.)

Thanks for any help!

-Janne
Answered 06/08/2004 by: saarja
Senior Yellow Belt

Please log in to comment
1
At a guess I'm thinking that the font is system installed correctly but for some reason on a User basis it is invalid. What happens if you install it to a clean system as admin and run the app?

Try that and check the HKCU entries for keys that may have been missed in your install.
Answered 06/10/2004 by: MSIMaker
Second Degree Black Belt

Please log in to comment
1
I successfully repackaged Adobe Photo Shop 8.0 CS using Wise Package Studio 4.61. I could not have done it without the help of the other posters here. I wanted to clarify a couple of items for which I had to do a little more digging before getting it to work (with a lot of detail for newbie repackagers out there like me):

STEP 1: You need to get rid of the Advertisement for typelibrary.tlb. To do this in Wise, go to Setup Editor, click on the Components tab, and navigate down to typelibrary.tlb. If you expand it, you'll see three sections - Files, Registry, and Advertising. It's the Advertising you'll want to get rid of. To do so, you'll need to expand Advertising, which will give you a folder named after some file; expand this too. There should be only one entry at this bottom level; click on it. Now, in the upper right pane, delete the only entry there. Even though the Advertising entry will still look like it's there, it will disappear when you re-compile. By the way, you can't just right-click "Advertising" in the left pane and delete it; it will be grayed out. You need to delete the actual file in the right pane.

THIS WILL GET RID OF THE "1911" ERROR YOU GET DURING INSTALL. [:D]

STEP 2: Next, you'll need to modify an entry in the Tables section (you're still in Setup Editor). But first, use regedit to find the key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{EFB21DE7...}. Now, find the value for ProductID and copy it. Back in Wise, click on the Tables tab and navigate down to the PROPERTY table. In the upper right pane, find the entry "ProductID". This may have "none" as its value at this point. Paste the value you copied above from the registry key. It should now have twenty characters followed by four "X"'s (e.g. 12345678901234567890XXXX).

STEP 3: Finally, you'll need to copy registry entries from the machine you created the package on TO the registry section of the package. To do so, go back to the Registry section of the Installation Expert in Wise. Making sure you click on "Complete" in the drop-down box at the top, find the key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{EFB21...}. Add this entire key to your package. This step should result in this structure in your package:
HKLM
SOFTWARE
Microsoft
Windows
CurrentVersion
Uninstall
{EFB21...}

This will get rid of the "MISSING OR INVALID PERSONALIZATION INFO" error message you get when you LAUNCH the app.[:D]

Recompile the package, do a test install, and if you're like me, it should work beautifully. Miller time, baby.[sm=tongue.gif]

I know some of this may seem basic for a lot of you out there, but I wanted to gear this to all levels of expertise. (We all have to start somewhere.) [:-]
Answered 06/10/2004 by: jbonbright
Senior Yellow Belt

Please log in to comment
1
I tried to repackage Photoshop CS and so far everything looked good.
But the problem came up when I installed MSI and lanched the apps.
Nonetheless, that during the repackaging process I captured all the information including activation part ( at least I tried to capture all the information), there was still the problem with it. The Photoshop still requires to activate it.
So the question is - if anybody know where that activation part is stored - in the registry or somewhere else? How to get rid of that activation crap?
thanks in advance! [:)]
Answered 06/15/2004 by: wildcat966us
Senior Yellow Belt

Please log in to comment
1
I never, at any point, got any activation requests, so I'm wondering if your version of CS is different than mine (i.e. retail vs. enterprise.) I'm thinking that might be the case here, because this seems like a different issue than the personalization error you encounter if you don't do steps 2 & 3 above.
Answered 06/15/2004 by: jbonbright
Senior Yellow Belt

Please log in to comment
1
Yeah, I have a retail version of that apps....
As far as I performed steps 1-3 mentioned above, I didn't have any personalization errors.
So may be this is the reason that I still need to activate the product - the retail version. Though I have no idea what the heck is the enterprise version. [:D]
Anyway, I tried to capture the difference before and after activation event. It didn't help too much, so I assume that there is something that might be hardcoded inside of the software and it makes impossible to get rid of that activation part.[:(]
Probably I should try to remove all the exclusions during the capturing process.
Answered 06/16/2004 by: wildcat966us
Senior Yellow Belt

Please log in to comment
1
This solution helped me get rid of the 1911 errormessage in my Photshop MSI-package... Thanks a lot! //Gatte
Answered 06/18/2004 by: Gatte
Yellow Belt

Please log in to comment
1
Further to the above solutions for repackaging Photoshop CS, the critical keys to be included in your msi are:

HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall\{GUID}\Serial
HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall\{GUID}\RegCompany
HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall\{GUID}\RegOwner

You can, as someone suggested, change your msi's ProductCode to the Photoshop CS GUID to create the Uninstall keys and then add the above 3 keys.

Caveat: This information applies to a volume license install that does not include the online license management.
Answered 08/30/2004 by: jendres
Senior Yellow Belt

Please log in to comment
1
you're best off contacting your supplier, you need a different setup CD.

Mine has "NON ACTIVATION" printed on the security sticker that has to be broke to open the CD case.

Also, cheers for the info about the reg keys in the "uninstall" key of registry. I'd be ripping my hair out by now trying to find why the error message was appearing whenever I ran the installed package.
Answered 09/22/2004 by: hayesey
Yellow Belt

Please log in to comment
1
if you are getting 1911 error, note down the file name for which it is giving an error, go to tables --> typelib, you will find the file name in there. just delete it. Your problem will be solved. If you are unable to find the file name then go with the component GUID.
Answered 09/22/2004 by: MSIram
Senior Yellow Belt

Please log in to comment
1
>MSIMaker wrote:
>At a guess I'm thinking that the font is system installed correctly but for some reason on >a User basis it is invalid. What happens if you install it to a clean system as admin and >run the app?

When I install "clean" install with admin rights its working correctly. When i try use IS Repackager utility and "capture" setup its "sniffs" these some filenames incorrectly. My own fix was rename all IS badly "sniffed" files manually in IS. (Its quite job because there was about 30-50 files with wrong filename.)
Answered 09/27/2004 by: saarja
Senior Yellow Belt

Please log in to comment
1
I've created a SnapShot for PhotoShop CS, and was able to repair the Snap using info from Neldog2.

I've located the needed Uninstall key and inserted it into my Novell Zen Snapshot, and as you said it did work. I'm much oblieged for this information. :)

My version of a repackager also doesn't seem to capture the Unstall information which is where Adobe seems to be storing its registration info, and it needs this to run.

With that key exported from the working machine where I built the Snap, and then used it on the one where the Snap recently had been run and it fixed it. I was able to include the needed registry info in my snapshot so on furture runs it lays this much needed key down onto the hard drive and Adobe PhotoShop CS works.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{EFB21DE7-8C19-4A88-BB28-A766E16493BC}]


**************************Entire Key Shown Below*************************
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{EFB21DE7-8C19-4A88-BB28-A766E16493BC}]
"DisplayVersion"="CS"
"HelpLink"=""
"HelpTelephone"=""
"InstallLocation"="C:\\Program Files\\Adobe\\Photoshop CS"
"InstallSource"="D:\\Photoshop\\"
"ProductID"="XXXXXXXXXXXXXXXXX"
"Serial"="xxxxxxxxxxxxxxxxxxxxxxx"
"Publisher"="Adobe Systems, Inc."
"RegCompany"="gisd"
"RegOwner"="garlandisd garlandisd"
"URLInfoAbout"="http://www.adobe.com/photoshop"
"URLUpdateInfo"="http://www.adobe.com/photoshop"
"VersionMajor"=dword:00000008
"VersionMinor"=dword:00000000
"DisplayName"="Adobe Photoshop CS"
"DisplayIcon"="C:\\Program Files\\Adobe\\Photoshop CS\\Photoshop.exe,0"
"Language"="en_US"
"UninstallString"="RunDll32 C:\\PROGRA~1\\COMMON~1\\INSTAL~1\\PROFES~1\\RunTime\\0701\\Intel32\\Ctor.dll,LaunchSetup \"C:\\Program Files\\InstallShield Installation Information\\{EFB21DE7-8C19-4A88-BB28-A766E16493BC}\\setup.exe\" -l0x9 "
"LogFile"="C:\\Program Files\\InstallShield Installation Information\\{EFB21DE7-8C19-4A88-BB28-A766E16493BC}\\setup.ilg"
"ProductGuid"="{EFB21DE7-8C19-4A88-BB28-A766E16493BC}"
"Version"=dword:08000000
"MajorVersion"=dword:00000008
"MinorVersion"=dword:00000000
"LogMode"=dword:00000001
Answered 11/17/2004 by: frankts
Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity