Hi guys.

A bit of a long shot, I know, but I'm trying to install a bespoke IT software system that uses some COM+ components. Essentially, I export a set of COM+ components as Application Proxies to allow remote clients to connect to a database via COM+.

However, whenever I try and install the exported application, I always get an error 1928 and the MSI fails to install. I've done a search on the net and MSKB where there are a few articles such as How to troubleshoot error 1928 "Error registering COM+ application". But I don't think it's related to that.

The system I'm working on is being installed from scratch and I've created a new domain, joined all the boxes to it. I've tried everything I can think of including trying to install with a domain admin account but still no luck so I don't think it's a permissions problem.

Also interesting is that the exported components work fine on another set of PCs located on another domain! I also tried using another set of exported COM+ components - those which were used on that other domain and tried to install them on my current system, but same error message.

I've done some fairly drastic things such as wipe a dozen servers, fresh install of WS2003, freshly created new domain, etc, but no joy.

Any ideas?

A few screenies

Possibly down to permissions, does the application run anonymously.

I would modify the permissions for com+ and test it again, granting the everyone group the local launch permission, and local activation permission

Does it work on a 2k machine? If so then I agree with F - almost certainly permissions as they were tightened up for 2k3.

ProcMon trace?

Does it work on a 2k machine? If so then I agree with F - almost certainly permissions as they were tightened up for 2k3.

ProcMon trace?

Yep, they removed the launch permissions from the "everyone" group and the IWAM USR account, it's great when they break things by fixing them (my buddies at MS that is)

But I've tried installing them with a local admin account and a domain admin account with no luck, so didn't think it was a permissions issue.

edit: oooh just a though, could it be something twisted like the domain "administrator" account is implicitly given rights, but another account with domain admin rights wouldn't unless explicitly listed? Our previous installs were done with the domain admin account and in an effort of trying to apply some common sense and best practices, I made a copy of the domain admin account and have logged on and tried with this other account, but maybe when it comes to COM+, he doesn't have the rights.....

I'll have a play, making everyone being able to take control over the world and see what havock I can produce

Or does the user who's logged on who exports the COM+ into an application proxy have an impact later on on who can install the produced MSI? Hmm more playing and MD5 checksumming

Edited 10 February, 200917 yr by tfboy

But I've tried installing them with a local admin account and a domain admin account with no luck, so didn't think it was a permissions issue.

installing is not the same as launching mate, seriously, check the Com+ permissions out and grant the 'everyone" group Local / remote launch and local / remote activation permissions.

I get a similar error on a lot of SMS / SCCM systems I have to troubleshoot

This screenshot is from W7 but you find the permissions in the same place from the admin tools on 2k3

I know the defaults and changing the limits.

Question though: when you say installing isn't the same as launching. I'm trying to install an MSI. Does it, at the time I try and install the MSI, check something inside the MSI that could determine whether I have the right to install it or not ?!?

I haven't got to the point of trying to use the application proxy COM+ components to access the database, it's just trying to get the stuff on there in the first place!

Off to have a play.

I know the defaults and changing the limits.

no offence meant Xav, I don't know how "much" you know, and I don't post much in here as I do this crap all day and really can't be that arsed doing any of it in my free time

If the MSI is trying to install COM+ components then it may need to use activation permissions at some point in the install, the app will do that anonymously (well most do) and with the default permissions that will be prevented.

no offence meant Xav, I don't know how "much" you know, and I don't post much in here as I do this crap all day and really can't be that arsed doing any of it in my free time

If the MSI is trying to install COM+ components then it may need to use activation permissions at some point in the install, the app will do that anonymously (well most do) and with the default permissions that will be prevented.

Whoops. Sorry, forgot to put a on the end of that. No offense intended and none taken in return

Just finished copying HP's new rapid deployment tools - over 3GB ISO image so the server is now free for some testing.

Thanks mate (and that is meant seriously)

Have you tried using the /regserve® command on the command line as well?

Sometimes that gives slightly more useful info

Hmm. I did play around and add the local and domain users specifically to the defaults and limits of COM+ security. It does seem to have an effect on the exported COM+ applicaton proxy MSI because the checksum changes.

But it still doesn't let me install them :(

Have you tried using the /regserve® command on the command line as well?

Sometimes that gives slightly more useful info

Aha, I did try installing via command line, and there is a handy /lv switch which gives you verbose logging. Of course, the install still fails, but I've attached the log in case it helps...

log.zip