Agent Deployment error (0xC0000471)

February 19, 2010, 2:56 am

≫ Next: Create customized boot media to bypass DHCP server

≪ Previous: Common Base Agent Not Loaded

$

0

0

When I'm deploying some agent, i'll the wscfg32.exe process will be terminated with statuscode 0xC0000471.

This also happens when i run it from ldlogon share without any installation options.

When it's run from scheduled task the return code is "successfull".

But there ain't get any files copied/installed !!

 

According to ntstatus.h in winsdk the errormsg  says :

STATUS_INVALID_CRUNTIME_PARAMETER #An invalid parameter was passed to a C runtime function.

 

This happens only at a view machines. Didn't find any shared issuses on that computers. (different software, OS: Win7 64 and XP32)

Since this sounds for me like an .net related problem. I tried to update all .net frameworks, removed all VisualC++ runtimes and installed that ones from ldlogon shrare.

Doesn't get any further. (also disabled virus scanner )

 

 

Does someone have same problem, hints or solutions ?

Thanks in advance!

 

System info : running LDMS 9.0 on windows server 2003 standard 32bit in vmware, with external oracle db.

---

Create customized boot media to bypass DHCP server

November 12, 2012, 4:42 am

≫ Next: Upgrading clients to SP3

≪ Previous: Agent Deployment error (0xC0000471)

$

0

0

Hi everyone

I have a LANDESK ver 9.0.2.3 setup as a core server in my datacentre, I have a secondary server locally on my network that synchs to the core, my clients are setup in DHCP to look at the secondary server. I am busy testing the new version and have setup a core server on my local network. I am trying to setup a provisioning boot media that can either bypass the DHCP (I have no control over the DHCP, so i cannot change anything) and boot up directly to the server OR connect to the DHCP but provide a different Proxy IP (to the new server), I have tried a few of the online suggestions but to no avail.

 

Anyone have any ideas?

 

Regards

Upgrading clients to SP3

May 13, 2009, 10:28 am

≫ Next: Failed to install agent (LDMS 9.5)

≪ Previous: Create customized boot media to bypass DHCP server

$

0

0

So, with the release of SP3 I am sure a question on how or what the best method to install it will come up, so lets get it out in the open now.

 

For those of you that have already started deploying, how did you do it?  Via an AdvanceAgent, or via a Patch?

 

LANDesk Staff... what do you recommend?

 

Should we complete similar steps as to what Ty introduced here (http://community.landesk.com/support/docs/DOC-4448)?

 

Anyone else have any comments/suggestions, please feel free to add to this thread.

 

Thanks,

Chris

Failed to install agent (LDMS 9.5)

February 20, 2013, 8:47 pm

≫ Next: Query for LANDesk version

≪ Previous: Upgrading clients to SP3

$

0

0

Agent installation return with error code 1081. It is a fresh installation. The client OS version is Windows Server 2003. The firewall and antivirus are already turn off. I can see the folder $ldcfg$ created and the installer file already copied but he installer file seem not executed at all. Can anyone give idea on how to resolve this issue?

 

Log file:

 

Tue, 19 Feb 2013 16:01:24 Processing task 3

Tue, 19 Feb 2013 16:01:24 Processing task 3

Tue, 19 Feb 2013 16:01:26 1 machines targeted to task

Tue, 19 Feb 2013 16:01:26 Getting handler associated with scheduled task.

Tue, 19 Feb 2013 16:01:26 1 machines for taskID 3

Tue, 19 Feb 2013 16:01:26 Remote operation timout = 1200

Tue, 19 Feb 2013 16:01:26 Reset remote operation timout = 1200

Tue, 19 Feb 2013 16:01:26 Building LDMS client setup package: C:\Users\Administrator\AppData\Local\Temp\tmp1E4.tmp Log: C:\Program Files (x86)\LANDesk\ManagementSuite\log\cab_3.log

Tue, 19 Feb 2013 16:01:46 Configuring client config thread limit to 1

Tue, 19 Feb 2013 16:01:46 SVR-PNG-001 Sending C:\Users\Administrator\AppData\Local\Temp\tmp1E4.tmp to C:\$ldcfg$\tmp1E4.tmp

Tue, 19 Feb 2013 16:01:46 SVR-PNG-001 creating dir C:\$ldcfg$

Tue, 19 Feb 2013 16:02:12 SVR-PNG-001 Copying to C:\$ldcfg$\IPCheck.exe

Tue, 19 Feb 2013 16:02:40 SVR-PNG-001 Copying to C:\$ldcfg$\tmp1E4.tmp

Tue, 19 Feb 2013 16:05:03 SVR-PNG-001 Copy of C:\$ldcfg$\tmp1E4.tmp to SVR-PNG-001 returned -2147482443

Tue, 19 Feb 2013 16:05:03 SVR-PNG-001 Removing temporary directory

Tue, 19 Feb 2013 16:05:12 SVR-PNG-001 Handling reboot options

Tue, 19 Feb 2013 16:05:12 SVR-PNG-001 Reboot not needed

Tue, 19 Feb 2013 16:05:12 SVR-PNG-001 DONE: retCode=-2147482443 machineRetCode=1081

Tue, 19 Feb 2013 16:05:12 Task complete, status 7

Query for LANDesk version

January 29, 2009, 7:33 am

≫ Next: 9.5 - LANDesk Agent Deployment Upgrade "Agent setup program returned an error" (Push Deployment)

≪ Previous: Failed to install agent (LDMS 9.5)

$

0

0

I am doing an agent install for 8.80 SP2A.  So I created a query based on who needed the patch, no problem.

 

Then I summed up those who have with those who needed and I didn't come up with all my devices.

 

Now I'm wondering if all the users didn't get SP2 and are on SP1

 

Can I create a query to find out what version of the agent is installed?

 

Thank you,

 

S.....

9.5 - LANDesk Agent Deployment Upgrade "Agent setup program returned an error" (Push Deployment)

February 5, 2013, 7:12 am

≫ Next: Error when going to video properties

≪ Previous: Query for LANDesk version

$

0

0

Upgraded agents from 9.0SP3 to 9.5AllPatches and a good portion of the agents failed to update during the push deployment. The error received in the scheduled tasks window is "Agent setup program returned an error". I remember seeing this occasionaly the last time we did a deployment but rerunning the task on the computers that had failed generally came back successful. Not the case with 9.5.

 

Every machine that fails has the same symptoms, which leads me to beleive they are failing for the same reason. If you check the services on a computer that had a failed installation, the ONLY landesk services that are present are "LANDesk Targeted Multicast" and "LANDesk(R) Management Agent". A way to repair the agent on the computer, is that I can run Uninstallwinclient.exe then install the agent manually with a self contained exe and the installer goes through just fine. The problem is I cannot afford to do this on every single computer that has failed. I am still working on a way to identify all of the agents that did not install correctly. At the moment I am considering a loginscript vbs file that checks for the existance of the core landesk services.

 

I have attached the wscfg32.xlg file with the hops that someone can point out why the agent install is failing on so many machines. If any other information is needed please let me know.

Error when going to video properties

January 30, 2012, 2:12 pm

≫ Next: Unable to install via wscfg32.exe on a Dell workstation

≪ Previous: 9.5 - LANDesk Agent Deployment Upgrade "Agent setup program returned an error" (Push Deployment)

$

0

0

When trying to view the video properties I recieve an error.

 

Invalid Display Settings.  The currently selected graphics display driver can not be used.  It was written for a previous version of Windows, and is no longer compatible with this version of Windows.

 

I am using Windows XP SP3.

 

This error will go away if I uninstall the Mirror Driver and will reappear as soon as I load it back.

Unable to install via wscfg32.exe on a Dell workstation

December 6, 2012, 2:14 pm

≫ Next: Mirror Drivers disable Windows Aero on Windows 7 64 bit

≪ Previous: Error when going to video properties

$

0

0

Hello,

I'm having difficulties installing LANDesk on a Dell workstation (XPS 720, yes, the BTX one!)

Running the agent uninstall then attempting reinstall did not work.

 

Not sure where the problem is. XLG log file attached.

---

Mirror Drivers disable Windows Aero on Windows 7 64 bit

January 25, 2010, 10:03 am

≫ Next: LDDrives.exe and freezing desktops

≪ Previous: Unable to install via wscfg32.exe on a Dell workstation

$

0

0

I discovered that if you install an agent using the Remote Control Mirror drivers on a Windows 7 64 bit pc it disabled the Windows Aero feature.  This was not the case on a 32 bit Windows 7 machine.  The machines I used were a Dell 755 (64bit) and a Dell D820 laptop (32bit).  Just wanted to pass this on should anyone else see it.  Once I changed the client and rebooted Aero started working again.  This was a version 9 client.

LDDrives.exe and freezing desktops

July 28, 2011, 9:23 am

≫ Next: Agent settings and status in console problems

≪ Previous: Mirror Drivers disable Windows Aero on Windows 7 64 bit

$

0

0

Our user community is complaining of temporary freeze-ups on their computers. These last anywhere from 10 seconds to several minutes. In our troubleshooting, one thing we found is that during the freeze, LDDrives.exe was running and then stopped around the time the computer became responsive again.

 

In looking for info on exactly what invokes this process. I can't find anything in the doc or on-line.

 

The only thing I find in the install is it's included as a file in the .ini file under [CommonFiles].

 

Can anyone give me insight into this or somewhere that I can look for more info?

 

Thanks,

Meg

Agent settings and status in console problems

December 8, 2012, 10:02 am

≫ Next: How to deploy Batch file to run windows command?

≪ Previous: LDDrives.exe and freezing desktops

$

0

0

LD9 SP3

I have my agent setting to scan on logon and at IP change. Also Landesk support had me turn off Delta scans.

I still keep getting computers I can't remote or run software jobs because they have a IP that has been assigned to another computer.

 

Due to the number of mobile phones and other devices connecting and taking a IP my Server Department changed the IP asignment to 5 days.

I have computers that don't get turned on for days or months.

I'm constantly calling a Tech at the remote site to turn on a computer and I get a answer back that it is on. I am assuming the computers are on but sleeping so they never see a ip change or logon. Or they could be on but not logged in.

Sometimes I can right click and run a inventory scan and it will pick up a new ip. If its asleep I can't.

 

If a computer is asleep, in the console, I see no status (no round red circle, no binoculars or remote icon) wake up is grayed out so I am forced to use a 3rd party wol utility to wake up the computer to get a status and run a inventory scan.

 

I've even had some that had a mini-scan (minimal inventory data), they have not been recently imaged, and the status icons are there but for some reason in the inventory the subnet info is garbage so I can't do anything with them.

Then there are those that are not in the console but when I remote desktop in the Landesk Agent is installed and running in processes and services.

 

Anyone else having this problem?

How to deploy Batch file to run windows command?

June 1, 2011, 1:34 am

≫ Next: CBA 8, unable to contact the remote agent

≪ Previous: Agent settings and status in console problems

$

0

0

I would to deploy a batch file, it is save a windows command.

When I deploy to client it have a error.

 

Status: Failed

Result: Package Deployment Failed

Return code: 1

 

Log:

Installation result 8DB50001

processing of package is complete, result -1917517823 (0x8db50001 - code 1)

CBA 8, unable to contact the remote agent

December 27, 2007, 9:49 pm

≫ Next: Uninstallwinclient.exe download?

≪ Previous: How to deploy Batch file to run windows command?

$

0

0

 

I have a machine that has agent installed fine, is displaying in the all devices. However i have noticed that the remote agent control status has not been loaded. When i run a scan from the machine itself it seems to work and data has been sent to the core server. When i run a scan from the LDMS server console it fails- cba8, unable to contact the remote agent

 

 

when i do a repair job it says straight away- Cannot Find Agent

 

 

The agent has been removed and re-installed. Same agent version as other machines.

 

 

i have re ran the cba8inst.msi file no issues.

 

 

Cant do any repair jobs or scans from the LDMS?!?!?

 

 

Any help would be appreciated. **(FYI-im away next week so no reponse until the following week)**

 

 

Uninstallwinclient.exe download?

February 6, 2008, 3:57 pm

≫ Next: Failed to install agent (LDMS 9.5)

≪ Previous: CBA 8, unable to contact the remote agent

$

0

0

 

As part of a trial I installed LANDesk agents on a number of my PC's.  Since it was a trial I had the core server on an old piece of hardware that died.  Where can I get a copy of uninstallwinclient.exe?  I'm using version 8.7.

 

 

 

 

 

Thank you,

 

 

Failed to install agent (LDMS 9.5)

February 20, 2013, 8:47 pm

≫ Next: Successful self-contained agent installation reports as failed

≪ Previous: Uninstallwinclient.exe download?

$

0

0

Agent installation return with error code 1081. It is a fresh installation. The client OS version is Windows Server 2003. The firewall and antivirus are already turn off. I can see the folder $ldcfg$ created and the installer file already copied but he installer file seem not executed at all. Can anyone give idea on how to resolve this issue?

 

Log file:

 

Tue, 19 Feb 2013 16:01:24 Processing task 3

Tue, 19 Feb 2013 16:01:24 Processing task 3

Tue, 19 Feb 2013 16:01:26 1 machines targeted to task

Tue, 19 Feb 2013 16:01:26 Getting handler associated with scheduled task.

Tue, 19 Feb 2013 16:01:26 1 machines for taskID 3

Tue, 19 Feb 2013 16:01:26 Remote operation timout = 1200

Tue, 19 Feb 2013 16:01:26 Reset remote operation timout = 1200

Tue, 19 Feb 2013 16:01:26 Building LDMS client setup package: C:\Users\Administrator\AppData\Local\Temp\tmp1E4.tmp Log: C:\Program Files (x86)\LANDesk\ManagementSuite\log\cab_3.log

Tue, 19 Feb 2013 16:01:46 Configuring client config thread limit to 1

Tue, 19 Feb 2013 16:01:46 SVR-PNG-001 Sending C:\Users\Administrator\AppData\Local\Temp\tmp1E4.tmp to C:\$ldcfg$\tmp1E4.tmp

Tue, 19 Feb 2013 16:01:46 SVR-PNG-001 creating dir C:\$ldcfg$

Tue, 19 Feb 2013 16:02:12 SVR-PNG-001 Copying to C:\$ldcfg$\IPCheck.exe

Tue, 19 Feb 2013 16:02:40 SVR-PNG-001 Copying to C:\$ldcfg$\tmp1E4.tmp

Tue, 19 Feb 2013 16:05:03 SVR-PNG-001 Copy of C:\$ldcfg$\tmp1E4.tmp to SVR-PNG-001 returned -2147482443

Tue, 19 Feb 2013 16:05:03 SVR-PNG-001 Removing temporary directory

Tue, 19 Feb 2013 16:05:12 SVR-PNG-001 Handling reboot options

Tue, 19 Feb 2013 16:05:12 SVR-PNG-001 Reboot not needed

Tue, 19 Feb 2013 16:05:12 SVR-PNG-001 DONE: retCode=-2147482443 machineRetCode=1081

Tue, 19 Feb 2013 16:05:12 Task complete, status 7

---

Successful self-contained agent installation reports as failed

June 27, 2011, 8:52 am

≫ Next: Extended log off times since 9.5 upgrade

≪ Previous: Failed to install agent (LDMS 9.5)

$

0

0

The self-contained agent installation that I create includes the LDAV and vulscan.exe requires a reboot of the computer after the installation. Because of this the agent installation sometimes gives an error at the end of the installation and says to look at the wscfg32.xlg file for details. Upon reboot, all services load just fine. Here are the last lines of a wscfg32.xlg file. Is there any way to prevent this error from occuring?

 

FAILED:  Finished
05/26/2011 11:01:09.702    4520    2860    file.cpp    123    SUCCEEDED:  Delete (c:\ENUNTCFG.MRL)
05/26/2011 11:01:09.703    4520    2860    ntstacfgDlg.cpp    2387    Vulscan wants to reboot the machine
05/26/2011 11:01:09.703    4520    2860    ntstacfgDlg.cpp    2564    gProcessExitCode set to ERROR_SUCCESS_REBOOT_REQUIRED
05/26/2011 11:01:09.703    4520    2860    ntstacfgDlg.cpp    2570    FAILED:  bCriticalError is true.  Setting exit code to ERROR_INSTALL_FAILURE
05/26/2011 11:05:21.977    4520    2596    ntstacfg.cpp    217    Application exit value is 1603
05/26/2011 11:05:21.977    4520    2596    xtrace.c    466    process log done

 

===================

 

I also sometimes receive an installation error when using the unattended configuration to receive the certificate from the core for the management gateway- for computers that are on site (http://community.landesk.com/support/docs/DOC-1888). I always receive an error when the computer is not on-site but I thought that this was the purpose of the brokerconfig.lng file. Is there a way to prevent this error message if the computer is unable to retrieve the certificate at the time of installation but is successful at copying the brokerconfig.lng file? The end of a wscfg32.xlg file when I receive a "brokerconfig.exe /r" error is below

 

 

INI:  EXEC1001=BrokerConfig.exe, /r, INSTALLONLY

03/31/2011 12:21:33.404 808 3892 tokens.cpp 562 Starting process: BrokerConfig.exe /r
03/31/2011 12:26:33.988 808 3892 tokens.cpp 596 Processes returned : -2146435027
03/31/2011 12:26:33.988 808 3892 tokens.cpp 484 CheckProcessExitCode processed app name: BrokerConfig.exe
03/31/2011 12:26:33.988 808 3892 tokens.cpp 616 FAILED:  Running application: BrokerConfig.exe /r
03/31/2011 12:26:33.988 808 3892 ntstacfgDlg.cpp 1553 FAILED:  bCriticalError set to TRUE. Processing BrokerConfig.exe

 

Core:

LANDesk v.9 SP2

 

Thanks,

Sundiata

 

Extended log off times since 9.5 upgrade

January 30, 2013, 12:59 pm

≫ Next: After upgrade to 9.5 from 9.0, will 9.0 agent and AV keep working till we upgrade them

≪ Previous: Successful self-contained agent installation reports as failed

$

0

0

After upgrading to LDMS 9.5 we are noticing increased log off times.  A normal log off would take 20-30 seconds is now taking 3-4 mintues.  There are times when the user will initiate the log off and the computer appears to be frozen but after 3-4 minutes it will then start the log off.  It almost reminds me that a scan is happening before the log off.

 

I know it is tied to this as I rolled a few machines back to the 9.0.3 client and they log off as before, in 20-30 seconds.

 

I have striped everything out of the client, so there Forms, RTI, Software Monitoring, just the base client and still have the issue.

 

Has anyone else seen or heard of this?

 

Thanks in advance.

 

James

After upgrade to 9.5 from 9.0, will 9.0 agent and AV keep working till we upgrade them

March 11, 2013, 9:19 am

≫ Next: Error when scheduling agent deployment (LANDesk 9.0 SP3)

≪ Previous: Extended log off times since 9.5 upgrade

$

0

0

We are preparing to upgrade from 9.0 to 9.5. We have large user base out in field and they do not connect regularly and for long time. My question is will 9.0 agent and LANDesk AV keep working and communicating until we upgrade them?

Error when scheduling agent deployment (LANDesk 9.0 SP3)

July 3, 2012, 8:38 am

≫ Next: Error when going to video properties

≪ Previous: After upgrade to 9.5 from 9.0, will 9.0 agent and AV keep working till we upgrade them

$

0

0

I've noticed on a lot of machines that I am getting an error when scheduling agent deployment.     We're running LANDesk 9,0 SP3 with LD90-SP3-CP_RC-2012-0605 and LD90-SP3-CP_BASE-2012-0605 installed on the core.

 

The machines will fail with the result "An internal error occured"  Return code is 1208

 

If I view the log, the machines say this....

 

[Exception occured, last attempted operation] RemoteExecute, program = tmp70B1.tmp exception = Object reference not set to an instance of an object.

 

or

 

[Exception occured, last attempted operation] RemoteExecute, program = tmp70B1.tmp exception = Could not find file 'C:\Users\zldsk2\AppData\Local\Temp\tmp78B.tmp'.

 

 

The agent install actually seems to work fine and the agent is updated but it is not reporting sucessfully when I push out the agent using schedule agent push

 

 

Any ideas?

Error when going to video properties

January 30, 2012, 2:12 pm

≫ Next: NMAP - OS Fingerprinting Ports Used in LANDesk 9 SP2

≪ Previous: Error when scheduling agent deployment (LANDesk 9.0 SP3)

$

0

0

When trying to view the video properties I recieve an error.

 

Invalid Display Settings.  The currently selected graphics display driver can not be used.  It was written for a previous version of Windows, and is no longer compatible with this version of Windows.

 

I am using Windows XP SP3.

 

This error will go away if I uninstall the Mirror Driver and will reappear as soon as I load it back.