Unable to run ComPlus generated Application Proxy on Client

[Howard Pinsley]

I have a DCOM/COM+ application consisting of eighteen
components. Back in the MTS days, the export feature
generated an EXE that could be run on the client to
register the type libraries, appid's etc. needed on the
client to call the remote server. Now, the export feature
generates a MSI install file. When running this file on
the client, I get an error(see below) that translates to
0x80110408 -- which is COMADMIN_E_APP_FILE_READFAIL.

The other error numbers (2945 and 1928) lead me to
Microsoft Knowledge Base Article - 308940 "HOWTO:
Troubleshoot Error 1928 "Error Registering COM+
Application"

I followed all the advice:

I defined my components with BOTH DLLs AND type libraries
so that the application proxy would only distribute the
type libraries (under the assumption that there is a
dependency issue at the root of the problem). The only
DLLs now in the Application proxy are two proxy/stub DLLs
needed for two of the eighteen components.

This did not fix the problem or change the error. The
second part of the article mentions that it might be a
permissions issue. I was skeptical since I am running as
a local administrator. Nevertheless, I tracked the
installation using SysInternal's FileMon (and RegMon). I
didn't find anything that seemed to fail that would cause
the installation to fail with the errors shown below.

I'm all out of ideas?


...
RegisterTypeLibraries: LibID: {5BD11033-46B4-11D3-8228-
00A0C92B9B8D}
Action 19:43:46: RegisterComPlus. Registering COM+
Applications and Components
RegisterComPlus: AppId: {DA629C8E-286E-4917-9191-
167B28274FE5}, AppType: 33, Users: , RSN: KS59
DEBUG: Error 2945: Installation of ComPlus App C:\Program
Files\COMPlus Applications\{DA629C8E-286E-4917-9191-
167B28274FE5}\APL34.tmp failed with error -2146368504.
Internal Error 2945. C:\Program Files\COMPlus
Applications\{DA629C8E-286E-4917-9191-167B28274FE5}
\APL34.tmp, -2146368504
Error 1928. Error registering COM+ Application. Contact
your support personnel for more information.
MSI (s) (98:1C): Product: KDocs (Application Proxy) --
Error 1928. Error registering COM+ Application. Contact
your support personnel for more information.

Action ended 19:44:02: InstallFinalize. Return value 3.

[Slava Gurevich]

Please post OS versions and Service packs verisions for both the
server and the client machines. Did you log in as a member of the
local admin group when you tried installing the COM+ application proxy
on a client?

Slava Gurevich

P.S: As far as I know, the export feature generates both .msi and .exe
files, which can be run on the client.



On Tue, 1 Jul 2003 08:18:28 -0700, "Howard Pinsley"

Post by Howard Pinsley
I have a DCOM/COM+ application consisting of eighteen
components. Back in the MTS days, the export feature
generated an EXE that could be run on the client to
register the type libraries, appid's etc. needed on the
client to call the remote server. Now, the export feature
generates a MSI install file. When running this file on
the client, I get an error(see below) that translates to
0x80110408 -- which is COMADMIN_E_APP_FILE_READFAIL.
The other error numbers (2945 and 1928) lead me to
Troubleshoot Error 1928 "Error Registering COM+
Application"
I defined my components with BOTH DLLs AND type libraries
so that the application proxy would only distribute the
type libraries (under the assumption that there is a
dependency issue at the root of the problem). The only
DLLs now in the Application proxy are two proxy/stub DLLs
needed for two of the eighteen components.
This did not fix the problem or change the error. The
second part of the article mentions that it might be a
permissions issue. I was skeptical since I am running as
a local administrator. Nevertheless, I tracked the
installation using SysInternal's FileMon (and RegMon). I
didn't find anything that seemed to fail that would cause
the installation to fail with the errors shown below.
I'm all out of ideas?
...
RegisterTypeLibraries: LibID: {5BD11033-46B4-11D3-8228-
00A0C92B9B8D}
Action 19:43:46: RegisterComPlus. Registering COM+
Applications and Components
RegisterComPlus: AppId: {DA629C8E-286E-4917-9191-
167B28274FE5}, AppType: 33, Users: , RSN: KS59
DEBUG: Error 2945: Installation of ComPlus App C:\Program
Files\COMPlus Applications\{DA629C8E-286E-4917-9191-
167B28274FE5}\APL34.tmp failed with error -2146368504.
Internal Error 2945. C:\Program Files\COMPlus
Applications\{DA629C8E-286E-4917-9191-167B28274FE5}
\APL34.tmp, -2146368504
Error 1928. Error registering COM+ Application. Contact
your support personnel for more information.
MSI (s) (98:1C): Product: KDocs (Application Proxy) --
Error 1928. Error registering COM+ Application. Contact
your support personnel for more information.
Action ended 19:44:02: InstallFinalize. Return value 3.

[Howard Pinsley]

Post by Slava Gurevich
Please post OS versions and Service packs verisions for both the
server and the client machines. Did you log in as a member of the
local admin group when you tried installing the COM+ application proxy
on a client?
Slava Gurevich
P.S: As far as I know, the export feature generates both .msi and .exe
files, which can be run on the client.

Slava:

I did indeed log in as a local administrator when running the .MSI file.
And I don't find an exe; just a .msi and a .msi.cab.

I created the COM+ package on Windows XP Professional SP1. The client
is Windows 2000 SP2.

Thanks!
Howard

[Jian-Shen Lin[MS]]

You can reverse the order that can works.

For example: Create the proxy package in Win2000 machine, then export to
all clients.

Thanks

Jian shen

This posting is provided "AS IS" with no warranties, and confers no rights.

[Howard Pinsley]

-----Original Message-----
You can reverse the order that can works.
For example: Create the proxy package in Win2000 machine,

then export to

all clients.
Thanks
Jian shen

I just did that. Same problem. What else can I look for?

[John Braham]

I think you need to select the option to preserve com+ 1.0
compatability, to go from xp to 2000, I had the same problem.

John Braham

Post by Howard Pinsley

Post by Slava Gurevich
Please post OS versions and Service packs verisions for both the
server and the client machines. Did you log in as a member of the
local admin group when you tried installing the COM+ application proxy
on a client?
Slava Gurevich
P.S: As far as I know, the export feature generates both .msi and .exe
files, which can be run on the client.

I did indeed log in as a local administrator when running the .MSI file.
And I don't find an exe; just a .msi and a .msi.cab.
I created the COM+ package on Windows XP Professional SP1. The client
is Windows 2000 SP2.
Thanks!
Howard

[Slava Gurevich]

In addition to John Braham's advice, which I think is right on, I
recommend updating your client machine to the most recent SP ( or at
least SP3). There were some bug fixes done that could apply to your
situation.

Regards,

Slava Gurevich

On Tue, 1 Jul 2003 16:57:52 -0400, Howard Pinsley

Post by Howard Pinsley

Post by Slava Gurevich
Please post OS versions and Service packs verisions for both the
server and the client machines. Did you log in as a member of the
local admin group when you tried installing the COM+ application proxy
on a client?
Slava Gurevich
P.S: As far as I know, the export feature generates both .msi and .exe
files, which can be run on the client.

I did indeed log in as a local administrator when running the .MSI file.
And I don't find an exe; just a .msi and a .msi.cab.
I created the COM+ package on Windows XP Professional SP1. The client
is Windows 2000 SP2.
Thanks!
Howard

[Howard Pinsley]

OK, I did two things:

(1) I upgraded my Windows 2000 client to SP4
(2) I exported from my XP machine specifying:
"Save application in COM+ 1.0 format - some properties may be lost"

I'm still getting an error, except now it is E_FAIL instead of
COMADMIN_E_APP_FILE_READFAIL. To get the most information in the log,
I'm running msiexec manually as follows:

msiexec /qf /L*v KDocsProxy.log /I KDocsProxy.msi

Here is the more verbose log. Any other suggestions? This is getting
frustrating... :-(

Thanks!


MSI (s) (F0:50): Executing op: ActionStart
(Name=RegisterComPlus,Description=Registering COM+ Applications and
Components,Template=AppId: , AppType: , Users: , RSN: )
Action 11:44:05: RegisterComPlus. Registering COM+ Applications and
Components
MSI (s) (F0:50): Executing op: ComPlusRegister(AppID={DA629C8E-286E-
4917-9191-167B28274FE5},AplFileName=C:\Program Files\COMPlus
Applications\{DA629C8E-286E-4917-9191-167B28274FE5}\APL13.tmp,AppDir=C:
\Program Files\COMPlus Applications\{DA629C8E-286E-4917
-9191-167B28274FE5}\,AppType=161,,RSN=KS59)
RegisterComPlus: AppId: {DA629C8E-286E-4917-9191-167B28274FE5}, AppType:
161, Users: , RSN: KS59
DEBUG: Error 2945: Installation of ComPlus App C:\Program Files\COMPlus
Applications\{DA629C8E-286E-4917-9191-167B28274FE5}\APL13.tmp failed
with error -2147467259.
Internal Error 2945. C:\Program Files\COMPlus Applications\{DA629C8E-
286E-4917-9191-167B28274FE5}\APL13.tmp, -2147467259
MSI (s) (F0:50): Note: 1: 1928
Error 1928. Error registering COM+ Application. Contact your support
personnel for more information.
MSI (s) (F0:50): Product: KDocs (Application Proxy) -- Error 1928. Error
registering COM+ Application. Contact your support personnel for more
information.

Action ended 11:44:56: InstallFinalize. Return value 3.
MSI (s) (F0:50): User policy value 'DisableRollback' is 0
MSI (s) (F0:50): Machine policy value 'DisableRollback' is 0

[John Braham]

This may sound daft, but make sure there isn't already an application
in component services by that name, it doesn't handle that in my
experience, and make sure none of the interfaces your regisering are
already registered, no other suggestions unfortunatly...

John Braham

Post by Howard Pinsley
(1) I upgraded my Windows 2000 client to SP4
"Save application in COM+ 1.0 format - some properties may be lost"
I'm still getting an error, except now it is E_FAIL instead of
COMADMIN_E_APP_FILE_READFAIL. To get the most information in the log,
msiexec /qf /L*v KDocsProxy.log /I KDocsProxy.msi
Here is the more verbose log. Any other suggestions? This is getting
frustrating... :-(
Thanks!
MSI (s) (F0:50): Executing op: ActionStart
(Name=RegisterComPlus,Description=Registering COM+ Applications and
Components,Template=AppId: , AppType: , Users: , RSN: )
Action 11:44:05: RegisterComPlus. Registering COM+ Applications and
Components
MSI (s) (F0:50): Executing op: ComPlusRegister(AppID={DA629C8E-286E-
4917-9191-167B28274FE5},AplFileName=C:\Program Files\COMPlus
\Program Files\COMPlus Applications\{DA629C8E-286E-4917
-9191-167B28274FE5}\,AppType=161,,RSN=KS59)
161, Users: , RSN: KS59
DEBUG: Error 2945: Installation of ComPlus App C:\Program Files\COMPlus
Applications\{DA629C8E-286E-4917-9191-167B28274FE5}\APL13.tmp failed
with error -2147467259.
Internal Error 2945. C:\Program Files\COMPlus Applications\{DA629C8E-
286E-4917-9191-167B28274FE5}\APL13.tmp, -2147467259
MSI (s) (F0:50): Note: 1: 1928
Error 1928. Error registering COM+ Application. Contact your support
personnel for more information.
MSI (s) (F0:50): Product: KDocs (Application Proxy) -- Error 1928. Error
registering COM+ Application. Contact your support personnel for more
information.
Action ended 11:44:56: InstallFinalize. Return value 3.
MSI (s) (F0:50): User policy value 'DisableRollback' is 0
MSI (s) (F0:50): Machine policy value 'DisableRollback' is 0

[Slava Gurevich]

This post might be inappropriate. Click to display it.

[Howard Pinsley]

Post by Slava Gurevich
Yes, go to the control panel, add/remove programs and make sure the
original proxy is uninstalled.

Post by John Braham
This may sound daft, but make sure there isn't already an application
in component services by that name, it doesn't handle that in my
experience, and make sure none of the interfaces your regisering are
already registered, no other suggestions unfortunatly...
John Braham

That was it! There was indeed a proxy listed in installed programs. I
uninstalled it and then it ran cleanly. Thanks guys!