The information in this article applies to:
SYMPTOMSWhen you use Windows Messaging in Microsoft Windows 95 OEM Service Release 2 to create a new fax that is scheduled to be sent at a certain time instead of being sent immediately, and you include one or more files with the fax, the fax may never be sent. CAUSEThis problem occurs when the fax's properties are modified while the fax is still in the outbound queue. After the Messaging Application Programming Interface (MAPI) dynamic-link library (DLL) is notified that the properties have been modified, the DLL may indicate that the properties were modified at the same time as the original fax was submitted. As a result, the fax is never sent. RESOLUTIONWindows 95 OEM Service Release 2A supported fix that corrects this problem is now available from Microsoft, but has not been fully regression tested and should be applied only to systems experiencing this specific problem.To resolve this problem, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web: http://support.microsoft.com/support/supportnet/default.aspThe English version of this fix should have the following file attributes or later:
NOTE: If you contact Microsoft to obtain this fix, a fee may be charged.
This fee is refundable if it is determined that you only require the fix
you requested. However, this fee is non-refundable if you request
additional technical support, if your no-charge technical support period
has expired, or if you are not eligible for standard no-charge technical
support.For more information about eligibility for no-charge technical support, see the following article in the Microsoft Knowledge Base: Q154871 Determining If Your Product Is Eligible for No-Charge Technical Support Exchange Server 4.0A supported fix that corrects this problem is now available from Microsoft, but has not been fully regression tested and should be applied only to systems experiencing this specific problem.To resolve this problem, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web: http://support.microsoft.com/support/supportnet/default.aspThe English version of this fix should have the following file attributes or later:
NOTE: If you contact Microsoft to obtain this fix, a fee may be charged.
This fee is refundable if it is determined that you only require the fix
you requested. However, this fee is non-refundable if you request
additional technical support, if your no-charge technical support period
has expired, or if you are not eligible for standard no-charge technical
support.For more information about eligibility for no-charge technical support, see the following article in the Microsoft Knowledge Base: Q154871 Determining If Your Product Is Eligible for No-Charge Technical Support Exchange Server 5.0A supported fix that corrects this problem is now available from Microsoft, but has not been fully regression tested and should be applied only to systems experiencing this specific problem. If you are not severely affected by this specific problem, Microsoft recommends that you wait for the next Microsoft Exchange Server version 5.0 service pack that contains this fix.To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web: http://support.microsoft.com/support/supportnet/default.aspThe English version of this fix should have the following file attributes or later:
NOTE: If you contact Microsoft to obtain this fix, a fee may be charged.
This fee is refundable if it is determined that you only require the fix
you requested. However, this fee is non-refundable if you request
additional technical support, if your no-charge technical support period
has expired, or if you are not eligible for standard no-charge technical
support.For more information about eligibility for no-charge technical support, see the following article in the Microsoft Knowledge Base: Q154871 Determining If Your Product Is Eligible for No-Charge Technical Support Exchange Server 5.5To resolve this problem, obtain the latest service pack for Exchange Server version 5.5. For more information, please see the following article in the Microsoft Knowledge Base:Q191014 XGEN: How to Obtain the Latest Exchange Server 5.5 Service PackThe English version of this feature should have the following file attributes or later:
STATUSMicrosoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. Additional query words: delayed
Keywords : exc55sp2fix |
Last Reviewed: November 10, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |