Howdie,

I am making a reflection9 msi package with wise package studio 4.6 on windows 2003 terminal server. I do this by making a snapshot before and after the installation and then compile all seperate files to one msi file.

It succeeds, but when I install with that reflection9.msi, I receive one error: error 1911: could not register type library for file .....\r2winlib.tlb.

How could I resolve this?

Many thanks for your reply!

BK
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

0
Hi,
Wise sets these files some times to try and self register, but the .TLB files don't need to be, so just open the msi find the file and select "Do not register", I'd do a check to make sure there are no other .TLB's in the package as well.
Good luck,
Answered 08/17/2004 by: WiseMonkey3
Senior Yellow Belt

Please log in to comment
0
The most common reasons for file registration errors are:

1) You are missing a dependant file,
2) Other existing files need to be registered first (registration order),
3) Your file cannot be registered using an API call and you must use RegSvr32.exe, and
4) as WiseMonkey pointed out, sometimes Wise, seeing that the self-registration bit in a file has been turned on, tries to register the file, when it shouldn't really be registered at all (not Wise's fault).

Good luck!

- Sean Roberts
Answered 08/17/2004 by: sean_c_roberts
Senior Purple Belt

Please log in to comment
0
Hi,
sometimes .tlb's do need to be registered, but in general they are registered during the launch of the application. If this is the case, do as WiseMonkey3 says and choose 'Do not Register' from the SelfRegistration tab.
If this is not the case, (you can only know by launching the app after installation) you should use REGTLIB.exe instead of REGSVR32.exe as a custom action at the end of the installation sequence, but before InstallFinalise.

Enjoy,
CR.
Answered 08/19/2004 by: cronayne
Yellow Belt

Please log in to comment
0
Any suggestions on how to proceed if yout TLB is NOT set to self-register? I am dealing with a package where the TLB is not set to self-register, but I am still getting this 1911 error.

Thanks,
Brian
Answered 11/19/2004 by: bsmtih530
Yellow Belt

Please log in to comment
0
You can use the Regtlib.exe to register TypeLib using a custom action.

Error 1911 - remove those entries from the TypeLib Table and test your recompiled .MSI.
Answered 11/19/2004 by: oofemioo
Blue Belt

Please log in to comment
0
I am having a similar problem when trying to package SQL Server 2000 Client components. I am getting error 1911, Could not register autoplt.rll.

Can anyone please help with my specific problem?
Answered 05/16/2005 by: ricaldo
Senior Yellow Belt

Please log in to comment
0
ORIGINAL: ricaldo

I am having a similar problem when trying to package SQL Server 2000 Client components. I am getting error 1911, Could not register autoplt.rll.

Can anyone please help with my specific problem?



I am getting the same thing when packaging the Server 2000 Client Components using Adminstudio 7.0 SMS edition. Can someone provide any insight.
Answered 06/15/2006 by: tippie2000
Yellow Belt

Please log in to comment
0
Hi,
I am also facing a similar kind of problem when packaging SQL Client 2000 Standard using WISE packaging Studio 7.

I am getting th error number as :1904

Error 1904: Module C:\ProgramFiles\Microsoft SQL Server\ 80\Tools\Bin\Resources\1033\sqlvdir.rll failed to register. HRESULT - 2147024769.

So i tried to reigister this file manually by using regsvr32 command which again gave me an error saying that it is not a .DLL or .OCX . So it cannot be registered.

How can i solve this issue? If you have found a solution or a way to resolve this, please share it. It would be of gr8 help.

Thanks,
elziarun.
Answered 11/28/2007 by: elziarun
Senior Yellow Belt

Please log in to comment
0
sqlvdir.rll

If ur selfreg tablee has entry sqlvdir.rll then remove it.It will work.
Answered 01/10/2008 by: sumeetgjain
Senior Yellow Belt

Please log in to comment
0
Hi Sumeetgjain,

I have a file acrobat.tlb that has the self registration feature set to "Do not register" and this file is not in the SelfReg table. I get the 1911 error when I install the msi on a test machine. Any ideas on what can be done to solve this?

Thanks.
Answered 04/02/2008 by: copycobol
Senior Yellow Belt

Please log in to comment
0
Look for hints in the TypeLib table.
Answered 04/03/2008 by: AngelD
Red Belt

Please log in to comment
0
Hi AngelD,

Sorry AngelD I don't know what I should be looking for. I checked the table and nothing seemed to be unusual.
I have copied below the entry of the acrobat.tlb from the Typelib Table.

"{E64169B3-3592-47D2-816E-602C5C13F328}","0","257","Acrobat","Complete","acrobat.tlb","","0"

Also

How can I create a custom action (using MSI Script tab) to register this file? I checked the Windows Installer SDK help but didnt find anything there or I should say Couldn't figure out what to do. (Sorry, never used the MSI script before)

Thanks very much for your help.

Regards.
Answered 04/03/2008 by: copycobol
Senior Yellow Belt

Please log in to comment
0
ORIGINAL: copycobol
I have a file acrobat.tlb that has the self registration feature set to "Do not register" and this file is not in the SelfReg table. I get the 1911 error when I install the msi on a test machine. Any ideas on what can be done to solve this?
The only other way this could be happening is if the file is being registered via a Custom Action.

Run the install with a verbose log. When the 1911 error appears, open the log file in a text editor. Use something other than Notepad as NP is unable to open files with locks on. At the foot of the log you'll find the name of the Custom Action. Then you need to determine what that CA is doing (i.e. what EXE it's running) and why it's failing to register the TLB. I'm willing to wager that there is a missing dependency, neatly highlighting the idiocy of registering files via CAs. I didn't think Adobe did that, though....
Answered 04/04/2008 by: VBScab
Red Belt

Please log in to comment
0
Hi VBScab,

I ran the installation with the verbose mode and this is the bit of the log file where it brings up the Error 1911

RegisterTypeLibraries: LibID: {78165D71-DF28-11D3-9A89-005004A56D53}
MSI (s) (08:3C) [15:26:20:406]: QueryPathOfRegTypeLib returned 0 in local context. Path is 'C:\Program Files\Adobe\Acrobat 7.0\Acrobat\acrobat.tlb'
RegisterTypeLibraries: LibID: {78165D71-DF28-11D3-9A89-005004A56D53}
MSI (s) (08:3C) [15:26:20:406]: Note: 1: 1402 2: UNKNOWN\TypeLib\{78165D71-DF28-11D3-9A89-005004A56D53}\100.0\0\win32 3: 2
MSI (s) (08:3C) [15:26:20:406]: CMsiServices::ProcessTypeLibrary runs in local context, not impersonated.
MSI (s) (08:3C) [15:26:20:500]: ProcessTypeLibraryCore returns: -2147312566. (0 means OK)
MSI (s) (08:3C) [15:26:20:500]: could not find the authored LIBID {78165D71-DF28-11D3-9A89-005004A56D53} and/or the locale 0 in the type library C:\Program Files\Adobe\Acrobat 7.0\Acrobat\acrobat.tlb
MSI (s) (08:3C) [15:26:20:500]: Note: 1: 2107 2: C:\Program Files\Adobe\Acrobat 7.0\Acrobat\acrobat.tlb 3: -2147312566
Info 1912. Could not unregister type library for file C:\Program Files\Adobe\Acrobat 7.0\Acrobat\acrobat.tlb. Contact your support personnel.
MSI (s) (08:3C) [15:26:20:515]: CMsiServices::ProcessTypeLibrary runs in local context, not impersonated.
MSI (s) (08:3C) [15:26:20:515]: ProcessTypeLibraryCore returns: -2147312566. (0 means OK)
MSI (s) (08:3C) [15:26:20:515]: could not find the authored LIBID {78165D71-DF28-11D3-9A89-005004A56D53} and/or the locale 0 in the type library C:\Program Files\Adobe\Acrobat 7.0\Acrobat\acrobat.tlb
MSI (s) (08:3C) [15:26:20:515]: Note: 1: 2108 2: C:\Program Files\Adobe\Acrobat 7.0\Acrobat\acrobat.tlb 3: -2147312566
DEBUG: Error 2835: The control ErrorIcon was not found on dialog ErrorDialog
Internal Error 2835. ErrorIcon, ErrorDialog

I found that in the TYPELIB table there are 2 entries for the acrobat.tlb, I deleted the first entry and compiled it. During the installation of the msi I didnt get any errors. Is this the right way to deal with an issue like this? Is there any other way to fix the two entries in the TYPELIB table? Please advise.

Thanks again for your help.

Regards
Answered 04/07/2008 by: copycobol
Senior Yellow Belt

Please log in to comment
0
Also I noticed that in the Setup Editor --> Components Tab --> Acrobat.exe is red, when I select "Show Errors" it says "Has as advertised shortcut and the keypath isn't a file in the component".

I tried to make a key a primary key but that hasnt helped much. Acrobat.exe still shows up in red. How can I fix this?
Answered 04/08/2008 by: copycobol
Senior Yellow Belt

Please log in to comment
0
ORIGINAL: copycobol
Also I noticed that in the Setup Editor --> Components Tab --> Acrobat.exe is red, when I select "Show Errors" it says "Has as advertised shortcut and the keypath isn't a file in the component".

I tried to make a key a primary key but that hasnt helped much. Acrobat.exe still shows up in red. How can I fix this?
Don't worry about it. Adobe's MSIs are a law unto themselves and best left as unmolested as possible. Almost all major vendor's MSIs will show what would normally be regarded as glaring errors: we just live with them and tut-tut quietly to ourselves whilst revelling in our superior packaging skills. LOL...

Coming to the 1911 error, the return value from the ProcessTypeLibraryCore Custom Action is -2147312566. That converts to hex 80029C4A. Looking at the Windows error header file, winerror.h:

// MessageId: TYPE_E_CANTLOADLIBRARY
//
// MessageText:
//
// Error loading type library/DLL.
//
#define TYPE_E_CANTLOADLIBRARY _HRESULT_TYPEDEF_(0x80029C4AL)
- Does Acrobat.TLB exist at 'C:\Program Files\Adobe\Acrobat 7.0\Acrobat' when that CA is executed?
- Have you tried registering the TLB manually before running the install or better, run the MSI through your authoring tool's debugger, set a break-point on the CA and register the TLB before continuing. You can register TLBs with REGTLIB, which can be d/l from various places but in any event is part of the Platform SDK, which is a free d/l from Microsoft. Run REGTLIB with ProcMon running alongside so that any errors such as missing dependencies are highlighted.
- The line with the text "could not find the authored LIBID {78165D71-DF28-11D3-9A89-005004A56D53} and/or the locale 0 in the type library" troubles me. I wonder whether there's a language/locale conflict here? Are you installing, say, US English Acrobat on to some other language/locale flavour of XP?
Answered 04/08/2008 by: VBScab
Red Belt

Please log in to comment
0
Hi VBScab,

Thanks for the reply. Relieved to know that I can ignore the red components for ADOBE MSIs.

THe ACROBAT.TLB file exists while the error 1911 message is displayed. I can successfully register the file using the regtlibv12 manually. I don't know how to register the files using a custom action. I red the SDK help menu and from my understanding I have to add an entry to the custom action table. I am bit lost there. How do I add an entry that registers the ACROBAT.TLB file?

I am installing an US English Acrobat in English (Australia) version of XP Pro.

I am not sure if the following method is the right way to fix the problem. As the TYPELIB table had two entries for ACROBAT.TLB file, I deleted the entry that had this LIBID {78165D71-DF28-11D3-9A89-005004A56D53}. It seems that this has fixed the problem. Not sure if this is the right way. Please let me know your thoughts on this.

Also I had to add the files msvcp71.dll and msvcr71.dll from the source PC (C:\Windows\System32\) to the Destination Computer and compile it. The MSI worked, was able to create pdf files without any issues.

Thanks again for your help with this.
Answered 04/09/2008 by: copycobol
Senior Yellow Belt

Please log in to comment
0
I don't think it's too much of a stretch to say that you can ignore all errors in vendor MSIs. Most QA folk will allow them, since fixing them involves futzing with the MSI itself, something which is recognised as A Very Bad Thing. You should obviously not introduce errors in any transform you apply to that MSI, however. I presume (hope!) you're using a transform to apply your changes?

Does the file register properly at the time the error is displayed, though? Registration failure is normally down to one of two things: missing dependencies or insufficient file/registry access rights so use ProcMon to show you file- and registry-wise what's going on when the error occurs.

Coming to Custom Action creation, I see your authoring tool is WPS:
- Add the registration EXE to your installation directly as a file
- Select 'MSI Script'
- Select the 'Execute Deferred' tab
- Choose 'If Statement'
- Add the condition 'If Not Installed'
- Choose 'Execute Program From Installation'
- Give the CA a name. I normally make the name reflect what the CA does with a suffix indicating where in the sequence the CA is, e.g. RegisterAcrobatTLB_ED (this just makes things easier if you're editing the tables directly as some point in the future)
- Browse to the registration EXE
- Add the command line argument:
[put the directory name where the TLB lives here, enclosed in square brackets]ACROBAT.TLB. Strictly speaking, you should use the name of the component here but let's keep it simple for now.
- Click OK

To be PC, we should add an 'unregister' CA which would be run on uninstallation but again, let's keep it simple for now.

Re: the locale question, that may be a red herring.

As for the 2 table entries, I missed that point. I'd leave the entries well alone.

The two MS runtime files....we (the forum members) could debate forever whether these should be in a merge module. Most of my clients use MMs so I have to go with the flow. Alternatively, they could be added to your build. It's strikes me as odd that the MSI doesn't include them if the application requires them...it's ages since I played with Acrobat so I can't recall its requirements in that area.
Answered 04/10/2008 by: VBScab
Red Belt

Please log in to comment
0
Thanks very much for taking time to give me a step by step instructions on Custom Action.

At the time of the error , the file acrobat.tlb is registered and I can find the file registered under the TYPELIB {78165D71-DF28-11D3-9A89-005004A56D53}.

I used Promon to find out what as happening but didnt really get what it was saying. Following entries were in the Procmon where the installation failed.











483218
14:53.1
msiexec.exe
1260
RegCloseKey
HKCR\TypeLib\{78165D71-DF28-11d3-9A89-005004A56D53}\1.0\HELPDIR
SUCCESS


483219
14:53.1
msiexec.exe
1260
CreateFile
C:\Program Files\Adobe\Acrobat 7.0\Acrobat\acrobat.tlb
SUCCESS
Desired Access: Generic Read, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Random Access, Attributes: n/a, ShareMode: Read, AllocationSize: n/a, OpenResult: Opened

483220
14:53.1
msiexec.exe
1260
ReadFile
C:\Program Files\Adobe\Acrobat 7.0\Acrobat\acrobat.tlb
SUCCESS
Offset: 0, Length: 64

483221
14:53.1
msiexec.exe
1260
QueryStandardInformationFile
C:\Program Files\Adobe\Acrobat 7.0\Acrobat\acrobat.tlb
SUCCESS
AllocationSize: 36,864, EndOfFile: 35,992, NumberOfLinks: 1, DeletePending: False, Directory: False

483223
14:53.1
msiexec.exe
1260
QueryStandardInformationFile
C:\Program Files\Adobe\Acrobat 7.0\Acrobat\acrobat.tlb
SUCCESS
AllocationSize: 36,864, EndOfFile: 35,992, NumberOfLinks: 1, DeletePending: False, Directory: False

483227
14:53.1
msiexec.exe
1260
CreateFile
C:\Program Files\Adobe\Acrobat 7.0\Acrobat\acrobat.tlb\2
PATH NOT FOUND
Desired Access: Generic Read, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Random Access, Attributes: n/a, ShareMode: Read, AllocationSize: n/a

483228
14:53.1
msiexec.exe
1260
CreateFile
C:\Program Files\Adobe\Acrobat 7.0\Acrobat\acrobat.tlb
SUCCESS
Desired Access: Generic Read, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Random Access, Attributes: n/a, ShareMode: Read, AllocationSize: n/a, OpenResult: Opened

483229
14:53.1
msiexec.exe
1260
ReadFile
C:\Program Files\Adobe\Acrobat 7.0\Acrobat\acrobat.tlb
SUCCESS
Offset: 0, Length: 64

483230
14:53.1
msiexec.exe
1260
CloseFile
C:\Program Files\Adobe\Acrobat 7.0\Acrobat\acrobat.tlb
SUCCESS


483232
14:53.1
msiexec.exe
1260
QueryOpen
C:\Program Files\Adobe\Acrobat 7.0\Acrobat\acrobat.tlb\2
PATH NOT FOUND

483233
14:53.1
msiexec.exe
1260
QueryOpen
C:\Program Files\Adobe\Acrobat 7.0\Acrobat\acrobat.tlb
SUCCESS
CreationTime: 12/01/2006 9:13:24 PM, LastAccessTime: 11/04/2008 11:14:53 AM, LastWriteTime: 12/01/2006 9:13:24 PM, ChangeTime: 11/04/2008 11:14:19 AM, AllocationSize: 36,864, EndOfFile: 35,992, FileAttributes: A

483234
14:53.1
msiexec.exe
1260
QueryOpen
C:\Program Files\Adobe\Acrobat 7.0\Acrobat\acrobat.tlb
SUCCESS
CreationTime: 12/01/2006 9:13:24 PM, LastAccessTime: 11/04/2008 11:14:53 AM, LastWriteTime: 12/01/2006 9:13:24 PM, ChangeTime: 11/04/2008 11:14:19 AM, AllocationSize: 36,864, EndOfFile: 35,992, FileAttributes: A

483235
14:53.1
msiexec.exe
1260
CreateFile
C:\Program Files\Adobe\Acrobat 7.0\Acrobat\acrobat.tlb
SUCCESS
Desired Access: Generic Read, Write Attributes, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Attributes: n/a, ShareMode: Read, Write, AllocationSize: n/a, OpenResult: Opened

483236
14:53.1
msiexec.exe
1260
SetBasicInformationFile
C:\Program Files\Adobe\Acrobat 7.0\Acrobat\acrobat.tlb
SUCCESS
CreationTime: 1/01/1601 9:59:59 AM, LastAccessTime: 1/01/1601 9:59:59 AM, LastWriteTime: 1/01/1601 9:59:59 AM, ChangeTime: 1/01/1601 9:59:59 AM, FileAttributes: n/a

483237
14:53.1
msiexec.exe
1260
ReadFile
C:\Program Files\Adobe\Acrobat 7.0\Acrobat\acrobat.tlb
SUCCESS
Offset: 0, Length: 512

483238
14:53.1
msiexec.exe
1260
ReadFile
C:\Program Files\Adobe\Acrobat 7.0\Acrobat\acrobat.tlb
SUCCESS
Offset: 0, Length: 8

483239
14:53.1
msiexec.exe
1260
ReadFile
C:\Program Files\Adobe\Acrobat 7.0\Acrobat\acrobat.tlb
SUCCESS
Offset: 0, Length: 12

483240
14:53.1
msiexec.exe
1260
RegOpenKey
HKCR\.tlb
SUCCESS
Desired Access: Read

483241
14:53.1
msiexec.exe
1260
RegQueryValue
HKCR\.tlb\(Default)
NAME NOT FOUND
Length: 144

483242
14:53.1
msiexec.exe
1260
RegCloseKey
HKCR\.tlb
SUCCESS


483243
14:53.1
msiexec.exe
1260
CloseFile
C:\Program Files\Adobe\Acrobat 7.0\Acrobat\acrobat.tlb
SUCCESS


483245
14:53.1
msiexec.exe
1260
QueryOpen
C:\Program Files\Adobe\Acrobat 7.0\Acrobat\acrobat.tlb
SUCCESS
CreationTime: 12/01/2006 9:13:24 PM, LastAccessTime: 11/04/2008 11:14:53 AM, LastWriteTime: 12/01/2006 9:13:24 PM, ChangeTime: 11/04/2008 11:14:19 AM, AllocationSize: 36,864, EndOfFile: 35,992, FileAttributes: A

483246
14:53.1
msiexec.exe
1260
CreateFile
C:\Program Files\Adobe\Acrobat 7.0\Acrobat\acrobat.tlb
SUCCESS
Desired Access: Generic Read, Write Attributes, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Attributes: n/a, ShareMode: Read, Write, AllocationSize: n/a, OpenResult: Opened

483247
14:53.1
msiexec.exe
1260
SetBasicInformationFile
C:\Program Files\Adobe\Acrobat 7.0\Acrobat\acrobat.tlb
SUCCESS
CreationTime: 1/01/1601 9:59:59 AM, LastAccessTime: 1/01/1601 9:59:59 AM, LastWriteTime: 1/01/1601 9:59:59 AM, ChangeTime: 1/01/1601 9:59:59 AM, FileAttributes: n/a

483248
14:53.1
msiexec.exe
1260
ReadFile
C:\Program Files\Adobe\Acrobat 7.0\Acrobat\acrobat.tlb
SUCCESS
Offset: 0, Length: 512

483249
14:53.1
msiexec.exe
1260
ReadFile
C:\Program Files\Adobe\Acrobat 7.0\Acrobat\acrobat.tlb
SUCCESS
Offset: 0, Length: 8

483250
14:53.1
msiexec.exe
1260
ReadFile
C:\Program Files\Adobe\Acrobat 7.0\Acrobat\acrobat.tlb
SUCCESS
Offset: 0, Length: 12

483251
14:53.1
msiexec.exe
1260
RegOpenKey
HKCR\.tlb
SUCCESS
Desired Access: Read

483252
14:53.1
msiexec.exe
1260
RegQueryValue
HKCR\.tlb\(Default)
NAME NOT FOUND
Length: 144

483253
14:53.1
msiexec.exe
1260
RegCloseKey
HKCR\.tlb
SUCCESS


483254
14:53.1
msiexec.exe
1260
CloseFile
C:\Program Files\Adobe\Acrobat 7.0\Acrobat\acrobat.tlb
SUCCESS


483256
14:53.1
msiexec.exe
1260
CloseFile
C:\Program Files\Adobe\Acrobat 7.0\Acrobat\acrobat.tlb
SUCCESS


483258
14:53.1
msiexec.exe
1260
ReadFile
C:\WINDOWS\Installer\24a672.msi
SUCCESS
Offset: 49,920, Length: 256

483260
14:53.1
msiexec.exe
1260
ReadFile
C:\WINDOWS\Installer\24a672.msi
SUCCESS
Offset: 50,688, Length: 220

483262
14:53.1
msiexec.exe
1268
RegOpenKey
HKLM\Software\Policies\Microsoft\Windows\Installer
SUCCESS
Desired Access: Read

483263
14:53.1
msiexec.exe
1268
RegQueryValue
HKLM\SOFTWARE\Policies\Microsoft\Windows\Installer\Logging
NAME NOT FOUND
Length: 144

483264
14:53.1
msiexec.exe
1268
RegCloseKey
HKLM\SOFTWARE\Policies\Microsoft\Windows\Installer
SUCCESS


483265
14:53.1
msiexec.exe
1268
QueryOpen
C:\Documents and Settings\CleanVMUser\Local Settings\Temp
SUCCESS
CreationTime: 21/02/2008 9:29:19 AM, LastAccessTime: 11/04/2008 11:12:40 AM, LastWriteTime: 11/04/2008 11:12:40 AM, ChangeTime: 11/04/2008 11:12:40 AM, AllocationSize: 0, EndOfFile: 0, FileAttributes: D

483266
14:53.1
msiexec.exe
1268
QueryOpen
C:\Documents and Settings\CleanVMUser\Local Settings\Temp\MSI14b72.LOG
NAME NOT FOUND

483267
14:53.1
msiexec.exe
1268
CreateFile
C:\Documents and Settings\CleanVMUser\Local Settings\Temp\MSI14b72.LOG
SUCCESS
Desired Access: Generic Write, Read Attributes, Disposition: Create, Options: Synchronous IO Non-Alert, Non-Directory File, Open No Recall, Attributes: N, ShareMode: Read, AllocationSize: 0, OpenResult: Created

483268
14:53.1
msiexec.exe
1268
CloseFile
C:\Documents and Settings\CleanVMUser\Local Settings\Temp\MSI14b72.LOG
SUCCESS


483270
14:53.1
msiexec.exe
1268
CreateFile
C:\Documents and Settings\CleanVMUser\Local Settings\Temp\MSI14b72.LOG
SUCCESS
Desired Access: Generic Write, Read Attributes, Disposition: OverwriteIf, Options: Non-Directory File, Open No Recall, Attributes: N, ShareMode: Read, Write, AllocationSize: 0, OpenResult: Overwritten

483271
14:53.1
msiexec.exe
1268
CreateFile
C:\Documents and Settings\CleanVMUser\Local Settings\Temp
SUCCESS
Desired Access: Synchronize, Disposition: Open, Options: Directory, Synchronous IO Non-Alert, Open For Backup, Attributes: N, ShareMode: Read, Write, AllocationSize: n/a, OpenResult: Opened

483272
14:53.1
msiexec.exe
1268
CloseFile
C:\Documents and Settings\CleanVMUser\Local Settings\Temp
SUCCESS


483274
14:53.2
msiexec.exe
1268
WriteFile
C:\Documents and Settings\CleanVMUser\Local Settings\Temp\MSI14b72.LOG
SUCCESS
Offset: 0, Length: 2

483275
14:53.2
msiexec.exe
1268
RegOpenKey
HKLM\Software\Policies\Microsoft\Windows\Installer
SUCCESS
Desired Access: Read

483276
14:53.2
msiexec.exe
1268
RegQueryValue
HKLM\SOFTWARE\Policies\Microsoft\Windows\Installer\Debug
NAME NOT FOUND
Length: 144

483277
14:53.2
msiexec.exe
1268
RegCloseKey
HKLM\SOFTWARE\Policies\Microsoft\Windows\Installer
SUCCESS


483278
14:53.2
msiexec.exe
1268
RegOpenKey
HKLM\Software\Microsoft\Windows NT\CurrentVersion\FontSubstitutes
SUCCESS
Desired Access: Read

483279
14:53.2
msiexec.exe
1268
RegQueryValue
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\FontSubstitutes\Tahoma
NAME NOT FOUND
Length: 144

483280
14:53.2
msiexec.exe
1268
RegCloseKey
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\FontSubstitutes
SUCCESS


483281
14:53.2
msiexec.exe
1268
ReadFile
C:\WINDOWS\system32\msihnd.dll
SUCCESS
Offset: 152,576, Length: 12,288, I/O Flags: Non-cached, Paging I/O, Synchronous Paging I/O

483282
14:53.2
msiexec.exe
1268
ReadFile
C:\WINDOWS\system32\msihnd.dll
SUCCESS
Offset: 276,992, Length: 16,384, I/O Flags: Non-cached, Paging I/O, Synchronous Paging I/O

483283
14:53.2
msiexec.exe
1268
ReadFile
C:\Documents and Settings\CleanVMUser\Local Settings\Temp\214b70.msi
SUCCESS
Offset: 46,848, Length: 60

483285
14:53.2
msiexec.exe
1268
ReadFile
C:\Documents and Settings\CleanVMUser\Local Settings\Temp\214b70.msi
SUCCESS
Offset: 493,221,248, Length: 128

483287
14:53.2
msiexec.exe
1268
ReadFile
C:\Documents and Settings\CleanVMUser\Local Settings\Temp\214b70.msi
SUCCESS
Offset: 493,221,888, Length: 690

483290
14:53.2
msiexec.exe
1268
ReadFile
C:\Documents and Settings\CleanVMUser\Local Settings\Temp\214b70.msi
SUCCESS
Offset: 49,920, Length: 256

483292
14:53.2
msiexec.exe
1268
ReadFile
C:\Documents and Settings\CleanVMUser\Local Settings\Temp\214b70.msi
SUCCESS
Offset: 50,688, Length: 220

483294
14:53.2
msiexec.exe
1268
QueryOpen
C:\WINDOWS\system32\msimsg.dll
SUCCESS
CreationTime: 4/08/2004 12:56:18 AM, LastAccessTime: 21/02/2008 9:11:17 AM, LastWriteTime: 4/08/2004 12:56:18 AM, ChangeTime: 21/02/2008 7:38:58 PM, AllocationSize: 884,736, EndOfFile: 884,736, FileAttributes: A

483295
14:53.2
msiexec.exe
1268
CreateFile
C:\WINDOWS\system32\msimsg.dll
SUCCESS
Desired Access: Generic Read, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Attributes: n/a, ShareMode: Read, Delete, AllocationSize: n/a, OpenResult: Opened

483297
14:53.2
msiexec.exe
1268
QueryStandardInformationFile
C:\WINDOWS\system32\msimsg.dll
SUCCESS
AllocationSize: 884,736, EndOfFile: 884,736, NumberOfLinks: 1, DeletePending: False, Directory: False

483301
14:53.2
msiexec.exe
1268
CloseFile
C:\WINDOWS\system32\msimsg.dll
SUCCESS


483302
14:53.2
msiexec.exe
1268
ReadFile
C:\WINDOWS\system32\msimsg.dll
SUCCESS
Offset: 0, Length: 32,768, I/O Flags: Non-cached, Paging I/O, Synchronous Paging I/O

483303
14:53.2
msiexec.exe
1268
RegOpenKey
HKCU
SUCCESS
Desired Access: Maximum Allowed

483304
14:53.2
msiexec.exe
1268
RegOpenKey
HKCU\Software\Policies\Microsoft\Control Panel\Desktop
NAME NOT FOUND
Desired Access: Read

483305
14:53.2
msiexec.exe
1268
RegOpenKey
HKCU\Control Panel\Desktop
SUCCESS
Desired Access: Read

483306
14:53.2
msiexec.exe
1268
RegQueryValue
HKCU\Control Panel\Desktop\MultiUILanguageId
NAME NOT FOUND
Length: 256

483307
14:53.2
msiexec.exe
1268
RegCloseKey
HKCU\Control Panel\Desktop
SUCCESS


483308
14:53.2
msiexec.exe
1268
RegCloseKey
HKCU
SUCCESS


483309
14:53.2
msiexec.exe
1268
ReadFile
C:\WINDOWS\system32\msi.dll
SUCCESS
Offset: 1,767,424, Length: 9,216, I/O Flags: Non-cached, Paging I/O, Synchronous Paging I/O

483310
14:53.2
msiexec.exe
1268
ReadFile
C:\WINDOWS\system32\msi.dll
SUCCESS
Offset: 161,280, Length: 32,768, I/O Flags: Non-cached, Paging I/O, Synchronous Paging I/O

483339
14:53.2
msiexec.exe
1268
QueryOpen
C:\WINDOWS\system32\MSIMTF.dll
SUCCESS
CreationTime: 4/08/2004 12:56:44 AM, LastAccessTime: 11/04/2008 11:14:44 AM, LastWriteTime: 4/08/2004 12:56:44 AM, ChangeTime: 21/02/2008 7:38:58 PM, AllocationSize: 159,744, EndOfFile: 159,232, FileAttributes: A

483340
14:53.2
msiexec.exe
1268
CreateFile
C:\WINDOWS\system32\MSIMTF.dll
SUCCESS
Desired Access: Execute/Traverse, Synchronize, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Attributes: n/a, ShareMode: Read, Delete, AllocationSize: n/a, OpenResult: Opened

483342
14:53.2
msiexec.exe
1268
QueryStandardInformationFile
C:\WINDOWS\system32\MSIMTF.dll
SUCCESS
AllocationSize: 159,744, EndOfFile: 159,232, NumberOfLinks: 1, DeletePending: False, Directory: False

483346
14:53.2
msiexec.exe
1268
CloseFile
C:\WINDOWS\system32\MSIMTF.dll
SUCCESS


484428
15:02.6
MsiExec.exe
1916
Thread Exit

SUCCESS
User Time: 0.0000000, Kernel Time: 0.0000000

484962
15:55.4
msiexec.exe
1260
Thread Exit

SUCCESS
User Time: 0.0000000, Kernel Time: 0.0156250


I did the custom action as you directed. The Custom action reads like this:

If Not Installed then
Execute Program From Installation Command Line [Acrobat]acrobat.tlb [RegisterAcrobatTlb_ED]
End

I still get the error 1911 on the same file. Any other ways to fix this issue?

Thanks very much for your assistance.
Answered 04/10/2008 by: copycobol
Senior Yellow Belt

Please log in to comment
0
ORIGINAL: copycobol
I did the custom action as you directed. The Custom action reads like this:

If Not Installed then
Execute Program From Installation Command Line [Acrobat]acrobat.tlb [RegisterAcrobatTlb_ED]
End

I still get the error 1911 on the same file. Any other ways to fix this issue?
...almost there. It *looks like* you omitted to tell the CA which executable to run, judging by these entries:

483240 14:53.1 msiexec.exe 1260 RegOpenKey HKCR\.tlb SUCCESS Desired Access: Read
483241 14:53.1 msiexec.exe 1260 RegQueryValue HKCR\.tlb\(Default) NAME NOT FOUND Length: 144
This is Windows trying to work out which EXE to use to open a.TLB file, something it wouldn't have to do if the entire command line were correct. Make sure you specify the EXE to use such that, when you double-click the line 'Execute Program From Installation Command Line [Acrobat]acrobat.tlb [RegisterAcrobatTlb_ED]' the resulting dialog looks like:

___Custom Action Name: RegisterAcrobatTlb_ED
___Executable File: regtlibv12.exe (presumably this file does register the TLB outside of the MSI? Did I ask that already?)
___Command Line: - [put the directory name where the TLB lives here, enclosed in square brackets]ACROBAT.TLB

I realise now that I may have confused you with my original instructions. It's bad practice to hard-code the actual path in CAs. I *meant* you to use the directory name as it appears in the Directory table. So, to find that out:

- Select 'Setup Editor' view
- Select the 'Directory' table
- In the right-hand pane, click the blue highlighted column titled 'Full Directory' so that it gets sorted into alphabetical order
- Find the line 'Program Files\Adobe\Acrobat 7.0\Acrobat'
- Now select the cell in the 'Directory' column of that same row
- Click once so that the text is highlighted
- Right-click and select 'Copy'
- Now return to the 'MSI Script' view
- In the 'Command Line:' text box,
- type a left square bracket
- right-click and choose 'Paste'
- type a right square bracket
- type 'ACROBAT.TLB'

It should now look like this (I have assumed Adobe use the directory name 'ACROBAT':
___Command Line: - [ACROBAT]ACROBAT.TLB

Note that WI resolves property names which are directories to include a trailing backslash, so you don't need to add one.

Try that...
Answered 04/11/2008 by: VBScab
Red Belt

Please log in to comment
0
If your getting a "Cant register type library" error during installation you need to move the typelib entry into the registry table rather than the "Typelib" com table. Microsoft have posted a best practice note that says dont use the Typelib table in an MSI but rather register them via the Registry. I would personally say, use the Typelib table but move the typelib entries out if you have problems.

Just my personal choice tbh but its at least good to know the view from big brother ;)

http://msdn2.microsoft.com/en-us/library/aa372092(VS.85).aspx

They talk about rollback functionality not working correctly if you use the Typelib table although its not something I generally have come across yet but worthy of note for best practice documentation.

Again, the problem your having can be resolved by removing the entry from the typelib table to the registry and never ever ever self reg files via custom actions!

P
Answered 04/11/2008 by: Inabus
Second Degree Green Belt

Please log in to comment
0
ORIGINAL: InabusAgain, the problem your having can be resolved by removing the entry from the typelib table to the registry and never ever ever self reg files via custom actions! Paul, this is a sentiment with which I'd normally wholeheartedly agree and have propogated it here on many occasions (ad nauseum, some might say). The problem we're trying to resolve, though, is in a vendor MSI and an Adobe one to boot. Once we determine whether or not the TLB can be registered at all, we can progress.
Answered 04/11/2008 by: VBScab
Red Belt

Please log in to comment
0
VBScab,
I see no mention that copycobol is using a manufacuter MSI, just because he says Adobe doesnt mean he hasn't snapped shotted it as I highly doudt, however naff adobe is, that they would have a problem like this in a main adobe 7 product.

Also it was kinda hard to find out which topic you where talking about as this post initially talks about refelctions9.msi, then sql and then adobe which is what we are discussing now.

Even if he is using an adobe product MSI, I would still transform it to resolve the problem if it wont deploy into the environment he is working in. Failing that go back to the vendor as this sort of problem, if received via their package, is their responsibility to resolve and not a packagers.

Incidently something I noticed in your TypeLib is the following:

{78165D71-DF28-11d3-9A89-005004A56D53}

Notice the lowercase d in section 11d3? that will potentially prevent the typelib registering correctly, make it an upper case and see if that helps.

Oh and I think:

Could not unregister type library for file C:\Program Files\Adobe\Acrobat 7.0\Acrobat\acrobat.tlb

That problem unregistering is what microsoft are talking about in there reason to not register type library's via the Tylelib table.

And 1 last thing, I couldnt help but notice:

"{E64169B3-3592-47D2-816E-602C5C13F328}","0","257","Acrobat","Complete","acrobat.tlb","","0"

Looks like it is going into the "Complete" feature, if thats the case it will be a snapshot not a vendor :)

Just my 2 cents.

P
Answered 04/11/2008 by: Inabus
Second Degree Green Belt

Please log in to comment
0
Hi Guys,

VBScab, Thank you very much for giving me step by step instruction on how to build the CA. I tried your method but for some reason it still gives me the Error 1911. Is there anything else that I can try?

Inabus, mate I tried your method, deleted the {78165D71-DF28-11D3-9A89-005004A56D53} entry from TYPELIB table and also made sure that the lowercase "d" in 11d3 is changed to 11D3. It installs Acrobat with no issues. But when I try and convert any word document into pdf files it gives me this error message "Unable to find Adobe PDF resource files. Do you want to run the installer in repair mode?"

I tried the solutions that is in the Adobe's KB but none of them worked for me.

I am packaging Acrobat 7.0 with the updates 7.0.5 till 7.0.9. All are .exe files. So I am using the Setup Capture to create the msi file.

Thanks Guys for your help with this.

Regards.
Answered 04/14/2008 by: copycobol
Senior Yellow Belt

Please log in to comment
0
ORIGINAL: Inabus
Looks like it is going into the "Complete" feature, if thats the case it will be a snapshot not a vendor :)
Good spot, Paul. Bingo, bingo, BINGO:
ORIGINAL: copycobol
I am packaging Acrobat 7.0 with the updates 7.0.5 till 7.0.9. All are .exe files. So I am using the Setup Capture to create the msi file.


No, no, no, no, NO! Do NOT capture vendor MSIs unless you have NO alternative. This applies in too many spade-loads to count when dealing with Adobe's MSIs. Although they're supplied as EXEs, they *DO* install from MSIs. What *may* be catching you out when looking for them is that these are extracted to the user's TEMP folder ('C:\Documents and Settings\[UserName]\Local Settings\Temp') which, by default, is hidden (or, at least, its container folder 'Local Settings' is...). Your packaging machine should have this option un-set (as well as having system files visible, and so on). So:

- set your folder options so that you can see ALL files, of ALL types. That includes making file extensions visible.
- clear your TEMP folder of the junk contained therein (which, on a packaging machine, should be empty anyway...)
- run the EXE, up to the point where you get the first dialog with a 'Next' button
- browse your TEMP folder to locate the MSI. It will be named with a random, alphanumeric name
- copy the MSI to your installation point, using a sensible name
- download Adobe's customisation tool and use it to create a transform for your installation
- remember the lesson: do NOT futz with vendor MSIs. ALWAYS use a transform. There will be exceptions but they are few and far between.

Lastly, although you will now be abandoning your captured MSI, coming to this item:
But when I try and convert any word document into pdf files it gives me this error message "Unable to find Adobe PDF resource files. Do you want to run the installer in repair mode?"
In this situation, use ProcMon to monitor what's going on. It will show you straight away what 'resource' is missing and you can then set about fixing it. And yes, I wish I *was* on commssion from SysInternals...I can't help it, though. You cannot do this job without ProcMon, period.
Answered 04/15/2008 by: VBScab
Red Belt

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