Le Café Central de

                    ... Deva blogs!!

  • Le Café Central de DeVa

    Download : Update Rollup 3 for Exchange Server 2007


    You can download the Update Rollup 3 (thanks, Greg for helping here) for Exchange Server 2007 SP2 (x86/x64). It resolves issues that were found in Exchange Server 2007 since the software was released. This update rollup is highly recommended for all Exchange Server 2007 customers.

    Per MSExchangeteam.com, some highlights of the product improvements and critical bug fixes were “…

    Also per TechNet, the Update Rollup 3 for Exchange Server 2007 fixes the following issues:




    An integer is added to the end of the legacyExchangeDN attribute of a newly created mailbox in Exchange 2007




    The attachment is not displayed when you use Outlook 2003 to open an e-mail message that contains an attachment




    Error message when the sender or the receiver of a meeting request has a double-byte character set (DBCS) display name in Exchange Server 2007: "The requested property was not found"




    Error message when a user tries to open a forwarded message to accept or to deny a resource request in Exchange Server 2007: "Cannot open the free/busy information"




    You receive a 5.2.0 non-delivery report (NDR) message when you send an e-mail message to an Exchange 2007 server that is running the Isinteg.exe tool in a dismounted mailbox store




    DBCS characters are converted into two question marks in a forwarded e-mail message in Exchange 2007




    Error message when you run the Test-ExchangeSearch cmdlet across domains in an Exchange 2007 environment: "The operation could not be performed because of a service"




    A POP3 mail client may receive an error code, and event ID 1009 is logged on an Exchange 2007 mail server




    The synchronization session of the mobile device fails, and you receive error code "0X85010015" when you try to synchronize a mobile device by using Exchange ActiveSync in Exchange Server 2007




    The outgoing message always displays the name of the sender even though the administrator configured the message to hide the name in Exchange Server 2007




    Certain IMAP clients cannot open the bodies of e-mail messages when users access their mailboxes on an Exchange Server 2007 server




    A user cannot log on when the user accesses the mailbox of an Exchange 2003 IMAP4 back-end server through an Exchange 2007 server that is serving in a CAS role




    The nickname of a mail user must be unique in a forest if you use the original release version of Exchange 2007




    You cannot move a mailbox across forests in an Exchange 2007 organization




    The Availability service may use a large amount of memory and the corresponding w3wp.exe process has a high memory usage in Exchange Server 2007


  • Le Café Central de DeVa

    Office Development : Open XML SDK 2.0 for Microsoft Office available for download


    After almost two years and involved the release of four Technical Previews, Zeyad announced the worldwide availability of the Open XML SDK 2.0 for Microsoft Office. The Open XML SDK plays an integral part in creating Office document solutions that work on the client or server. The Open XML SDK allows you to create, consume, and manipulate Open XML files without needing to automate Office client applications.

    Download the Open XML SDK 2.0 for Microsoft Office:
    This download provides strongly typed part and content classes for use with Office 2007 & Office 2010 Open XML documents. http://www.microsoft.com/downloads/details.aspx?FamilyID=c6e744e5-36e9-45f5-8d8c-331df206e0d0

    Please note:

    • Open XML SDK 2.0 is freely redistributable by any solution provider implementing the formats
    • Office applications are not required to use the Open XML SDK 2.0, and no software purchase is required.
    • Developers can freely use the Open XML SDK to build document processing solutions for Microsoft Office files and for other implementations of the IS29500 standard

    If you want learn more about Open XML SDK, then i would recommend to try with Brian Jones related articles (a lot of real world scenarios/solutions that are built with the SDK). Apart from this, here is a summary of links that will help you learn more about the Open XML SDK:

  • Le Café Central de DeVa

    System.Net.Mail: Mail sent via Network delivery throws exception “Command not implemented/supported”


    One of the customer reported that whenever he tries to send e-mail by using System.Net.Mail API they get the following error “System.Net.Mail.SmtpException error message: Command not implemented. The server response was: Command not Supported

    I had a look at the application. They built a Microsoft Visual Studio 2005 based application and tried to send e-mail by using the System.Net.Mail.SmtpClient class. They use the DeliveryMethod.Network method from the Microsoft .NET Framework 2.0. The application receive the following System.Net.Mail.SmtpException error message: Command not implemented. The server response was: Command not Supported.

    During the investigation, we found that this problem occurs because the remote SMTP server does not support the SMTP extended Hello (EHLO) command. The exception occurs when the remote SMTP server returns the 502 reply code and the System.Net.Mail.SmtpClient class expects the 500 reply code.

    To overcome this issue, Microsoft released a hot fix downloaded from http://code.msdn.microsoft.com/KB913616/Release/ProjectReleases.aspx?ReleaseId=789. Also you can refer the detailed Knowledge base article regarding this issue and hot fix.

  • Le Café Central de DeVa

    Coding practices : Outlook automation using VB.Net


    You can try when you do programming with VB.Net and Outlook automation:

    • When you start automation code by declaring object variables with a specific object type that represents the top-level object and then declaring any child objects you want to reference.
      Dim olApp  As Outlook.Application

    • You then create an instance of the top-level object by using the Set statement and the New keyword.
    • Set olApp = New Outlook.Application

    Please note: You need to understand that the New keyword can't be used to create a new instance of a child object.

    • To create an instance of a child object, use the appropriate method of the parent object along with the Set statement.
    • Set MailMessage = olApp.CreateItem(olMailItem)

    • At the end of the procedure, each object variable is destroyed by explicitly setting it equal to the Nothing keyword. If you do this, there is no need to use a Set statement to instantiate the object. However, this technique is not recommended because you have no control over when the object variable is created.
    • In detail, if your code must test to see if an object exists by using a statement such as If olApp Is Nothing Then, this test will return True if you have created an instance of the object in the Dim statement. Additionally, you might not need to use an object except at the user's request.
    • If you create an instance of the object by using New in the Dim statement, the object will be created even if it isn't used. To maintain control over when an object is created, don't use the New keyword in the Dim statement, and instantiate the object by using a Set statement at the point in your code where you must use the object.
Page 1 of 1 (4 items)