When i try to open one special Incident i get the following Error "There is an error in XML document (28,403)"
I edit the title and details in the database to remove the invalid character, but the error is still there.
I try the following DOC´s
http://community.landesk.com/support/docs/DOC-3767
http://community.landesk.com/support/docs/DOC-23300
nothing helps.
Kind regards
René Hoffmann
Is it possible to import SQL queries inside LDMS console (Query)?
If yes please guide me how to do that.
Apply: LD9.5, Core and DB server are separated.
When logon the console, the error dialog popup: Authentication failed. Verify the credentials are corrrect and that th account is not locked or disabled.
On console.exe.log:
06/14/2013 15:47:56 INFO 17308:1 RollingLog : FormMain: Enter constructor
06/14/2013 15:47:57 INFO 17308:1 RollingLog : Current language: ENU
06/14/2013 15:47:57 INFO 17308:1 RollingLog : Using culture info: en-US
06/14/2013 15:47:57 INFO 17308:1 RollingLog : FormMain: InitializeComponent
06/14/2013 15:47:57 INFO 17308:Main Thread RollingLog : FormMain: Leave constructor
06/14/2013 15:47:57 INFO 17308:Main Thread RollingLog : There is an error in XML document (2, 3).
06/14/2013 15:48:00 INFO 17308:Main Thread RollingLog : Starting authentication
06/14/2013 15:48:00 INFO 17308:Main Thread RollingLog : Resolving rights for [user name is here]
06/14/2013 15:48:00 INFO 17308:Main Thread RollingLog : AuthenticationException Exception: Failed to authenticate
The core server OS, date and time is out of sync with DB server. Then it cannot connect to connect.
Change the date and time of the core server OS or DB server, making them sync on date and time can resolved this problem.
Repeated this twice.
User with limited scope, makes changes using Preferences - Custom Columns, sets the view as default and imediately clicks on my devices, it will show all devices once and allow targeting of the system.
Anyone else had this issue?
When installing the remote console you get a failure on the "Installing the Remote Console" step.
This can occasionally show up when upgrading a core server as well, but it will be on the "Upgrading the Core Server" step.
The resolution is the same.
In the log you will find something similar to the below
MSI (s) (0C:CC) [10:14:45:217]: Doing action: LDCopyApplyHotFixLocally
Action ended 10:14:45: LDWriteRemoteRegKey. Return value 1.
MSI (s) (0C:CC) [10:14:45:217]: Note: 1: 2235 2: 3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'LDCopyApplyHotFixLocally'
MSI (s) (0C:E4) [10:14:45:218]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI8247.tmp, Entrypoint: LDCopyHotFixLocally
Action start 10:14:45: LDCopyApplyHotFixLocally.
HOTFIX: Failed to copy HotFix helper file D:\LANDeskSoftware950\landesk\\SetupFiles\ApplyHotFix.exe to C:\Users\<User>\AppData\Local\Temp\ApplyHotFix.exe
CustomAction LDCopyApplyHotFixLocally returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Cause: This is caused when the install finds a Hotfix directory and trying to copy the ApplyHotFix.exe
Normally it will be found in either the user temp directory or on the root of c:\
You can do a search for hotfix and find where we may be seeing the folder.
Note:
You may need to do the search from command line as the windows search is not always reliable.
From a command prompt cd to the root of c:\
Run the command c:\> dir /s hotfix
Solution: Once you find the Hotfix directory, you can temporarily rename the folder, or delete it if it is no longer needed and run the install again.
This time the install should complete and you can name the folder back if needed.
Hey Guys,
Our LANDesk implementation has been going well. We now want to share the tools to our Admin team to help them manage their servers. As with everything, we do not want to give them full reign in the system. We have utilized the Role Based Access control, which is awesome. The side effect is that this impacted the "Right Click" options on a device.
For example, one admin lost the ability to right click and perform either a "Ping" or "Trace Route". Another admin lost the ablity to "Archive to Asset Control". I am randomly turning on and off rights to see what appears in teh right click menu. Is there any document that list what needs to be enabled for various Right click Menu options. For now, I need know which are associted to "Ping" and "TraceRT", and "Archive to Asset Control". Any advice or guidance would be greatly appreciated.
- Ton
Running LDMS 9.0 SP2 on Win2k3. The console is on Win7x64.
I have recently reinstalled the console and I'm getting this error when I try to login to a remote console. I have tried installing it from the 9.0 install file with SP2 slipstreamed into it. And I have applied the rollup patches that the core has as well.
Any ideas on what is causing this error?
Hello
I am trying to access smartvue by going to the "core/smartvueweb/ " site but am having no luck as it displays a 404 error... Are there additional steps to take past installing the app?
After updating to 9.5 (w/o SP1) I am noticing a mismatch between the agent status shown in the Core Server console and my remote console.
I generally work from my remote console and I've been seeing that machines show the red circle w/line through it even though the machine is turned on. If I switch over to the core the agent status shows the machine is turned on.
In the most recent case, yesterday, the computer which was not displaying a correct status was on the same subnet as my machine w/remote console. I could ping the other machine from mine.
Does anyone know the cause of this and/or a fix? I suspect this is also part of the slow agent status refresh that I've been seeing in 9.5. I believe there was a patch for the slow repsonse but I don't know if it also resolved the incorrect status issue-that patch was recalled and I couldn't get it a few weeks ago.
Any thoughts?
I'm trying to get the v9.5 remote console to be included as part of a new template. I've tried using a batch file, and also running the setup.exe from the install folder with the /s and CORE=myserver, switches. I also tried copying the install folder to the software/distribution package share, but I always wind up with a failed template.
However, I am able to open the console on the target machine, and the core is already selected. So I don't know why it comes back as failed, which stops the template in it's place, when it actually is getting installed as I want. I also need to get two patches applied as well.
Does the install require a reboot in order to report it is completed? And if so, can I kick off the patch install(s) after that reboot?
Or should I try to tell LANDesk to not stop the template and just keep going, complete the patches, and then do a reboot?
Description:
After applying the SP1 for LANDesk Management suite, the menu "HII Driver Management" is missing :
This menu should be located under Distribution packages :
Cause:
The XXXtools.xml (XXX is your installed language prefix) file in C:\Program Files (x86)\LANDesk\ManagementSuite doesn't contains the correct information.
Solution
Replace the xml in C:\Program Files (x86)\LANDesk\ManagementSuite by the one attached to this article. You only need to select the one for your installed language :
English : enutools.xml
French : fratools.xml
German: deutools.xml
Environment:
Landesk Management suite 9.5 SP1
So what is with the 9.5 execution options for scheduled tasks. It used to be that you started a task via start now. Failed machiens could be retried either individually or by selecting a group of them and chosing the retry option.
In 9.5 you now have 4 options when selecting START NOW.
1) ALL
2) Devices that did not succeed
3) Devices that did not try to run the task
4) Waiting or currently working
It used to be that once we kicked off a task we were not to touch it until all participants completed or failed out of the task. Doing so could mean that any successfully participating machines would reset on the task and fail out. We took the options in 9.5 to mean that we could remeidate any failed machines without affecting any which were already working. In recent testing I am not seeing this to be true and I'm wondering what the options are for exactly. Are the options a simple rehash of what was already there before or is there supposed to be some expanded capability with them?
Example situation:
I've got a group of machines selected for a provisioning task. I kcik the task off and all but one of the machines begin the task and get on their way. I work on remediating the problem with the one failed machine. When I think that machine is ready to try again I select option 2 from above on the scheduled task-keep in mind all of the other machines in the task are moving right along w/o problem. Upon selecting the option 2 I see the other machines fail out of the task almost immediately. The one that had originally failed before has also failed.
Curriously enough, if I watch the other machines, they continue to follow the provisioning task even though the console shows they have failed. Then for whatever reason they give up before provisioning is complete.
Is it me or is this half baked? Is there some description of what these 4 options really mean? the online help here:
http://help.landesk.com/Product/Index/ENU/LDMS/9.5/
doesn't seem to reference these options.
I am simply trying to figure out how we are supposed to use them.
-thanks
Hi,
Assigned rol and rights to a user to only see Scripts, Distribution and Scheduled Tasks from a Web console. Although the web console user is not an administrator he is able to see all the scripts and packages in the core server even though these scripts are set as private for a different user. All scripts and packages are shown as "PUBLIC" in LDMS 9.5 web console even though these packages are set as private in the native console.
Anybody found same problem?
What happened to ability to right-click on Inventory, Add or Remove Programs, Programs, and choose export to csv? We seemed to have lost this functionality after installing sp1. Was this change intentional, and if so, is functionality replaced by something else?
We just did a fresh install of Landesk 9.5 with upgraded 9.0 database. This is installed on a Windows Server 2008 R2 machine with IIS 7. When going to http://landesk_Machine/Remote, the login box appears. After entering my login information, the page just displays Redirect frameset.aspx. Nothing loads. This happens in IE 9. If I use Firefox or Chrome, it asks me if I want to download a file.
Is there something that I need to configure to get this to work? Did I not set something up?
***Update***
If I manually type in http://landesk-machine/remote/frameset.aspx, the Web Console will load.
If I don't add the frameset.aspx, it just displays a page stating "redirect to frameset.aspx".
Any Ideas?
LDDrive.exe is part of “Real-time Inventory and Monitoring”
1. You could replace the ‘LDDrives.exe’ on the affected client, but copying over the file from one not reporting the issue. LDClient directory
2. Since we depend on the Visual Studio file ‘msvcr90.dll’ reinstalling Visual C++ via the vcredist_x86.exe or vcredist_x64.exe from the LDClient folder. (this is the 2008 version)
3. Another option is to turn off the “Real-time” monitoring and redistribute the agent
4. Re-install the agent on this machine. It could be that during the initial install something corrupted the file.
5. Rename LDDrives.exe
Where are the instructions or best known methods doc for installing the Web and/or stand alone console for LDMS 9.5
Why is this information NOT included in the LDMS 9.5 user guide
Description:
If you suspect an IIS configuration issue between two core servers, on way to quickly identify differences is to export the IIS configuration to a set of files and compare those files using a file comparison tools.
Solution
A. export/backup IIS configuration for IIS 7.5
To export configuration to files on IIS 7.5, you need to use the appcmd.exe tools that is located in the C:\Windows\System32\inetsrv folder.
To create a backup, run the following command:
appcmd.exe add backup <BACKUPNAME>
<BACKUPNAME> is the name you want to give to your backup folder.
The files will be stored in the folder C:\Windows\System32\inetsrv\backup\<BACKUPNAME>\
B.compare configuration files
a way to compare files is to use an editor like notepad++ ( http://notepad-plus-plus.org/) with the file comparison plugin (http://sourceforge.net/projects/npp-compare/)
Environment:
Any Core server installed on Windows 2008 R2 (IIS 7.5)
Description:
If you try to activate the core server, this error appears:
The authorization file is invalid.
The activation file at this location appears to be invalid. 'C:\...\authorization file.txt' Make sure an inventory scan has been run for this core server and run this utility again. Contact customer support for further assistance.
Cause:
There is some issue with the amp activation mode. This only apply to Landesk 9.0 and 9.0 SP1
The login screen of the contact should contain the Avocent logo:
Solution
Switch the activation mode from amp to ldms by running the following command on your Core server and any Windows console:
"C:\Program Files (x86)\LANDesk\ManagementSuite\LicensingServiceProvider.exe /provider=ldms"
Environment:
Apply only to LANDesk Management Suite 9.0 and 9.0 SP1
Environment
LANDesk Management Suite 9.50.0.530, Windows Server 2008R2 SP1 Standard Edition
Problem/Issue/Symptoms
LDMS Console fails to initialize after renaming the core server machine, reporting the following pop-up window error:
The error reported in the console log is the following:
Exception Details: </b>System.ArgumentNullException: Error calling ParseLocalConnectionString<br>Parameter name: local_connection_string<br><br>
In this scenario, opening the "LANDesk configure services" from Start > All Programs > LANDesk > LANDesk Configure Services fails to start, reporting a pop up window error.
Where W2008R2SP1ENG is the previous machine name, and W2008R2SP1NEW is the new one.
Cause
This problem occur after changing the hostname of the core server.
It is strongly recommended not to change the hostname of the core, especially in a production environment.
Solution
Locate the previous machine name lingering in the LANDesk registry keys
- Open the registry editor
- Find the previous machine version
- Replace it with the current one
The following keys are the three basic to change to have the console running again, but more are stored in the registry, that's why it's not recommended to change the hostname of the core server.
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\LANDesk\ManagementSuite]
"CoreServer"="previous machine name"
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Intel\LANDesk\LDWM\DBUtil]
"Inventory Server Name"="previous machine name"
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\LANDesk\ManagementSuite\Setup]
"CoreServer"="W2008R2SP1ENG"