Hello,

I've upgraded our Configuration Manager server to SP1, and updated the Software point with the new client agent.

For the most part, everything went fine, I'd say that atleast 95% of our client agents upgraded without any problems. However, it seems that 5 or so are being a PITA, not upgrading, and spewing out the following error in the eventlog:

Event Type: Error

Event Source: MsiInstaller

Event Category: None

Event ID: 11904

Date: 6/17/2008

Time: 11:16:50 AM

User: NT AUTHORITY\SYSTEM

Computer: NITROGEN

Description:

Product: Configuration Manager Client -- Error 1904. Module C:\WINDOWS\system32\CCM\VAppRegHandler.dll failed to register. HRESULT -2147221164. Contact your support personnel.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Data:

0000: 7b 43 45 36 41 38 35 44 {CE6A85D

0008: 38 2d 44 36 42 39 2d 34 8-D6B9-4

0010: 37 39 41 2d 39 46 45 39 79A-9FE9

0018: 2d 41 30 36 45 35 36 38 -A06E568

0020: 38 31 45 36 31 7d 81E61}

I've attempted removing the client from the machine and reinstalling it via the client install, however, it results in the same error.

Any suggestions??

Thanks!

Warren

Hi,

Try to register the file manually, if this fails perhaps there are some permissions issues or a new error messages is displayed with more information.

You can register theDLL with the following command:

regsvr32 C:\WINDOWS\system32\CCM\VAppRegHandler.dll

I am working with Warren on this issue.

When attempting to register manually I get the error:

RegSvr32:

DllRegisterServer in C:\Windows\System32\CCM\VAppRegHandler.dll failed.

Return code was: 0x80040154

Still getting the error he posted every hour.

Thanks,

Kevin

Hi,

That doesn't sounds good and you probably will get this error with any DLL you are trying to register. Since 95% of clients are installed correct I think this is more a client OS problem then a SCCM problem or bug.

Try posting your problem in on of the client communities, perhaps they havea solution for your problem.

http://www.microsoft.com/communities/newsgroups/default.mspx

That error code just means "Class not registered"

I agree that since it works on 95% of the systems, it is not a Configuration Manager issue, but some sort of a client corruption/configuration issue.

Hi Guys,

We have the same problem at a customers site..

90% of the machines went fine,last 10% only that dll error!

(this was not even an upgrade, installation isa new one)

Manual registering didn't fix the issue either (just gave the same error).

The 'trouble' machines are a mix of XP-SP2 and Vista-SP1

Any suggestions ??

Brgds,

Maarten van der Hoek

If you can't fix it by re-registration, and it works on 90+% of the clients, then it is not a Configuration Manager issue, so must be a client build issue. You could try opening a case with product support, however, if you've already re-registered the dlls, then my guess is that they'd tell you to rebuild those systems, as it works on the vast majority.

To fix the problem try this:

ccmsetup /uninstall on teh station in question

then

regsvr32 atl.dll

After that, try to install the client again. In all cases where I have had this problem, this solves it.

(Knowledge Disclaimer: Problem solution foundfrom userSKISSINGER on another forum)