There is no more storage space left of the c: drive of the core server. Can any files be deleted or some moved to another drive to make more space?

Occasionally you'll see an error saying to check the application event log or to use the command-line sxstrace.exe tool.

Below is a how-to for using the sxstrace tool. The how-to is copied from Troubleshooting side by side issues using sxstrace - bits and bytes, but I've included the text here in case the link stops working.

How to troubleshoot Side by Side errors using sxstrace?

As the error message suggests let use sxstrace.exe. The usage of sxstrace is pretty easy to understand…

C:\windows\system32>sxstrace

WinSxs Tracing Utility.

Usage: SxsTrace [Options]

Options:

     Trace -logfile:FileName [-nostop]

          Enabling tracing for sxs.

          Tracing log is saved to FileName.

          If -nostop is specified, will not prompt to stop tracing.

     Parse -logfile:FileName -outfile:ParsedFile  [-filter:AppName]

          Translate the raw trace file into a human readable format and save the result to ParsedFile.

          Use -filter option to filter the output.

     Stoptrace

          Stop the trace if it is not stopped before.

Example:

     SxsTrace Trace -logfile:SxsTrace.etl

     SxsTrace Parse -logfile:SxsTrace.etl -outfile:SxsTrace.txt

Collecting sxstrace logs

The command usage message shows us two sample commands and that’s exactly what we’re going to try. Please make sure you’re running an elevated command prompt…

Run the following command…

C:\>SxsTrace Trace -logfile:SxsTrace.etl

Tracing started. Trace will be saved to file SxsTrace.etl.

Press Enter to stop tracing...

So now you’re in tracing mode. Go ahead and run your application which threw the side by side error. Press enter on the command prompt window once you’re done repro’ing the error, this will stop the side by side tracing that’s going on. Once you press enter the ETL trace file will be dumped into the current folder. The dumped trace file is not in human readable format…

Binary output from SxsTrace tool

Parsing sxstrace logs

To make it readable, we’ll need to parse this file using sxstrace tool. Run following command to do that…

C:\>SxsTrace Parse -logfile:SxsTrace.etl -outfile:SxsTrace.txt

Parsing log file SxsTrace.etl...

Parsing finished! Output saved to file SxsTrace.txt.

So now we have a text file as output. Lets open the file and find out what went wrong… Contents are as follows…

Parsed output from sxstrace

hallo zusammen,

ich will LANDESK im Auftrag einer Firma testen, hab schon die Test-Version heruntergeladen und in meinem VMWare installieret. Leider aus technischen Gründen hat mein VMWare kein Internet-Zugang.

Um LanDesk offline zu aktivieren habe ich dann auch die Aktivierung-Datei per email an support geschickt und dann auch .AUTH zurück bekommen, die auch im richtigen Ordner liegt.

Nun aber wenn ich LanDesk CoreServer starte, bekomme ich wieder das Fester wo ich "Kontaktname" und  "Kennwort" eingeben muss, 45-Test Version Option ist nicht wählbar. Unter Lizenzen sehe ich, dass das LANDesk Management Suite für 45 Tage lizenziert ist. Es geht aber nicht weiter. Ich habe nur unten als Buttons "Lizenzen",  "Aktivieren" und "Abbrechen"

wie komme ich nun weiter?

VG

Any idea when LD96-CP_BASE-2015-0812 Download will become available?

It's random. It will blue screen on some thin clients but not others. I can have two of the same model thin client running a clean image I just burned to them, one will BSOD and one won't. It's always the same stop code (0x0000008e). This seems to only happen on our embedded devices (HP thin clients) running WES7e. This was happening at about a 15% rate on the older models (t5740e and t610) but is almost all of the new ones (t620).

We are running 9.60.0.244 SP1.

I have tried:

• 9.5 agent exe/msi

• 9.6 agent exe/msi

• 9.6sp1 agent exe/msi

• 9.6sp1 push from server

• Reimage thin client to default HP out of box state

• Imaged w/ landesk agent preinstalled

• Tried using the non-embedded agent

• Adjusted memory management

• Adjusted page file

• Write filter on/off

• Wired network/wireless/no network connectivity

• BIOS upgrade to newest version

• Environment Variables-point to C drive instead of Z

• Deploying agent without remote control feature

• Deploying agent without mirror driver

• Created a new core and generated a new agent from it (which made the thin client BSOD upon installation)

All result in the thin client eventually blue screening within an hour or two. Removing the agent stops the BSODing and system goes back to being stable. We're not using encryption or antivirus. These are not domained. Nothing specifically seems to cause it. No one will be using the computer and it'll just bsod.

All the thin clients are running the newest image provided by HP for its model. I've reached out to Landesk support twice and sent in a thin client that would BSOD at least once a day and they had it for over a month and were never able to recreate the problem. There are way too many of them in my opinion for this to be a hardware problem, but I don't understand how it's software if they're running the same image. If it was a driver problem, it should be consistently affecting all of those models and it's not. 3 different models (different internal hardware) all BSOD with the same 8E stop code. None of our w7 professional or xp professional computers have had this BSOD at all.

Other software installed on the thin client: Citrix Receiver, HP Device Manager Agent, Abbott Data Repeater, Rubbermaid Cart Interface, and UltraVNC.

Please, I need suggestions! I'm out of ideas.

Problem

When attempting to run the Core Server Activation tool, it may crash before even opening. You will see an error similar to this:

Note: Notice that 'Problem Signature 05' is '4.6.81.0'. That is the .NET version.

The additional information says:

Problem signature:

  Problem Event Name: CLR20r3

  Problem Signature 01: X2UPWFWXVZFTNW0S0M22QP3WRZ5C5DOQ

  Problem Signature 02: 9.60.3.64

  Problem Signature 03: 5530a4d8

  Problem Signature 04: System.Windows.Forms

  Problem Signature 05: 4.6.81.0

  Problem Signature 06: 5584e675

  Problem Signature 07: 4900

  Problem Signature 08: 0

  Problem Signature 09: System.AccessViolationException

  OS Version: 6.3.9600.2.0.0.272.7

  Locale ID: 1033

  Additional Information 1: 3116

  Additional Information 2: 3116107111c8880d6265b2360d5a954d

  Additional Information 3: 7526

  Additional Information 4: 7526aeea74a808346c2825c4bb746d2b

 

Read our privacy statement online:

  http://go.microsoft.com/fwlink/?linkid=280262

 

If the online privacy statement is not available, please read our privacy statement offline:

  C:\Windows\system32\en-US\erofflps.txt

Additionally, there will be two errors in the Application Event Log:

Source: .NET Runtime - Event ID: 1026

Application: LANDesk.ManagementSuite.Licensing.ActivateCore.exe

Framework Version: v4.0.30319

Description: The process was terminated due to an unhandled exception.

Exception Info: System.AccessViolationException

Stack:

  at System.Windows.Forms.IntSecurity.get_WindowAdornmentModification()

  at System.Windows.Forms.Form.get_IsRestrictedWindow()

  at System.Windows.Forms.Form.get_WindowText()

  at System.Windows.Forms.Form.FillInCreateParamsBorderIcons(System.Windows.Forms.CreateParams)

  at System.Windows.Forms.Form.get_CreateParams()

  at System.Windows.Forms.Control..ctor(Boolean)

  at System.Windows.Forms.ScrollableControl..ctor()

  at System.Windows.Forms.ContainerControl..ctor()

  at System.Windows.Forms.Form..ctor()

  at LANDesk.ManagementSuite.Licensing.ActivateCore.ActivateCoreForm..ctor()

  at LANDesk.ManagementSuite.Licensing.ActivateCore.ActivateCoreForm.Main(System.String[])

Source: Application Error - Event ID: 1000

Faulting application name: LANDesk.ManagementSuite.Licensing.ActivateCore.exe, version: 9.60.3.64, time stamp: 0x5530a4d8

Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000

Exception code: 0xc0000005

Fault offset: 0x000000001e0d3ab8

Faulting process id: 0xe18

Faulting application start time: 0x01d0f00cd2b1e4e1

Faulting application path: C:\Program Files\LANDesk\ManagementSuite\LANDesk.ManagementSuite.Licensing.ActivateCore.exe

Faulting module path: unknown

Report Id: 107b0d58-5c00-11e5-80cb-00155d653201

Faulting package full name:

Faulting package-relative application ID:

Resolution

This problem is caused by .NET 4.6. You can remove .NET 4.6 and it will work as expected. The .NET 4.6 update can often be found as KB 3045560 - https://support.microsoft.com/en-us/kb/3045560

• On Windows Vista SP2, Windows 7 SP1, Windows Server 2008 SP2, or Windows Server 2008 R2 SP1, Microsoft.NET Framework 4.6 is installed under Programs and Features in Control Panel.
• On Windows 8 or Windows Server 2012, Update for Microsoft Windows (KB3045562) is displayed under Installed Updates in Control Panel.
• On Windows 8.1 or Windows Server 2012 R2, Update for Microsoft Windows (KB3045563) is displayed under Installed Updates in Control Panel.

Client Side Logfile locations by LANDESK component

For More Information...

For a list of 9.6 SP1 Client Side Log locations, see LANDESK Management Suite 9.6 SP1 Client Log File Locations

For a list of 9.6 Client Side Log locations, see LANDESK Management Suite 9.6 Client Log File Locations

For a list of 9.5 Server Side Log locations, see 9.5 LANDesk Server Log File Locations for Troubleshooting

Agent Installation

Please consult the document available here : Where are the Agent install log files?

Alerting

C:\Program Files\ LANDesk\shared files\alert.log

C:\Program Files\LANDesk\LDClient\alertsync.log

C:\Program Files\LANDesk\LDClient\lddetectsystem.log

C:\Program Files\LANDesk\LDClient\createmonitorroot.log

AMT

C:\Program Files\LANDesk\LDClient\amtmon.Log

AntiVirus (LANDesk)

C:\ProgramData\LANDeskAV\ldav.log

C:\ProgramData\LANDeskAV\ldav_scan.log

C:\ProgramData\LANDeskAV\ldav_update.log

C:\ProgramData\LANDeskAV\ldav_install.log

C:\ProgramData\LANDeskAV\msi_install.log

CBA8 logs (Common Base Agent)
C:\Program Files\LANDesk\shared files\residentagent.log
C:\Program Files\LANDesk\shared files\residentagent.old
C:\Program Files\LANDesk\shared files\servicehost.log
C:\Program Files\LANDesk\shared files\servicehost.old

C:\Program Files\LANDesk\LDClient\fwregister.log

Cloud Services Appliance

C:\Program Files\LANDesk\shared files\proxyhost.log

C:\Program Files\LANDesk\LDClient\brokerconfig.log

Endpoint Security

Files within C:\Program Files\LANDesk\LDClient\HIPS:

DCM.log (Device Control – Logs Device Information)

DCMVolumes.log (Device Control – Logs Volume Information)

ERROR.LOG (Shows Endpoint Security service errors)

NetworkDetection.log (Shows Network Location Awareness information)

ShadowCopy.log (Device Control – Shadow copy information)

Files within C:\Documents and Settings\All Users\Application Data\LDSec

LDSECSETUP32-HIPS-debug.log (Debug level log for installation)

LDSECSVC-DCM-debug.log (Debug level log for Device Control)

LDSECSVC-HIPS-debug.log (Debug level log for HIPS)

Files within C:\Documents and Settings\All Users\Application Data\Vulscan

Vulscan.log (logs Endpoint installation, settings changes, etc)

For more information on troubleshooting Endpoint Security and logs please see Community DOC-9853

InventoryScanner

C:\Program Files\LANDesk\LDClient\ldiscn32.log

C:\Program Files\LANDesk\LDClient\data\ldiscn32.log
(This log appears when ldiscn32.exe is run with the "/debug" switch)

C:\Program Files\LANDesk\LDClient\ldiscnupdate.log

Local Scheduler tasks

C:\Program Files\LANDesk\LDClient\localsch.log

C:\Program Files\LANDesk\LDClient\LDSystemEventCapture.log

Macintosh

\Library\Application Support\LANDesk\LANDesk.log(All Components)

Security and Patch Manager
C:\ProgramData\vulScan\vulscan.log

C:\ProgramData\vulScan\vulscan.#.log
(The vulscan log will roll and create a vulscan.1.log, vulscan.2.log, etc)
C:\Program Files\LANDesk\LDClient\vulscan.log

C:\ProgramData\vulScan\softmon.log

Software Distribution
C:\Program Files\LANDesk\LDClient\data\sdclient_task#.log
C:\Program Files\LANDesk\LDClient\data\sdclient.log

C:\Program Files\LANDesk\LDClient\tmcsvc.log

C:\Program Files\LANDesk\LDClient\data\SDClientTask.[Core-Name].[task#].log

C:\Program Files\LANDesk\LDClient\data\[MSI Name].log (created during installation of MSI packages)

C:\Program Files\LANDesk\LDClient\CurrentDownloads.log (information regarding whether a file has been downloaded from the source or from a preferred server)

Software Distribution - Policies

C:\Program Files\LANDesk\LDClient\policy.cgi.log

C:\Program Files\LANDesk\LDClient\policy.client.portal.log

C:\Program Files\LANDesk\LDClient\policy.client.invoker.log

C:\Program Files\LANDesk\LDClient\policy.sync.log

Software License Monitoring
C:\Program Files\LANDesk\LDClient\data\gatherproducts.log
C:\Program Files\LANDesk\LDClient\data\proddefs\*.xml

Remote Control logs

Please refer to this document here : What log files are used for Remote Control Troubleshooting?

Hi,

We found in core server LANDesk SQL data base is suddenly increased, found in D drive the SQL database file D:\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\landesk.ldf file it's nearly to 130 GB, please let me know how it's increased suddenly, and provide the resloution for the same.

Regards

Srinath YN

Hi,

we just migrated our SQL 2005 DB to a 2008R2 Server. The old system was kind of unorganized and messed up regarding the rights of the DB users.

Now we want to grant only the needed permissions on the SQL DB. In our envrionment we have two Core servers and on Rollup core.

We already had some issues when taking away the sysadmin permission of the DB user. As soon as we did this, the rollup didn't work anymore.

Is there any document on what exact permissions the DB user has to have?

Regards

Johann

One of our net admins informed me this morning that the backup for our LANDesk SQL DB grew overnight by almost 4GB.  The previous three or four nights it only increased by 50 or 60 MB (if that). Any suggestions on what I should look for here?

Thanks

We are about to update our SQL environment, our DBA has informed me that the new SQL servers will be "mirrored". Can I move the LANDesk database from a traditional SQL server to a mirrored SQL 2008 R2 server?

Many thanks

J

Would anyone be able to comment on recommended hardware specs for a new SQL server. We're currently at LDMS 8.8 SP3, but will probably upgrade in 2012.

Microsoft licensing requires due diligence on such matters. I'm sure you've gone down that $$ road before. Specifically, we want to confirm processor and core requirements.

Thanks in advance for any feedback.

Regards,

Bill Suggs

Fort Worth, TX

Hi, i would like to know if there is an official document LANDesk - Oracle Regular Maintenance - BEST Methods for LANDesk Management suite

Hello

I am too stupid. I don't find the way to change the database to another Server. I move the LDMS Database to another Server, but where can i change the AMP-database Server.....

thanks

Thomas

I was at a recent user group meeting and we were told about a new health check tool.

Does anyone know where to find this ?

Thanks

Graeme

What process needs to be done to convert from SQL 2008 to SQL 2005

Hi There ,

Please advice on how to do clean up the MSSQL  Server.

Regards,

Muru

Environment:

LDMS 9.6 SP2

Error message:

Failed saving to db, core: (corename) as user (username) method: WebService

Problem:

Remote console users are unable to create scheduled tasks.

Cause:

Bad DLLs or DLLs not being updated during the installation of SP2.

Solution / Workaround:

Reinstall SP2 or replace the 2 DLL.s listed below with the DLLs attached to this article on both the Core and the Remote Console computers:

Core Path - C:\Program Files\LANDesk\ManagementSuite\landesk\managementsuite\core\core.secure\bin

and

Remote Console Path - C:\Program Files\LANDesk\ManagementSuite\

DLLs:

landesk.managementsuite.data.dll

landesk.managementsuite.database.dll

Additional Information:

Here is the Log for this error:

Excerpt from Console.exe.log

07/01/2015 15:29:27 INFO 1908:Main Thread RollingLog : SaveToDB: OnceAgainIntotheFRAY, (type Tasks and Policies)

07/01/2015 15:29:27 INFO 1908:Main Thread RollingLog : Routing request to save OnceAgainIntotheFRAY to core

07/01/2015 15:29:27 INFO 1908:Main Thread RollingLog : Not an ExportableContainer. Adding it to an empty container.

07/01/2015 15:29:27 INFO 1908:Main Thread RollingLog : ETask.BeforeExport for 'OnceAgainIntotheFRAY': NOT reloading info

07/01/2015 15:29:27 INFO 1908:Main Thread RollingLog : EPackage.BeforeExport for 'OnceAgainIntotheFRAY': NOT reloading info

07/01/2015 15:29:28 INFO 1908:Main Thread RollingLog : SaveBytesToDB: target core = CORESERVER.LOCAL, failIfCoresDontMatch = False, whatToSave level = DerivedClass

07/01/2015 15:29:28 INFO 1908:Main Thread RollingLog : Save via Web Service method selected.

07/01/2015 15:29:28 INFO 1908:Main Thread RollingLog : @@There was an error while trying to save via Web Service. See Core.secure.dll.log on core CORESERVER.LOCAL for details.

07/01/2015 15:49:54 INFO 1908:Main Thread RollingLog : SaveToDB: OnceAgainIntotheFRAY, (type Distribution package)

07/01/2015 15:49:54 INFO 1908:Main Thread RollingLog : SaveToDB: OnceAgainIntotheFRAY, (type Tasks and Policies)

07/01/2015 15:49:54 INFO 1908:Main Thread RollingLog : Routing request to save OnceAgainIntotheFRAY to core

07/01/2015 15:49:54 INFO 1908:Main Thread RollingLog : Not an ExportableContainer. Adding it to an empty container.

07/01/2015 15:49:54 INFO 1908:Main Thread RollingLog : ETask.BeforeExport for 'OnceAgainIntotheFRAY': NOT reloading info

07/01/2015 15:49:54 INFO 1908:Main Thread RollingLog : EPackage.BeforeExport for 'OnceAgainIntotheFRAY': NOT reloading info

07/01/2015 15:49:54 INFO 1908:Main Thread RollingLog : SaveBytesToDB: target core = CORESERVER.LOCAL, failIfCoresDontMatch = False, whatToSave level = DerivedClass

07/01/2015 15:49:54 INFO 1908:Main Thread RollingLog : Save via Web Service method selected.

07/01/2015 15:49:54 INFO 1908:Main Thread RollingLog : @@There was an error while trying to save via Web Service. See Core.secure.dll.log on core CORESERVER.LOCAL for details.

Excerpt from core.secure.log

07/01/2015 15:49:54 INFO 11840:80 RollingLog : ImportFromStream: stream does not represent a ExportableContainer

07/01/2015 15:49:54 INFO 11840:80 RollingLog : System.InvalidOperationException: There is an error in XML document (19, 8). ---> System.FormatException: The string '' is not a valid Boolean value.

at System.Xml.XmlConvert.ToBoolean(String s)

at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderExportableContainer.Read48_ETask(Boolean isNullable, Boolean checkType)

at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderExportableContainer.Read5_Exportable(Boolean isNullable, Boolean checkType)

at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderExportableContainer.Read32_ExportableContainer(Boolean isNullable, Boolean checkType)

at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderExportableContainer.Read259_ExportableContainer()

--- End of inner exception stack trace ---

at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)

at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle)

at LANDesk.ManagementSuite.Data.Exportable.ImportFromStreamOrTextReader(Object s, Type type)

at LANDesk.ManagementSuite.Data.Exportable.ImportFromByteArray(Byte[] input, Type type)

at core.secure.CoreRequest.SaveExportableContainer(Byte[] bytes, Boolean failIfCoresDontMatch, Int32 saveLevel)

Description: This article contains a script that can be run on any particular database. The script generates a temporary table with the returned information. That temporary table can then be deleted with the second script below. Just copy and paste these scripts into the SQL Query window.

1st Script (creates the temp table and displays the information)

SET NOCOUNT ON

/*DATABASE TABLE SPY SCRIPT

DESCRIPTION

Returns TABLE Size Information

SORTING USAGE

@Sort bit VALUES

0 = Alphabetically BY TABLE name

1 = Sorted BY total space used by TABLE

*/

DECLARE @cmdstr varchar(100)

DECLARE @Sort bit

SELECT @Sort = 1 /* Edit this value FOR sorting options */

/* DO NOT EDIT ANY CODE BELOW THIS LINE */

--Create Temporary Table

CREATE TABLE #TempTable

( [Table_Name] varchar(50),

Row_Count int,

Table_Size varchar(50),

Data_Space_Used varchar(50),

Index_Space_Used varchar(50),

Unused_Space varchar(50)

)

--Create Stored Procedure String

SELECT @cmdstr = 'sp_msforeachtable ''sp_spaceused "?"'''

--Populate Tempoary Table

INSERT INTO #TempTable EXEC(@cmdstr)

--Determine sorting method

IF @Sort = 0

     BEGIN

--Retrieve Table Data and Sort Alphabet

--     ically

     SELECT * FROM #TempTable ORDER BY Table_Name

END

ELSE

     BEGIN

/*Retrieve TABLE Data AND Sort BY the size OF the Table*/

     SELECT * FROM #TempTable ORDER BY Row_count DESC

END

2nd Script (deletes the temporary table)

--Delete Temporay Table

DROP TABLE #TempTable

Environment:

LANDesk Management Suite 9.5, LANDesk Management Suite 9.5 SP1

Description:

After running a LANDesk  Service pack or patch setup in LANDesk Management suite 9.5, you get the following error :

If you click on the setup log, you can see the following error :

ERROR: There was an error with the BackGroundWorker     (BackgroundWorker.OnRunWorkerCompleted())

Solution:

The setup files that were extracted are corrupted or the setup self extract executable is corrupted.

Solution:

• Delete or rename the folder were the setup extracted the files. For the 9.5 SP1, the files are extracted to \\<CORENAME>\c$\ProgramData\LANDesk\ManagementSuite\Install\9.50\Data\9.50.2
• Download the setup again from the LANDesk website directly on the server and run. Do not extract the files using a 3rd party tools.