Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

DCP (Data Collection Package) is unable to upload logdata

57 views
Skip to first unread message

rsc

unread,
Nov 19, 2009, 8:53:02 AM11/19/09
to
First excuse my bad english. Now to the Problem.

Our DCP is unable to load the Logfiles (cabs) to the Log processing share.

We are using the ACT 5.5
The DCP is rolled out to windows xp Clients. The ACT Database & ACT
Logshare is installed on a Windows XP machine wich is in special use for ACT.
All clients are Members in a NT4 Domain.

The Logshare is configured like described in the technet :
http://technet.microsoft.com/en-us/library/cc722443(WS.10).aspx - Verifying
Your ACT Log-Share Permissions

Copying the DCPlog manually from the client to the share works without
problems, but it couldn’t be the solution.
Here some abstractions from the eventlog:

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: [uploader.exe]
[Uploader] please verify share \\Derscn286\ACT-DATABASE\ACT-LOGS
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: [uploader.exe]
copying file C:\Documents and Settings\All Users\Application
Data\Microsoft\Application Compatibility Toolkit
5\DataCollector\Logging\AM-STATCOMP-{3BF5AAEF-847F-44b3-91DB-F8CC5E27D366}\STATUS-DERSCD391{807995F2-2982-45F9-8E55-87822ECF0BE9}.xml.cab
to
\\Derscn286\ACT-DATABASE\ACT-LOGS\STATUS-DERSCD391{807995F2-2982-45F9-8E55-87822ECF0BE9}.xml.cab fails, error details: Access is denied.
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]
Windows Compatibility Evaluators 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: [dep.exe] Error in
setting up ETW session.

Some Questions I have :

It seems that the DCP cannot access the share, but its configured like
described in the help. Anyone have some hints?
What account uses the DCP (especially the uploader.exe) to upload the
logdata, the user which is logged on ?
Is this account configurable ?
Are there known issues using ACT 5.5 in NTDomain Environment?


Gary

unread,
Nov 21, 2009, 12:00:28 PM11/21/09
to
Just a shot in the dark. Try enabling the Guest account and giving it NTFS
full control on the folder. Also give the Everyone group NTFS Full Control

--
Gary Dunlop
"rsc" <r...@discussions.microsoft.com> wrote in message
news:86442E97-8CCD-44C1...@microsoft.com...

rsc

unread,
Nov 25, 2009, 8:36:16 AM11/25/09
to
We resolved the problem by activating Anonymous access and null session
access. (it is also recommend in the help by the Additional Troubleshooting
Notes ;) )

"Gary" wrote:

> .
>

rsc

unread,
Nov 25, 2009, 8:38:01 AM11/25/09
to
We resolved the problem by activating Anonymous access and null session
access. (it is also recommend in the help, in the additional troubleshooting
section ;)

"Gary" wrote:

> .
>

0 new messages