Permissions Denied issue when deploying components on a Cluster with a NFS GDS even though app.server starting user has been given read and write permissions to GDS.

When deploying LC components through LCM on JBoss Cluster running on RH Linux with a NFS GDS permissions denied error is thrown and deployment fails. This is seen even though the user starting the app.server has been granted read and write permissions to the GDS.
The following error is seen in LCM logs -
[2009-09-02 12:27:58,159], SEVERE, Thread-7, com.adobe.livecycle.lcm.feature.deployment.DeployDSCsTask, Task failed com.adobe.livecycle.lcm.core.LCMException[ALC-LCM-030-200]: Failed to deploy component
….
…
Caused by: com.adobe.idp.DocumentError: java.io.IOException: Server returned HTTP response code: 500 for URL: http://10.8.224.110:9080/DocumentManager
In Server log the following error is seen -
com.adobe.idp.DocumentError: java.io.IOException: Permission denied
Cause – the issue happens if the netapp level permissions for this share are set to “NTFS” or “UNIX”.
Resolution – The permissions at the netapp level for the GDS share should be set to “mixed” instead of “NTFS” or “UNIX”.

View the original article here

Contribute CS5 Launch Issue ... Updated

Contribute CS5 Launch Issue … Updated « All things contribute… The Adobe Contribute Blog function clearSearch() {document.search_form.s.value = "";} adobe.com      All things contribute… The Adobe Contribute Blog / Contribute CS5 Launch Issue … Updatedby Shilpa Reddy  

View the original article here

Fix for issue with April public update for Outlook 2007

Some users experience error messages when you use print preview in Outlook 2007 after you install the Public update April. Work print still correctly despite the error message. We have an update as a Microsoft hotfix that addresses print preview error message appears, and is referred to as a KB article KB2512788. If you encounter this problem, download and install the hotfix here. This update will be distributed also part of a future public update from Microsoft Update.

Thank you for your patience and feedback. We improve our processes to prevent and respond to similar problems.

The Outlook team

View the original article here