/build/static/layout/Breadcrumb_cap_w.png

Application Compatibility Toolkit 5.5 Error

I installed Microsoft's Application Compatibility Toolkit 5.5. I then made and installed a test DCP MSI file on three different computers, including the machine where ACT is installed. On every machine the DCP gives me the following error: Inventory Collector - Agent had a runtime error. The Everyone group has Modify, Read, and Write rights to the logfile share. Any help that will get this working would be appreciated. Thanks.

Event log entries:

The description for Event ID ( 1008 ) in Source ( ACT-DC ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: [actdcsvc.exe] Inventory Collector agent had a runtime error.

The description for Event ID ( 1008 ) in Source ( ACT-DC ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: [actdcsvc.exe] Framework is exiting because the following system agents failed: Inventory Collector.

The description for Event ID ( 1017 ) in Source ( ACT-DC ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: [actdcsvc.exe] Framework is uninstalling because it encountered a fatal error.

0 Comments   [ + ] Show comments

Answers (3)

Posted by: MicrosoftBob 14 years ago
Blue Belt
0
The permission you list sound like NTFS permissions. Check the Share permissions to see that everyone can write. Then test it by copying files to the share from another computer.
Posted by: anonymous_9363 14 years ago
Red Belt
0
ProcMon - as ever - will show you exactly wat's going on. Without it, or your favoured process/file/registry monitor, you'll spend forever trying this option, that option until you end up forcefully engaging your forehead with the nearest wall.
Posted by: MicrosoftBob 14 years ago
Blue Belt
0
Actually now that I think about it....you should use a logging option with msiexec when installing the DCP MSI. I use /l*v c:\logfile.log. The log file should tell you the fatal error or you can post it here.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ