SCCM SP1 Agent issues

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

June 17th, 2008 7:35pm

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

Free Windows Admin Tool Kit Click here and download it now
June 18th, 2008 8:42pm

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

June 24th, 2008 1:53pm

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

Free Windows Admin Tool Kit Click here and download it now
June 24th, 2008 7:26pm

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.

June 24th, 2008 10:23pm

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

Free Windows Admin Tool Kit Click here and download it now
July 23rd, 2008 12:48pm

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.

July 27th, 2008 1:19am

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)

Free Windows Admin Tool Kit Click here and download it now
August 21st, 2008 8:31pm

TheMetalicOne wrote:

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)



I want to confirm this fixed the handful of machines with this error. Thanks!
September 16th, 2008 6:30pm

Excellent!This fixworked on 4 out of 5 machines where I was having the problem.

The exact error message in \windows\system32\ccmsetup\client.msi.log is:

Error 1904. Module C:\WINDOWS\system32\CCM\VAppRegHandler.dll failed to register. HRESULT -2147221164

Thanks,

Nick.

Free Windows Admin Tool Kit Click here and download it now
September 24th, 2008 5:12pm

I am having this same problem on about 650 of the 1300 computers I am trying to upgrade from SMS 2003 client to SCCM 2007 client. What is wrong locally that reregistering atl.dll fixes? Why would it only happen on some of the computers?
Is there no other option than reregistering atl.dll to fix the problem?
Thanks. Zach
September 25th, 2008 4:41pm

How does a regular person like me who is not a computer tech go about performing the solutions posted here? I can't install an updated version of a program that requires Flash Player 7. I get the said error in the event viewer. The installer for the program says to install that flash player, which IS installed. Where do I go from here?

Free Windows Admin Tool Kit Click here and download it now
November 22nd, 2008 5:51am

I also want to confirm this solution.

Thnx TheMetalicOne
March 11th, 2009 4:32pm

Hey all

regsvr32 atl.dll fixed my machine also

Cheers
Free Windows Admin Tool Kit Click here and download it now
August 12th, 2009 3:34am

I hvae exact the same error in event log, Module C:\WINDOWS\system32\CCM\VAppRegHandler.dll failed to register. but I don't have the CCM folder under system32. I did a search for file: VAppRegHandler.dll, not found ! 
October 8th, 2009 9:41pm

I had the same problem....I could not see the CCM folder...i created one and then i manualy registered the dll but did not work...i strongly feel its an OS issue rather than an SCCM issue
Free Windows Admin Tool Kit Click here and download it now
December 9th, 2009 7:23pm

I got over from the "VAppRegHandler.dll" problem by doing these steps:

1. Manually create folder "CCM" under C:\WINDOWS\system32\ to the problem computer

2. Copy "VAppRegHandler.dll" to the problem computer's C:\WINDOWS\system32\CCM\ folder either from the SCCM server or from a computer where the client is working properly.

3. On the problem computer, run in the console: regsvr32 atl.dll

4. On the problem computer, run in the console: regsvr32 C:\WINDOWS\system32\CCM\VAppRegHandler.dll

After those steps i managed to get the client installed and working properly with both client push install and manual install.

 

  • Proposed as answer by ALaRose Tuesday, November 23, 2010 9:47 PM
September 1st, 2010 10:10am

I got over from the "VAppRegHandler.dll" problem by doing these steps:

1. Manually create folder "CCM" under C:\WINDOWS\system32\ to the problem computer

2. Copy "VAppRegHandler.dll" to the problem computer's C:\WINDOWS\system32\CCM\ folder either from the SCCM server or from a computer where the client is working properly.

3. On the problem computer, run in the console: regsvr32 atl.dll

4. On the problem computer, run in the console: regsvr32 C:\WINDOWS\system32\CCM\VAppRegHandler.dll

After those steps i managed to get the client installed and working properly with both client push install and manual install.

 

  • Proposed as answer by ALaRose Tuesday, November 23, 2010 9:47 PM
Free Windows Admin Tool Kit Click here and download it now
September 1st, 2010 10:10am

Thank you Metalic, SKISSINGER solution is metalic
September 1st, 2010 10:15am

has anyone heard of WHY this may be happening?

I'm very thankful for the answers as we have an XP environment which HAD the SCCM Client, but then lost communication with it for whatever reason. They began showing up in the NON Client lists, and when I read CCMSETUP logs on them, all have been having the VAppRegHandler.dll failure message.

 

I'm manually fixing all of these ,but why have they all of a sudden stopped?

Any ideas?

Free Windows Admin Tool Kit Click here and download it now
November 23rd, 2010 9:49pm

I have tried above all but no luck..

Finally it got resolved by http://www.mssccm.com/sccm-2007/sccm-client-installation-failed-vappreghandler-dll-failed-to-register/

August 7th, 2015 5:25pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics