LANDESK Security and Patch News
· (June 12, 2015) Microsoft has released KB3054830 which is a Project 2013 update. This update provides the following improvements and fixes:
Fixes the following issues:
•When Project Professional 2013 opens a Project Server-based project from the local cache, Project Professional 2013 crashes.
•You cannot assign a resource in Project Professional 2013 if the resource name contains a semicolon and if the semicolon is set as the list separator on the client computer.
•When you print a project that contains tasks, resources or assignments that have multiline notes, Project 2013 crashes. This issue occurs if the Print notes option in the Page Setup dialog box is selected.
•When tasks have resource assignments, and the assignments on the task do not share the same start date as the task, resource leveling does not level resources as expected.
•After you set the Week starts on field to a value other than Sunday, calendar nonworking time exceptions are highlighted incorrectly in usage type views.
•When you import resource data from an Excel, TXT, or CSV format file in Project 2013, the resource is not imported successfully. Instead, you see an error that resembles the following:
The file "." cannot be opened.
* Check that the file name and path are correct.
* Check that the file format is recognized by Project.
Additionally, when you edit a data map, you may see a message that resembles the following if you try to add a field on the Map Options page of the Import Wizard:
The field "" does not exist.
In the part of this message that states "characters listed here," garbage characters are displayed instead of a field name.
•When you save a project in Project Professional or Project Web App, custom field values are lost.
Note This issue occurs after you apply the March 10, 2015 update for Project Server 2013 (KB2956178)
•When you open a project in Project Professional, you find that local custom fields are copied from the enterprise global template into your project. The enterprise global should not have local custom fields in it, and these fields should not be copied to individual projects. This fix prevents these fields from being incorrectly copied into your project and overwriting local custom fields that you may have already defined.
Please visit the following page for more details: http://support2.microsoft.com/kb/3054830
· Vulnerability ID – 3054830_INTL
· Vulnerability ID – N/A
New Patch Downloads
Where to Send Feedback
At LANDESK, we are constantly striving to improve our products and services and hope you find these changes reflective of our ongoing commitment to listen to you—our partners and customers—in providing the best possible solutions to meet your needs now and in the future. Please continue to provide feedback by contacting our local support organization.
LANDESK Product Support
Copyright © 2015 LANDESK Software. All rights reserved. LANDESK is either a registered trademark or trademark of LANDESK Software, Ltd. or its affiliated entities in the United States and/or other countries. Other names or brands may be claimed as the property of others.
Information in this document is provided for information purposes only. The information presented here is subject to change without notice. This information is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including any implied warranties and conditions of merchantability or fitness for a particular purpose. LANDESK disclaims any liability with respect to this document and LANDESK has no responsibility or liability for any third party products of any content contained on any site referenced herein. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission. For the most current product information, please visit http://www.LANDESK.com.